At ACDE #165, Ethereum developers discussed a hoop buffer, builder protection flags for the engine API, progress on Cancun/Deneb testing efforts, and influence evaluation on EIP-6466 and 6406.
First, the two code modifications EIP-6466 and EIP-6406 switch the information encoding in the two block header fields transactions root and receipts root from RLP to SSZ.
A comparison of the effects of EIP-6466 and EIP-6406 on deployed and actively used smart contracts on Ethereum was conducted by the security auditing firm Dedaub.
According to the analysis, three crucial tasks—LayerZero, zkBridge (cross-chain bridge), and Oracle—will be impacted by the SSZ replacement. Although the applications were impacted, Dedaub director Neville Grech stated that all three applications could be modified to take into account the code changes implemented by EIP-6466 and 6406.
Parithosh Jayanthi, a DevOps engineer on the Ethereum Basis, recognized that the Cancun/Deneb improvement was successfully published on June 30 in relation to the Cancun/Deneb test. A few issues with the customer implementation have been found, and the testnet is being successfully completed.
After the customer team resolves the outstanding issues, Jayanthi said he’ll try to send blob transactions to the network for a prolonged length of time to see how the network responds to the load of three goal blobs/block (up from the goal of two blobs/block during the last testnet).
Mikhail Kalinin, a developer for Teku (CL), asked the EL customer team if they would be willing to accept the engine API changes in the Cancun improvement regarding the addition of builder override flags. In order to voice their objections to their inclusion in Cancun before July 10th, Kalinin is requesting that customer groups review the builder flag Engine API changes on GitHub.
If there are no objections to this change, Kalinin acknowledged that he would provide the necessary modifications to the Engine API specification for inclusion in the Cancun/Deneb upgrade; modifications to the Engine API won’t be recorded as EIPs.
Additionally, EIP-4788 adds a new recompilation, a cheap reasonable contract process that can reveal information about CL on EL to avoid overusing storage space through code changes.
This feature will open up a variety of use cases for decentralized applications that benefit from trust-minimized access to CL state, such as staking pools and re-staking protocols.
The adjustment may be incorporated into the final EIP-4788 specification for implementation in Cancun as soon as possible, according to Ethereum Basis researcher Alex Stokes.
