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.
The five-minute read
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.
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.
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.
Where the claim stops
This is a design note, not a security proof.
One action, walked through
- Post blobs or blocks to the data layer.
- Rollup nodes download them and execute.
- Light nodes of the data layer check availability, not the rollup's rules.
- Who executes the transactions?
The argument, unpacked
Why it is still on the desk
A project that says 'secured by Celestia' may only mean 'the bytes were published'. Ask who executes and who can fork.
After the text
The note shaped how modular chains are sold. The data layer's own fraud proofs are a different paper.
What has to be true
- This is a design note, not a security proof.
- Sovereign means the rollup can fork without the data layer's permission. It also means Ethereum does not defend it.
- Do not call it an Ethereum rollup.
What happened after the paper
The note shaped how modular chains are sold. The data layer's own fraud proofs are a different paper.
What to check before you use the idea
- Who executes the transactions?
- Can the rollup fork without a contract on Ethereum?
- What does a light node of the data layer actually verify?
Terms
- 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.
The problem the paper 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
- Post blobs or blocks to the data layer.
- Rollup nodes download them and execute.
- Light nodes of the data layer check availability, not the rollup's rules.
What this page does not treat as proven
- This is a design note, not a security proof.
- Sovereign means the rollup can fork without the data layer's permission. It also means Ethereum does not defend it.
- Do not call it an Ethereum rollup.
Why a venture studio still reads it
A project that says 'secured by Celestia' may only mean 'the bytes were published'. Ask who executes and who can fork.
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.