Rollup

Overview

Why Rollup matters

Executing every transaction directly on a general-purpose Layer 1 limits capacity and can raise fees. A rollup batches execution to spread base-layer data and settlement costs across many transactions. The important question is how the base chain can enforce the correct result if the rollup operator behaves badly.

How it works

Users submit transactions to a rollup sequencer or comparable operator. Transactions execute in the rollup environment, and compressed transaction data or required inputs are published to the base layer under the design's data-availability rules. Optimistic rollups initially accept proposed state transitions and permit challenges within a dispute window. Validity rollups use cryptographic proofs to show that a state update follows the computation rules. Different systems make different assumptions about forced inclusion, upgrade governance and data availability. An L2 transaction may appear final to a wallet before the base-chain settlement process makes all kinds of withdrawal available. Payment software must decide which state meets its risk policy and separately handle cross-chain exits.

Why data availability affects withdrawal safety

Imagine a rollup operator claims a new state but refuses to reveal enough transaction data for others to reconstruct it. Even if a fraud-proof mechanism theoretically allows challenges, honest participants may lack the information needed to show that the state is wrong. That is why data availability is a central part of rollup security rather than an optional performance detail. Some designs publish required data to Ethereum; others use separate committees or systems and therefore have different trust assumptions. In validity-proof rollups, correctness proofs can establish the state transition, but data availability can still be crucial for users to reconstruct balances and exit safely. Merchant integrators should read the network's actual data and exit design instead of treating all validity-proving systems as identical.

A real-world payment example

A store accepts a stablecoin on a rollup for a $35 subscription. It verifies the rollup token contract and payment status. At the end of the week, it withdraws proceeds to Ethereum Mainnet. That treasury transfer follows bridge and settlement mechanics distinct from the original customer's checkout.

Limits and common misunderstandings

Rollups are not interchangeable merely because they share Ethereum-style addresses. "Secured by Ethereum" is shorthand that needs clarification about which assets, withdrawal mechanisms, data assumptions and upgrades apply. Merchant receipts and withdrawal finality must not be conflated.

How it differs from related concepts

A rollup is a specific Layer-2 design. A sidechain generally runs its own consensus with different settlement assumptions. A bridge is the mechanism used to move or represent value between networks.

Explore further

Official background: technical documentation.

Related glossary terms: Layer 2, Ethereum Mainnet, Arbitrum Network.