Rollups: Optimistic vs ZK

A rollup is the most widely used kind of Layer 2. It executes transactions off-chain, compresses the results, and posts both the data and some evidence of correctness back to the Layer 1 - 'rolling up' many transactions into one compact submission.

That evidence of correctness is what separates a rollup from just trusting an operator's word. It's also where the two major rollup designs diverge.

An optimistic rollup posts a batch and assumes it's correct by default. For a set challenge window - commonly around a week - anyone watching can download the data, re-run it, and submit a fraud proof if something's wrong. A successful fraud proof reverts the bad batch and penalizes whoever posted it.

The trade-off is that withdrawals back to the Layer 1 have to wait out that challenge window, since the network needs time to make sure no one disputes the batch.

A ZK-rollup (zero-knowledge rollup) takes a different approach: it submits a validity proof alongside every batch - a compact cryptographic proof that mathematically guarantees the transactions were executed correctly. There's no need to wait for a challenge window, because the math itself rules out cheating.

The trade-off shifts elsewhere: generating those proofs is computationally heavy, and building a system that can produce valid proofs for arbitrary smart-contract code is a harder engineering problem than an optimistic design.

Neither design is strictly better. Optimistic rollups have historically been simpler to build and run general-purpose smart contracts on, at the cost of slower withdrawals. ZK-rollups offer near-instant finality back to the L1, at the cost of harder engineering - though that gap has been closing quickly.

In practice, most users notice the difference mainly as 'how long until my withdrawal to the base layer clears' - fast for ZK, delayed by a challenge window for optimistic.