LibraryConsensus2018Design paperCorpus record
Solana cluster and consensus documentation
Solana core. Solana Labs and Anza.
The Solana white paper describes proof of history and the architecture. The cluster documentation is the operational consensus text: tower votes, forks, and how a leader schedule is supposed to behave.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
The Solana white paper describes proof of history and the architecture. The cluster documentation is the operational consensus text: tower votes, forks, and how a leader schedule is supposed to behave.
- 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
Proof of history in the paper is not a warranty that a given client implements the paper. The client docs are the closer text.
Claim 02 · Paper model
The proposal
The Solana white paper describes proof of history and the architecture. The cluster documentation is the operational consensus text: tower votes, forks, and how a leader schedule is supposed to behave.
Claim 03 · Paper model
The mechanism
A leader schedule assigns slots. Tower BFT is the vote lockout rule the docs describe. They are different mechanisms that the white paper compresses.
Claim 04 · Paper model
The bound
This note does not quote a slot time as a promise.
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
Proof of history in the paper is not a warranty that a given client implements the paper. The client docs are the closer text.
Model
What has to hold
You are reading the Anza validator documentation. The white paper is the other study.
Falsifier
What would retire it
Which client is the page describing?
02 The proposal
Observation
What the study says
The Solana white paper describes proof of history and the architecture. The cluster documentation is the operational consensus text: tower votes, forks, and how a leader schedule is supposed to behave.
Model
What has to hold
You are reading the Anza validator documentation. The white paper is the other study.
Falsifier
What would retire it
What confirmation level is required before an application treats a slot as final?
03 The mechanism
Observation
What the study says
A leader schedule assigns slots. Tower BFT is the vote lockout rule the docs describe. They are different mechanisms that the white paper compresses.
Model
What has to hold
You are reading the Anza validator documentation. The white paper is the other study.
Falsifier
What would retire it
Which client is the page describing?
04 The bound
03 Sequence
One action, as an operating tape
- 01A leader schedule assigns slots. Tower BFT is the vote lockout rule the docs describe. They are different mechanisms that the white paper compresses.
- 02A fork is still possible. Confirmation levels the docs name are not the same as a single finality bit.
- 03A client team, such as the one maintaining the docs you opened, can ship a different schedule than another client. Agreed behaviour is whatever both implement.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
The Solana white paper describes proof of history and the architecture. The cluster documentation is the operational consensus text: tower votes, forks, and how a leader schedule is supposed to behave.
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 2018 white paper remains the separate study.
What actually moves
The cut
A fork is still possible. Confirmation levels the docs name are not the same as a single finality bit.
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
A client team, such as the one maintaining the docs you opened, can ship a different schedule than another client. Agreed behaviour is whatever both implement.
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
Firedancer or another client is not this page unless the page says so.
05 Register
What has to be true
Model · Not re-measured
You are reading the Anza validator documentation. The white paper is the other study.
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
Firedancer or another client is not this page unless the page says so.
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
Proof of history in the paper is not a warranty that a given client implements the paper. The client docs are the closer text.
What the design proposes
- A leader schedule assigns slots. Tower BFT is the vote lockout rule the docs describe. They are different mechanisms that the white paper compresses.
- A fork is still possible. Confirmation levels the docs name are not the same as a single finality bit.
- A client team, such as the one maintaining the docs you opened, can ship a different schedule than another client. Agreed behaviour is whatever both implement.
How the mechanism is specified
- A leader schedule assigns slots. Tower BFT is the vote lockout rule the docs describe. They are different mechanisms that the white paper compresses.
- A fork is still possible. Confirmation levels the docs name are not the same as a single finality bit.
- A client team, such as the one maintaining the docs you opened, can ship a different schedule than another client. Agreed behaviour is whatever both implement.
What this page does not treat as proven
- This note does not quote a slot time as a promise.
- The 2018 white paper remains the separate study.
- Firedancer or another client is not this page unless the page says so.
09 Lexicon
Terms, opened into the record
- Tower
- The vote lockout rule. It is not proof of history.
- Leader schedule
- The assignment of slots to block producers. It is not the vote rule.
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.