According to BlockBeats, Ethereum's core developers held their 137th All Core Developers Consensus (ACDC) meeting on July 11, 2024, via Zoom. The ACDC meetings, which occur every two weeks, are a platform for developers to discuss and coordinate changes to Ethereum's consensus layer (CL), also known as the beacon chain. The meeting was chaired by Alex Stokes, a researcher from the Ethereum Foundation (EF).
During the meeting, the progress of Pectra Devnet 1 and PeerDAS Devnet 1 was discussed. The developers also discussed research generated by the fork choice test led by the research team TxRx within the blockchain software company Consensys.
The consensus layer and execution layer clients are ready to launch Pectra Devnet 1. The developers expect to launch the next test network next week. A developer named 'pk910' stated that his team, likely the EF DevOps team, is testing client combinations between Nethermind, Geth, Teku, Nimbus, Lodestar, and Grandine. Gajinder Singh, a developer for EthereumJS and Lodestar, later pointed out that the EthereumJS client is ready for testing on Pectra Devnet 1.
EF DevOps engineer Barnabas Busa stated that the CL client team is fixing bugs from PeerDAS Devnet 1. Once all clients are fixed, Busa said developers plan to restart PeerDAS Devnet 1 this weekend. Stokes shared updates on his pull request (PR) to change the hardcoded blob gas limit on EL and CL. He said he is working to define the PR's impact on CL and EL and formalize it into an Ethereum Improvement Proposal (EIP) for possible inclusion in the Pectra upgrade.
Consensys' TxRx research team has implemented the initial version of their fork choice test generator. This test generator aims to identify bugs in client software that could lead to chain splits and any areas where client software deviates from CL specifications in non-trivial ways. This research is funded by EF. The team, represented by Alexander Vlasov and Mikhail Kalinin, asked for feedback on their work during the call as they seek to refine the test suite and implement more flexible test generation.
