LibraryConsensus2025Design paperCorpus record
MonadBFT and deferred execution
Monad. Monad.
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 6
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
High throughput claims that do not say what is agreed before execution are not yet a consensus design.
Claim 02 · Paper model
The proposal
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
Claim 03 · Paper model
The mechanism
Leaders propose an order. Finality, in the docs, is about that order, not about a price.
Claim 04 · Paper model
The bound
This note does not quote transactions per second or a validator count.
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
High throughput claims that do not say what is agreed before execution are not yet a consensus design.
Model
What has to hold
You are reading Monad's own architecture pages. A later client release can change a parameter without changing this paragraph.
02 The proposal
Observation
What the study says
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
Model
What has to hold
You are reading Monad's own architecture pages. A later client release can change a parameter without changing this paragraph.
03 The mechanism
Observation
What the study says
Leaders propose an order. Finality, in the docs, is about that order, not about a price.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
04 The bound
Observation
What the study says
This note does not quote transactions per second or a validator count.
Model
What has to hold
You are reading Monad's own architecture pages. A later client release can change a parameter without changing this paragraph.
03 Sequence
One action, as an operating tape
- 01Leaders propose an order. Finality, in the docs, is about that order, not about a price.
- 02Deferred execution means the execution result is not what the vote finished. A client that needs the result still has to execute or obtain a proof of execution.
- 03Parallel execution is a claim about the virtual machine's dependency analysis. It is a different claim from BFT safety.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
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 note does not quote transactions per second or a validator count.
What actually moves
The cut
Deferred execution means the execution result is not what the vote finished. A client that needs the result still has to execute or obtain a proof of execution.
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
Deferred execution changes when a user can treat a receipt as final. The docs have to be read for that delay, not guessed.
What a later deployment may change
The cut
Parallel execution is a claim about the virtual machine's dependency analysis. It is a different claim from BFT safety.
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
Deferred execution changes when a user can treat a receipt as final. The docs have to be read for that delay, not guessed.
05 Register
What has to be true
Model · Not re-measured
You are reading Monad's own architecture pages. A later client release can change a parameter without changing this paragraph.
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
Deferred execution changes when a user can treat a receipt as final. The docs have to be read for that delay, not guessed.
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
High throughput claims that do not say what is agreed before execution are not yet a consensus design.
What the design proposes
- Leaders propose an order. Finality, in the docs, is about that order, not about a price.
- Deferred execution means the execution result is not what the vote finished. A client that needs the result still has to execute or obtain a proof of execution.
- Parallel execution is a claim about the virtual machine's dependency analysis. It is a different claim from BFT safety.
How the mechanism is specified
- Leaders propose an order. Finality, in the docs, is about that order, not about a price.
- Deferred execution means the execution result is not what the vote finished. A client that needs the result still has to execute or obtain a proof of execution.
- Parallel execution is a claim about the virtual machine's dependency analysis. It is a different claim from BFT safety.
What this page does not treat as proven
- This note does not quote transactions per second or a validator count.
- A testnet parameter is not the proof.
- Deferred execution changes when a user can treat a receipt as final. The docs have to be read for that delay, not guessed.
Why the desk still reads it
Monad's published design splits consensus on the order of transactions from execution of those transactions, and it names a BFT protocol for the order.
09 Lexicon
Terms, opened into the record
- Deferred execution
- Consensus finishes an order before the state that order produces is required.
- MonadBFT
- The consensus protocol named in the Monad docs. It is not Tendermint by synonym.
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.
Protocols
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.