What Is a Rollup? How Ethereum Layer 2s Scale the Network

A rollup is a layer 2 scaling technology that executes transactions outside of Ethereum's main chain (layer 1) but posts data back to Ethereum in a way that lets anyone verify those transactions were processed correctly, inheriting Ethereum's security while dramatically reducing the cost of individual transactions.

The Basic Idea

Instead of every transaction being processed and stored directly on Ethereum's base layer — which is secure but limited in throughput and can get expensive during congestion — a rollup batches many transactions together off-chain, processes them, and then submits a compressed summary (plus supporting proof data) back to Ethereum. Because a single rollup transaction on Ethereum can represent hundreds or thousands of underlying user transactions, the cost per user transaction drops substantially.

Crucially, a rollup isn't just "a separate, faster blockchain" — the design specifically aims to inherit Ethereum's security guarantees, rather than asking users to trust a new, independent set of validators from scratch. This is the key distinction between a genuine rollup and a fully independent sidechain.

How Security Is Inherited

Rollups achieve this inherited security through two main proof approaches:

• Optimistic rollups assume transactions are valid by default and post them to Ethereum, but allow a window of time during which anyone can submit a fraud proof showing a specific batch was processed incorrectly. If a fraud proof succeeds, the invalid batch is reverted and the party that submitted bad data is penalized.
• ZK-rollups (validity proofs) generate a cryptographic proof alongside every batch, mathematically demonstrating the batch was processed correctly, which Ethereum's base layer can verify directly without needing to trust anyone or wait out a challenge period.

Our dedicated comparison of optimistic rollups vs. ZK-rollups covers the practical differences in withdrawal times, trust assumptions, and technical maturity between the two approaches in more depth.

Why Data Availability Matters

For either type of rollup to be genuinely trustworthy, the underlying transaction data needs to actually be available on Ethereum — not just a compressed summary or a claim that "trust us, it's valid." This is why rollups post data back to the base layer at all, historically as calldata and now increasingly through dedicated "blob" space introduced by proto-danksharding. Our explainer on danksharding covers how Ethereum is scaling this data availability layer specifically to support more and cheaper rollup activity.

What Rollups Actually Give Users

• Lower transaction fees compared to executing directly on Ethereum's base layer, especially since the blob-fee reductions from proto-danksharding took effect.
• Faster transaction confirmation on the rollup itself, often near-instant from a user's perspective, though final settlement security still depends on the underlying Ethereum posting/verification process.
• The same underlying assets and, generally, compatible tooling as Ethereum mainnet, since most rollups are built to be EVM-compatible, letting existing wallets and much existing smart contract code work with minimal changes.

Rollups vs. Sidechains

It's worth distinguishing rollups from sidechains, since both are sometimes casually lumped together as "layer 2s." A sidechain is an independent blockchain with its own validator set and security model, connected to Ethereum via a bridge, but not directly inheriting Ethereum's security. A rollup, by contrast, is specifically designed so that its correctness can be verified using Ethereum itself, either through fraud proofs or validity proofs. This is a meaningful trust distinction, even though both categories are often grouped under the general layer 2 umbrella in casual conversation.

Rollup Types at a Glance

Aspect	Optimistic Rollups	ZK-Rollups
Validity assumption	Assumed valid, challengeable	Proven valid upfront
Proof type	Fraud proof (only if challenged)	Validity (cryptographic) proof
Typical withdrawal delay to L1	Days (challenge period)	Much shorter, often near-instant after proof verification
Computational overhead	Lower	Higher (proof generation)
EVM compatibility maturity	Generally more mature historically	Rapidly improving

Risks Rollups Don't Eliminate

Rollups reduce trust requirements compared to fully independent chains, but they don't eliminate risk entirely. Sequencer centralization is a common concern — many rollups currently rely on a single, centralized party to order and batch transactions, which introduces a liveness and censorship risk even if the underlying validity is still cryptographically or economically secured. Bridging assets to and from rollups also carries its own risks, discussed in our guide to crypto bridges.

Bottom Line

Rollups scale Ethereum by processing transactions off-chain while posting data and proofs back to the base layer, letting anyone verify correctness without trusting a brand-new validator set from scratch. The two main flavors — optimistic and ZK — trade off proof complexity against withdrawal speed and trust assumptions differently, and a rollup's real-world safety still depends on details like data availability and sequencer decentralization. Compare activity and fees across rollups on MrDeFi's chains page.