The 113th Ethereum Core Developer Consensus Meeting: After Dencun, the next CL upgrade of Ethereum will be named at the beginning of "E"

Christine Kim, Vice President of Galaxy Research, published an article summarizing the 113th Ethereum Core Developers Consensus Meeting. Developers discussed the possibility of reducing the verifier loss limit, that is, the rate at which verifiers enter and exit on the beacon chain, so as to slow down the increase in the size of the verifier set. growth, and complete the Deneb/Cancun (Dencun) upgrade in time. First, about the Deneb test upgrade. Devnet #7 is a dedicated testnet for EIP 4844 and has been active for two weeks. Almost all EL and CL client combinations have been tested so far, with the exception of the Erigon (EL) client. The blockchain explorer for Devnet #7 tracking blob data has been updated. As for Devnet #8, that will include tests for the entire Dencun EIP feature suite, not just EIP 4844. Once the client version passes the Hive tests, the developers will first launch a local testnet, followed by Devnet #8. In parallel to the Dencun test, the developers are continuing to explore different optimizations for the Ethereum peer-to-peer layer by introducing blob transactions. The developers also discussed the name of the Ethereum upgrade after Dencun, the next EL upgrade after Cancun will be called Prague, and the CL upgrade is agreed to be named after the star. Given that the CL upgrade after Deneb will be the fifth hard fork upgrade of the beacon chain, and the CL upgrade will start with the letter "E", the most popular among developers seems to be Electra. Additionally, there is a separate GitHub issue for tracking EIPs that will be considered for inclusion in CL upgrades after Deneb, including EIP-6110 (Append validator deposits to EL block structure and transfer responsibility for deposit inclusion to EL ), EIP-7251 (increase validator's max effective balance), EIP-7002 (create new precompilation to trigger validator exit from EL), Verkle tree (replace Merkle Patricia tree with Verkle tree, provably more efficient), Big EOF (a series of upgrades to the EVM), RLP to SSZ (updates the Ethereum EL block serialization format to reflect the same scheme as that used by CL), BLS Signatures (creates new precompiles for BLS signatures and SNARK verification) . Over the next few months, developers will start discussing the proposed EIPs above, as well as any other EIPs proposed on GitHub issues, and prioritize a subset for inclusion in the next Ethereum upgrade after Dencun. Developers also discussed standardization work on Web3Signer, an open-source development tool built by Consensys for remotely signing transactions across multiple protocols using private keys stored on a separate cryptographic device, including Ethereum EL, Beacon Chain Or Filecoin. Finally, an anonymous developer named "Dapplion" from the Lodestar (CL) client team shared a proposal to limit the growth rate of the validator set, because Ethereum does not want to have a large validator set size. Dapplion's proposal is to limit churn to 12 validator entries and exits per epoch. Currently, the churn limit grows exponentially as the size of the active validator set grows. By setting a cap on validator churn, developers can effectively reduce the growth rate of the validator set. The developers had extensive discussions about this proposal.