LibraryScaling2023Design paperCorpus record
Avail: data availability with validity proofs of the data commitment
Avail DA. Avail.
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 7
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 validity proof of a data commitment proves the commitment was built correctly. It does not prove a rollup's execution.
Claim 02 · Paper model
The proposal
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
Claim 03 · Paper model
The mechanism
Block producers order data. A proof relates the commitment to that data. Sampling or reconstruction is how a client gets the bytes.
Claim 04 · Paper model
The bound
No throughput figure is stated here.
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
A validity proof of a data commitment proves the commitment was built correctly. It does not prove a rollup's execution.
Falsifier
What would retire it
What does the validity proof claim: encoding, availability, or execution?
02 The proposal
Observation
What the study says
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
Falsifier
What would retire it
What does the validity proof claim: encoding, availability, or execution?
03 The mechanism
Observation
What the study says
Block producers order data. A proof relates the commitment to that data. Sampling or reconstruction is how a client gets the bytes.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What does the validity proof claim: encoding, availability, or execution?
04 The bound
Observation
What the study says
No throughput figure is stated here.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What does the validity proof claim: encoding, availability, or execution?
03 Sequence
One action, as an operating tape
- 01Block producers order data. A proof relates the commitment to that data. Sampling or reconstruction is how a client gets the bytes.
- 02A rollup using Avail still needs an execution proof or a fraud proof somewhere else if it wants execution correctness.
- 03The validator set that orders the data is a consensus assumption. The proof does not remove it.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
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 proof that data was encoded is not a proof that the encoded transactions are valid.
What actually moves
The cut
A rollup using Avail still needs an execution proof or a fraud proof somewhere else if it wants execution correctness.
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 proof that data was encoded is not a proof that the encoded transactions are valid.
What a later deployment may change
The cut
The validator set that orders the data is a consensus assumption. The proof does not remove it.
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 proof that data was encoded is not a proof that the encoded transactions are valid.
05 Register
What has to be true
Model · Not re-measured
You are reading Avail's documentation, not a rollup's bridge contract.
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
A proof that data was encoded is not a proof that the encoded transactions are valid.
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 validity proof of a data commitment proves the commitment was built correctly. It does not prove a rollup's execution.
What the design proposes
- Block producers order data. A proof relates the commitment to that data. Sampling or reconstruction is how a client gets the bytes.
- A rollup using Avail still needs an execution proof or a fraud proof somewhere else if it wants execution correctness.
- The validator set that orders the data is a consensus assumption. The proof does not remove it.
How the mechanism is specified
- Block producers order data. A proof relates the commitment to that data. Sampling or reconstruction is how a client gets the bytes.
- A rollup using Avail still needs an execution proof or a fraud proof somewhere else if it wants execution correctness.
- The validator set that orders the data is a consensus assumption. The proof does not remove it.
What this page does not treat as proven
Why the desk still reads it
Avail publishes a data-availability chain whose commitment a client can check with a validity proof, so the client is not only trusting a committee's signature that the data exists.
09 Lexicon
Terms, opened into the record
- Data commitment
- A compact binding to the bytes. It is not the bytes.
- Validity proof of encoding
- A proof the commitment matches a coded block. It is not a rollup state proof.
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.