Ethereum rollups: which confirmation matters?

L1 means Ethereum mainnet. An L2 is a second-layer network built on it that executes transactions outside the main chain. An optimistic rollup is one L2 design: it publishes transaction data and results to Ethereum. Its acceptance rules include an opportunity to challenge incorrect execution.

A sequencer receives and orders L2 transactions and provides an initial result. Some withdrawals back to L1 must wait for the challenge window, allowing incorrect results to be disputed.

“Done” can mean different things

A fast response from a sequencer, inclusion of data on L1, and completion of a withdrawal are different events. A payment interface should name the event it is showing. A challenge period affects some cross-layer actions; it is not the latency of every interaction inside the rollup.

For an application, record the network, transaction identifier and required settlement condition together. Otherwise a generic “confirmed” label can hide which system accepted the operation and whether an L1 exit is complete.

This is also why comparing every rollup with a single withdrawal-time number is unhelpful. Compare the same user action and trust assumptions. OCAP can explain a common query approach, but a common API does not merge those settlement rules.

Sources and further reading

See Base as a concrete example.