LibraryConsensus2018Design paperCorpus record
EOS.IO Technical White Paper
EOSIO. Daniel Larimer and block.one.
The 2018 technical paper for EOSIO: delegated proof of stake, named block producers, and an operating-system metaphor for accounts, permissions and resource allocation. It is a design document. It is not a description of later governance fights around any one chain that used the software.
This page covers the 2018 technical design only. It is not an account of later block-producer governance.
EOS.IO describes a delegated proof-of-stake chain in which a small elected set of block producers takes turns, users vote with staked tokens, and the software is built around high throughput and named accounts.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 4
- Records linked
- 5
Code
Source, repository, and what is actually hosted
- EOS.IO technical white paperhttps://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md
- EOSIO/DocumentationRepository taken from the source URL. No other study cites this repository. This is not an audit.
- 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
Delegation is the consensus
Token holders vote for block producers. The top producers take turns making blocks. This is a known, small set by design, not an accident of mining pools.
Claim 02 · Paper model
The paper promises seconds, not probabilistic hours
Producers sign a schedule. A block is treated as irreversible after a defined set of later producers have built on it. The speed comes from the size of the set.
Claim 03 · Paper model
Resource models replace the simple fee
The paper discusses staking for CPU, bandwidth and later state, so a user does not attach a gas price to every action. That model is easy to misread as 'free'. It is a different rationing system.
Claim 04 · Paper model
Accounts and permissions are first class
Human-readable accounts, thresholds and keys are part of the platform paper. So is the idea that applications will update themselves under governance. Those are product choices with trust consequences.
Claim 05 · Paper model
The constitution is outside the code and inside the design
The text expects dispute processes and producer agreements. A purely technical reading that ignores the political layer will not understand why producers can pause an account.
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 Delegation is the consensus
Observation
What the study says
Token holders vote for block producers. The top producers take turns making blocks. This is a known, small set by design, not an accident of mining pools.
Model
What has to hold
Token holders vote, and votes are not entirely purchased by the producers being elected.
Falsifier
What would retire it
How many producers sign blocks, and how concentrated is the vote that elected them?
02 The paper promises seconds, not probabilistic hours
Observation
What the study says
Producers sign a schedule. A block is treated as irreversible after a defined set of later producers have built on it. The speed comes from the size of the set.
Model
What has to hold
Token holders vote, and votes are not entirely purchased by the producers being elected.
Falsifier
What would retire it
After how many subsequent producers is a block irreversible in this implementation?
03 Resource models replace the simple fee
Observation
What the study says
The paper discusses staking for CPU, bandwidth and later state, so a user does not attach a gas price to every action. That model is easy to misread as 'free'. It is a different rationing system.
Model
What has to hold
Resource prices or stake requirements are knowable before a user needs to transact.
Falsifier
What would retire it
What must a user hold or rent before an action is included?
04 Accounts and permissions are first class
Observation
What the study says
Human-readable accounts, thresholds and keys are part of the platform paper. So is the idea that applications will update themselves under governance. Those are product choices with trust consequences.
Model
What has to hold
Resource prices or stake requirements are knowable before a user needs to transact.
Falsifier
What would retire it
Which authority can freeze an account, and is that authority in the paper's constitution, the code, or both?
05 The constitution is outside the code and inside the design
Observation
What the study says
The text expects dispute processes and producer agreements. A purely technical reading that ignores the political layer will not understand why producers can pause an account.
Model
What has to hold
The active producer set stays online in rotation. One absent producer is a skipped slot. Many absent producers are a halt.
Falsifier
What would retire it
Which authority can freeze an account, and is that authority in the paper's constitution, the code, or both?
03 Sequence
One action, as an operating tape
- 01Holders stake tokens and cast votes for producer candidates.
- 02The protocol ranks producers. The active schedule of the top set is what signs blocks.
- 03Each producer in the schedule has a slot. They broadcast a block, and the next producer builds on it.
- 04After enough subsequent producers have acknowledged a block, it is treated as irreversible under the paper's rule.
- 05A user action declares which account permission signed it. Resource billing is checked against the stake or the market the implementation uses.
04 Load-bearing
The argument, and where a pitch drops it
Twenty-one names is a governance fact
The cut
A set that small can coordinate. That is why blocks are fast. It is also why capture, collusion or a court order aimed at the set is a different event from capturing a million anonymous miners. The paper chooses the small set with open eyes. Reviews should too.
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 small producer set is easy to name and easy to pressure. The paper does not remove that.
Voting markets were predictable
The cut
Vote-for-producer with a reward for the voter creates a market for votes. The paper's incentive sketch does not fully prevent producers from paying for the rank they then hold. Later history of vote buying is relevant as a check on the incentive section, not as a surprise.
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
Later events on EOS public networks — governance, resource markets, block-producer politics — are outside the 2018 text.
'Feeless' rationing still excludes
The cut
If CPU is full, a user without stake waits or rents. The pain is real even though no gas token moved in the transaction. A study should describe the rationing, not repeat the slogan.
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
We do not describe the original token sale. The historic ICO notes on this site are a separate archive.
05 Register
What has to be true
Model · Not re-measured
Token holders vote, and votes are not entirely purchased by the producers being elected.
Network · Not re-measured
The active producer set stays online in rotation. One absent producer is a skipped slot. Many absent producers are a halt.
Model · Not re-measured
Users understand which permission signed. Account recovery and multisig only help if they are configured.
Stake and threshold · Not re-measured
Resource prices or stake requirements are knowable before a user needs to transact.
06 Divergence
What happened after the paper
EOS launched from this paper, saw concentrated producer votes, resource crunches, and later changes including to its resource model and governance. The 2018 paper is the delegated-producer design. It should be read with that record, not as a promise the record automatically fulfilled.
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 4 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
General-purpose chains that bill every action through a volatile fee market are hard to use as an application host. EOSIO's paper proposes named producers and explicit allocations of CPU, network and state, so an application can reason about resources.
What the design proposes
- Token holders vote for block producers. A small active set produces blocks in a schedule.
- Accounts have permission hierarchies, rather than a single key that can do everything.
- Resources are framed as staking for capacity. That is a product choice with its own failure modes.
How the mechanism is specified
- BFT-style finality among the active producers is the confirmation story, under the assumption that they do not collude past the threshold.
- The paper's 'operating system' language means accounts, permissions and inter-process messages. It does not mean a desktop OS.
- Delegation concentrates power by design. The paper treats voter oversight as the check.
What this page does not treat as proven
- Later events on EOS public networks — governance, resource markets, block-producer politics — are outside the 2018 text.
- A small producer set is easy to name and easy to pressure. The paper does not remove that.
- We do not describe the original token sale. The historic ICO notes on this site are a separate archive.
Why the desk still reads it
Read EOSIO when a venture wants 'no user fees' and a permission system that looks like an organisation chart. Then ask who the producers are, how they are removed, and what happens to state when the stake that bought capacity is gone.
09 Lexicon
Terms, opened into the record
- Block producer
- An elected operator scheduled to produce blocks. The active set is small on purpose.
- Delegated proof of stake
- A system in which token voting appoints the producers, rather than each holder producing with their own weight.
- Irreversible block
- A block the schedule has acknowledged deeply enough that the protocol tells applications to stop expecting a reversal.
- Resource stake
- Tokens committed so an account may use CPU, bandwidth or state. It is a ration, not a tip.
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.