Author: Christine kim; Translated by: Vernacular Blockchain
On January 16, 2025, Ethereum protocol developers held the 203rd All Core Developers Execution (ACDE) meeting via Zoom. This week's meeting was hosted by Tim Beiko, head of protocol support at the Ethereum Foundation (EF). The ACDE meeting is a biweekly meeting series where developers discuss and coordinate changes to the Ethereum Execution Layer (EL).
At the 203rd ACDE meeting, developers discussed the launch of Pectra Devnet 5 and the unfinished Pectra specification updates. They also discussed the next steps for testing the increase in the Gas limit on the Holesky testnet, progress in RPC standardization, and specifications for minimum hardware and bandwidth requirements for nodes.
1. Pectra Devnet 5 Launch
Developers launched Pectra Devnet 5 half an hour before the meeting. Parithosh Jayanthi, developer operations engineer at the Ethereum Foundation, said he found gas estimation issues in the development network and planned to collect relevant logs and share the issues in the Ethereum R&D Discord channel.
2. Pectra specification update
Developers discussed five unfinished updates to the Pectra code specification:
1) EIP 7623: Increase Calldata cost The first update is a modification to EIP 7623 to clarify how Gas refunds are handled. The update has been merged on GitHub and incorporated into the testing of Pectra Devnet 5.
2) EIP 7840: Add Blob Scheduling to Execution Client Profile The second update concerns the base fee fraction in EIP 7840. There were no objections at the meeting, and developers agreed to merge the relevant changes into GitHub before the Pectra testing meeting on January 20 (next Monday).
3) Update of Blob Base Fee The third update is also related to Blob Base Fee, involving how to calculate excess Gas during Pectra activation. Alex Stokes, head of research at the Ethereum Foundation, explained that the calculation relies on information from the previous block header. If the change in Blob capacity is activated on the fork boundary (Pectra activation block), the excess Gas calculation will be based on the information of the previous block built using the old fork rules. Stokes believes that it is necessary to clarify whether the Blob capacity increase is activated at the fork boundary or one block after the fork boundary. "It doesn't matter which way we choose, but we need to unify our approach," he said. Developers unanimously agreed to clarify EIP 7691, setting the effective time of the Blob capacity increase to one block after the fork boundary, so that only the new fork rules are used for calculations. Ethereum test developer Mario Vega said that the client is testing this logic. Geth developer "Lightclient" promised to update EIP 7691 before the test meeting next Monday.
4) EIP 2537: Precompilation cost calculation for BLS12-381 curve operations The fourth update is related to the multiplication cost calculation in EIP 2537. Developers agreed to explicitly specify the calculation as integer division in the EIP. Client teams that have passed the Pectra Devnet 5 test should have implemented this logic in the code, so only modifications are needed in the specification. Ethereum virtual machine developer Paweł Bylica said that he will make changes to the EIP on GitHub and complete it before the test meeting next Monday.
Through these updates, developers continue to improve and coordinate Pectra-related work, paving the way for future Ethereum mainnet upgrades.
5) Finally, the fifth update is related to EIP 7702, which aims to add a new transaction type that allows external accounts (EOAs) to set code permanently. Julian Rachman, COO of Otim Labs, proposed a behavioral modification to this EIP, namely enabling code introspection. According to the document written by the Otim Labs team, code introspection refers to the ability of legacy contracts to inspect their own bytecode or the bytecode of external contracts and adjust their behavior based on that information.
Although the Ethereum Virtual Machine Object Format (EOF) development team plans to disable code introspection in future Ethereum upgrades, it is mentioned in the document and meeting that enabling code introspection to check the "delegate_address" of the EOA will not hinder the development of EOF. The benefit of allowing code introspection to check the delegate address of EIP 7702-type transactions is that it supports the safe use of relayers and other external accounts when EIP 7702 features such as gas sponsorship are enabled.
Geth developer "Lightclient" supported the inclusion of this update in the Pectra specification. He said: "This update is very easy to implement. We are already determining whether an account is an EIP 7702 delegate account, and it is a very simple thing to add a specified return address." Meeting moderator Beiko suggested that participants spend a few more days reviewing the changes before deciding whether to include them in the final specification. He suggested revisiting this topic at the testing meeting next Monday.
Beiko also asked Rachman's team to formally submit a pull request containing all EIP 7702 modification proposals on GitHub for developers to discuss on Monday. As for whether this update requires developers to start a new Pectra development network for testing, Jayanthi said that the change can be included in the shadow fork of the public test network without starting a new development network. Beiko added that all other specification updates discussed at the meeting also do not require a new Pectra development network, so developers can move forward with updates to the public testnet after further testing of Pectra Devnet 5 is complete.
3. Pectra system contract audit update
Fredrik Svantes, a protocol security researcher at the Ethereum Foundation (EF), said that all third-party audits of the Pectra system contracts have been completed. The audit found no major issues, and the relevant reports will be uploaded to GitHub for review by the client team. Svantes suggested that a special time be scheduled at the next ACDE meeting for auditors to present their audit results and answer questions from the client team.
4. Pectra testnet upgrade plan
Tim Beiko proposed a preliminary timetable for the testnet upgrade. He suggested that the next two ACD meetings be used to determine the block height for upgrading the Sepolia and Holesky testnets, and that the client release be prepared by February 3, 2025. The Sepolia fork is scheduled for the week of February 12, followed by the Holesky fork in the week of February 19. If there are no major vulnerabilities or issues, the Pectra upgrade may be launched on the Ethereum mainnet in early to mid-March, which is about three to five weeks after the Holesky fork. No one in the meeting opposed this proposal, and Stokes also suggested that the client release be tied to the Sepolia and Holesky testnet upgrades.
5. Holesky Gas Limit
EF General Engineer Sophia Gold proposed to set the default Gas limit of the client in the Holesky upgrade release to 36 million (36m), and continue to increase the default Gas limit of Holesky so that it is always higher than the Gas limit of the Ethereum mainnet. This will ensure that any increase in the mainnet Gas limit can be tested on Holesky, and no one in the meeting opposed the proposal. Representatives from the Teku, Besu, Prysm, and Nethermind teams said that their Holesky client releases have set the default Gas limit to 36 million.
6. RPC standardization efforts
Geth developer Felix Lange is disappointed that the client team has not given enough feedback on the Ethereum JSON-RPC specification standardization efforts. One of the issues he mentioned at the meeting was the lack of a clear definition of the scope of RPC standardization and which ecosystem stakeholders should be included. Lange detailed his standardization efforts and next steps in a blog post. Beiko suggested further discussing this issue on Discord and arranging a workshop for this. Besu developer Justin Florentine said he would be responsible for coordinating the timing of the workshop.
7. Node Hardware and Bandwidth Requirements Specification
EF Application Researcher Kevaundray Wedderburn requested feedback on its documentation on the minimum hardware and bandwidth requirements for Ethereum nodes. Beiko asked whether these requirements should be drafted in the form of an informative EIP for reference by developers and the broader Ethereum community. Prysm developer "Potuz" pointed out that the hardware requirements for validating nodes and full nodes are different, so the document should clearly distinguish between the two. Beiko agreed with Potuz's point of view and suggested further discussion on Discord on node hardware and bandwidth requirements and the next steps for formalizing Wedderburn's document.
8. EIP Editing Workshop
Finally, the meeting mentioned a special workshop on the EIP editing process, but the specific content and timing have not yet been determined and may be discussed in further detail in subsequent meetings.
The Ethereum Cat Herders team will host an EIP editing workshop on January 17, 2025 at 16:00 (UTC). This meeting will provide an overview of the EIP editing process, and all Ethereum community members interested in the EIP workflow and editing process are welcome to participate. The recording of the meeting will be uploaded to YouTube after the meeting for everyone to watch.
