LibraryStorage and networks2024Design paperCorpus record
Walrus: blob storage with a committee, published beside Sui
Walrus. Mysten Labs.
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
- 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
A certificate on Sui is not the blob. Availability is the committee's property. The certificate is a claim about that committee.
Claim 02 · Paper model
The proposal
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
Claim 03 · Paper model
The mechanism
A blob is erasure-coded across storage nodes. A certificate says enough of them acknowledged it.
Claim 04 · Paper model
The bound
This note states no blob size and no node count.
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 certificate on Sui is not the blob. Availability is the committee's property. The certificate is a claim about that committee.
Falsifier
What would retire it
What does the certificate prove: acknowledgements, retrievability, or both?
02 The proposal
Observation
What the study says
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
Falsifier
What would retire it
What does the certificate prove: acknowledgements, retrievability, or both?
03 The mechanism
Observation
What the study says
A blob is erasure-coded across storage nodes. A certificate says enough of them acknowledged it.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What do storage nodes lose if they drop shards, according to the docs?
04 The bound
Observation
What the study says
This note states no blob size and no node count.
Falsifier
What would retire it
What does the certificate prove: acknowledgements, retrievability, or both?
03 Sequence
One action, as an operating tape
- 01A blob is erasure-coded across storage nodes. A certificate says enough of them acknowledged it.
- 02Retrieval is a separate act from certification. A user who cannot fetch the blob does not have the file, whatever the certificate says.
- 03The committee's economic penalty for losing shards is the security assumption. If the docs do not specify a penalty, do not invent one.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
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
Walrus is not Filecoin's replication proof and not Celestia's sampling, unless the page you opened actually says it is.
What actually moves
The cut
Retrieval is a separate act from certification. A user who cannot fetch the blob does not have the file, whatever the certificate says.
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
Sui consensus finalises the certificate. It does not store the blob.
What a later deployment may change
The cut
The committee's economic penalty for losing shards is the security assumption. If the docs do not specify a penalty, do not invent one.
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.
05 Register
What has to be true
Model · Not re-measured
You are reading the Walrus docs. The blob is not on Sui.
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
Sui consensus finalises the certificate. It does not store the blob.
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 certificate on Sui is not the blob. Availability is the committee's property. The certificate is a claim about that committee.
What the design proposes
- A blob is erasure-coded across storage nodes. A certificate says enough of them acknowledged it.
- Retrieval is a separate act from certification. A user who cannot fetch the blob does not have the file, whatever the certificate says.
- The committee's economic penalty for losing shards is the security assumption. If the docs do not specify a penalty, do not invent one.
How the mechanism is specified
- A blob is erasure-coded across storage nodes. A certificate says enough of them acknowledged it.
- Retrieval is a separate act from certification. A user who cannot fetch the blob does not have the file, whatever the certificate says.
- The committee's economic penalty for losing shards is the security assumption. If the docs do not specify a penalty, do not invent one.
What this page does not treat as proven
Why the desk still reads it
Walrus publishes blob storage where a committee encodes and holds blobs, and Sui records the availability certificate rather than the blob.
09 Lexicon
Terms, opened into the record
- Availability certificate
- An on-chain object that records a committee's acknowledgement of a blob.
- Erasure coding
- Splitting a blob so a subset of shards can rebuild it. The subset size is a parameter.
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.