Curious about a word? Tap a dotted term for its meaning.

ROUTE 07 / Go deeper

A transaction on a rollup

Trace execution, batch data, proofs, and the route back.

A faster local confirmation can be useful without being the final settlement event. This path separates a rollup’s execution, ordering, data publication, and verification, then follows the dependencies that matter when withdrawing.

  1. 01
  2. 02

    Layer-two networks

    Separate the layers

    Execution outside the base chain still needs a credible settlement path.

  3. 03

    Optimistic rollups

    Inspect the challenge route

    A disputable state claim relies on functioning challenge mechanisms.

  4. 04

    Validity proofs and rollups

    Inspect the proof route

    A proof checks a specified computation, not the fairness of every application.

  5. 05

    Data availability

    Find the reconstruction data

    Verification and the ability to recover state need usable data.

  6. 06

    Bridges and wrapped claims

    Follow a withdrawal

    Bridge contracts and upgrade controls can add dependencies beyond the proof system.

CHECK YOUR UNDERSTANDING

Does an immediate sequencer receipt prove that an L1 withdrawal is immediately available?

Reveal the explanation

No. Sequencer confirmation, L1 data inclusion, settlement verification, and withdrawal availability are separate stages. Their timing and controls depend on the particular rollup.

Another route through the ecosystemRead beyond the token ticker →