Shard Blob Transactions

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.

1. Claim 01 · Paper model

   Two resources

   Execution gas and blob gas are different. A cheap blob market does not make execution cheap, and a full blob market does not mean the EVM is congested.

2. Claim 02 · Paper model

   Commitment, not body

   Contracts cannot read blob bytes. They can see that a commitment was published. A design that needs the bytes on-chain forever has not got what the EIP provides.

3. Claim 03 · Paper model

   A window, then gone

   The protocol's job is to make the blobs available long enough for interested parties to fetch them. After that, Ethereum does not promise a copy.

4. Claim 04 · Paper model

   KZG is the check

   The commitment scheme lets a node test that the blob matches. It is the same polynomial commitment discussed in the KZG paper, used here as plumbing.

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.

1. 01 Two resources

   Observation

   What the study says

   Execution gas and blob gas are different. A cheap blob market does not make execution cheap, and a full blob market does not mean the EVM is congested.

   Model

   What has to hold

   The blob fee market is independent. Quoting an execution fee as the blob price is a mistake.

   Falsifier

   What would retire it

   Does the contract read the blob, or only a commitment?

2. 02 Commitment, not body

   Observation

   What the study says

   Contracts cannot read blob bytes. They can see that a commitment was published. A design that needs the bytes on-chain forever has not got what the EIP provides.

   Model

   What has to hold

   The blob fee market is independent. Quoting an execution fee as the blob price is a mistake.

   Falsifier

   What would retire it

   Does the contract read the blob, or only a commitment?

3. 03 A window, then gone

   Observation

   What the study says

   The protocol's job is to make the blobs available long enough for interested parties to fetch them. After that, Ethereum does not promise a copy.

   Model

   What has to hold

   Enough nodes actually propagate blobs during the window. The EIP specifies the rule. It does not conjure bandwidth.

   Falsifier

   What would retire it

   How long is the retention window in the citation?

4. 04 KZG is the check

   Observation

   What the study says

   The commitment scheme lets a node test that the blob matches. It is the same polynomial commitment discussed in the KZG paper, used here as plumbing.

   Model

   What has to hold

   A later fork can change the target and the window. Cite the fork if you cite the number.

   Falsifier

   What would retire it

   Does the contract read the blob, or only a commitment?

03 Sequence

One action, as an operating tape

1. 01A rollup posts a blob-carrying transaction with a KZG commitment.
2. 02Consensus clients propagate and temporarily store the blob.
3. 03The execution payload records the commitment and burns the blob base fee.
4. 04Anyone who needs the bytes fetches them during the window.
5. 05A validity proof or a fraud proof is a separate object. The blob does not replace it.

04 Load-bearing

The argument, and where a pitch drops it

1. Availability is not validity

   The cut

   A rollup can publish a blob of nonsense and still pay the fee. Whether that blob is a valid state transition is the rollup's proof system, not this EIP.

   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 blob is not a validity proof. An optimistic rollup still has a challenge. A zk rollup still needs a proof.

2. Expiry is a choice

   The cut

   Keeping data for a window is how the EIP stays cheaper than calldata. A product that needs historical blobs is relying on some other archive. That archive is not Ethereum consensus.

   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 blob is not a validity proof. An optimistic rollup still has a challenge. A zk rollup still needs a proof.

05 Register

What has to be true

• Model · Not re-measured

  Enough nodes actually propagate blobs during the window. The EIP specifies the rule. It does not conjure bandwidth.

• Stake and threshold · Not re-measured

  The blob fee market is independent. Quoting an execution fee as the blob price is a mistake.

• Cryptography · Not re-measured

  KZG setup assumptions apply. The EIP does not switch Ethereum to a transparent proof system.

• Model · Not re-measured

  A later fork can change the target and the window. Cite the fork if you cite the number.

06 Divergence

What happened after the paper

Proto-danksharding is this EIP. Full danksharding was the longer roadmap and is not what shipped with 4844. The honest sentence is: blobs added a priced, expiring data lane. It did not add permanent storage or a proof system.

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

1. Kill test 1Does the contract read the blob, or only a commitment?
2. Kill test 2How long is the retention window in the citation?
3. Kill test 3What proves the rollup transition, separately from the blob?
4. Kill test 4Who stores the bytes after expiry?
5. 0 of 4 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

09 Lexicon

Terms, opened into the record

Blob

A large data payload carried by a transaction, stored temporarily by consensus nodes, and not readable as EVM state.

Blob base fee

The separate inclusion price for blob gas, adjusted toward a target number of blobs.

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.

11 Related

The next papers, as theses

• KZG commitments · 2010

  Constant-Size Commitments to Polynomials and Their Applications

  Commit to a polynomial and later open it at a point, in constant size, with a pairing. The commitment is binding if the setup's trapdoor stays secret. Modern data-availability schemes use this as a brick. The paper is older than those schemes.

• Fraud and data availability proofs · 2018

  Fraud and Data Availability Proofs

  Light clients can refuse a block if a fraud proof shows it is invalid, but only if the block's data was actually published. The paper shows how erasure coding and sampling let clients check publication without downloading everything.

• Celestia · 2019

  LazyLedger: A Distributed Data Availability Ledger With Client-Side Smart Contracts

  Al-Bassam's LazyLedger paper, the research origin of Celestia. The base layer orders and makes data available. It does not execute application transitions. Clients check availability with sampling, and applications execute on their own.