Verifying your smart contract creates transperancy, thus increasing trust.
Steps to verify your deployed contracts:
Go to FTMScan Verify Contract
Input your contract address
Choose compiler type (single file is recommended)
Choose the compiler version (according to your contract)
Choose the open-source license
Click Continue
If you select a single file as compiler type, then you can use a library like sol-merger to flatten your contract. It creates a single file that contains all the imports.
Make sure there is only one line of '// SPDX-License-Identifier'. If there are multiple lines of this, remove them except the first one.
6. Choose yes for optimization (if you deployed your contract using Hardhat) .
7. Paste the source code.
8. If the contract has a constructor, then you need to create the ABI code for the values passed to the constructor. Use https://abi.hashex.org/. Copy the result and paste it to the Argument (Constructor) section.
9. Tick the box to indicate that you are not a robot.
10. Verify and publish.
Screenshots
Via Command Line and Script
You then need to store the API Key in a .env file which is read by your configuration file, such as:API_KEY={your API Key}
- Using the Hardhat command line: When verifying using the Hardhat command line, you need to specify the values in a JavaScript file. In the example above, it is assumed that the file is under the scripts folder. Please refer to https://hardhat.org/hardhat-runner/plugins/nomiclabs-hardhat-etherscan.
- Using the Truffle command line: however, you do not need to specify any value that you passed to the contract's constructor. Truffle records these when you deploy the contract.
If you use Hardhat, you can also use the verify:verify command in a script to verify your contract. You can include this script in your deployment script. Here is an example:https://github.com/Fantom-foundation/example-deployment/blob/main/Hardhat/scripts/sample-script.js
