The State of Source Code Verification Closed, Painful, and Ready for Change
summary
Claims that verification is a closed, unreproducible black box lead to concrete fixes: an open‑source, browser‑friendly verification library, a unified Remix plugin and autoscan local explorer, and a shared Verifier Alliance Postgres that publishes daily in parquet format. The public dataset mirrors to BigQuery and already holds 10 million+ contracts from about 180 chains, supports IPFS pinning, and enables parallel verification and bulk analysis; Etherscan API rate limits (250 posts/day) remain a practical constraint.
AI-written summary · about
chapters (17)
- 0:00Source code verification issues
- 2:08Closed verifiers and data problems
- 5:42Sourcify’s mission
- 6:25Sourcify’s structure
- 7:10Verify Alliance solution
- 8:14Open source verification
- 9:21OpenChain XYZ enrichment
- 10:01Self-hosted Sourcify instances
- 10:44Multi-platform verification
- 12:09Remix IDE plugin
- 12:30Parallel verification
- 12:51Verified data sets
- 13:34BigQuery access
- 14:18AI playground
- 15:22EVM tooling innovation
- 16:31Call to action
- 17:14Q&A
related talks
27mHuman-friendly Contract Interactions with Sourcify Verification
16mHuman Friendly Contract Interactions w/ Sourcify
23mThanks for all the bugs!
13mDon’t Trust, Verify. Reproducible Builds in Bitcoin
15mOn the Impact of Formal Verification on Software Development
22mInteractive Source-to-Source Optimizations Validated using Static Resource Analysis
23mFireside Chat
44mWhat your auditor REALLY thinks but is afraid to tell you...