What is ZK Rollup?
Last reviewed 2026-05-03
First defined in: A Rollup-Centric Ethereum Roadmap (2020) by Vitalik Buterin
Cite / Read deeper: DeFi Intel zk rollups deep-dive
A ZK rollup uses validity proofs to attest correct execution to L1, enabling fast finality (no fraud-proof window). Major implementations: zkSync Era, Starknet, Polygon zkEVM, Linea, Scroll, Taiko (based, hybrid).
How it works
Users send transactions to the rollup's sequencer, which orders and executes them off-chain against the rollup's own state, then groups hundreds or thousands of them into a batch. Because execution happens off Ethereum, every transaction in the batch shares one fixed L1 settlement cost.
A prover then generates a validity proof (a ZK-SNARK or ZK-STARK) for the batch: a compact cryptographic argument that every state transition followed the protocol rules. Producing the proof is computationally expensive, but verifying it is cheap and fast regardless of batch size.
The operator posts the new state root, the proof, and compressed transaction data to a verifier contract on L1. The contract checks the proof; if it passes, the state root is finalized immediately — there is no fraud-proof challenge window to wait out. Because the transaction data is published on L1 (as calldata or blob data), anyone can reconstruct the rollup's state and withdraw funds even if the sequencer and prover go offline. Withdrawals only need the batch's proof to be verified on L1, which is why ZK rollup exits settle in hours rather than the days an optimistic rollup requires.
Why it matters
ZK rollups eliminate the 7-day withdrawal window of optimistic rollups and offer post-quantum (STARK) and constant-time settlement.
Real-world examples
zkSync Era, Starknet, Polygon zkEVM, Linea, Scroll, Taiko (based hybrid).
Related terms
Go deeper
Read the full DeFi Intel topic deep-dive or browse the complete crypto glossary.
ZK Rollups deep-dive Browse GlossaryFrequently asked questions
What is a ZK rollup?
A ZK rollup uses validity proofs to attest correct execution to L1, enabling fast finality with no fraud-proof window.
How does a ZK rollup achieve fast finality?
The operator posts a new state root, proof, and compressed transaction data to an L1 verifier contract; if the proof passes, the state root is finalized immediately without a fraud-proof challenge window.
Which major implementations of ZK rollups are listed?
Major implementations include zkSync Era, Starknet, Polygon zkEVM, Linea, Scroll, and Taiko (based, hybrid).