Must provide the profile name as the build_hint. This significantly reduces verification time by limiting how many times we have to compile the repo.
Must provide the creation transaction hash for each chain you want to verify on.
This means that for all deployments we currently expect to be able to verify both creation code AND deployment code. If either fails, this should be considered a bug.
Without this restriction, we have to binary search for the creation transaction, and trace the transaction if deployment was from an supported factory / internal call. This significantly increases RPC usage, and requires an archive node.
Must have deployed the contract via one of 3 approaches:
Standard create deployments where to == null in the transaction
The following chains are supported: Mainnet, Goerli, Sepolia, Optimism, Arbitrum, Polygon, Gnosis Chain
Requires one request to the cove /verify endpoint for
The verify_counters test is a live integration test that runs against Goerli and Sepolia and verifies all contracts that live in the deploys.txt file in the cove-test-repo
Summary of Current Status
User requirements:
build_hint. This significantly reduces verification time by limiting how many times we have to compile the repo.createdeployments whereto == nullin the transactioncreate2deployments from0x4e59b44847b379578588920cA78FbF26c0B4956Ccreate2deployments from0x0000000000FFe8B47B3e2130213B802212439497Additionally:
/verifyendpoint forverify_counterstest is a live integration test that runs against Goerli and Sepolia and verifies all contracts that live in thedeploys.txtfile in the cove-test-repo