If you're new to developing on Ethereum and unsure where to start, or if you want to learn how to deploy and interact with smart contracts, check out this step-by-step guide.
Source code verification provides transparency for users interacting with smart contracts. By uploading the source code, Etherscan will match the compiled code with that on the blockchain. Just like contracts, a "smart contract" should provide end users with more information on what they are "digitally signing" for and give users an opportunity to audit the code to independently verify that it actually does what it is supposed to do.
Please be informed that advanced settings (e.g. bytecodeHash: "none" or viaIR: "true") can be accessed via Solidity (Standard-Json-Input) verification method. More information can be found under Solidity's "Compiler Input and Output JSON Description" documentation section.
To update token information on Etherscan, the contract address code for the token must be verified. This is to ensure that the contract code is exactly what is being deployed onto the blockchain and also allows the public to audit and read the contract. Etherscan ensures that all token contract must be verified before they can be updated with information submitted by the contract owner.
If you are the contract owner and would like to verify your contract, kindly follow the steps below:
Under the contract address page, next to the “Token Transfers” tab, you will be able to find the “Contract” tab. Then click on “Verify And Publish.”
For Truffle deployed contracts, contract owner can use Etherscan’s Contract Source Code Verifier.
Please enter the required information, including the contract name, compiler version, and the complete contract code. Ensure that the contract code is in its deployed form, as a single file (flattened), with all imports removed.
You can also input the optimization options, constructor arguments, and any other libraries at the bottom of the same page.
Upon successful contract verification, you can
If you have deployed the same contract (with same address) on other chains, you can now verify your contract on multiple chains with a single API key from Etherscan, instead of creating a new API key on each explorer.
In case of verification error, you'll get details on where it failed with:
When the contract has been verified, the “Contract” page will be filled with the contract details. The source code of the contract is now publicly available on Etherscan.
