All Core Devs - Execution (ACDE) #245, September 10, 2026

Agenda

Meeting Time: Thursday, September 10, 2026 at 14:00 UTC (90 minutes)

GitHub Issue

2 Likes

Video, transcript & chatlog

News coverage

Resources

Meeting Summary:

The AllCoreDevs meeting focused on scoping decisions for the upcoming Hekota hard fork, with a brief update on EIP 8253, which was not added to the Glamsterdam scope. The group reviewed and discussed numerous EIPs, making several DFI (defer for inclusion) decisions on proposals with low client support, such as EIP 7819, EIP 7851, EIP 2488, EIP 8219, EIP 8182, EIP 7645, EIP 8188, EIP 8358, EIP 8115, EIP 8200, EIP 7862, and EIP 7807. Some EIPs, like EIP 7979, EIP 7923, EIP 8163, EIP 8372, and EIP 8304, were delayed for further discussion due to stakeholder interest or the need for more information. The meeting also confirmed that Frame Transactions would be a headliner for Hekota. The process for the next meeting was discussed, with a focus on preparing for CFI (consider for inclusion) decisions on the highest-ranked EIPs.

Click to expand detailed summary

The team discussed EIP 8253, which replaces EIP 7610 for bumping nonce of zero nonce storage accounts. Jochem explained that since it’s a mainnet-only fork with no changes needed for Goerli and Sepolia, it could potentially be added to the Goerli scope. After discussion, the team decided not to last-minute add it to Glamstedam and agreed it should be considered for Goerli instead, with formal decision to be made during the Goerli decision block. The meeting then moved on to discuss the Goerli fork block agenda.

Kamil requested permission to PFI the Fast Payload Broadcast EIP post-deadline instead of Blocks and Blocks EIP, with a decision to be made on the ACDC call next week. The team confirmed Frame Transactions as a headliner for the fork, and Ansgar reviewed the status of various EIPs, noting that Frame Transactions would no longer be discussed as a decision item since it was already SFI’d. The conversation ended with a review of EIP statuses, including six withdrawn EIPs and one open EIP (EIP8360) regarding the TCreate opcode, which requires further discussion to determine its inclusion in the fork.

The team discussed the status of EIP-8360 (TCreate), with Maria clarifying that it should be PFId and Milos offering to champion it. Ansgar proposed reviewing 37 EIPs grouped into five categories, with clients providing brief opinions on each EIP before making decisions. The group agreed to focus on EIPs with clear majority support while giving attention to minority voices on more contentious items, with anything below a 1.0 rating being considered for DFI approval.

The team discussed reviewing and making decisions on EIPs, focusing on DFI and CFI decisions. They agreed to first go through all five pages to make DFI decisions and then conduct a second pass for CFI decisions. Ansgar presented several EIPs for DFI consideration, and the group unanimously rejected four EIPs with low ratings. They also identified three additional EIPs for potential DFI decisions, though the discussion was cut off before reaching a conclusion on these.

The team discussed three EVM-related EIPs, with the main focus on EIP-7979 (control flow) and EIP-7923 (linear memory model). Jochem raised concerns about the process for EVM evolution, suggesting a need for better stakeholder engagement. Greg strongly advocated for implementing EIP-7979, citing its technical benefits and past efforts by himself and others. The group decided to postpone the DFI decision on EIP-7979 and EIP-8163 (extension opcode) to the next meeting in two weeks, ensuring compiler teams and other stakeholders can provide input. Regarding EIP-7923, while Charles presented its merits, client teams expressed that it should not be a priority for the current fork due to its B-tier classification.

The meeting focused on reviewing and deciding on various EIPs (Ethereum Improvement Proposals) for potential inclusion in the next hard fork. Key decisions included:The team decided to delay several EIPs, including EIP-8163 (reserve extension), EIP-8372 (normalized state gas limit), and EIP-8304 (trustless log and transaction index), with plans to revisit them in two weeks. For EIP-7862 (delayed state route), the team made a DFI (Definitely For Inclusion) decision, though with the understanding that it might be revisited in future forks, especially in combination with binary trees.The group also discussed EIP-7807 (SSZ execution blocks) and EIP-8094 (ETHVHashBlobAwareMempool), ultimately deciding to delay decisions on these as well, with plans to reassess them in the next meeting based on further discussion and potential updates from EIP authors and clients.Next steps include clients reviewing the highest-rated EIPs (particularly those with ratings of 2.5 or higher) and preparing to discuss potential CFI (Certainly For Inclusion) candidates in the next meeting. The team aims to finalize scoping decisions before DEFCON.

Next Steps:

  • Ansgar: Async clarify the status of EIP 8360 (TCreate) with Alchemy and Milos, and request client opinions by next call.
  • Kamil: Share links to the Fast Payload Broadcast EIP, relevant Discord discussions, and P2P call discussions in the chat.
  • All client teams: Review and prepare to discuss the highest ranked EIPs (8 EIPs with rating 2.5 or higher) for the next call, including concerns and what would change their minds.
  • All client teams: Async raise concerns about high-support EIPs before the next ACDC call, to allow champions to address them.
  • Piotr: Gather signals from L2s about their interest in EIP 8163 (reserve extension opcode) by the next call.
  • Zsolt (Geth) and EIP 8304 champions: Engage with Besu and Reth teams to discuss the value and implementation of EIP 8304 (Trustless Log and Transaction Index) over the next two weeks.
  • All champions of delayed EIPs (7979, 8163, 8304, 8372): Iterate on their EIPs and form new opinions or gather necessary support by the next call.

Recording Access:

YouTube Stream Links: