The latest updates on Ethereum execution layer are here. The 228th core developer meeting(ACDE) was just held, and several important decisions are worth noting.

First is the EIP-7843(slot opcode) proposal, which involves coordination between the consensus layer and execution layer. It has been temporarily deferred to be included in BALs Devnet-2. What does this mean? Simply put, although this feature has been added to the agenda, more time is needed to complete cross-layer validation.

Another piece of news is that all seven EIPs proposed in this round were ultimately rejected from the Glamsterdam upgrade. This is not bad news — it indicates that the development team is carefully evaluating the necessity and stability of each proposal.

It is worth mentioning EIP-7954, which concerns the bytecode limit for smart contracts — expanding from 24KB to 32KB. This adjustment may seem like a technical detail, but it directly impacts the deployment capabilities of complex DeFi contracts. Relaxing the bytecode limit means developers have more space to implement more complete functionalities and more complex on-chain logic.

The core focus of this meeting was balancing innovation and stability — some proposals are interesting but not yet mature enough in terms of timing and technology. The next upgrade direction of the Ethereum ecosystem is gradually becoming clearer through these decisions.