LibraryMarkets2023Design paperCorpus record
SUAVE: a separate chain for preferences and block building
SUAVE. Flashbots.
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
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
A preference is not a transaction on Ethereum. If the essay's boundary is blurred, the design has been oversold.
Claim 02 · Paper model
The proposal
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
Claim 03 · Paper model
The mechanism
Users submit preferences. Executors or builders match them. Settlement of the resulting transaction still happens on the target chain.
Claim 04 · Paper model
The bound
This is an architecture essay. It is not proof the system runs as described.
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
A preference is not a transaction on Ethereum. If the essay's boundary is blurred, the design has been oversold.
Model
What has to hold
You are reading the SUAVE essay. A repository that only partially implements it is a narrower object.
Falsifier
What would retire it
Who can read a preference?
02 The proposal
Observation
What the study says
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
Model
What has to hold
You are reading the SUAVE essay. A repository that only partially implements it is a narrower object.
Falsifier
What would retire it
What is stored on the SUAVE chain versus on the target chain?
03 The mechanism
Observation
What the study says
Users submit preferences. Executors or builders match them. Settlement of the resulting transaction still happens on the target chain.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What is stored on the SUAVE chain versus on the target chain?
04 The bound
Observation
What the study says
This is an architecture essay. It is not proof the system runs as described.
Model
What has to hold
You are reading the SUAVE essay. A repository that only partially implements it is a narrower object.
Falsifier
What would retire it
What is stored on the SUAVE chain versus on the target chain?
03 Sequence
One action, as an operating tape
- 01Users submit preferences. Executors or builders match them. Settlement of the resulting transaction still happens on the target chain.
- 02Confidentiality of preferences is a claim the essay makes with a specific mechanism. If that mechanism is not in the deployment, do not import the claim.
- 03SUAVE does not replace Ethereum consensus. It tries to replace the relay's role in the builder market.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
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
Confidentiality of preferences is a claim the essay makes with a specific mechanism. If that mechanism is not in the deployment, do not import the claim.
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
This is an architecture essay. It is not proof the system runs as described.
What a later deployment may change
The cut
SUAVE does not replace Ethereum consensus. It tries to replace the relay's role in the builder market.
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 the SUAVE essay. A repository that only partially implements it is a narrower object.
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
MEV-Boost remains the deployed sidecar study. Do not merge them.
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
A preference is not a transaction on Ethereum. If the essay's boundary is blurred, the design has been oversold.
What the design proposes
- Users submit preferences. Executors or builders match them. Settlement of the resulting transaction still happens on the target chain.
- Confidentiality of preferences is a claim the essay makes with a specific mechanism. If that mechanism is not in the deployment, do not import the claim.
- SUAVE does not replace Ethereum consensus. It tries to replace the relay's role in the builder market.
How the mechanism is specified
- Users submit preferences. Executors or builders match them. Settlement of the resulting transaction still happens on the target chain.
- Confidentiality of preferences is a claim the essay makes with a specific mechanism. If that mechanism is not in the deployment, do not import the claim.
- SUAVE does not replace Ethereum consensus. It tries to replace the relay's role in the builder market.
What this page does not treat as proven
- This is an architecture essay. It is not proof the system runs as described.
- No privacy proof is imported beyond what the essay itself contains, and this note does not add one.
- MEV-Boost remains the deployed sidecar study. Do not merge them.
Why the desk still reads it
SUAVE proposes a chain where users send preferences and builders compute on them, so order flow is not handed to a single relay by default.
09 Lexicon
Terms, opened into the record
- Preference
- A signed statement of what the user wants. It is not the settlement transaction.
- Executor
- A party who turns a preference into a transaction on a target chain.
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.