LibraryScaling2023Design paperCorpus record
Astria: a shared sequencer for rollups
Astria. Astria.
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 5
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
Shared ordering without shared execution means two rollups can take the same sequence and still disagree about state if their virtual machines differ. That is allowed. It is not a bug in the sequencer.
Claim 02 · Paper model
The proposal
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
Claim 03 · Paper model
The mechanism
The sequencer produces an ordered log. A rollup derives its transactions from a namespace or filter in that log.
Claim 04 · Paper model
The bound
No latency is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
Shared ordering without shared execution means two rollups can take the same sequence and still disagree about state if their virtual machines differ. That is allowed. It is not a bug in the sequencer.
Falsifier
What would retire it
What do users do if the sequencer stops, according to the rollup rather than the sequencer?
02 The proposal
Observation
What the study says
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
Falsifier
What would retire it
What do users do if the sequencer stops, according to the rollup rather than the sequencer?
03 The mechanism
04 The bound
03 Sequence
One action, as an operating tape
- 01The sequencer produces an ordered log. A rollup derives its transactions from a namespace or filter in that log.
- 02Settlement of the rollup's state is not the sequencer's signature.
- 03If the sequencer halts, the rollup's escape hatch is whatever the rollup's own bridge says. Astria's docs do not supply it by brand.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What actually moves
The cut
Settlement of the rollup's state is not the sequencer's signature.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What a later deployment may change
The cut
If the sequencer halts, the rollup's escape hatch is whatever the rollup's own bridge says. Astria's docs do not supply it by brand.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Model · Not re-measured
You are reading Astria's docs. The rollup's bridge is a second document.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
Ordering is not data availability.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Shared ordering without shared execution means two rollups can take the same sequence and still disagree about state if their virtual machines differ. That is allowed. It is not a bug in the sequencer.
What the design proposes
- The sequencer produces an ordered log. A rollup derives its transactions from a namespace or filter in that log.
- Settlement of the rollup's state is not the sequencer's signature.
- If the sequencer halts, the rollup's escape hatch is whatever the rollup's own bridge says. Astria's docs do not supply it by brand.
How the mechanism is specified
- The sequencer produces an ordered log. A rollup derives its transactions from a namespace or filter in that log.
- Settlement of the rollup's state is not the sequencer's signature.
- If the sequencer halts, the rollup's escape hatch is whatever the rollup's own bridge says. Astria's docs do not supply it by brand.
What this page does not treat as proven
- No latency is stated here.
- This is not Espresso's document, though the role is similar.
- Ordering is not data availability.
Why the desk still reads it
Astria publishes a shared sequencer that rollups can treat as their order source, with the rollup still responsible for execution and settlement.
09 Lexicon
Terms, opened into the record
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Papers
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.