Understanding EIP-4844 Blob Storage on Ethereum

Ethereum's growth has brought significant demand for block space, leading to network congestion and high transaction costs. Layer-2 networks, particularly Optimistic and Zero-Knowledge rollups, emerged to alleviate this pressure by processing transactions offchain and settling them on the mainnet. However, these rollups still faced substantial costs when posting transaction data back to the base layer. EIP-4844 blob storage was introduced to solve this bottleneck. By creating a dedicated space for temporary transaction data, this upgrade drastically lowers the cost of operating rollups. This article explores the mechanics of EIP-4844 blob storage, its benefits and limitations, and how it prepares the Ethereum network for long-term scalability.

What Is Blob Storage (EIP-4844)?

EIP-4844, widely known as Proto-Danksharding, is a major network upgrade designed to improve the scalability of the Ethereum blockchain. The core feature of this proposal is the introduction of a new transaction type that accepts "blobs" of data. A blob stands for Binary Large Object, which is a standard computer science term for a collection of binary data stored as a single entity.

In the context of Ethereum, a blob is a temporary data payload attached to a transaction. Before EIP-4844, layer-2 networks had to store their rolled-up transaction data permanently on the Ethereum mainnet using standard transaction data fields. This permanent storage was highly expensive and consumed valuable block space. EIP-4844 changes this architecture by allowing rollups to post data in blobs instead.

These blobs are processed differently from standard transaction data. They are cryptographically committed to the blockchain, meaning their existence and integrity can be verified by the network, but the actual data inside the blob is not accessible to the Ethereum Virtual Machine (EVM). Because the EVM doesn't need to execute or permanently store this data, the cost of processing a blob is significantly lower than standard data storage. Proto-Danksharding represents an intermediate step in the Ethereum scaling roadmap, providing immediate relief for layer-2 networks while establishing the necessary cryptographic and structural foundation for future, more extensive sharding implementations.

Why Ethereum Needs EIP-4844

The primary driver behind the implementation of EIP-4844 blob storage is the need to reduce transaction fees across the Ethereum environment. As decentralized finance (DeFi) and other blockchain applications gained traction, the demand for Ethereum block space outpaced its processing capacity. Layer-2 rollups were developed to scale the network by bundling thousands of transactions offchain and submitting a compressed summary to the mainnet.

Despite this efficiency, rollups previously relied on a mechanism called calldata to post their transaction summaries to Ethereum. Calldata is processed by all network nodes and stored permanently on the blockchain. Because permanent storage on a distributed ledger is inherently resource-intensive, the cost of posting calldata remained the largest expense for layer-2 operators. These costs were inevitably passed down to end users. This made microtransactions and high-frequency onchain interactions economically unviable during periods of network congestion.

Ethereum required an intermediate scaling solution to support continued network growth without compromising decentralization or security. Relying solely on continuous hardware upgrades for node operators would lead to centralization, as fewer participants could afford to run the necessary infrastructure. EIP-4844 addresses this by decoupling data availability from execution. By giving rollups a dedicated, cost-effective way to post their data, the network can accommodate a much higher volume of transactions. This structural change ensures that Ethereum can remain the base settlement layer for an expanding network of interconnected layer-2 networks.

How Blob Storage Works

EIP-4844 introduces a new transaction format known as a blob-carrying transaction. When a layer-2 rollup submits a batch of transactions to the Ethereum mainnet, it now attaches the transaction data as a blob rather than embedding it directly into the smart contract execution data.

Once a blob-carrying transaction is broadcast, the blob data is downloaded and verified by Ethereum consensus nodes. To prevent the blockchain from growing to an unmanageable size, blob data is strictly temporary. The network retains this data for approximately 18 days. This retention period is long enough to ensure that network participants, specifically those monitoring Optimistic rollups, have ample time to download the data, verify the state transitions, and submit fraud proofs if necessary. After the 18-day window expires, the blob data is automatically deleted from the consensus nodes.

To manage the pricing of this new storage mechanism, EIP-4844 implements a separate fee market specifically for blob gas. Standard Ethereum transactions use regular gas, which fluctuates based on the demand for computational resources and permanent storage. Blob gas operates on its own supply and demand curve. If the demand for standard block space spikes, the cost of blob storage remains unaffected unless the demand for blob space also increases simultaneously. This separation ensures that layer-2 networks can continue to post large batches of data predictably and affordably, insulated from the volatility of mainnet execution gas fees.

EIP-4844 vs. Full Danksharding

While EIP-4844 provides immediate scaling benefits, it is technically a precursor to a much larger architectural upgrade known as full Danksharding. Understanding the distinction between these two phases is essential for grasping the long-term Ethereum roadmap.

