Computational cryptography › Not live yet › Hash-based
ZK PROOFPlanned, not live yetPlanned: K*

Mandatory zkEVM proofs

In plain words

Planned for around 2029: every block must come with a proof that it was executed correctly.

Why it matters: The path to much higher throughput on Ethereum itself.

The details

On the map: every block needs a proof (1-of-1)

Map note, rests on: one sound zkVM + hash security

Strawmap fork K* (around 2029)[1]: every block must come with a proof of correct execution, and validators check the proof instead of re-executing. This is the path to the "gigagas L1" goal of about 10,000 transactions per second[2].

Security then rests on the soundness of the proof system, with no fallback to re-execution, which is why formal verification and multi-proof designs come first.

Rests on

If any of these breaks, this breaks too.

If it falls

If this breaks, these break with it.

Nothing on the map depends on it: it is an end point of the roadmap.

On the roadmap

Next-step links, not dependencies: these don't fall together.

References

  1. Justin Drake, Julian Ma, Toni Wahrstätter and Vitalik Buterin. L1 Strawmap: Ethereum Draft Roadmap. Ethereum Foundation Protocol, 2026. strawmap.org
  2. Ethereum Foundation. Shipping an L1 zkEVM #1: Realtime Proving. Ethereum Foundation blog, 2025. blog.ethereum.org/en/2025/07/10/realtime-proving