Category: zk proving benchmark public good / Ethereum L1 proof explorer / enshrined-proofs research infrastructure
Summary: Ethproofs is worth cataloging not as just another zkVM team page or benchmark dashboard, but as neutral comparison infrastructure for the race to prove Ethereum L1 blocks in near real time. Its primary materials describe a public-good platform that aggregates proof runs from multiple zkVM teams, distinguishes verified from merely reported data, exposes proof metadata and downloadable artifacts, and frames the work as a stepping stone from early proving experiments toward enshrined proofs and eventually light-client-friendly Ethereum verification. That makes Ethproofs a useful comparison point for zkVM stacks, prover marketplaces, benchmark suites, and Ethereum research infrastructure because the control surface is not the proving system itself, but who defines eligibility thresholds, benchmark cohorts, provenance standards, open schemas, and the public scoreboard that shapes the ecosystem’s understanding of credible progress.
What it does:
Tracks Ethereum L1 block-proof performance across multiple zkVM teams instead of publishing a single-vendor benchmark
Exposes public dashboards for latency, cost, eligibility, proving status, proof distribution, and prover-specific metadata
Distinguishes neutral measurement and provenance from self-reported vendor claims through verified-versus-reported framing in its public materials
Lets users inspect proofs by block, prover, guest, cluster, and zkVM version rather than only headline leaderboard numbers
Publishes integrated-zkVM lists and open-source repositories so the benchmark surface can be inspected and extended
Frames the whole platform as a public-good research interface on Ethereum’s path from early-phase proving toward mandatory and eventually enshrined proofs
Key claims:
The strongest reason to keep Ethproofs in the corpus is that it makes benchmarking and proof-legibility a first-class layer in the Ethereum proving stack. It is not building one prover; it is shaping how multiple provers get compared in public.
The homepage and GitHub organization are unusually explicit that the mission is to make proving progress credible, comparable, and verifiable. That is a more useful categorization clue than dashboard or analytics site because it points to governance over methodology, provenance, and benchmark interpretation.
The Learn page says Ethproofs aggregates data from various zkVM teams and provides cost, latency, and proving-time views for Ethereum block proofs. That makes it a comparison substrate sitting above any single proving architecture.
The public phase model — early adopters, delayed proving, mandatory proofs, enshrined proofs — is analytically useful because it frames Ethproofs as infrastructure for Ethereum’s proving transition, not as an isolated research toy.
The zkVMs page shows a versioned, named registry of integrated runtimes and requires specific IDs for cluster API operations. That makes runtime/version curation part of the benchmark control plane.
Ethproofs also belongs in the corpus because neutral benchmark is never fully neutral in practice. Eligibility thresholds, cohort definitions, hardware assumptions, open-schema choices, and which proof metadata becomes legible all influence the ecosystem’s narrative about what counts as real progress.
Whitepaper: No standalone Ethproofs whitepaper surfaced in this pass. The strongest primary materials were the official site, Learn page, zkVM registry docs, GitHub organization overview, and repository README collected in ../whitepapers/ethproofs-primary-sources-2026-05-13.md.