Galaxy Digital: Ethereum developers discuss major upgrades in latest consensus currency

Ethereum developers gather for ACDC currency #134.

On May 30, 2024, Ethereum developers gathered via Zoom for All Core Developers Consensus (ACDC) call #134. These bi-weekly meetings serve as a collaborative platform for developers to discuss and coordinate changes to Ethereum’s consensus layer (CL), also known as the beacon chain. galaxy digital. The session was chaired by Ethereum Foundation (EF) researcher Alex Stokes, who led discussions on various upgrades, including Pectra Devnet 0 and potential changes to the scope of Pectra upgrades.

Devnet 0 Summary

The developers have revisited the release of Pectra on Devnet 0, agreeing to keep the proof behavior affected by EIP 7549 unchanged during the hard fork activation. This decision follows previous discussions in which the developers considered several options to prevent false proofs during the fork. Ultimately, they decided to activate EIP 7549 at the same time as other Pectra EIPs rather than complicate the upgrade.

Uncertainty remains as to whether the integration of EIP 7251 with staked ETH should begin at the Execution Layer (EL). This feature can benefit staking pools by allowing stake consolidation through smart contracts without relying on node operators. Stokes suggested revisiting the issue after further implementation.

The developer also answered public questions about confirming validator deposits under EIP 6110. Teku developer Mikhail Kalinin outlined the way forward in a GitHub comment ahead of the call. The discussion also included version control for the Engine API’s “GetPayloadBodies” request, raised by Lighthouse developer “sean”. Stokes encouraged feedback on this issue through a GitHub pull request.

EIP 7549 changes

Nimbus developer Etan Kissling proposed minor adjustments to EIP 7549 to improve the stability of the generalized exponent. The proposal to relocate new fields to the end of the container to avoid index reallocation received no opposition. Stokes advised developers to review Kissling’s pull requests on GitHub.

Another proposed change to EIP 7549 included designing requests and other EL triggered operations as sidecars to EL blocks. Mikhail Kalinin praised this design for simplifying EL. Stokes recommended further reviewing GitHub’s proposal and revisiting this topic at the next CL call.

Spectrascope Discussion

Developers discussed whether to include several CL-centric EIPs, such as EIP 7688 and PeerDAS, in the Pectra upgrade. EIP 7688 aims to ensure future compatibility by adopting parts of the “StableContainer” SSZ data structure. Significantly improving data availability in the network, PeerDAS can increase the number of blob transactions per block from 3 to over 64.

EF Developer Operations Engineer Barnabas Busa reports that early versions of PeerDAS have been released on devnet, revealing a variety of issues. Stokes questioned the feasibility of adding PeerDAS to Pectra if there was a risk of delays in the upgrade. Debate considering splitting Pectra in two hard fork To accommodate PeerDAS.

Developers like “Nishant” and “atd” expressed different views on separating PeerDAS from other Pectra EIPs. Atd highlighted the logistical challenges of coordinating multiple upgrades in a short period of time. Ultimately, the developers agreed to further test Pectra EIP and PeerDAS together by later enabling PeerDAS on devnet and testnet.

The meeting concluded with the developers agreeing to move forward with this testing strategy, with discussion on the inclusion of EIP 7688 postponed to the next ACDC meeting.

Image source: Shutterstock

. . .

tag