The 113th Ethereum Core Developers Consensus Meeting: The next CL upgrade after Dencun will be named starting with "E"
ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 113th Ethereum Core Developers Consensus Meeting, where developers discussed potential measures to reduce validator attrition limits, specifically the rate at which validators can enter and exit the beacon chain, in order to slow the growth of the validator set and timely complete the Deneb/Cancun (Dencun) upgrade. First, regarding the Deneb test upgrade. Devnet #7 is a dedicated test network for EIP 4844, which has been active for two weeks. So far, almost all combinations of EL and CL clients have been tested, except for the Erigon (EL) client. The blockchain explorer used for tracking Blob data on Devnet #7 has been updated. As for Devnet #8, it will include testing for the entire Dencun EIP feature set, not just EIP 4844. Once the client version passes Hive testing, developers will first launch a local testnet before launching Devnet #8. While conducting Dencun testing, developers are also continuing to explore different optimizations for the Ethereum peer-to-peer layer by introducing blob transactions.Developers also discussed the naming of Ethereum upgrades after Dencun, with the next EL upgrade after Cancun being called Prague, and the CL upgrade being conventionally named after stars. Given that the CL upgrade after Deneb will be the fifth hard fork upgrade of the beacon chain, the CL upgrade will start with the letter "E," with Electra currently being the most favored among developers. Additionally, there is a separate GitHub issue to track EIPs that will be considered for inclusion in the CL upgrade after Deneb, including EIP-6110 (appending validator deposits to the EL block structure and transferring the responsibility of included deposits to EL), EIP-7251 (increasing the maximum effective balance of validators), EIP-7002 (creating a new precompile to trigger validators to exit from EL), Verkle trees (replacing Merkle Patricia trees with Verkle trees for more efficient proofs), Big EOF (a series of upgrades to the EVM), RLP to SSZ (updating Ethereum EL block serialization format to reflect the same scheme used with CL), and BLS signatures (creating new precompiles for BLS signatures and SNARK verification). In the coming months, developers will begin discussing the proposed EIPs mentioned above, as well as any other EIPs proposed in the GitHub issue, prioritizing the inclusion of a subset in the next Ethereum upgrade after Dencun.Developers also discussed the standardization work of the open-source development tool Web3Signer, built by Consensys, which is used to remotely sign transactions across multiple protocols using private keys stored on separate cryptographic devices, including Ethereum EL, the beacon chain, or Filecoin. Finally, an anonymous developer from the Lodestar (CL) client team, known as "Dapplion," shared a proposal to limit the growth rate of the validator set, as Ethereum does not wish to have a large validator set size. Dapplion's suggestion is to restrict the attrition limit to 12 validator entries and exits per epoch. Currently, as the size of the active validator set grows, the attrition limit increases exponentially. By setting a cap on validator attrition, developers can effectively reduce the growth rate of the validator set. There was extensive discussion among developers regarding this proposal. (Source link)