Yesterday, Ethereum core developers conducted the 191st All Core Developers Execution (ACDE) conference call. Community user abcoathup shared a summary of the call on the Ethereum forum. The summary included updates on the Pectra upgrade, the consideration of EIP-7212 for inclusion in the Pectra upgrade, and other proposal discussions.
The meeting commenced with discussions on the upcoming significant upgrade, Pectra. Key points from the meeting include:
– Prior to the release of Devnet-1 testnet, readiness of more clients is awaited, expected to be completed in the next 1-2 weeks.
– The latest developments of EIP-7702 will be integrated into devnet-2 testnet, anticipated to be merged within the coming week. Notably, devnet-1 testnet will reflect the current specifications of EIP-7702.
Turning to EIP-7212, abcoathup summarized the discussion into three points:
– EIP-7212 introduces several optimizations concerning key/wallet management, garnering broad developer support.
– We deliberated on formally incorporating it into Pectra but decided to defer the decision to the next ACDE meeting. Despite its beneficial features, EIP-7212 requires careful consideration alongside the extensive functionalities already present in Pectra.
– Additionally, EIP-7212 has minor issues to resolve, such as mirroring precompiled addresses between L2 and L1 deployments, which will be addressed within the next two weeks for further discussion in the subsequent meeting.
EIP-7212 aims to achieve secure and economically efficient verification using the secp256r1 (P256) curve. Its proposal for Rollups is driven by its significant impact on account abstractions in L2 and the prevalence of SE-based AA wallets on L2.
Furthermore, the meeting discussed several proposals, including:
– Adding events in pre-deployed system contracts to facilitate cross-layer communication with EIP-7002 and EIP-7251. Developers unanimously agreed that this change is justified, and relevant contracts will be updated.
– To streamline the deployment effects of EIP-7702 and Verkle migration, developers decided to no longer require EIP-158 and to disregard that proposal.
Additionally, developers discussed progress in other protocol improvements, such as expiry of historical records and changes to Blob mempool to optimize blob usage for users like Rollups. There were also calls for regular updates on the progress of EIP-4444, hoping for smarter handling of processes from blob generation to on-chain inclusion by rollups and clients.
Related Reports
Latest Ethereum Meeting: Pectra Upgrade Scheduled for Q1 2025, Including EVM Improvement Proposals EOF and EIP-7702
Implementing Account Abstraction: What is EIP-3074 Included in the Ethereum Prague Upgrade, and Its Impact on Wallets and DApps