In this track: Scaling and layer 2
intermediate · 3 MIN READ

Blob data in plain language

A separate data channel supports scaling use cases with specific access and retention rules.

LET’S PICTURE IT

A service can add a special cargo compartment without putting all its contents into the driver’s ordinary notebook.

SEE IT FOR YOURSELF
Link blocks, then see what an edit breaksStep 1 / 4
Link blocks, then see what an edit breaksBLOCK 1Maya → Leo: 3Fingerprint A1A classroom model, not a live blockchainBLOCK 1Fingerprint A1BLOCK 2Parent A1Fingerprint B2The direction shows a relationship, not a transfer of ownershipBLOCK 1Hash A1BLOCK 2Parent A1Hash B2BLOCK 3Parent B2Hash C3Independent validation and consensus are additional requirementsEDITED BLOCK 1Maya → Leo: 9Hash X9BLOCK 2Parent A1 ≠ X9Invalid parentBLOCK 3Ancestor link invalidRevalidation neededRecalculating toy hashes does not rewrite Ethereum consensus

The first toy block records Maya sending Leo three units. A1 is an illustrative fingerprint label, not a real cryptographic digest.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

A distinct resource

Blob-carrying transactions attach data under the protocol’s blob mechanism. Execution handles commitments and specified operations, while the full blob is not ordinary calldata readable directly by arbitrary EVM code.

Rollups can use the data channel

Publishing compressed transaction information through this mechanism can serve rollup data needs. Allocation and fee accounting belong to the specific protocol and rollup design.

Retention is not endless by definition

Protocol availability requirements and long-term archival services answer different questions. A system needing historical data beyond the protocol window must consider how it remains retrievable.

One gas calculator is not every fee

Blob gas uses a separate pricing dimension from ordinary execution. Our manual tool explicitly calculates execution-fee inputs only and does not pretend to quote live blob costs.

QUICK CHECK · NO PRESSURE

Can arbitrary contract code read the entire blob exactly as if it were ordinary calldata?

Your progress stays in this browser.
Keep exploring the original referenceEthereum Improvement Proposals ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.