LibraryScaling2017Design paperCorpus record
Plasma: Scalable Autonomous Smart Contracts
Plasma. Joseph Poon and Vitalik Buterin.
A 2017 construction for trees of child chains whose state commitments are posted to a parent chain, with exits so a user can leave if the child operator misbehaves. It is an ancestor of later rollup and validium designs, not a synonym for them.
Plasma proposes child chains that post a commitment to a root chain, and it tries to make exits safe even if the child operator cheats, provided users watch and challenge.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 4
- Records linked
- 5
Code
Source, repository, and what is actually hosted
- plasma.io paperhttps://plasma.io/plasma.pdf
- The source URL is not a GitHub repository. No code remote is invented.
- 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
The child chain is not trusted to keep your money
An operator orders transactions and posts a hash of the result upward. Users are supposed to be able to leave with their funds on the root chain.
Claim 02 · Paper model
Exits are the security mechanism
A withdrawal asks the root chain to pay out after a challenge window. Anyone who can show a later spend, or a withheld state, is supposed to be able to stop a false exit.
Claim 03 · Paper model
Mass exits are the acknowledged disaster drill
If the operator disappears, many users exit at once. The root chain must have room. The paper names this. It does not make it cheap.
Claim 04 · Paper model
Data availability is the crack
A user cannot challenge a state they were never shown. Withholding the data freezes the challenge game. Later rollup designs exist in part because of this crack.
Claim 05 · Paper model
The paper is a framework, not one chain
Minimum Viable Plasma, Cash, and other variants specialise the exit rules. Cite the variant. The 2017 paper is the parent argument.
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 child chain is not trusted to keep your money
Observation
What the study says
An operator orders transactions and posts a hash of the result upward. Users are supposed to be able to leave with their funds on the root chain.
Model
What has to hold
The root contract's challenge rules match the child chain's transaction format.
Falsifier
What would retire it
What happens if the operator publishes a root and withholds the block?
02 Exits are the security mechanism
Observation
What the study says
A withdrawal asks the root chain to pay out after a challenge window. Anyone who can show a later spend, or a withheld state, is supposed to be able to stop a false exit.
Model
What has to hold
The root chain accepts exits within the window even under load. This is an economic assumption, not a cryptographic one.
Falsifier
What would retire it
How long is the challenge window, and who is watching it?
03 Mass exits are the acknowledged disaster drill
Observation
What the study says
If the operator disappears, many users exit at once. The root chain must have room. The paper names this. It does not make it cheap.
Model
What has to hold
The root chain accepts exits within the window even under load. This is an economic assumption, not a cryptographic one.
Falsifier
What would retire it
What happens if the operator publishes a root and withholds the block?
04 Data availability is the crack
Observation
What the study says
A user cannot challenge a state they were never shown. Withholding the data freezes the challenge game. Later rollup designs exist in part because of this crack.
Model
What has to hold
The root contract's challenge rules match the child chain's transaction format.
Falsifier
What would retire it
How long is the challenge window, and who is watching it?
05 The paper is a framework, not one chain
Observation
What the study says
Minimum Viable Plasma, Cash, and other variants specialise the exit rules. Cite the variant. The 2017 paper is the parent argument.
Model
What has to hold
The root contract's challenge rules match the child chain's transaction format.
Falsifier
What would retire it
Can the root chain absorb an exit by every user in the same week?
03 Sequence
One action, as an operating tape
- 01A user deposits on the root chain into a contract that recognises a child-chain operator.
- 02The operator includes the user's transactions in a child block and posts a Merkle root upward.
- 03The user is expected to receive enough data to know their new balance and to build an exit proof.
- 04To leave, the user submits an exit referring to that inclusion. A challenge window opens.
- 05If no valid challenge arrives, the root contract releases the funds. If the operator withholds data, the user is supposed to exit from the last state they do know.
04 Load-bearing
The argument, and where a pitch drops it
Watching is the user's job
The cut
Plasma safety is not 'set and forget'. It is 'notice a bad root, and get an exit in before the window'. A design that cannot notify a phone in time has a different security model from the one the paper proves.
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
Plasma is not an optimistic rollup and not a zk-rollup. Those publish different data and different proofs.
Availability beats clever exits
The cut
The most careful exit priority still fails if the user never saw the block that spent their coin. The paper's limit is structural. Rollups that publish data, or validity proofs that do not need a challenge, are responses to this exact limit.
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
Many Plasma variants were never deployed as specified. The paper is still the right citation for the idea.
The root chain is the scarce resource in a panic
The cut
A mass exit is a crowd trying to post transactions when everyone is afraid. Fees rise. The paper's guarantee is only as good as the root chain's capacity at the worst moment, which is the moment the guarantee is needed.
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
Many Plasma variants were never deployed as specified. The paper is still the right citation for the idea.
05 Register
What has to be true
Model · Not re-measured
Users, or someone they trust, watch the roots they were promised.
Model · Not re-measured
The root contract's challenge rules match the child chain's transaction format.
Data · Not re-measured
Data of the user's own outputs is obtainable in normal operation.
Cryptography · Not re-measured
The root chain accepts exits within the window even under load. This is an economic assumption, not a cryptographic one.
06 Divergence
What happened after the paper
Plasma variants were implemented and largely overtaken, in public Ethereum scaling, by optimistic and validity rollups that treat data availability more strictly. The 2017 paper remains the clear statement of exit games and of why withholding data breaks 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 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
A single chain that re-executes every contract call will not hold every application. Plasma's proposal is a child chain that posts a commitment upward, and a parent-chain exit game so users are not trapped when the child operator censors or lies.
What the design proposes
- The parent chain stores commitments, not every child transaction.
- Users must be able to exit to the parent with their assets, given enough data and time.
- Fraud is handled by challenges and withdrawals, not only by proving every transition up front.
How the mechanism is specified
- The operator can withhold data. The paper's response is an exit, which only works if the user has the data they need and watches the chain.
- Mass exits are a congestion event on the parent. The paper does not make that free.
- Map-reduce language in the paper is an analogy for nested chains. It is not an implementation.
What this page does not treat as proven
Why the desk still reads it
Any venture pitching a 'child chain' owes this paper an answer: if the operator disappears tonight, what does a user post on the parent, and do they have the data. If the answer is 'trust the operator', it is not Plasma.
09 Lexicon
Terms, opened into the record
- Child chain
- A chain whose blocks are summarised by a hash posted to a root contract.
- Exit
- A withdrawal on the root chain that pays out after a challenge window.
- Challenge
- A proof that an exit is based on an old or invalid state, submitted during the window.
- Data withholding
- Publishing a root without the block body, so users cannot see or prove what changed.
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.