LibraryScaling2023Design paperCorpus record
Celestia: data-availability sampling as a deployed network
Celestia. Celestia Labs.
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
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
The paper and the network are different texts. Sampling in production has parameters the paper does not freeze.
Claim 02 · Paper model
The proposal
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
Claim 03 · Paper model
The mechanism
Light nodes sample shares. They do not download every byte. That is the availability claim, and it fails if they do not actually sample.
Claim 04 · Paper model
The bound
This note does not quote a blob size or a sampling security number.
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
The paper and the network are different texts. Sampling in production has parameters the paper does not freeze.
Model
What has to hold
You are reading Celestia's docs. The LazyLedger paper is the separate study already in this library.
Falsifier
What would retire it
Who must sample, and what do they sample?
02 The proposal
Observation
What the study says
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
Model
What has to hold
You are reading Celestia's docs. The LazyLedger paper is the separate study already in this library.
03 The mechanism
Observation
What the study says
Light nodes sample shares. They do not download every byte. That is the availability claim, and it fails if they do not actually sample.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
Who must sample, and what do they sample?
04 The bound
Observation
What the study says
This note does not quote a blob size or a sampling security number.
Model
What has to hold
You are reading Celestia's docs. The LazyLedger paper is the separate study already in this library.
Falsifier
What would retire it
Who must sample, and what do they sample?
03 Sequence
One action, as an operating tape
- 01Light nodes sample shares. They do not download every byte. That is the availability claim, and it fails if they do not actually sample.
- 02A rollup that posts to Celestia and settles proofs elsewhere has split availability from settlement. Both links have to be named.
- 03Namespaced data is how one rollup avoids downloading another's bytes. The namespace is part of the design, not a folder metaphor.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
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
LazyLedger remains the research paper. This is the network documentation.
What actually moves
The cut
A rollup that posts to Celestia and settles proofs elsewhere has split availability from settlement. Both links have to be named.
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
Availability of bytes is not execution correctness.
What a later deployment may change
The cut
Namespaced data is how one rollup avoids downloading another's bytes. The namespace is part of the design, not a folder metaphor.
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
Availability of bytes is not execution correctness.
05 Register
What has to be true
Model · Not re-measured
You are reading Celestia's docs. The LazyLedger paper is the separate study already in this library.
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
Availability of bytes is not execution correctness.
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
The paper and the network are different texts. Sampling in production has parameters the paper does not freeze.
What the design proposes
- Light nodes sample shares. They do not download every byte. That is the availability claim, and it fails if they do not actually sample.
- A rollup that posts to Celestia and settles proofs elsewhere has split availability from settlement. Both links have to be named.
- Namespaced data is how one rollup avoids downloading another's bytes. The namespace is part of the design, not a folder metaphor.
How the mechanism is specified
- Light nodes sample shares. They do not download every byte. That is the availability claim, and it fails if they do not actually sample.
- A rollup that posts to Celestia and settles proofs elsewhere has split availability from settlement. Both links have to be named.
- Namespaced data is how one rollup avoids downloading another's bytes. The namespace is part of the design, not a folder metaphor.
What this page does not treat as proven
- This note does not quote a blob size or a sampling security number.
- LazyLedger remains the research paper. This is the network documentation.
- Availability of bytes is not execution correctness.
Why the desk still reads it
Celestia's docs describe a network that samples data availability, the idea in the LazyLedger paper, as an operational chain rather than only as a 2019 construction.
09 Lexicon
Terms, opened into the record
- Data-availability sampling
- Checking random shares instead of downloading the whole block. It has a security assumption the docs must state.
- Namespace
- A partition of the block's data so a rollup can fetch its own shares.
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.
Papers
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.