Add zkEVM for L1 block verification page#16975
Merged
Merged
Conversation
- New roadmap page explaining zkEVM for L1 (distinct from L2 zkEVM rollups) - Covers re-execution problem, benefits, real-time proving challenges - Lists current implementations (OpenVM, RISC0, Airbender, Jolt, Zisk) - Adds cross-links from zero-knowledge-proofs, zk-rollups, and statelessness pages Based on Ethereum Foundation zkEVM research at zkevm.ethereum.foundation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wackerow
requested changes
Dec 24, 2025
|
|
||
| ### Predictable finality {#predictable-finality} | ||
|
|
||
| Proof verification operates in constant time regardless of block complexity. This makes attestation timing more predictable and reduces missed attestations that can occur when validators struggle to process complex blocks in time. |
Member
There was a problem hiding this comment.
small suggestion
Suggested change
| Proof verification operates in constant time regardless of block complexity. This makes attestation timing more predictable and reduces missed attestations that can occur when validators struggle to process complex blocks in time. | |
| Proof verification operates in constant time regardless of block complexity (`O(1)` runtime). This makes attestation timing more predictable and reduces missed attestations that can occur when validators struggle to process complex blocks in time. |
Comment on lines
+106
to
+114
| ## Current progress {#current-progress} | ||
|
|
||
| zkEVM L1 verification is in active research. Key milestones: | ||
|
|
||
| - Multiple zkVM implementations passing comprehensive test suites | ||
| - Research into real-time proving approaches | ||
| - Client integration specifications being developed | ||
|
|
||
| This technology is not yet integrated into production Ethereum clients. Full mainnet deployment is expected to take several years as proving speeds improve and the technology matures. |
Member
There was a problem hiding this comment.
Just noting these as time-sensitive comments which will need to be maintained
Comment on lines
+56
to
+58
| ### Stronger decentralization {#stronger-decentralization} | ||
|
|
||
| With zkEVM verification, validators only need to verify proofs rather than execute transactions. This dramatically lowers the hardware requirements for running a validator, enabling more people to participate in securing the network. Greater validator diversity strengthens Ethereum's censorship resistance and resilience. |
Member
There was a problem hiding this comment.
Would it be worth addressing the question of "does this introduce a new point of centralization?"
Member
Contributor
|
This issue is stale because it has been open 30 days with no activity. |
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
|
Changes pushed in 649b44a:
Reviewed by Claude (claude-opus-4-6) |
- Add centralization/prover market discussion to decentralization section - Fix Airbender link (archived era-boojum -> zksync-airbender) - Remove stale test counts from implementation table - Replace verbose "Current progress" section with compact warning Alert - Fix zkVM tracker link attribution - Add Ethproofs to further reading - Add zkEVM card to roadmap landing page Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Add translated zkEVM content for all 24 non-English locales: JSON keys (page-roadmap-zkevm-title, page-roadmap-zkevm-description) and markdown paragraphs (zero-knowledge-proofs, zk-rollups alert, statelessness). Bengali skipped for 2 missing content files. Co-Authored-By: Gemini 2.0 Flash <gemini-cli@google.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
wackerow
approved these changes
Mar 26, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Adds a new roadmap page explaining zkEVM for L1 block verification - using zero-knowledge proofs to verify Ethereum block execution without re-running all transactions.
This is distinct from the existing zk-rollups page which covers L2 zkEVM rollups. L1 zkEVM verification is a key part of Ethereum's roadmap ('The Verge') that would enable:
Changes
New page:
/roadmap/zkevm/index.mdcovering:Cross-links added in:
/zero-knowledge-proofs/- in verifiable computation section/developers/docs/scaling/zk-rollups/- distinguishing L1 vs L2 zkEVM/roadmap/statelessness/- as complementary technologySources
Content based on:
Preview links
https://deploy-preview-16975.ethereum.it/roadmap
https://deploy-preview-16975.ethereum.it/roadmap/zkevm