Comment on page
How to Verify a Smart Contract on HashScan
How to verify a smart contract using the HashScan Smart Contract Verification tool.
Verifying smart contracts helps ensure the deployed bytecode matches the expected source files. HashScan Smart Contract Verifier is a tool that simplifies this process. This guide will walk through the basic steps of smart contract verification using the HashScan Smart Contract Verifier tool.
Smart Contract Verification Flow
Open a web browser and navigate to HashScan. Make sure you are on the correct Hedera network (Mainnet, Testnet, or Previewnet), and search for the deployed contract address in the search bar at the top of the page. In the Contract Bytecode section click on Verify Contract. The source code file importer popup window will open.
Add your Solidity source code files in the source file importer popup. Source files include the smart contract (
.sol) source code file and metadata (
.json) file. The metadata file can be found in the
artifacts/directory of your smart contract project and its name correlates with the smart contract. For example, the metadata for the
HelloHedera.solcontract would be called
HashScan Verification Source File Importer Popup
📣 Different compiling tools require specific verification source files. Here's a brief outline of what is needed for popular tools:
- 3.Solidity Compiler (solc):
- Required for Full Match Verification: Both the metadata file (generated by
forge-build) and the smart contract's Solidity file.
Note: Uploading only the Solidity file without the metadata file will result in a Partial Match.
After importing the source files, if you get the "Contract <contract name> is ready to be verified" message, click VERIFY to initiate the verification process. Sourcify will then compare the deployed contract bytecode to the source files you imported in the previous step.
- Full Match: Indicates the bytecode is a full (perfect) match, including all the metadata. The contract source code and metadata settings are identical to the deployed version.
- Partial Match: Indicates the bytecode mostly (partially) matches with the deployed contract, except for the metadata hash like comments or variable names. It is usually sufficient for most verification purposes.
To view the verified contract repository, click View Contract Sources in the Contract Bytecode section on HashScan. This will open a verified contract repository search page window.
A summary of your contract's verification details will be displayed in the new window. Verification details include the contract address, source code files, match type, chain ID, metadata, and an option to open the repository in Remix.
Verified contract repository
To be directed to the Sourcify Contract Repository search page, click on
Sourcify Contract Repository search page
If you change your contract or want to upgrade your contract from a Partial Match to a Full Match, there are two options for re-verification:
Enter the smart contract address and chain, then click Verify.