-
-
Save Anish-Agnihotri/8c16906310f406d0d79cab0e45594191 to your computer and use it in GitHub Desktop.
| getting too easy | |
| Times mainnet auction address for tomorrow: | |
| https://etherscan.io/token/0xdd69da9a83cedc730bc4d3c56e96d29acc05ecde |
@Anish-Agnihotri any ideas on how to create a bot fighter in the smart contract to block this type of behavior, and make sure the minting process is decent and front runners don’t have this "privileged access"?
coz this is so unfair and will harm the NFT industry as a whole, I will reach out to the alchemist team to elaborate more on this issue
Some smart contracts of recent NFT projects require a signature from the backend, in which the msg.sender and quantities are signed by their private key. On the contract side, they will validate the signature, if the signature is correct, the transaction will be processed.
However, the crawler can also request the signature, and commit the transaction, but more difficult than usual.
Black-hat perspective: how do you extract address from a frontend? Do you do this manually searching for "web3.eth.Contract" etc, debugger breakpoints; Or is there some smart automated way?
Black-hat perspective: how do you extract address from a frontend? Do you do this manually searching for "web3.eth.Contract" etc, debugger breakpoints; Or is there some smart automated way?
Damn, sorry, your second tweet literally answers this:
https://twitter.com/_anishagnihotri/status/1441072865764429825?s=20
How can I call method to mint if contract has different method name?