3 months ago
26 ARTICLE AD
Topics discussed also include the transitioning from the Mplex protocol to the new yamux multiplexer to debating whether or not to include EIP 7688 in the Pectra upgrade, among many other things.
On August 8, 2024, Ethereum core developers gathered for the 139th All Core Developers Consensus (ACDC) call. For the most part, the bi-weekly meeting, which was chaired by Ethereum Foundation researcher Alex Stokes, focused on the Ethereum Pectra upgrade. That is, the latest progress, as well as the obstacles being encountered with the ongoing upgrade.
The discussions bordered on updates on network stability, development networks, and major enhancements to the Beacon Chain’s consensus layer.
Major Achievements and Challenges with Pectra Devnet 2
One of the main highlights of the discussion was the stability of Pectra Devnet 2. According to Developer Operations Engineer Barnabas Busa, it has recorded an impressive 85% network participation rate so far.
Ethereum Foundation Researcher Hsiao Wei Wang announced the upcoming alpha.4 release of the Pectra consensus layer specifications, addressing several bugs identified in execution layer (EL) clients. Despite these advancements, however, challenges remain. More so, with EthereumJS and Erigon clients, which are currently experiencing technical difficulties.
Buba also raised some minor issues about the Prysm client, citing that they might need deeper attention. Whereas, Parithosh Jayanthi brought ongoing concerns with Lighthouse, Teku, and Besu nodes to the notice of fellow developers.
Developers Keen on Enhanced Coordination for Future Development
The meeting also addressed communication lapses experienced during Devnet 2’s launch, notably affecting Prysm’s awareness of network startup. To prevent similar issues, developers have decided to initiate weekly meetings to discuss Pectra testing updates. Scheduled for Mondays, these brief sessions will enhance coordination among client teams and ensure that everyone stays informed about developments related to PeerDAS and EOF.
Meanwhile, speaking about future developments, Devnet 3 is expected to carry a bear-similar setup to Devnet 2. However, little changes might come up that would likely affect the revised EIP 7702 design.
In the meeting, Gajinder Singh from Lodestar highlighted issues with EIP 7251 on Devnet 2. Particularly around consolidating validator staked ETH deposit balances. However, the issues are reportedly being addressed and will require further validation in the upcoming devnet.
Several other topics were discussed. They ranged from the transitioning from the Mplex protocol to the new yamux multiplexer to debating whether or not to include EIP 7688 in the Pectra upgrade, among many other things.
As the call wrapped up, Prysm developer “Potuz” urged a timely review of proposed changes to the execution payload structure. He said this is to allow adequate updates to consensus layer specifications. This ongoing dialogue and development highlight Ethereum’s commitment to continuous improvement and innovation in its network infrastructure.
