ACDE #197: Vitalik Voices His Support for More Blobs

In this episode of the Infinite Jungle, key takeaways from the Ethereum core developers execution call, ACDE #197, are discussed. A significant development is the growing consensus to limit the upcoming Pectra upgrade to eight Ethereum Improvement Proposals (EIPs) currently live on Pectra DevNet 3, a decision that has gained wider acceptance among developers. The conversation also explored the potential addition of four EIPs focused on enhancing Ethereum's data availability, especially since Pyrdas is excluded from Pectra.

Developers stressed the importance of prioritizing roll-ups on Ethereum, with minor improvements to data availability being crucial for their future. The finalized eight EIPs for Pectra include max EB, execution layer trickleable withdrawals, and attestation refactoring, while the inclusion of the four data availability-related EIPs remains under consideration.

Looking ahead, the next Ethereum hard fork will be named Fusaka, which will incorporate Pirdas and EOF, with further code changes to follow after these implementations. The subsequent upgrade, Amsterdam, will also consider the delayed Virkl upgrade.

A notable moment in the call was the unanimous support for a proposal to simplify execution layer triggerable requests, showcasing a rare instance of agreement among developers. Vitalik Buterin's participation highlighted the importance of data availability improvements in Pectra. He argued that enhancing blob capacity is essential for scaling Ethereum and ensuring the operational viability of roll-ups. Vitalik emphasized that making data availability cheaper would economically benefit roll-ups, supporting Ethereum's scalability and user activity.

Developers like Dan Cradd Fist advocate for including additional EIPs in the Pectra upgrade, while concerns were raised about the impact of increased blob counts on home stakers. Issues such as missing blocks affecting rewards were highlighted by Teku developer Enrico and Ben Edgington, indicating that some home stakers are being disconnected from the network. Developers are urged to investigate how changes in data availability could impact Ethereum's decentralization and the ability for individuals to run nodes.

Plans for data-driven investigations over the next month aim to assess the implications of increasing blob capacity. Pectra DevNet 4 is set to launch within two weeks, with updates to EIPs and specifications being finalized. The timeline for the mainnet activation of Pectra is tentatively targeted for February, though March or April may be more realistic. Proposed changes include increasing the blob count per block, adjusting the minimum base fee for blob gas, raising call data costs, and uncoupling blob counts between the consensus and execution layers.

A base developer, Francis, emphasized the need to establish minimum requirements for running an Ethereum node to track changes over time. As hardware requirements evolve, it’s crucial for home stakers to be aware of potential upgrades. The viability of home staking is essential, as most block production is currently managed by regulated entities. Maintaining a decentralized network of validators is vital for Ethereum's security, especially in adverse regulatory environments. Future initiatives will aim to ensure fair compensation for home stakers, addressing concerns about the differentiation between home and non-home staking entities. The conversation underscores the balance between scaling Ethereum and preserving its decentralization, with ongoing discussions about the implications of proposed changes for the network's future.