Computational cryptography › Live on mainnet today
Ethereum component

ZK rollups

In plain words

Layer 2 chains that post a proof with each batch, so Ethereum checks correctness itself.

The idea: The rollup executes transactions offchain and posts a proof that the new state follows from the old one by the rules. Ethereum checks the proof, which takes about the same small effort however many transactions the batch contained, so the batch is final as soon as the proof is accepted, with no waiting for challenges.

Why it matters: Their safety rests on the proof system having no flaws.

The details

On the map: validity proofs checked on L1

Rollups that post a validity proof with each batch, so Ethereum checks correctness directly instead of waiting for challenges.

Some verify STARK proofs directly. Many wrap their proof in a Groth16 or PLONK proof on BN254 to keep gas low, which brings in pairing assumptions and a trusted setup. Proof-system bugs are the most practical risk today[1], which is why many rollups keep security councils or multiple provers[2].

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, something people use directly.

References

  1. Stefanos Chaliasos, Jens Ernstberger, David Theodore et al. SoK: What don't we know? Understanding Security Vulnerabilities in SNARKs. arXiv:2402.15293, 2024. arxiv.org/abs/2402.15293
  2. L2BEAT. Rollup stages. 2023. l2beat.com/stages