← All guides

Layer 2 rollups explained: what settles on Ethereum, and what does not

Market basics · 7 min read

Financial disclaimer, not financial advice. This article is general information and education only. It does not recommend buying, selling, or holding any crypto asset, fund, or product, and it is not personalised financial, tax, or legal advice. Crypto assets are volatile and speculative and can lose all of their value. Consider your own circumstances and, where appropriate, speak with a qualified professional in your jurisdiction before making any financial decision.

Your transfer confirmed in seconds. So why does the withdrawal back to Ethereum take days?

That gap is the whole subject. A rollup runs two clocks at once. The first clock is the layer 2 network itself, which orders and confirms your transaction quickly. The second clock is Ethereum, the layer 1, which accepts the rollup results only after a verification step has run its course. Most confusion about layer 2 networks, and most bad deposits, comes from watching the first clock and assuming the second one agrees with it.

What a rollup actually does with your transaction

Start with the job. Ethereum computation is the slow and expensive part of using Ethereum, so a rollup moves execution somewhere cheaper. The rollup operator takes your transaction off the main chain, executes it alongside many others, bundles the batch, and posts the transaction data back to Ethereum as calldata or in blobs, the temporary data space Ethereum reserves for this purpose. Smart contracts on Ethereum hold the rollup state, track deposits, and receive each new state root, the fingerprint of every balance and contract after the batch.

Posting the data back is not bookkeeping. It is the security arrangement. Because the transaction data sits on Ethereum, anyone can rebuild the rollup state from it and check that a batch was executed correctly. Ethereum ends up guaranteeing two things for a true rollup: the correctness of the offchain computation can be enforced on layer 1, and the data behind that computation is available to anyone who wants to verify it. A network that skips the second part has changed the deal, whatever its marketing calls it.

The scale on offer is real but loosely quoted. Ethereum's own documentation says optimistic rollups can offer up to 10 to 100 times the scalability of the base layer, because computation is the bottleneck being removed. Read that as a range for a mechanism, not as a speed rating for any named network. Throughput figures in project marketing are measured under conditions the project chooses.

Two ways to convince layer 1: fraud proofs and validity proofs

Every rollup must answer one question for Ethereum: why should the main chain accept this new state? The two families answer in opposite directions.

Optimistic rollups assume the batch is right. The operator posts the batch and a new state root without a proof of validity, and a challenge period opens, typically about seven days. During that window anyone can compute a fraud proof showing a transaction was executed incorrectly. If the proof succeeds, the protocol re-executes the disputed work, corrects the state, and penalises the operator responsible. Operators post a bond before producing blocks, and that bond can be slashed. The security model is economic and social at once: cheating is expensive, and the system assumes at least one honest watcher will check the work and challenge in time.

ZK rollups prove the batch is right. Operators execute the batch offchain, then generate a cryptographic validity proof, a compact mathematical argument that the state transition followed the rules. A contract on Ethereum verifies that proof, and only then does the state update stand. There is no challenge period because there is nothing left to challenge: an incorrect transition cannot produce a valid proof. The cost sits elsewhere, in the computing power needed to generate proofs for every batch.

One family trusts and verifies after the fact. The other verifies and trusts nothing. Both anchor to Ethereum, which is what makes both of them rollups.

Side by side, including the networks that are not rollups

QuestionOptimistic rollupZK rollupSidechain
How is a batch accepted?Assumed valid, open to challengeA validity proof is verified on layer 1 firstIts own validators accept blocks under its own consensus
What punishes cheating?A successful fraud proof, re-execution, and a slashed operator bondAn invalid state cannot produce a valid proofWhatever its own consensus and validator set provide
Where does transaction data live?Posted to Ethereum as calldata or blobsPosted to Ethereum, in reduced form, since the proof carries the verificationOn the sidechain itself
Withdrawal to Ethereum via the canonical bridgeAfter the challenge period, typically about seven daysOnce the batch proof is verified, often minutes to hoursThrough a two way bridge, under the bridge's own trust model
Where does security come from?Ethereum, plus at least one honest challengerEthereum, plus the cryptography of the proof systemThe sidechain itself, not Ethereum

Two boundary cases complete the map. A validium uses validity proofs like a ZK rollup but stores transaction data somewhere other than Ethereum, so its proof system is strong while its data availability rests on a different party. Plasma designs also verify work on Ethereum with fraud proofs but keep data off the main chain. Ethereum's scaling documentation groups sidechains, validiums and plasma chains together on one side of a line: they communicate with the main chain, but they derive their security separately from it. Rollups and state channels sit on the other side. The label layer 2 belongs on the rollup side of that line.

Two clocks: confirmation on layer 2, settlement on layer 1

Now the withdrawal wait makes sense. On an optimistic rollup your transaction can feel instant on layer 2, because the sequencer has ordered and confirmed it. But a withdrawal through the rollup's own bridge is a layer 1 event, and layer 1 accepts the batch only once the challenge period has elapsed with no successful challenge. Ethereum's documentation puts it plainly: rollup transactions are final after the rollup block is accepted on Ethereum. Until then, the layer 2 confirmation is a strong promise, not a settled fact.

On a ZK rollup the second clock runs fast. Once Ethereum verifies the validity proof for the batch containing your withdrawal, the state settles, often within minutes to hours, and the withdrawal can complete. There is no waiting period equivalent to the challenge window.

Third party services will happily sell you the difference. A fast exit service pays you on layer 1 immediately and takes your place in the queue for the canonical withdrawal. That can be a reasonable purchase, but name it correctly: your counterparty has changed, from a protocol rule to a company with a balance sheet and terms. The seven day clock did not shrink. Someone else is waiting it out for you, for a fee.

The checkpoint: five checks before you deposit

  1. Is it actually a rollup? Check whether the network posts transaction data to Ethereum and settles there. If it runs its own validator consensus and connects by bridge, it is a sidechain, and your risk assessment should price its own security, not Ethereum's.
  2. Which proof system, and is it live? Fraud proofs or validity proofs, and whether the proof system is fully operational or still restricted. The project's own documentation, checked against Ethereum's scaling pages, is the source. A roadmap item is not a security property.
  3. What is the withdrawal clock? Find the canonical bridge terms: the challenge period on an optimistic rollup, the proof cadence on a ZK rollup. If the number is not published, that is your answer about the network's maturity.
  4. What happens if the operator stops? On a documented rollup, posted data lets another node reproduce the state, users can build Merkle proofs of ownership to withdraw, and transactions can be submitted through layer 1 if the sequencer censors or stalls. A network with no documented escape route is asking for trust its design has not earned.
  5. What does the sequencer control? One operator ordering transactions is a centralisation fact, not automatically a disqualifier. It decides ordering, can delay inclusion, and is the party whose bond and behaviour the fraud proof system polices. Know that before the deposit, not during an outage.

Claims to retire

Three claims fail the checks above. First, that layer 2 is a quality label: it is a technical description of where security comes from, and several networks wearing the label derive their security from themselves. Second, that a fast layer 2 confirmation means your money has settled: settlement is a layer 1 event with its own clock, and on optimistic rollups that clock runs about seven days. Third, that the proof debate has a winner: fraud proofs buy simplicity and pay in time, validity proofs buy speed and pay in proving cost. The honest comparison is which currency you would rather spend, stated before you deposit, not discovered during a withdrawal.

, Sterling Cole, Money Writer. Earning Desk

Reminder: Crypto Investing is educational content only, not financial advice. Crypto assets are volatile and can lose all value. Product terms, fees, and rules change, read the current prospectus, terms, or manufacturer documentation for any product you are considering.