A concrete example
A quick sequencer receipt can precede stronger base-layer settlement guarantees.
In context
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.
The related mechanism, visually
- 01L2 ordering
- 02Publish data and commitment
- 03Prove or dispute state
- 04Settle and release withdrawal
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
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.
Put the mechanism into context
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.
Apply it in the workshop →What this mechanism does not guarantee
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.
Explore the full explanation
Layer 2 rollups explained
A rollup executes activity outside the base layer and publishes information connecting its state to Ethereum.