Ethereum Blob Storage: How Ethereum Blobs Work

Last updated: November 7, 2026

Ethereum blob storage lets rollups publish transaction data to Ethereum without making that data part of normal smart contract execution. The data is available for a limited period, while a cryptographic commitment lets the network check that it matches what the rollup claims.

That distinction matters: blobs help rollups make data available, but they are not permanent archives. Here’s how blobs work, what changed with PeerDAS, and what their limits mean for users.

How Ethereum blobs work

EIP-4844 introduced type-3 transactions that carry blobs. A blob contains 4,096 field elements of 32 bytes each, or 131,072 bytes (128 KiB). The blob itself is not readable by the Ethereum Virtual Machine (EVM). Instead, the transaction exposes a cryptographic commitment that a contract can access.

A rollup batches activity away from Ethereum’s main execution layer, then posts data needed to check its transactions. In this process, it submits blob data and a KZG commitment. According to Ethereum.org’s danksharding documentation, the commitment allows the posted data to be checked against the rollup’s claim, even though the content remains outside normal EVM execution.

Think of the commitment as a compact way to check the posted data against a particular claim, not as a copy of the data itself. Ethereum transactions and fees work differently at the execution layer, where nodes process transactions and contracts. Rollup data in a blob is published for availability, rather than executed as ordinary contract instructions. See the EIP-4844 specification for details about blob-carrying transactions.

What happens to blob data?

Ethereum does not keep blob contents forever on its nodes. Ethereum.org says blob data is automatically pruned after 4,096 epochs, approximately 18 days. Rollups need the data to remain available long enough for provers to check it or challenge posted transaction data, not as a permanent onchain archive.

That makes the term “storage” slightly misleading. Blobs provide temporary data availability: the network helps users and rollup systems access the data during the relevant period, but the design does not promise indefinite retrieval. Applications that need long-term records must use another storage arrangement.

How blob fees and capacity work

Blob gas has its own fee market, separate from ordinary execution gas, according to EIP-4844. This means blob space and standard Ethereum transactions use separate fee mechanisms. The Ethereum Foundation’s original EIP-4844 parameters targeted three blobs per block, with a maximum of six; those parameters have since changed.

As of January 20, 2026, the Ethereum Foundation reported that the BPO2 update raised the target to 14 blobs per block and the maximum to 21. The Foundation described that as a 2.3-fold increase in Layer 2 data space compared with before Fusaka. These are protocol capacity settings, not a promise that a particular rollup’s fees will fall by a fixed amount.

Ethereum.org’s resources dashboard displayed 24.9 million total blobs and a $0.42 average blob fee when retrieved on November 7, 2026. Those are live dashboard readings, not stable rates. Actual costs can change as demand and network parameters change.

What PeerDAS changes

Fusaka activated on Ethereum mainnet on December 3, 2025, bringing PeerDAS, according to Ethereum.org. PeerDAS uses erasure coding and sampling so nodes can check blob-data availability without downloading every blob in full. This changes how nodes verify availability; it does not make blob data permanent.

EIP-7594 says a node can reconstruct the full data matrix after obtaining at least 50% of its columns. Under the current parameters described in the EIP, a node downloads about one-eighth of total blob data for a local availability check. Sampling reduces the amount each node needs to download for that check.

Pros and cons of blobs

Blobs address one part of scaling: the cost and handling of rollup data. They do not ensure that every app is safe or that all data will remain easy to retrieve after the availability window. Users still face smart contract, bridge, exchange, volatility, and scam risks.

Who uses blob data?

Blob data is mainly a protocol tool for Ethereum rollups and the nodes that check whether their posted data is available. For users, it helps explain how rollups publish the information needed to check batches and why their fees can differ from mainnet transaction fees.

It is not a personal file-storage service or a permanent record archive. Nor does seeing blob data mean a user can read it through an ordinary smart contract call. People relying on a rollup should understand that data availability, transaction execution, and the security of the rollup’s contracts are related but distinct issues.

Bottom line

Ethereum blob storage gives rollups a dedicated, temporary place to publish data, backed by cryptographic commitments and a separate fee market. Since Fusaka, PeerDAS lets nodes sample that data to check availability without downloading every blob in full. The key limit remains: blobs are pruned after about 18 days, so “available on Ethereum” does not mean “stored forever.”

Sources

• EIP-4844: Shard Blob Transactions (eips.ethereum.org)
• Ethereum price and market data (CoinGecko)
• Ethereum devs won’t fork Glamsterdam on Hoodi until smart contract risks resolved (Cointelegraph)

This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrencies are highly volatile; always do your own research before investing.