Verifying your smart contracts on RWALayer is a crucial step to ensure transparency and trust. RWALayer supports
verification through popular tools like Hardhat and Foundry. Below is a comprehensive guide to help you navigate
the verification process using these tools.
forge requires a value for the --etherscan-api-key option even if a valid API key is not necessary. You can use
a placeholder in such cases.
Configuring Verification Endpoints
It’s crucial to direct your verification requests to the appropriate API endpoint. For Hardhat, this is configured in
the apiUrl within your settings. For Foundry, you need to specify this via the --verifier-url in your forge command:
Contract verification using Foundry
To verify your contracts during deployment or for an existing deployment using Foundry, follow these steps:
Contract verification using Hardhat
For Hardhat users, successful contract verification involves proper configuration of your hardhat.config.ts or
hardhat.config.js file. This includes setting up the networks and etherscan properties.
Config
During Deployment
After Deployment