ChainCatcher message, the 171st Ethereum Execution Layer Core Developer Meeting (ACDE) was held on September 28. Ethereum supporter Tim Beiko summarized the meeting, stating that the main topics discussed were:Progress of the Devnet developer testnet (Devnet-9 is expected to go live tomorrow, and the next step is to launch Devnet-10, primarily for testing EIP-7514, which sets the validator activation queue limit Max Epoch Churn Limit to 8, slowing the growth of ETH staking rates to allow time for designing a better validator reward scheme; once completed, it will enter the public testnet phase);Review of the EIP-4788 audit (mainly identified two major issues related to zero timestamps and Ring Buffer size; EIP-4788 aims to allow contracts on the EL to access the CL, primarily related to staking & MEV);Review of the Holesky restart (there were some issues an hour before the launch, but the network gradually stabilized afterward and achieved finality);Introduction of EIP-7503 (to implement privacy transfers of ETH, where users send ETH to a provably unspendable address, and then, using a new transaction type, they can provide proof that they burned the ETH and re-minted it at another address), and the removal of a small note in EIP-6780 (this EIP mainly modifies the functionality of the SELFDESTRUCT opcode, primarily to prepare for future applications of Verkle trees), etc.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 108th Ethereum Core Developers Consensus Meeting. Among them, developers agreed to consider including EIP-4788 and EIP-6987 for testing in Deneb. EIP-4788 will enable consensus layer state proofs on the execution layer for trustless verification via smart contracts. Previously, PR #3175 was in the process of being formatted as an EIP and will be changed to EIP-6987, which aims to prevent slashed validating nodes from being selected as block proposers for security reasons. Developers discussed introducing an additional variable and constant in the Deneb specification to allow the execution layer greater flexibility to adjust the maximum number of blob transactions per block independently of the consensus layer.Ethereum core developer Tim Beiko reminded the consensus layer client teams that it is still uncertain to what extent the new SSZ type introduced by EIP-4844 should be compatible with the upcoming SSZ upgrade or optimized for the current RLP standard.Ryan stated that the use of the "flat hash" SSZ type in EIP-4844 is a lose-lose situation, as it does not format for RLP but also does not take full advantage of complete SSZ serialization. Developers will continue to discuss this issue in next week's ACDE conference call. Additionally, the transformation of the beacon chain proof subnet (attnet) was launched on May 4. Developers also discussed PR #317 on the beacon chain API GitHub repository.In light of the recent MEV-Boost vulnerability attack, relays now verify block content before broadcasting via gossip. This feature requires custom forks for the Lighthouse and Prysm clients. Lighthouse client developer Michael Sproul proposed a standard query parameter to enable the same functionality across all consensus layer clients. Prysm client developer Terence Tsao indicated that introducing such a feature in some respects would increase dependency on MEV-Boost, a temporary software for earning MEV on Ethereum, and it should be deprecated to support PBS. (Source link)