Vitalik Buterin, co-founder of Ethereum, has identified peer data availability sampling (Peerdas) as a key tool to address the growing demand for blob storage in networks. Peerdas is a feature of future Fusaka upgrades.
His remarks arrive as Ethereum records six chunks per block. This is a milestone that reinforced concerns about data bloating across ecosystems.
The BLOB was introduced as a temporary on-chain data container through EIP-4844 and was designed to reduce the cost of layer 2 rollups while avoiding permanent storage pressure. Unlike call data, Blobs expires after about two weeks, reducing long-term storage needs while maintaining integrity for transaction validation.
This construction allows the rollup to work cheaper and improves the scalability of Ethereum.
However, its design has led to the rapid adoption of blobs across blockchain networks. On September 24th, chain analyst Hildbuby reported that several Ethereum Layer 2 solutions, including Base, World Coin, Sonyum and scrolls, currently rely heavily on blobs.
With this in mind, analysts pointed out that Validator now needs more than 70 gigabytes of space to manage Blobs.
This rapid increase has forced developers to look for solutions that balance scalability and storage efficiency.
How Peerdas works
Buterin explained that Peerdas solves this challenge by preventing a single node from storing the entire dataset and distributing responsibility across the network.
According to him:
“The mechanism behind Peerdas is that each node only requires a small number of ‘chunks’. This is a method of probabilistically verifying that more than 50% of chunks are available. If 50% or more chunks are available, the node can download those chunks and recover the rest using erase coding. ”
However, he noted that the system requires complete block data at certain stages, such as during the initial broadcast and whether blocks need to be reconstructed from partial data.
To prevent manipulation, Butarin emphasized the importance of “honest actors” playing these roles. However, he emphasized that Peerdas is resilient to a large group of fraudulent participants, as other nodes can take responsibility when they need it.
Increased mass
Buterin noted that Ethereum’s core developers are cautious about deploying Peerdas despite years of research into the project.
To minimize the risk, they agreed to stage the rollout via a BLOB parameter only (BPO) fork, rather than a single leap of capacity. The first fork, scheduled for December 17th, will raise the BLOB target from 6/9 to 10/15. The second fork, scheduled for January 7, 2026, will again increase the limit to 14/21.
This step-by-step approach allows developers to monitor and tweak network performance over time. Buterin expects Blob counts to rise with these changes and lays the foundation for a more aggressive increase.
In his view, Peerdas is essential to maintain layer 2 growth and prepare the base layer of Ethereum, in order to handle higher gas restrictions and ultimately move the running data to the blob.