Ethproofs is not primarily another proving stack; it is a public-good comparison layer for Ethereum L1 proving progress.
The Learn page gives the clearest concise framing: Ethproofs is a block proof explorer for Ethereum that aggregates data from various zkVM teams and exposes metrics like cost, latency, and proving time.
The homepage adds a stronger research-program framing than a normal dashboard would. It stages the proving journey as early adopters → delayed proving → mandatory proofs → enshrined proofs, which makes the platform part of Ethereum’s long-run proving roadmap rather than a one-off benchmark contest.
The GitHub organization description is especially useful because it foregrounds tracking, benchmarking, and accelerating zk proving for Ethereum's L1 on the path to enshrined proofs and emphasizes neutral, research-grade interfaces, open schemas, in-browser verification, and verified-versus-reported provenance.
The zkVMs docs page shows that runtime/version curation is part of the control plane. Each integrated zkVM version gets a unique ID used in cluster API workflows, which means benchmark inclusion and naming are structured governance surfaces rather than incidental UI details.
The durable mechanism insight is that proving ecosystems are shaped not just by prover design, but by benchmark methodology: who defines eligibility, what hardware and proof metadata are surfaced, how provenance is distinguished, and which metrics become socially legible.
Specific source signals worth retaining
The official site is the best source for the live-race framing (race to mainnet-grade L1 zkEVMs) and for the phase/eligibility dashboard vocabulary.
The Learn page is the best source for the plain-language explanation of what Ethproofs is for, why zkVM proving matters, and the claimed benefits like single-proof state validation and groundwork for multi-proof systems.
The GitHub org overview is the best concise source for the public-good platform language plus the verified-vs-reported, open-schema, and research-grade interface claims.
The zkVM registry docs are the best source for the fact that Ethproofs curates a versioned universe of integrated runtimes and exposes those IDs to API users.
The repo README is not analytically rich, but it confirms the app/repo implementation surface and local development stack.
Why this entry belongs in the corpus
It adds a benchmark-governance and public-comparison layer above the existing zkVM / proving entries.
It helps separate proving-system architecture from proving-legibility infrastructure, which are often flattened together.
The durable insight is that public scoreboards, cohort policy, provenance labels, and open schemas can become as influential as prover code when an ecosystem is trying to converge on credible progress.