EIP-4844: Shard Blob Transactions (Proto-Danksharding)

This page is an educational summary of an Ethereum protocol proposal. It is not investment advice or a verbatim reproduction of the source.

Directories Ethereum Whitepapers & Research
Paper title EIP-4844: Shard Blob Transactions
Authors Vitalik Buterin; Dankrad Feist; Diederik Loerakker; George Kadianakis; Matt Garnett; Mofi Taiwo; Ansgar Dietrichs
Year 2022
Project Ethereum
License CC0 (copyright and related rights waived)
Official source Ethereum Improvement Proposal EIP-4844

EIP-4844: Shard Blob Transactions, commonly called Proto-Danksharding, was created on February 25, 2022 and activated with Ethereum’s Dencun upgrade on March 13, 2024. It introduced blob-carrying transactions so rollups could publish data through a dedicated data-availability path. The proposal is not full Danksharding, and its original launch limits are no longer the network’s current limits. The word “shard” describes the proposal’s longer-term direction; EIP-4844 itself did not split Ethereum into shards.

What EIP-4844 was designed to change

Ethereum rollups execute transactions on separate networks and publish data or proofs to Ethereum so that their results can be checked. Before blobs, rollups commonly placed data in transaction calldata, which competes for ordinary execution gas. EIP-4844 added a type-3 transaction that can carry blobs. The EVM cannot read a blob’s contents directly; it can use the blob’s versioned hash and commitment, while the consensus layer handles availability.

Blob data has a bounded availability window. Ethereum’s documentation describes a minimum request window of 4,096 epochs, about 18 days. After that, clients may prune the data; some rollups, services, or archival operators may keep copies longer. This is temporary data availability, not a promise that every node stores every blob forever.

How blob transactions and fees work

Each blob is 4,096 field elements of 32 bytes, or 131,072 bytes (128 KiB). A KZG commitment lets the protocol verify that data supplied for a blob matches its commitment without making the blob contents directly readable by smart contracts. The EIP introduced a blob-gas fee that responds to blob demand separately from ordinary execution gas. A blob-carrying transaction can still incur both execution costs and blob costs.

Since Fusaka, EIP-7918 also sets an execution-cost-related reserve price for blob gas. The blob market therefore remains a distinct fee mechanism, but it should not be described as completely isolated from execution costs. A lower protocol data cost can help a rollup, but it does not guarantee a particular fee for an end user; execution, proof, sequencing, congestion, and the rollup’s own fee policy also matter.

Launch settings and current mainnet settings

Item At Dencun launch Current at review date
Blob target per block 3 14
Maximum blobs per block 6 21
Blob size 128 KiB 128 KiB
Availability window 4,096 epochs (about 18 days) Bounded; clients may prune after the request window

The 3-blob target and 6-blob maximum are historical Dencun launch parameters. Ethereum later raised capacity in stages. The current BPO2 schedule lists a target of 14 and maximum of 21 blobs per block. Blob schedules can change through later coordinated upgrades, so these figures are dated network parameters rather than permanent properties of EIP-4844.

PeerDAS and the longer-term roadmap

Fusaka went live on December 3, 2025 and brought PeerDAS to Ethereum mainnet. PeerDAS uses data-availability sampling: nodes custody and sample subsets of blob data instead of requiring every node to download every blob. That makes higher blob throughput possible while limiting the data each node needs to handle.

PeerDAS is a major step in Ethereum’s scaling roadmap, but it does not mean that every part of full Danksharding is complete. Capacity is being increased incrementally, and further protocol work remains. Older projections such as “64 or more blobs” or “about 16 MB per block” should not be presented as today’s settings or as a guaranteed delivery date.

The KZG ceremony

The KZG trusted setup used for blob commitments ran from January to August 2023. The Ethereum Foundation reports 141,416 contributions. That is a contribution count, not a verified count of unique people: the Foundation cautions that some contributors may have participated more than once. The security argument relies on at least one honest contribution, not on treating the total as unique identities.

Social Media Sentiment

A March 28, 2024 discussion in r/ethtrader about early blob-fee spikes showed the kind of mixed reaction that followed Dencun: commenters were enthusiastic about lower-cost rollup use, while the thread also focused on a temporary surge in blob demand during inscription activity. It is one self-selected discussion from the first weeks after launch, not a representative survey or a measure of current fees.

Last updated: 2026-10

Related Terms

See Also

Sources

Last updated: 11 October 2026