Encyclopedia Ethereum · Entry 22
Ethereum blobs and data availability
In this article
At a glance
Key facts
Other people need the inputs, not just a claimed result
A rollup can announce a new state commitment, but a commitment is only a compact reference to data. Independent participants need the relevant data to reconstruct balances and execution, challenge incorrect results where applicable, and prepare operations such as withdrawals.
Data availability asks whether that data can be obtained when the network accepts the result. It differs from execution validity, which asks whether the state transition follows the rules. A system needs an explanation for both questions.
Blob data travels beside execution
EIP-4844 introduced a transaction type that refers to blobs through cryptographic commitments. The execution layer processes the transaction while the blob data is handled separately. The EVM has access to a versioned hash reference, not an instruction that reads arbitrary bytes from the blob.
This separation lets Ethereum price and handle data publication differently from ordinary execution. A rollup can use that publication channel while its own software interprets the data. A blob is not a smart contract, a new account or a general promise to host a file forever.
Example: sharing a publication cost across a batch
Suppose a hypothetical rollup spends 0.001 ETH publishing data for a batch containing 100 equally sized actions. Dividing that one cost equally gives 0.00001 ETH per action. This illustrates how batching can spread a shared publication expense.
It is not a fee quote. Real batches contain different data sizes, compression varies, blob demand changes, and users also pay for execution and other protocol costs. A rollup’s pricing policy decides how those expenses appear in the user’s final fee.
Availability and long-term retrieval are different services
The protocol has a bounded obligation to serve blob data rather than a promise that every node retains it permanently. Historical reconstruction beyond that availability window requires retained copies or archival services. A hash proves which data was committed; it cannot regenerate missing bytes.
Blob capacity, pricing parameters and distribution mechanisms can change with network upgrades. This entry describes the mechanism and deliberately does not present the original EIP’s capacity constants as current limits. For a live operational limit, identify the active fork and client specification.
Direct answers
Questions people ask
Can a smart contract read all the bytes in a blob?
Not directly through normal EVM execution. EIP-4844 exposes references and a verification mechanism, while blob contents are handled outside the execution data available to contracts.
Does availability mean the data is stored forever?
No. Availability at acceptance and permanent archival retrieval are separate guarantees. Older blob data requires retained copies.
Do blobs make every rollup transaction cheap?
No. They provide a separate data publication channel. Demand, batch usage, execution costs and the rollup’s fee policy still affect what a user pays.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Blobs are a way to publish data alongside Ethereum transactions, designed for uses such as rollups. Their data is handled separately from EVM execution and has a separate fee market. Availability lets others obtain and check the data; it is not a promise of permanent storage.
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimPurpose: Publish data needed by systems such as rollups
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimExecution: EVM execution can reference blob commitments but cannot read arbitrary blob contents directly
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimCost: Blob gas has a fee market distinct from execution gas
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- EIP-4844: Shard Blob TransactionsEthereum Improvement Proposals
Defines blob commitments, separately priced blob gas and time-limited data serving; original capacity constants are not treated as current limits.
Locator: Abstract; gas accounting; consensus-layer validation; rationale · Version / scope: ac912ca6a9685590345dd8e5736cda75976d0131 · Retrieved: 2026-10-02T14:35:51.590523+00:00Open source - Data availabilityethereum.org contributors
Supports why a hash is not sufficient to reconstruct data and why availability differs from permanent historical storage.
Locator: Data availability problem; rollups; availability versus retrievability · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.112785+00:00Open source - Zero-knowledge rollupsethereum.org contributors
Supports validity proofs and public rollup data; no claim that every withdrawal is instant or that every ZK system is private.
Locator: Data availability; validity proofs; withdrawals; EVM compatibility · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.579728+00:00Open source - Optimistic rollupsethereum.org contributors
Supports challenge periods, dispute verification, sequencer ordering and withdrawal distinctions; concrete timings depend on the implementation.
Locator: Fraud proving; censorship resistance; exiting the rollup · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.579696+00:00Open source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Ethereum blobs and data availability.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-blobs-data-availability/