Ethereum developers

Latest content from the Ethereum core developer meeting: Devnet update progress, EIP-7514 confirmed as part of the Dencun upgrade, etc

ChainCatcher message, Ethereum core developer Tim Beiko summarized the latest Ethereum core developer execution meeting (ACDE), which introduced Devnet updates, new content for Dencun, and provided a comprehensive overview of Reth:Devnet-8 Status Update: The network is being finalized, and many clients have begun pushing new updates to it. Meanwhile, testing of the MEV/block building process has started using the developer tool system Kurtosis. Nethermind shared that their blob transaction pool is ready, and after a few days of testing on a single node, they have deployed it to all Dencun test nodes. Geth's blob transaction pool is also nearing completion. Besu is conducting broader maintenance on its transaction pool (to limit the size of Blob + non-Blob transactions), which is expected to be released in the next version. Erigon is still developing its pool, aiming to be ready for devnet-9.The meeting continued the discussion from last week's ACDC call regarding whether to add a constant cap to the validator activation queue. Subsequently, the proposal was officially named EIP-7514 (Add Maximum Epoch Loss Limit). In short, this would slow down the growth rate of the ETH staking percentage in the worst-case scenario.The meeting discussed another last-minute proposal: adding an opcode to the EVM to reveal the base fee of blobs. We have a similar opcode that can reveal the BASEFEE of EIP-1559, which was introduced simultaneously with the activation of the EIP. This allows L2 to more easily determine the correct gas price to charge users based on L1 data costs.The meeting discussed some updates to EIP-4788, which stores the beacon root in contracts on the EL. Over the past few weeks, we have conducted multiple audits and fuzz tests on the contracts, leading to some subtle changes described in this PR. The first is to explicitly handle a 0 timestamp, rolling it back (like other invalid timestamps) instead of returning 0. The second change is the buffer size. Assuming the slot time has changed, considering how modulo works, the original contract would lead to storage waste. By using a prime number (8191), it should utilize 100% of the buffer regardless of the slot time. Finally, gas optimizations were made to reduce the number of times CALLDATA needs to be loaded. Auditors will review these changes, and the final report is expected before the next ACDE. To ensure the smooth progress of fuzz testing and implementation, developers agreed to merge the proposed changes now.The meeting discussed how clients should handle cases where the system contract address is part of the state but is empty at the end of execution. Although this is practically impossible on the mainnet, it is an edge case that arises in testing by setting the address at genesis. Given the uniqueness of this edge case and the lack of explicit normative behavior, developers agreed to spend more time thinking about this issue and continue the discussion in Monday's testing call. This is a specification change.All of the above content is planned to be included in devnet-9. The client teams unanimously agreed that everything should be implementable and testable before next week's ACDC. The release date for devnet-9 will be agreed upon in that call.

The 111th Ethereum Developer Consensus Meeting has confirmed that the scope of the Cancun upgrade includes 6 improvement proposals, including EIP-4844

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 111th Ethereum Core Developers Consensus Meeting. This meeting finalized the scope of the Cancun upgrade, including EIP-4844 (proto-danksharding) and EIP-4788, EIP-6988, EIP-7044, EIP-7045, and EIP-4788. Additionally, developers suggested increasing the maximum effective validator balance from 32 ETH to 2048 ETH and raising the maximum blob count per block from 4 to 6.First, developers discussed which CL-centric EIPs to include in Deneb. Teku developer Mikhail Kalinin provided an update on EIP-6988, which proposes a code change to prevent slashed validators forcibly ejected from the network from being selected by the protocol as block proposers. EIP-7044 proposes a code change to improve the staking experience, ensuring that signed validator exits remain permanently valid. EIP-7045 proposes a code change to enhance network security by expanding the inclusion range of proof slots. EIP-4788 proposes a code change to improve the staking experience by publicly disclosing the root of beacon chain blocks, which contain EVM internal chain state information for trust-minimized access by DApp developers. Ethereum Foundation researcher Alex Stokes stated that there are plans to merge the aforementioned three EIPs into the Deneb specification in the coming weeks and encouraged CL client teams to review them as soon as possible.Meanwhile, the CL client teams have agreed to test the increased blob count on the next EIP-4844 testnet Devnet 6 and will make a final decision on this matter within two weeks. In relation to the discussion around the maximum blob count, Nimbus developer arnetheduck raised the issue of increasing block reorganization on the mainnet after the Shanghai upgrade. arnetheduck proposed considering changing the 4-second deadline to aggregate validator proofs and send them through the network, and decided to investigate further.Ethereum Foundation researcher Michael Neuder proposed removing the 32 ETH staking cap to help reduce the growth of the active validator set. Developers discussed the potential drawbacks of this change and the possibility of launching partial and full withdrawals directly from the EL as part of the proposal for smart contract initiation. Developers agreed to continue discussing the implementation details of asynchronously changing the effective balance of Ethereum validators on ETHMagicians and Discord. Additionally, Ethereum core developers held their first coordination call regarding the launch of the Holesky testnet, which is expected to replace the existing Goerli testnet by the end of the year. (source link)

Ethereum developers announced that the Shapella upgrade will be activated on the Sepolia testnet on February 28

ChainCatcher news reports that according to the latest official announcement, the core developers of the Ethereum blockchain plan to conduct the Shanghai+Capella upgrade on the Sepolia test network on February 28 at epoch 56832. Shanghai+Capella, also known as Shapella, aims to enable ETH withdrawals from network validators, a feature that was not enabled during the network's transition to PoS consensus ("the Merge").This upgrade combines changes to both the execution layer (Shanghai) and the consensus layer (Capella). In order to complete the final upgrade in March, developers plan to conduct multiple phases of public testing. The upcoming release on Sepolia is the second public testnet for the deployment upgrade.Earlier this month, Shapella was tested on the Zhejiang testnet. After deploying Shapella to the Sepolia testnet, developers expect to transition to the Goerli testnet for the final phase of testing before the mainnet release in early March.Previously, ChainCatcher reported that the Ethereum Foundation stated in a recently published article that the Shanghai+Capella (Shapella) mainnet upgrade is entering its final pre-release sequence—public testnet. Shapella includes many features, but the most important for stakers and the consensus layer is the support for withdrawals. Exiting validators can withdraw their full balance, while active validators with a balance exceeding 32 ETH can make partial withdrawals. Additionally, the first long-standing public testnet, Sepolia, is scheduled for an upgrade on February 28. (source link)
ChainCatcher Building the Web3 world with innovators