EIP-4844, often called proto-danksharding, is an Ethereum protocol upgrade designed to make transactions cheaper and the network faster by adding a new transaction format that carries large chunks of off-execution data called blobs. For everyday users and rollup developers, this change reduces costs, raises effective throughput, and paves the way for a fuller sharding solution in the future.
At a high level, EIP-4844 introduces blob-carrying transactions. These look like ordinary transactions but can attach separate binary data objects — blobs — to blocks. Blobs are not processed by the Ethereum Virtual Machine (EVM) and live on the consensus layer for only a limited time, which allows the network to carry far more data for temporary use without the long-term storage cost of regular block data.
The distinction between blobspace and traditional blockspace is central to understanding the upgrade. Here are the practical differences:
Because blobs are cheaper and short-lived, they let rollups and other layer‑2 systems post more data to Ethereum at far lower cost, improving throughput without forcing every full node to store everything forever.
Blobs are attached to blocks and are propagated across the network, but they are not part of EVM state. That means smart contracts cannot directly read blob contents; instead, layer‑2 systems use blobs as an efficient way to publish large amounts of calldata that rollups can later reconstruct and prove.
Blobs are priced lower because they are treated as temporary consensus-layer data with bounded storage costs and no execution gas. The protocol charges for the bandwidth and short-term storage required, but the fee model makes posting large volumes of data far cheaper than stuffing the same bytes into permanent blockspace.
While EIP-4844 does not implement full sharding, it adds many building blocks needed for the eventual transition to danksharding, such as multi-dimensional fee logic and verification rules that let the network handle blob data efficiently. In other words, it’s an intermediate step that brings meaningful scaling gains now while preparing the stack for larger changes later.
EIP-4844 fits into a broader roadmap that also considers how block proposers and builders interact and how maximal extractable value (MEV) is managed. One key idea in future plans is separating the roles of proposers (validators who select block contents) and builders (entities that assemble block payloads), which helps reduce conflicts and centralization pressure when many shards or blob-channels are active.
Once deployed, proto-danksharding should deliver tangible improvements:
For typical wallet users this generally means lower transaction fees on rollups and snappier interactions, while infrastructure teams will have an easier time scaling data availability without massive long-term storage burdens.
It’s important to set expectations correctly. EIP-4844 is a transitional upgrade, not the final sharding solution. Blobs are short-lived, so long-term archival storage still needs external systems to retain data beyond the blob retention window. Also, some architectural changes that accompany full danksharding will arrive later, so certain advanced scaling targets remain a future task.
The proposal moved quickly through design and testing phases and was targeted for implementation in the near term, but protocol timelines can shift based on testing results and coordination among client teams. Developers and node operators should watch release notes from client maintainers and prepare for changes to fee handling and data propagation logic.
EIP-4844 represents a pragmatic step toward dramatically increasing Ethereum’s data throughput without sacrificing decentralization. By introducing blob-carrying transactions and cheaper temporary data storage, the upgrade lowers costs for rollups, improves transaction efficiency, and lays the groundwork for full danksharding. For users, that translates into cheaper and faster layer‑2 transactions; for developers, it opens simpler paths to scale off-chain computation while relying on Ethereum for secure data availability.
