Ethereum Developers Gather for ACDC Call #134
On May 30, 2024, Ethereum developers gathered via Zoom for the All Core Developers Consensus (ACDC) call #134. These biweekly meetings serve as a collaborative platform where developers discuss and coordinate changes to Ethereum’s consensus layer (CL), also known as the Beacon Chain. Milky Way digital. This session was chaired by researcher Alex Stokes from the Ethereum Foundation (EF), who led discussions on various upgrades, including the Pectra Devnet 0 and possible changes to the Pectra upgrade scope.
Developer 0 Summary
Developers revisited the launch of Pectra on Devnet 0 and agreed to leave the attestation behavior affected by EIP 7549 unchanged during hard fork activation. This decision follows previous discussions in which developers considered multiple options to prevent invalid attestations during the fork. Ultimately, they decided not to complicate the upgrade, but opted to activate EIP 7549 simultaneously with other Pectra EIPs.
Uncertainty remains regarding EIP 7251 and whether staked ETH consolidations should be initiated from the execution layer (EL). This feature could benefit staking pools by enabling stake consolidation via smart contracts instead of relying on node operators. Stokes suggested revisiting this issue after further progress on implementation.
In addition, developers answered open questions about the completion of validator deposits under EIP 6110. Teku developer Mikhail Kalinin outlined a path forward in a GitHub note prior to the call. The discussions also covered versioning for the ‘GetPayloadBodies’ request in the Engine API, which was made by Lighthouse developer ‘sean’. Stokes encouraged feedback on this issue via a GitHub pull request.
EIP 7549 Changes
Nimbus developer Etan Kissling proposed a minor tweak to EIP 7549 to improve stability for generalized indexes. The suggestion to move a new field to the end of a container to avoid index redistribution was not opposed. Stokes advised developers to review Kissling’s pull request on GitHub.
Another proposed change to EIP 7549 involved designing requests and other EL-triggered actions as a sidecar for EL blocks. Mikhail Kalinin praised this design because it simplifies the EL. Stokes recommended discussing this topic again in the next CL call after further review of the proposal on GitHub.
Pectra Scope Discussion
Developers debated whether to include several CL-focused EIPs, such as EIP 7688 and PeerDAS, in the Pectra upgrade. EIP 7688 aims to ensure forward compatibility by inheriting part of the “StableContainer” SSZ data structure. Significantly improving network data availability, PeerDAS could increase the number of blob transactions per block from three to 64 or more.
EF Developer Operations Engineer Barnabas Busa reported that an early version of PeerDAS was launched on a devnet, revealing several issues. Stokes questioned the feasibility of adding PeerDAS to Pectra if it risks delaying the upgrade. The discussions also considered splitting Pectra in two hard forks to house PeerDAS.
Developers like “Nishant” and “atd” had different views on decoupling PeerDAS from other Pectra EIPs. Atd highlighted the logistical challenges of coordinating multiple upgrades within a short period of time. Ultimately, the developers agreed to further test Pectra EIPs and PeerDAS together, with PeerDAS activated on devnets and testnets at a later date.
As discussions on the inclusion of EIP 7688 were postponed until the next ACDC call, the call ended with developers agreeing to move forward with this testing strategy.
Image source: Shutterstock
. . .
Labels