LibraryScaling2023Design paperCorpus record
Espresso: a shared sequencer with a hotshot-style consensus
Espresso. Espresso Systems.
Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 7
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 sequencing is an ordering service. It is not the rollup's fraud proof or validity proof, and it does not make two rollups one chain.
Claim 02 · Paper model
The proposal
Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool.
Claim 03 · Paper model
The mechanism
The sequencer consensus finalises an order. Each rollup derives its own state from the slice of that order it claims.
Claim 04 · Paper model
The bound
No latency number 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
02 The proposal
Observation
What the study says
Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool.
Model
What has to hold
You are reading Espresso's docs. A rollup's own bridge docs are still required.
Falsifier
What would retire it
What do rollups treat as final: a sequencer commitment, or the settlement bridge?
03 The mechanism
04 The bound
03 Sequence
One action, as an operating tape
- 01The sequencer consensus finalises an order. Each rollup derives its own state from the slice of that order it claims.
- 02A rollup that can fall back to its own sequencer has a different censorship assumption from one that cannot. The docs have to say which.
- 03Confirmations from the shared sequencer are not settlement on Ethereum. Settlement is still the rollup's bridge.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool.
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
HotShot as a research name and the deployed sequencer may differ. Cite the doc you opened.
What actually moves
The cut
A rollup that can fall back to its own sequencer has a different censorship assumption from one that cannot. The docs have to say which.
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
HotShot as a research name and the deployed sequencer may differ. Cite the doc you opened.
What a later deployment may change
The cut
Confirmations from the shared sequencer are not settlement on Ethereum. Settlement is still the rollup's bridge.
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
HotShot as a research name and the deployed sequencer may differ. Cite the doc you opened.
05 Register
What has to be true
Model · Not re-measured
You are reading Espresso's docs. A rollup's own bridge docs are still required.
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 and not execution.
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 sequencing is an ordering service. It is not the rollup's fraud proof or validity proof, and it does not make two rollups one chain.
What the design proposes
- The sequencer consensus finalises an order. Each rollup derives its own state from the slice of that order it claims.
- A rollup that can fall back to its own sequencer has a different censorship assumption from one that cannot. The docs have to say which.
- Confirmations from the shared sequencer are not settlement on Ethereum. Settlement is still the rollup's bridge.
How the mechanism is specified
- The sequencer consensus finalises an order. Each rollup derives its own state from the slice of that order it claims.
- A rollup that can fall back to its own sequencer has a different censorship assumption from one that cannot. The docs have to say which.
- Confirmations from the shared sequencer are not settlement on Ethereum. Settlement is still the rollup's bridge.
What this page does not treat as proven
- No latency number is stated here.
- HotShot as a research name and the deployed sequencer may differ. Cite the doc you opened.
- Ordering is not data availability and not execution.
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.
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.