second-state/smart-contract-search-engine

Add bytecode to configuration

tpmccallum opened this issue · 2 comments

tpmccallum commented

The search engine will fetch the bytecode from the original transaction and compare this with the bytecode in the config. If the two bytecodes match then the search engine will provide a URL to the official bytecode.
The same is done for the ABI.

tpmccallum commented

This has now been implemented.
The search engine also provides a clickable link to the transaction hash, block number, owner's EOA address and the contract's address.
This is very hand for end users who need to confirm the integrity of an item which they can see in the search results.
Reasons for implementing:

  • Anyone can deploy a smart contract with the same ABI but with slight different source code (i.e. same ERC20 token acronym, exact same ABI functions available but a different totalSupply etc.)
  • Anyone can deploy a smart contract (at a new contract address) which not only looks like the original one but is actually exactly the same as the original (i.e. same source code and ABI deployed again at a different address). This can even be the case for ERC20 tokens which have the same token acronym, but a completely different instance of the contract at a new address.