Optimistic vs zero-knowledge rollups: a week to object, or a stamp up front
Optimistic rollups assume each batch is right and give anyone about a week to prove it wrong, so withdrawals wait. Zero-knowledge rollups attach a proof that the batch is right, so they can release funds in hours, at the cost of expensive proving and complex code.
Two side keepers work the village market. Both copy every line of their sheets into the notebook each evening. The difference is what they bring with it.
The first keeper writes her totals and pins a note to the door: "Object within a week, or these stand." The second keeper writes her totals and presses a stamp beside them, a stamp that can only be made if every sum on the sheet adds up.
Grandma Rosa asks the obvious question: which one gets her coins home faster? The stamp. Which one is simpler and cheaper to run? The note on the door. That's optimistic versus zero-knowledge rollups, and neither is free.
What it is
Both are rollups: they run transactions off Ethereum and post the data back to it. They differ in how Ethereum learns the result is right.
- Optimistic rollups assume it's right. During a challenge period, anyone can submit a fraud proof to show a batch was wrong. ethereum.org says the system "relies on the existence of one honest node" (ethereum.org).
- Zero-knowledge rollups submit a validity proof with each batch, and Ethereum's contract checks it before accepting the new state. Scroll's docs describe the step: a batch is finalised "with a validity proof", and only then can its state root "be used trustlessly" (Scroll docs).
How the proofs work is in "Zero-knowledge proofs explained". Here, we only need what they cost and what they buy.
How it works: two withdrawals, timed
Rosa moves coins from a rollup back to Ethereum through its official bridge.
On an optimistic rollup.
- OP Mainnet: you start the withdrawal, prove it on Ethereum, then wait out the fault challenge period: "7 days on mainnet" (Optimism docs). 7 × 24 = 168 hours.
- Arbitrum One: the dispute window is 45,818 Ethereum blocks (Arbitrum docs). At 12 seconds per block, that's 549,816 seconds: 6 days, 8 hours, 43 minutes and 36 seconds, or about 152.7 hours.
On a zero-knowledge rollup.
- In principle, no wait at all: ethereum.org says "There are no delays when moving funds from a ZK-rollup to Ethereum" once the contract has verified the proof (ethereum.org).
- In practice, ZKsync adds a deliberate time lock, cut "from 21 hours to a 3 hour minimum", to "prevent a quick drain of the protocol in the case a critical bug is discovered". Its docs add that busy periods can take another 1 to 2 hours (ZKsync docs).
The sum: Arbitrum's 549,816 seconds against ZKsync's 3-hour minimum is about 51 times longer. OP Mainnet's 168 hours against 3 is 56 times.
Now look at the ZKsync delay again. A ZK-rollup that trusts its maths completely wouldn't need a safety lock. The lock is there because the proving code is complex and could have a bug. The stamp is only as good as the stamp-maker.
What each one trusts
- Optimistic: at least one honest, awake watcher who checks every batch and objects in time. The checking is cheap; the waiting is not.
- Zero-knowledge: the maths, and the code that turns transactions into proofs. Some proof systems "require a trusted setup which, if mishandled, could potentially compromise" security, and proving "requires specialized hardware, which may encourage centralized control" (ethereum.org). Vitalik Buterin wrote in 2021 that ZK proving can be "potentially many thousands of times more expensive than running the computation directly" (Buterin, 2021).
- Both: whoever can upgrade the contracts. "Arbitrum and Optimism explained" covers the security councils.
Why it matters
- Users pay for the difference in time or in fees. Optimistic rollups make you wait; ZK-rollups pass on the proving cost.
- Apps that move money between chains often prefer faster finality on Ethereum, which favours proofs.
- Fast-bridge operators earn fees by fronting users the money during an optimistic rollup's week, and carry the risk themselves.
Where people get it wrong
- "Zero-knowledge means private." Most ZK-rollups use the proof for correctness. The transactions are usually still visible.
- "Optimistic means unsafe." It means one honest watcher is enough. That's a weak assumption, which is a good thing.
- "ZK withdrawals are instant." The maths allows it. Proving takes time, and some teams add safety delays on top.
- "The week is a fee in disguise." It's the time anyone gets to object. Shorten it, and you shorten everyone's chance to catch a mistake.
Read the exit line
Before you choose a rollup, look up two numbers in its own documentation: how long a withdrawal to Ethereum takes, and why. A week means a challenge period. Hours mean a proof plus whatever safety delay the team chose.
One keeper asks you to trust a watcher. The other asks you to trust a stamp. Neither asks you to trust nobody.
Frequently asked questions
What is the difference between optimistic and ZK-rollups?
Optimistic rollups assume batches are correct and allow a challenge period, about a week, for anyone to submit a fraud proof. ZK-rollups attach a validity proof to each batch, which Ethereum checks before accepting it. Both post their transaction data to Ethereum.
Why do optimistic rollup withdrawals take a week?
The official bridge waits for the challenge period to pass so anyone can prove a batch wrong. On OP Mainnet that is 7 days; on Arbitrum One it is 45,818 Ethereum blocks, about 6.4 days. Third-party fast bridges can pay you earlier for a fee.
Are ZK-rollup withdrawals instant?
Not quite. Funds can move once Ethereum has verified the batch's validity proof, but producing the proof takes time. ZKsync also applies a deliberate time lock of at least 3 hours as a safety measure against bugs.
Which is more secure, optimistic or ZK-rollups?
They trust different things. Optimistic rollups need at least one honest watcher to object in time; ZK-rollups rely on correct maths and correct proving code, sometimes with a trusted setup. In both, the people who can upgrade the contracts matter as much as the proof system.
Do ZK-rollups make transactions private?
Usually not. Most ZK-rollups use the proof to show the batch was processed correctly, while the transaction data stays visible. Privacy only exists where a system is designed to hide the inputs.

