Contract Verification Calculator
Estimate source code and formal verification costs
Contract Details
Source Code Verification
Formal Verification (Optional)
Additional Services
Total Verification Cost
Source Verification Details
Formal Verification Details
Time Breakdown
Verification Methods Comparison
| Method | Cost | Time/Contract | Multi-Chain | Best For |
|---|---|---|---|---|
| Manual (Etherscan UI) | Free | 10-30 min | Tedious | Single contract, one chain |
| Hardhat Plugin | Free | 2-5 min | Config per chain | Hardhat projects |
| Foundry (forge verify) | Free | 1-3 min | Config per chain | Foundry projects |
| Sourcify | Free | 5-10 min | Automatic | Multi-chain deploys |
| Tenderly | Freemium | 2-5 min | Good | Debugging + verification |
Formal Verification Providers
Certora
- • Industry leader
- • CVL specification language
- • $30K-$150K typical
- • 4-12 weeks
Runtime Verification
- • K Framework
- • Academic rigor
- • $25K-$100K typical
- • 3-8 weeks
In-House / Tools
- • Slither, Mythril, Echidna
- • Lower cost, less rigorous
- • $5K-$20K (dev time)
- • Ongoing
When to Use This Calculator
Multi-Chain Launch
Deploying on 10 chains? Calculate total verification time and budget for your DevOps team.
Formal Verification Budget
Considering Certora for your DeFi protocol? Get a ballpark estimate before reaching out.
Sprint Planning
How many dev hours for verification? Plan your sprint with accurate time estimates.
Client Proposals
Building for clients? Include verification costs in your project quotes.
Tool Comparison
Manual vs Hardhat vs Foundry? Compare time savings across verification methods.
Complex Systems
20 contracts with proxies and libraries? Calculate the full verification scope.
Frequently Asked Questions
Why verify contracts?
Trust. Unverified contracts are black boxes. Users can't see what they're interacting with. Verified = transparent = trustworthy. It's expected for any serious project.
Do I need formal verification?
Depends on TVL. Holding $100M+? Strongly consider it. Under $1M? Probably overkill. Formal verification catches bugs audits miss, but costs 10-50x more.
Verification keeps failing?
Check: exact compiler version, optimizer runs, EVM version, constructor args (ABI encoded). Use the same settings as deployment. Foundry's --show-standard-json-input helps debug.
What about proxy contracts?
Verify both proxy and implementation. Link them on Etherscan using "Is this a proxy?" feature. Users need to see the actual logic, not just the proxy shell.
Can I verify after deployment?
Yes, anytime. But do it immediately - you need exact source code and compiler settings. Lose those, and verification becomes painful or impossible.
Sourcify vs Etherscan?
Sourcify is decentralized and multi-chain. Etherscan is the standard users check. Do both if possible. Sourcify verification often auto-populates to other explorers.
No comments yet. Be the first to share your thoughts!