Contract Verification
Verify your contracts on fork
For contracts that have been verified, the simulated transactions can be debugged using the Debug Transaction feature of Phalcon Explorer.
Verifying a contract means making its source code available in that Fork, along with the compiler settings you used.
If you want to delete the source code, delete the associated Fork.
Contract verification is supported for Hardhat
, Foundry
and Truffle. Others should be supported.
Get Acess Key, Fork RPC ID and Fork ID
The first step is getting the API access key (FORK_API_ACCESSS_KEY
), the Fork RPC ID (FORK_RPC_ID
) and the FORK_ID
. Please refer to this link.
Hardhat
Verifying a contract in Fork is similar to verifying it on Etherscan. Read this manual on Hardhat on contract verification on Etherscan.
You need to change the configuration to verify a contract on Phalcon Fork.
Then using the following command to verify the deployed contract.
If you have not deployed your contract, using the following command to deploy your contract first.
Foundry
In Foundry, you can use the verify-contract
for verification. Please refer the document on Foundry.
the_contract_address: The contract address
the_contract_code_path: The path of the local contract code, e.g., src/MyToken.sol:MyToken.
The verification process is showing in the terminal.
Truffle
Please refer this document for how to verify the contract using Truffle.
Phalcon Fork provides the compatible APIs of Etherscan. One convenient way is to add the Phalcon Fork into verify
section of a network.
Note that the previous configuration is just an example. Since our API is Etherscan compatible, please refer to the development framework document for more information on contract verification.
Verified Contracts
Detailed information on the verified contracts is shown in the Contracts
of the Phalcon Fork Panel.
Click on the contract address to see detailed information on the contract.
Last updated