Proto-Danksharding

Proto-Danksharding is the common name for Ethereum’s EIP-4844 blob transaction design. It added a lower-cost way for rollups to post data for availability checks, as a step toward scaling data availability; it did not implement full sharding.

What a blob transaction changes

A blob-carrying transaction includes data commitments and blob data handled by Ethereum’s consensus layer. The EVM can access the commitment but not read the blob payload as ordinary contract data. Blob gas has its own fee market, so the cost depends on blob demand as well as each rollup’s batching and fee design. Blobs are retained temporarily under protocol rules, not as a permanent archive.

How PeerDAS fits

PeerDAS is a later data-availability-sampling protocol specified separately in EIP-7594. Nodes sample assigned data columns rather than each downloading all blob data, while erasure coding allows reconstruction when enough data is available. Ethereum.org reports that PeerDAS shipped with the Fusaka upgrade, which went live on December 3, 2025. It extends the blob system introduced by EIP-4844; it does not turn blobs into permanent storage.

What “proto” means

The proposal is a partial step in Ethereum’s data-availability roadmap, not a promise that every rollup becomes cheap or that historical data stays available forever. Rollups still need to decide how they publish data, manage fees and preserve older records. Permanent data access may require separate archives or other storage systems.

Social Media Sentiment

In an October 2025 Ethereum Magicians thread, an Aztec developer raised concerns about retrieving blob data and the network resources operators might need as they prepared for PeerDAS. Other developers described different retrieval and archival approaches. This was a small technical discussion before Fusaka activated, not a survey of operators after launch. the October 2025 blob-retrieval discussion

Last updated: 2026-10

Related Terms

See Also

Sources