A rollup is a layer 2 network that processes transactions outside a base blockchain, bundles ("rolls up") many of them together, and posts the transaction data and a commitment to the resulting state back to the base chain. Because anyone can reconstruct the rollup's state from the data on the base layer, and because the base chain decides which state is valid, a rollup inherits much of the security of the underlying network while handling far more transactions at lower cost.
Rollups are the main scaling approach on the Ethereum blockchain, where they are often called layer 2s. They differ from sidechains, which have their own validators and security, and from payment channels, which only work between fixed participants. Much of the day-to-day activity in stablecoin payments and decentralised finance now takes place on rollups rather than on the base chain itself.
How a rollup works
Users send transactions to the rollup, where a component called the sequencer orders them, executes them and produces new blocks, usually within seconds. Periodically, the rollup publishes a batch to a smart contract on the base chain containing the compressed transaction data and the new state root, a short cryptographic summary of all balances and contract storage after the batch.
Publishing the data matters because it guarantees data availability: even if the rollup operator disappears, anyone can rebuild the state and prove what they own. Ethereum's Dencun upgrade in March 2024 added a cheaper, temporary form of data storage called blobs designed for rollup data, which cut fees on many rollups sharply. Some designs post data to a separate data availability layer instead; these are often called validiums or optimiums and offer weaker guarantees.
Optimistic and zero-knowledge rollups
Rollups differ mainly in how the base chain is convinced that a posted state is correct:
- Optimistic rollups. An optimistic rollup assumes each batch is valid unless challenged. During a challenge window, commonly about seven days, any observer can submit a fraud proof showing that a state transition was wrong, and the invalid batch is reverted. Arbitrum and OP Mainnet are well-known examples.
- Zero-knowledge rollups. A ZK rollup posts a validity proof with every batch, a cryptographic proof that the new state follows correctly from the old one. Once the base chain verifies the proof, the batch is final, with no challenge window. Examples include zkSync, Starknet and Scroll.
Optimistic designs are simpler and were easier to make compatible with the Ethereum Virtual Machine, while ZK designs offer faster final withdrawals at the cost of heavy computation to generate proofs. Variants such as the based rollup hand transaction ordering to base-chain validators instead of a separate sequencer.
Withdrawals, bridging and finality
Assets move onto a rollup by being locked in its contract on the base chain, and move back by being released from that contract once the rollup's state is accepted. On an optimistic rollup this means a native withdrawal waits for the challenge window to close; third-party liquidity providers and cross-chain bridges offer faster exits for a fee and add their own risk.
Finality therefore comes in layers. A rollup transaction is usually confirmed by the sequencer in seconds, becomes harder to reverse once its batch is posted, and is fully final on the base layer only after the proof is verified or the challenge window passes. Exchanges usually wait for at least the batch to be posted before crediting deposits from a rollup. Payment firms that accept stablecoin settlement on rollups need to decide which of these points counts as settlement, a question covered more generally under blockchain transaction finality.
Why stablecoin payments use rollups
Transfers on a rollup typically cost a small fraction of the same transfer on the base chain, which makes small payments and payouts practical. Several stablecoin issuers mint their tokens natively on major rollups, so holders can redeem them directly rather than holding a bridged copy, as discussed under native and bridged stablecoins. Rollups also absorb demand that would otherwise cause network congestion on the base chain.
Risks and criticism
Most rollups still rely on a single sequencer run by the project team, which can delay or censor transactions and becomes a single point of failure if it goes down. Many also have upgradeable contracts controlled by a multisignature group or admin key, meaning a small group could change the rules or, in the worst case, the bridge contract that holds user funds. Some optimistic rollups launched without permissionless fraud proofs, so the security model described above was not fully in place. Community trackers grade rollups by stages of decentralisation to make these trade-offs visible. Liquidity is also split across many rollups, which complicates interoperability and pushes users toward bridges, a frequent target of large hacks.
External links
Ref 1070001073