B.BlockAxis⌕ Search
Menu

Layer 2 rollups explained

A rollup executes activity outside the base layer and publishes information connecting its state to Ethereum.

AdvancedContent revised · 13.09.20263 min reading · allow 5–10 more minutes for the workshopBlockAxis

Your learning plan

Identify the rollup’s actual security boundary

By the end, explain the diagram in your own words, solve the case and justify the correction.

Prerequisites : Consensus and finality · EVM and smart contract composability

Level 3 · Advanced →

Reading path · 2 / 17 · Advanced

Key takeaway

A rollup executes activity outside the base layer and publishes information connecting its state to Ethereum.

The essentials

A rollup executes activity outside the base layer and publishes information connecting its state to Ethereum. Optimistic rollups allow invalid claims to be challenged; validity rollups use proofs of correct execution. Data publication and verification arrangements differ across systems.

How it works

A sequencer may provide a quick receipt before Ethereum settlement gives stronger guarantees. Native withdrawals from optimistic systems may include a challenge period. A liquidity bridge can offer a faster route by adding a separate provider or pool, with additional fees and risks.

What to watch

A Layer 2 can charge gas in ETH while using a different governance token. Network activity does not imply proportionate demand for that token. Compare upgrade keys, forced exits, sequencing, proof systems and data availability. A low quoted fee says little about whether users can safely exit during an outage.

Understand the details

A rollup executes transactions outside L1 and publishes commitments and relevant data to its settlement layer. The sequencer orders activity; a proof or dispute mechanism supports verification of state transitions. Optimistic and validity-based systems establish correctness differently. A quick sequencer acknowledgement is not identical to finalized settlement or an immediately available bridge withdrawal.

Boundaries and common mistakes

Inspect data availability, upgrade keys, proof maturity, censorship escape routes and bridge design. The label “L2” alone does not answer these questions. A validity proof does not guarantee that users can obtain all data they need, and a centralized sequencer outage can interrupt normal service without necessarily invalidating the last settled state.

The mechanism at a glance

  1. L2 ordering
  2. Publish data and commitment
  3. Prove or dispute state
  4. Settle and release withdrawal
Identify the rollup’s actual security boundary. Conceptual map: read these four landmarks together with the explanation above.
Applied workshop · work at your own pace

Apply the lesson to a case

A user sees a successful L2 payment immediately, but a canonical withdrawal requires additional settlement steps. Draw separate clocks for acknowledgement, L1 publication, proof or challenge processing, and withdrawal availability. Avoid inserting one universal delay: implementations differ.

What changes if a fast bridge pays before canonical settlement completes?

Choose one answer.

Optional video · English audio

Ethereum in 30 minutes

Vitalik Buterin · Ethereum Foundation · 2024

Identify the separate roles of L1 and L2. The talk describes Ethereum in 2024: roadmap statements and numerical parameters are historical context, not current guarantees.

Loading connects to YouTube. No video is loaded before your click. The written lesson is sufficient without watching. Publisher page and alternative access ↗

Interactive explainer · conceptual model

Inside a Layer 2 rollup

Transaction

The user signs on the selected Layer 2, which has its own chain identifier.

No real transaction is sent.
Terms in this lesson
Rollup
A scaling system that links off-chain execution to a base layer using published information and a proof or challenge mechanism.
Gas
A measure of execution resources; gas units and the price per unit are separate quantities.
Prepare a correction note

Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.