Proto-Danksharding implements the basic transaction types, cryptographic commitments, and independent fee markets required for blob storage. However, it doesn't actually partition or shard the Ethereum network. Under EIP-4844, every consensus node must still download and verify all blob data. The number of blobs per block is capped at a relatively low limit to ensure that standard consumer hardware can still process the network state without being overwhelmed by massive data requirements.

Full Danksharding will expand upon this foundation by introducing data availability sampling. In the final Danksharding implementation, nodes will no longer need to download entire blobs to verify them. Instead, they will use advanced cryptographic techniques to sample small random portions of the data. If multiple nodes successfully sample different pieces, the network can probabilistically confirm that the entire blob is available. This sampling mechanism will allow the network to increase the number of blobs per block drastically, expanding data throughput from megabytes to potentially gigabytes per second. EIP-4844 lays the necessary groundwork today. This ensures that when data availability sampling is ready, the transaction formats and fee structures are already battle-tested and operational.

Benefits of Blob Storage

The most immediate and measurable benefit of EIP-4844 blob storage is the drastic reduction in transaction fees for layer-2 networks. Before this upgrade, posting data to the Ethereum mainnet accounted for the vast majority of operational costs for both Optimistic and Zero-Knowledge rollups. By transitioning from permanent calldata to temporary blob storage, these networks experience significantly lower overhead. This cost reduction translates directly to the end user, with layer-2 transaction fees dropping by orders of magnitude.

Lower fees enable new possibilities for decentralized applications that require high throughput and frequent state updates. Use cases that were previously restricted by gas costs, such as high-frequency trading, decentralized gaming, and complex social protocols, become economically feasible. Users can interact with smart contracts more frequently without spending excessive amounts on gas, which fundamentally improves the user experience across the Web3 economy. 

Additionally, EIP-4844 increases the overall data throughput of the Ethereum network. By moving rollup data out of the main execution layer and into a parallel data availability layer, valuable block space is freed up for standard mainnet transactions. This structural efficiency helps stabilize gas prices on the base layer during periods of high demand. Blob storage enables Ethereum to scale horizontally, supporting a growing multitude of interconnected layer-2 networks while maintaining the security guarantees of the underlying mainnet.

Challenges and Limitations

Despite its significant advantages, EIP-4844 blob storage introduces new structural challenges to the Ethereum network. One primary concern involves the increased hardware and bandwidth requirements for node operators. Although blob data is temporary, consensus nodes must still download, process, and propagate large files across the network in real time. This requirement demands higher internet bandwidth and stronger storage capabilities, which could marginally increase the barrier to entry for individuals running independent nodes.

The temporary nature of blob data also creates a new dynamic for historical data availability. Because the Ethereum protocol automatically deletes blobs after approximately 18 days, the base layer no longer serves as a permanent archive for all layer-2 transaction histories. While this is necessary to keep node requirements manageable, it shifts the responsibility of long-term data preservation to external actors.

Block explorers, indexing services, and specialized archival nodes must now step in to store and serve historical blob data for users and developers who need to audit past transactions. If a user needs to reconstruct the complete history of a rollup from genesis, they must rely on these third-party archives rather than querying the Ethereum mainnet directly. Ensuring that these external storage providers remain reliable and decentralized is an ongoing challenge, as the network adapts to a model where the base layer guarantees only short-term data availability rather than permanent historical records.

The Role of Chainlink in a Scaled Ethereum Environment

As EIP-4844 blob storage drives down transaction costs and increases throughput across layer-2 networks, the infrastructure supporting decentralized finance must scale in tandem. Chainlink provides the data, interoperability, and computation infrastructure required to power advanced smart contracts in this highly scalable environment.

Cheaper layer-2 transactions directly benefit oracle operations. With reduced gas fees, decentralized oracle networks can deliver more frequent and cost-effective updates to onchain applications. This environment is highly conducive to the Chainlink data standard, which encompasses Data Feeds for reliable, push-based onchain market data and Data Streams for pull-based, low-latency data. By using blob storage on layer 2s, DeFi protocols such as lending markets and perpetual exchanges can access high-frequency data with sub-second accuracy, which enhances their overall security and efficiency without prohibitive gas costs.

Furthermore, a scaled Ethereum environment relies heavily on secure cross-chain communication. As more activity moves to various layer-2 rollups using blob storage, the fragmentation of liquidity and data becomes a pressing issue. The Cross-Chain Interoperability Protocol (CCIP), which powers the Chainlink interoperability standard, solves this by enabling secure messaging and token transfers across 60+ blockchains. This ensures that users and institutions can interact across multiple layer-2 environments from a single integration, preventing siloed liquidity.