What Is EIP-4844? Understanding Proto-Danksharding
EIP-4844, also known as Proto-Danksharding, is an Ethereum network upgrade that introduces a new transaction type carrying data blobs. This reduces data availability costs for layer-2 rollups and lowers overall network transaction fees.
Scaling throughput without sacrificing security is a primary engineering challenge for blockchain networks. Ethereum relies on layer-2 rollups to process transactions offchain and batch the results back to the main network. However, the cost of posting these batches to Ethereum using standard transaction data fields created a bottleneck. This kept fees relatively high for layer-2 users.
EIP-4844, widely known as Proto-Danksharding, directly addresses this limitation. By introducing a new method for handling temporary data, EIP-4844 alters how layer-2 networks interact with Ethereum. This upgrade provides a dedicated, cost-effective data availability layer, enabling higher throughput and lower fees across decentralized finance (DeFi) applications.
What Is EIP-4844 (Proto-Danksharding)?
EIP-4844 is a major protocol upgrade for the Ethereum blockchain that serves as the centerpiece of the Dencun network update. The acronym EIP stands for Ethereum Improvement Proposal, which is the formal mechanism developers use to introduce and debate new features or standards for the network. Specifically, EIP-4844 introduces a concept called Proto-Danksharding. This is a scaling solution designed primarily to benefit layer-2 networks, which operate on top of Ethereum to provide faster and cheaper transactions.
Proto-Danksharding represents a shift in how Ethereum handles the large amounts of data generated by layer-2 rollups. Before this upgrade, rollups had to store their transaction data permanently on the Ethereum base layer. This permanent storage is secure but computationally expensive. EIP-4844 changes this architecture by creating a new, temporary space specifically dedicated to the data that layer-2 networks need to post.
By implementing Proto-Danksharding, Ethereum provides a specialized data availability solution that separates the storage of layer-2 transaction batches from the permanent execution history of the main blockchain. This separation is an important step in Ethereum's long-term scaling roadmap. It allows the network to process exponentially more activity by optimizing how data is stored and verified. For developers and users, EIP-4844 acts as the infrastructure layer that lowers the cost to build and interact with complex decentralized applications.
The Problem: Ethereum Scalability and Calldata
Before the upgrade, rollups achieved scalability by executing thousands of transactions offchain, bundling them into a single batch, and submitting a cryptographic proof and the transaction data back to the Ethereum mainnet. This process ensures anyone can verify the state of the layer-2 network using the security of the Ethereum base layer.
Historically, rollups posted this batch data using a feature called calldata. Calldata was originally designed to carry the inputs for smart contract function calls, not to serve as a large storage medium for layer-2 transaction logs. Because calldata is processed by the Ethereum Virtual Machine (EVM) and stored permanently on every Ethereum node, it consumes significant block space. Consequently, posting data via calldata requires high gas fees. During periods of high network congestion, the cost of this data availability could account for more than 90 percent of the total fees paid by layer-2 users.
This architecture created a bottleneck for Ethereum scalability. As more users migrated to layer-2 networks, the demand for calldata increased, driving up costs and limiting the maximum throughput of the network. The system required a dedicated data availability solution that could bypass the EVM and avoid the costs of permanent storage. A cheaper method for rollups to post their transaction batches was essential to lower gas fees and support the next phase of growth for onchain applications.
How Proto-Danksharding Works: Data Blobs Explained
Proto-Danksharding solves the calldata bottleneck by introducing a new transaction type known as a blob-carrying transaction. A data blob is a large, fixed-size chunk of data attached to a standard Ethereum transaction. Instead of forcing layer-2 networks to cram their transaction batches into expensive calldata, they can now place this information inside these dedicated blobs.
The technical innovation of EIP-4844 lies in how the Ethereum network processes and stores these blobs. Unlike standard transaction data, the contents of a blob are entirely inaccessible to the EVM. Smart contracts can't read or execute the data inside a blob directly. They can only access a cryptographic commitment to the data, which proves the data exists and is accurate. By bypassing the EVM execution environment, the network saves significant computational resources.
Furthermore, data blobs are stored on the Ethereum consensus layer rather than the execution layer. The consensus layer is responsible for network agreement and security, while the execution layer handles smart contract logic. Because blobs aren't needed for executing mainnet smart contracts, they do not need to be stored permanently. Ethereum nodes only hold onto blob data for a temporary period, typically around 18 days. This temporary storage model reduces the hardware requirements for node operators while still providing exactly what layer-2 rollups need: a secure, short-term data availability layer to verify transaction batches before they are finalized.
Proto-Danksharding vs. Full Danksharding
While EIP-4844 introduces significant improvements, it is not the final destination for Ethereum scalability. Proto-Danksharding serves as a transitional stepping stone toward a larger upgrade known as Full Danksharding. The current implementation provides the cryptographic framework and the new transaction types required for data blobs, but it does so with strict limitations to maintain network stability.
Under Proto-Danksharding, the Ethereum network enforces a fixed blob limit per block. Currently, a single block can hold a target of three blobs and a maximum of six blobs. This controlled capacity provides an immediate boost to layer-2 data availability without overwhelming the storage and bandwidth capabilities of existing node operators. It is a practical compromise that delivers fee reductions while developers prepare the network for more advanced architectures.
Full Danksharding will expand upon this foundation by massively increasing the number of blobs attached to each block. To achieve this without requiring node operators to store unmanageable amounts of data, Full Danksharding will implement data availability sampling (DAS). DAS allows nodes to verify that blob data is available by downloading only small, random portions of the data rather than the entire blob. This upgrade will theoretically allow Ethereum to process over 100,000 transactions per second, fully realizing the network's rollup-centric scaling roadmap.
The Future of Ethereum Scaling
EIP-4844 fundamentally changes the economics of operating and using layer-2 networks. By introducing data blobs and separating data availability from transaction execution, Proto-Danksharding removes the high costs associated with permanent calldata storage. This architectural shift lowers gas fees for users interacting with decentralized applications and creates a more scalable environment for developers building onchain. As Ethereum continues to evolve toward Full Danksharding, the principles established by EIP-4844 will remain central to the network's ability to support global financial infrastructure.
