Skip to content

ZK Rollup

How a ZK rollup differs from an optimistic rollup: it posts a cryptographic validity proof with every batch, letting Ethereum verify correctness immediately rather than after a challenge window.

A ZK rollup (zero-knowledge rollup) posts a cryptographic validity proof — typically a zk-SNARK or zk-STARK — alongside every batch of transactions it submits to Ethereum. That proof lets a smart contract on L1 verify, directly and quickly, that the claimed state transition followed the rollup’s rules correctly, without re-executing every transaction and without needing a challenge period.

The “zero-knowledge” part refers to the proof technique, not necessarily to privacy; most ZK rollups in production today are fully transparent about transaction contents. The proof’s job is compact, verifiable correctness, not confidentiality, though some designs do layer privacy features on top.

Why it matters

Because correctness is checked cryptographically rather than assumed, withdrawals from a well-functioning ZK rollup back to L1 don’t need to wait out a multi-day challenge window the way an optimistic rollup’s canonical exit does. The cost is engineering complexity: generating these proofs, especially for general-purpose smart contract execution, has historically been harder and more compute-intensive than the optimistic approach, though that gap has been narrowing.

Example

A ZK rollup batches a set of trades, generates a proof that every balance update followed the rollup’s rules, and posts both the compressed data and the proof to an L1 verifier contract, which accepts or rejects the batch in one check.

Related · Rollups

← All glossary terms

Not financial advice.