Yesterday, Ethereum core developers held the 191st All Core Developers Execution (ACDE) conference call. Community member abcoathup shared a summary of the call on the Ethereum forum. Topics discussed included updates on the Pectra upgrade, consideration of EIP-7212 for inclusion in Pectra, and other proposal matters.
The meeting began with updates on the upcoming major upgrade, Pectra. Highlights from the discussion included:
– Preparation for the release of Devnet-1 testnet, awaiting readiness from more clients, expected completion within the next 1-2 weeks.
– Progress on EIP-7702 to be incorporated into Devnet-2 testnet, slated for merging next week. Notably, Devnet-1 will reflect the current specifications of EIP-7702.
Regarding EIP-7212, abcoathup summarized discussions into three points:
– EIP-7212 introduces optimizations for key/wallet management and has garnered broad developer support.
– Consideration for formal inclusion in Pectra was discussed but deferred pending a decision at the next ACDE. Despite its attractive features, alignment with existing extensive functionalities of Pectra remains a consideration.
– Additionally, minor issues with EIP-7212, such as mirroring precompiled addresses in L2 and L1 deployments, are slated for resolution within the next two weeks to facilitate further discussion at the next meeting.
EIP-7212 aims to achieve secure and economically efficient verification of the secp256r1 (P256) curve. Its proposal for Rollups is driven by its significant impact on account abstraction in L2 and the prevalence of SE-based AA wallets on L2.
Other proposals discussed include:
– Adding events to pre-deployed system contracts for cross-layer communication with EIP-7002 and EIP-7251, deemed reasonable and contracts will be updated accordingly.
– Simplifying deployment effects of EIP-7702 and Verkle migrations by deciding to no longer require EIP-158 and ignoring the proposal.
– Further discussions on protocol improvements such as expiration of historical records and changes to Blob mempool to optimize user (e.g., Rollups) blob usage. Regular updates on EIP-4444 progress were also advocated, aiming for smarter handling from blob generation to on-chain inclusion by Rollups and clients.
