LibraryScaling2022Design paperCorpus record
The Espresso Sequencer
Espresso. Espresso Systems.
A shared sequencer orders transactions for many rollups. Each rollup still executes its own state. The sequencer sells order, not execution.
A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.
Ask what a rollup does when the shared sequencer stops. If the answer is 'it waits', the sequencer is a dependency, not a convenience.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 2
Code
Source, repository, and what is actually hosted
- Espresso notehttps://hackmd.io/@EspressoSystems/EspressoSequencer
- The source URL is not a GitHub repository. No code remote is invented.
- Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
- Add to a reading list
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
Every rollup that runs its own sequencer rebuilds the same leader, the same liveness risk, and a separate place to extract order.
Claim 02 · Paper model
The rule
A shared sequencer orders transactions for many rollups. Each rollup still executes its own state. The sequencer sells order, not execution.
Claim 03 · Paper model
How it is put together
Order is a service. Execution stays with the rollup. A shared leader is also a shared censorship point, unless the design says otherwise.
Claim 04 · Paper model
Where the claim stops
The note is not a claim that the sequencer is decentralised on day one.
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
Every rollup that runs its own sequencer rebuilds the same leader, the same liveness risk, and a separate place to extract order.
Model
What has to hold
The note is not a claim that the sequencer is decentralised on day one.
02 The rule
03 How it is put together
Observation
What the study says
Order is a service. Execution stays with the rollup. A shared leader is also a shared censorship point, unless the design says otherwise.
Model
What has to hold
Sharing a sequencer does not share security of execution.
04 Where the claim stops
Observation
What the study says
The note is not a claim that the sequencer is decentralised on day one.
Model
What has to hold
The note is not a claim that the sequencer is decentralised on day one.
03 Sequence
One action, as an operating tape
04 Load-bearing
The argument, and where a pitch drops it
Why it is still on the desk
The cut
Ask what a rollup does when the shared sequencer stops. If the answer is 'it waits', the sequencer is a dependency, not a convenience.
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
The note is not a claim that the sequencer is decentralised on day one.
After the text
The cut
Astria and others proposed variants. The split between order and execution is the part worth keeping.
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
Sharing a sequencer does not share security of execution.
05 Register
What has to be true
Model · Not re-measured
The note is not a claim that the sequencer is decentralised on day one.
Model · Not re-measured
Sharing a sequencer does not share security of execution.
Data · Not re-measured
A rollup can still publish its own data elsewhere.
06 Divergence
What happened after the paper
Astria and others proposed variants. The split between order and execution is the part worth keeping.
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
Every rollup that runs its own sequencer rebuilds the same leader, the same liveness risk, and a separate place to extract order.
What the design proposes
- Order is a service.
- Execution stays with the rollup.
- A shared leader is also a shared censorship point, unless the design says otherwise.
How the mechanism is specified
What this page does not treat as proven
- The note is not a claim that the sequencer is decentralised on day one.
- Sharing a sequencer does not share security of execution.
- A rollup can still publish its own data elsewhere.
Why the desk still reads it
Ask what a rollup does when the shared sequencer stops. If the answer is 'it waits', the sequencer is a dependency, not a convenience.
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.
Concepts
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.