From follow-up Protocol Update 001I would like to introduce an approach to Blob scaling. L1 serves as a robust foundation for expanding your L2 systems, and the required component of a secure L2 solution is the availability of data provided by L1. Data availability ensures that updating L2 returns to L1. Because blobs are a unit of data availability in today’s protocols, scaling the number of blobs per block is an important requirement to guide the wave of L2 adoption for use cases such as real-time payments, Defi, social media, gaming, AI/agent applications.
Our work is constructed as a series of incremental changes in Ethereum’s blob architecture. To accelerate the speed of scaling, we are expanding from the “fork-centric” philosophy to ship incremental optimizations in non-broken ways when ready. Therefore, it is tied not only to the following projects related to both network upgrades, but also to the period between them (“interfolk”).
tl; dr
- Fusaka will introduce you Pildasa new data architecture that allows blob scaling beyond today’s throughput levels from 6 blobs/blocks to 48 blobs/blocks
- BLOB parameters only (BPO) fork Enhanced by gradually increasing the number of mainnet blobs and increasing peer-to-peer bandwidth optimization
- Advanced networking techniques planned for Gram Stardom repeat to further expand Peerdas’ design
- Mempool Sharding is saved The value of Ethereum Data continues to expand
- Research on next-generation DAS unlocks the evolution of safe DA scaling
Pildas of Fusaka
The first milestone is Peerdas’ delivery in Fusaka Network upgrades. Peerdas introduces availability sampling (DAS) for data in which individual nodes download only a subset of BLOB data in a particular block. With randomized sampling by node, the computational load acquires boundaries even as the total BLOB count increases. Nodes no longer need to download all the blobs in a block, allowing them to increase their blob count without comparable increases in node requirements.
Fusaka is scheduled for later this year, with the implementation of all Ethereum clients. Extensive testing has been carried out in development networks (“Devnets”) including non-financial scenarios and hostile “data withholding” conditions. At this point in the R&D process, we continue to strengthen our existing developers and plan to deploy them to our testnets and mainnets. Barnabas’ busa Here we are leading the fees here to ensure smooth progress through the final stages of the upgrade pipeline.
Peerdas V1.x
There are two nonconsensus changes in the strategy of gradually scaling the mass between Fusaka and Gramaster Dam upgrades: BPOS and bandwidth optimization. These are additive because better bandwidth utilization allows resources to be utilized for higher throughput.
BPO
Peerdas introduced in Fusaka sets a theoretical stage of an eight-fold increase from today’s Ethereum throughput (i.e. ~64 kb/s to ~512 kb/s). Rather than jumping straight to this theoretical maximum during Fusaka’s deployment, the core developers chose a more gentle increase “BLOB parameters only” Hard fork. This mechanism allows core developers to program automatic blob capacity increases over time, maintaining a continuous growth trajectory. BPOS does not require manual intervention to become active after it is programmed. Additionally, multiple previously reserved BPO steps may be included in the same client release. Between steps, monitor the network and respond to scaling bottlenecks that may present themselves only to the mainnet, paving the way for the next increase. Barnabas Busa works closely with the client team alongside others on the EF Pandaops team to distill the correct schedule and achieve eight times the scale from today.
Bandwidth Optimization
There is much you can do to make the bandwidth on your network more efficient. Raul Kriparani With Marco Munizaga This is the main initiative of the network engineering work. A particularly promising optimization is the introduction of “cell-level messaging” which allows nodes to more intelligently query some of the samples introduced in Peerdas. This change reduces redundant communications on the network and allows bandwidth savings to be focused on secure provisioning of even more blob capacity. No consensus or execution protocol changes are required to unlock this milestone. Therefore, we can ship the Interfork before Gramaster Dam next year.
Peerdas V2
This project refers to the next generation of Peerdas designs, which will scale even more, taking advantage of the bandwidth savings achieved through pipelining introduced by EIP-7732 (which will be included in Gramas Terdam). Further improvements to cell-level messaging and data reconstruction techniques that allow individual parts of the node to be sampled more flexibly in the individual parts of the mass to fully represent the core ideas of DAS. These benefits set us up to scale beyond the limits of an imminent Peerdas design, along with the advantages of pipelining that allow for more efficient use of time between blocks. There are a lot of inspiring parts, and while the BLOB count actually expands in production settings, accurate numbers need to be adjusted for both implementation performance and mainnet analysis, this work should provide a final multiple of DA throughput before you need to seek an alternative design.
This batch of updates will be the expected Gram Stardom upgrade in mid-2026. Alex Stokes And Raúl Kripalani is now adjusting the R&D to keep the blob throughput scaling.
Blob Pool Scaling
The benefits of scaling are clear, but you must do so while maintaining the core values of Ethereum. One of these directly related to blob scaling is censorship resistance. Mempool acts as a distributed network of blob inclusion and directly provides censorship resistance that generates most blocks in Ethereum in the face of a centralized builder network. The instance of censorship has improved over time, but ensuring that Blob Mempool also scales with it is equivalent to a scaling strategy.
Csaba Kiraly We are doing our main work here to help us maintain this important resource. The current implementation supports recent BLOB throughput Active the study Fuzaka and later unlocked higher levels, the best way to expand memory.
Da’s future
Beyond future iterations of Peerdas, there are various research directions to continue scaling DAs while maintaining Ethereum security properties. The proposal generally applies Monica’s Furrudus There are several flavors under active research. All of these proposals involve peer-to-peer networking innovations, allowing a highly diverse audience to destroy more samples while still maintaining resistance to hostile actors. Works such as Robust Distributed Array Formalize this concept. Other considerations include low latency inclusion, censorship resistance and the evolution of the BLOB fee market, which can facilitate on-chaining of BLOBs.
The research here is stewarded Francesco Damat And very active – reach out if you want to cooperate!
