Verifying Smart Contracts

tutorial
#1

Verifying a smart contract in BlockScout

Once verified, a smart contract or token contract’s source code becomes publicly available and verifiable. This creates transparency and trust. Plus, it’s easy to do!

  1. Go to blockscout.com, verify you are on the chain where the contract was deployed, and type the contract’s address into the search bar. Your contract details should come up.

  2. Select the Code tab to view the bytecode.

BlockScout_1
BlockScout_1.jpg1162×660 94.2 KB

  1. In the code tab view, click the Verify & Publish button.

Blockscout_2
Blockscout_2.jpg927×262 64.7 KB

  1. On the following screen, enter your contract details:

    1. Contract Address: The 0x address supplied on contract creation.
    2. Contract Name: Name of the class whose constructor was called in the .sol file. For example, in contract MyContract {.. MyContract is the contract name.
    3. Compiler: derived from the first line in the contract pragma solidity X.X.X. Use the corresponding compiler version rather than the nightly build.
    4. Optimization: If you enabled optimization during compilation, check yes.
    5. Enter the Solidity Contract Code: You may need to flatten your solidity code if it utilizes a library or inherits dependencies from another contract. We recommend the POA solidity flattener or the truffle flattener
    6. Click the Verify and Publish button.

  2. If all goes well, you will see a green checkmark next to the code, and an additional tab where you can read the contract. In addition, the contract name will appear in BlockScout with any transactions related to your contract.

Troubleshooting:

If you receive the dreaded There was an error compiling your contract message this means the bytecode doesn’t match the supplied sourcecode. Unfortunately, there are many reasons this may be the case. Here are a few things to try:

  1. Double check the compiler version is correct.

  2. Check that an extra space has not been added to the end of the contract. When pasting in, an extra space may be added. Delete this and attempt to recompile.

  3. Copy, paste and verify your source code in Remix. You may find some exceptions here.

Note: BlockScout does not currently support validation of contracts containing constructor arguments.