LibraryScaling2022Design paperCorpus record
Rollups as Sovereign Chains
Sovereign rollups. Celestia Labs.
Publish transaction data to a data-availability layer. Let the rollup's own nodes interpret it. Fraud or validity proofs are checked by those nodes, not by an Ethereum bridge, unless someone adds one.
A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.
A project that says 'secured by Celestia' may only mean 'the bytes were published'. Ask who executes and who can fork.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 6
Code
Source, repository, and what is actually hosted
- Celestia learnhttps://celestia.org/learn/sovereign-rollups/an-introduction/
- 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 defect
A classic rollup settles its state on Ethereum. A chain that only wants cheap data does not have to rent Ethereum's execution.
Claim 02 · Paper model
The rule
Publish transaction data to a data-availability layer. Let the rollup's own nodes interpret it. Fraud or validity proofs are checked by those nodes, not by an Ethereum bridge, unless someone adds one.
Claim 03 · Paper model
How it is put together
Data availability and settlement are separate products. The rollup defines its own fork-choice rule. A bridge back to Ethereum is an extra contract, not a consequence of posting data.
Claim 04 · Paper model
Where the claim stops
This is a design note, not a security proof.
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
02 The rule
Observation
What the study says
Publish transaction data to a data-availability layer. Let the rollup's own nodes interpret it. Fraud or validity proofs are checked by those nodes, not by an Ethereum bridge, unless someone adds one.
03 How it is put together
Observation
What the study says
Data availability and settlement are separate products. The rollup defines its own fork-choice rule. A bridge back to Ethereum is an extra contract, not a consequence of posting data.
04 Where the claim stops
Observation
What the study says
This is a design note, not a security proof.
Model
What has to hold
This is a design note, not a security proof.
Falsifier
What would retire it
Who executes the transactions?
03 Sequence
One action, as an operating tape
04 Load-bearing
The argument, and where a pitch drops it
Why it is still on the desk
The cut
A project that says 'secured by Celestia' may only mean 'the bytes were published'. Ask who executes and who can fork.
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.
After the text
The cut
The note shaped how modular chains are sold. The data layer's own fraud proofs are a different paper.
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
Sovereign means the rollup can fork without the data layer's permission. It also means Ethereum does not defend it.
05 Register
What has to be true
06 Divergence
What happened after the paper
The note shaped how modular chains are sold. The data layer's own fraud proofs are a different paper.
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 classic rollup settles its state on Ethereum. A chain that only wants cheap data does not have to rent Ethereum's execution.
What the design proposes
- Data availability and settlement are separate products.
- The rollup defines its own fork-choice rule.
- A bridge back to Ethereum is an extra contract, not a consequence of posting data.
How the mechanism is specified
What this page does not treat as proven
Why the desk still reads it
A project that says 'secured by Celestia' may only mean 'the bytes were published'. Ask who executes and who can fork.
09 Lexicon
Terms, opened into the record
- Sovereign
- The rollup's nodes, not a parent contract, decide the canonical state.
- Data availability
- Evidence the bytes were published, not that they were valid.
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.