ZK Rollup
A ZK rollup, or zero-knowledge rollup, is a Layer 2 scaling system that processes many transactions outside a Layer 1 blockchain and submits cryptographic proofs that demonstrate the validity of the resulting state changes.
✦ Key Insight
ZK rollups can increase blockchain transaction capacity while reducing the amount of computation that must occur directly on the Layer 1. They are important for: Ethereum scaling DeFi Payments Token transfers On-chain trading Blockchain applications Unlike optimistic rollups, ZK rollups rely on validity proofs rather than primarily depending on a challenge period for detecting invalid state transitions.
✕ Common Misconceptions
Assuming "zero knowledge" always means transactions are private
Treating every ZK rollup as technically identical
Ignoring sequencer dependencies
Confusing validity proofs with fraud proofs
Assuming bridges have no additional risk
Assuming Layer 2 eliminates Ethereum fees entirely
Detailed Explanation
How It Works
Many Layer 2 transactions are processed together.
The system generates a cryptographic proof showing that the batch followed the required rules.
That proof is submitted to the Layer 1 smart contract.
The Layer 1 verifies the proof without needing to repeat every individual transaction calculation.
Different ZK rollups use different proof systems and architectures.
FAQs
Are ZK rollups automatically private?
No. Zero-knowledge proof technology can be used without hiding transaction information from users.
How are they different from optimistic rollups?
ZK rollups use validity proofs, while optimistic rollups generally use a dispute mechanism for potentially invalid state transitions.
In Practice
Dig Deeper
Layer 2
A Layer 2 is a scaling network built on top of a Layer 1 blockchain.
Optimistic Rollup
An optimistic rollup is a Layer 2 scaling system that processes transactions outside the main blockchain and submits compressed transaction data or results back to a Layer 1 network such as Ethereum. It is called "optimistic" because transactions are generally assumed to be valid unless someone challenges them during a defined dispute period.