Verify with Chiliz Block Explorer
Chiliz Block Explorer is a service built by Blockscout. You can therefore rely on their documentation for your everyday use.
Blockscout provides several ways to verify your smart contract on Chiliz Chain:
For most contracts: using their verification feature.
For more complex contracts: using command-line tools, such as Hardhat.
For easy contracts: using their API.
See Blockscout's documentation on contract verification.
Using the Chiliz Block Explorer verification feature
Chiliz Block Explorer provides a contract verification feature for each deployed contract. It is also documented here: https://docs.blockscout.com/devs/verification/blockscout-ui
Steps:
Once the contract is deployed, you can view the transaction in detail on the Chiliz Block Explorer.
Select the Code tab to start verifying your contract.
Copy and save the Copy Contract Creation Code for future reference.
Select Verify & Publish.
Choose the relevant verification method, then click "Next".
Enter the required details in the relevant fields. Copy the smart contract code used to compile the smart contract. Paste it in the Enter the Solidity Contract Code field.
The following table explains this New Smart Contract Verification form in detail.
Contract Address
The address provided after contract creation
Contract Name
Name of the contract given whilst creating the contract
Include nightly builds
Select Yes to add nightly build values to your report. It also depends on your compiler.
Compiler
Compiler version used while deploying the contract. For Chiliz Chain, use Solididy 0.8.24+xxxxx.
EVM version
Use the dropdown and select the same EVM version used to deploy the contract. Choose "shangai", or "default" if not available.
Optimisation
Select Yes, if you have enabled Optimisation while compiling the contract
Enter the Solidity Contract Code
Enter the ERC-20 script used to compile the smart contract
Try to fetch constructor arguments automatically
Choice to fetch constructor arguments
ABI-encoded Constructor Arguments (if required by the contract)
Choice to fetch constructor arguments, only if the contract requires
Add Contract Libraries
Enter the name and 0x address for any required libraries called in the called in the .sol file
Your contract is now verified ✅
Using command-line tools
Blockscout own documentation features detailed guides on how to use command-line tools for verification. This is particularly useful if you're already want to automate contract verification in your development environment.
You can read their guides on deploying & verifying with:
... and more!
Using Blockscout's API
Blockscount has a dedicated contract verification API:
Last updated
Was this helpful?