Ethereum Developers Discuss Pectra and PeerDAS Upgrades in Core Call #150

In a recent assembly of Ethereum's core developers, known as the All Core Developers Consensus (ACDC) call #150, significant discussions were held regarding upcoming changes to Ethereum's consensus layer. The meeting, chaired by Ethereum Foundation (EF) Researcher Alex Stokes, focused on the Pectra and PeerDAS upgrades, among other topics, according to Galaxy.

Pectra Upgrade and Testnet Plans

The developers agreed to incorporate a 30-day buffer between the final public testnet upgrade and the mainnet upgrade for Pectra. This decision aims to provide stakeholders with ample time for necessary software updates. Assuming testnet launches proceed smoothly, the mainnet activation is tentatively scheduled for April 8.

Pectra Devnet 6, launched on February 5, is reportedly running without major issues. Minor technical adjustments are being addressed, including an API issue with the Lighthouse client. EF Developer Operations Engineer Parithosh Jayanthi confirmed that MEV workflows are being successfully tested.

Fork Scheduling and Security Considerations

Tim Beiko presented three potential timelines for the testnet and mainnet upgrades. The second option, favoring a client testnet release by February 13, was preferred by the development teams. A 30-day buffer between the final testnet upgrade and mainnet activation was supported, enhancing security measures, as noted by EF Security Researcher Fredrik Svantes.

Beiko mentioned that client teams should prepare releases for the Holesky and Sepolia upgrades by February 13, with a public announcement planned for February 14. Developers aim to finalize the mainnet upgrade date by March 6.

Advancements in PeerDAS

Testing for the PeerDAS upgrade is progressing smoothly, with plans to launch a multi-client devnet soon. Lighthouse developer Sean Anderson proposed shifting the responsibility of building KZG proofs to transaction senders, potentially easing validator computation bottlenecks. This idea, while adding complexity, could significantly enhance network scalability.

Stokes emphasized the potential for PeerDAS to support a significant increase in blob capacity, though further analysis of BPO forks might be necessary for future upgrades.

Validator Hardware and Bandwidth Requirements

The impact of the max blobs flag on validator hardware was discussed, aiming to prevent network constraints tied to local block builders. Ahmad Bitar from Nethermind supported the proposal but highlighted the need for long-term solutions to maintain the participation of independent validators.

The discussion also touched on how the max blobs flag might affect Layer-2 rollups' cost calculations, with plans to address this in upcoming meetings with L2 teams.

Future Prospects and Retrospective Insights

Developers were encouraged to review proposed EIPs for the Fusaka upgrade and consider feedback from the Pectra retrospective. A disciplined approach to fork scoping is being advocated to avoid delays experienced in previous upgrades.

Additionally, a Pectra bug bounty hackathon is being organized, offering up to $2 million in rewards for identifying security vulnerabilities. This initiative is aimed at bolstering the robustness of client implementations ahead of the mainnet upgrade.

As Ethereum continues its evolution, these discussions underscore the collaborative efforts and strategic planning necessary to enhance its blockchain infrastructure.