ACDE #245 · EIP-8141 Frames Hegota headliner

AllCoreDevs - Execution #245 · 2026-09-10

Frame transactions were confirmed as Hegota's flagship feature.

Frame Transactions (EIP-8141) were officially confirmed as the headliner of the next fork, Hegota. The rest of the time was spent going through 37 EIPs for Hegota scoping and making a large number of DFI decisions that remove them from priority candidacy.

Why it matters

With frame transactions set as the centerpiece of Hegota, client teams can start development and testing work against this spec. At the same time, the fork scope is being narrowed by first excluding low-rated EIPs, which speeds up the schedule of finishing Hegota scoping before Devcon.

Decisions

EIP-8253 excluded from Glam: It was decided not to add EIP-8253 to Glamsterdam late. There is no security urgency, so this nonce adjustment proposal will be handled in Hegota as originally planned, and the request to make it SFI in Hegota immediately was deferred to the scoping block, leaving it only as a candidate.
EIP-8141 headliner: Frame Transactions (EIP-8141) were confirmed as the headliner of Hegota. This formalizes that this EIP, already in SFI status, is the flagship feature of the fork, and the spec is still being refined.
Two AA EIPs DFI: EIP-7819 (set delegate instruction) and EIP-7851 (code-controlled EOA delegation) were excluded (DFI) from Hegota candidacy. Both EIPs had client ratings below 1.0 and no one championed them.
Four EVM EIPs DFI: EIP-2488 (CALLCODE deprecation), EIP-8219 (checked arithmetic opcodes), EIP-8182 (private ETH/ERC-20 transfers), and EIP-7645 (aliasing ORIGIN to sender) were excluded. All four were unanimously rated low by every client (0.0 to 0.8).
EIP-7979 on hold: EIP-7979, which adds call/return opcodes to the EVM, had its decision postponed today. It gets a two-week grace period until the Solidity and Vyper compiler teams give their views on whether they would actually integrate it, and with no progress the default is an automatic DFI.
EIP-7923 DFI: Linear page-based memory pricing (EIP-7923) was excluded. The improvement was acknowledged but judged not a priority, with a caveat that it can be revisited if capacity opens up.
EIP-8163 on hold: EIP-8163, which reserves an EXTENSION opcode for other EVM chains, had its decision postponed by two weeks. The champion must gather real demand signals from L2s and alternative L1s, and if that does not happen, DFI is the default.
Three gas EIPs DFI: EIP-8188 (last write block for accounts and slots), EIP-8358 (per-account change gas metering), and EIP-8115 (batch processing of priority fees at the end of a block) were excluded. All three had low ratings, and only 8115 was backed by Nethermind, which stepped back saying it was not an issue worth fighting for.
EIP-8200 DFI: EIP-8200, which covers turning precompiles into EVM code, was excluded from Hegota. Everyone agreed the direction is good, but the judgment was that it is premature because benchmarks for the replacement bytecode performance are not yet mature.
EIP-8372 on hold: The normalized state gas limit (EIP-8372) was not DFI'd today. It will be decided together with the widely supported EIP-8368 (CPSB recalibration), and the call can be made after observing demand once Glamsterdam is deployed.
EIP-7862 DFI: Delayed state root (EIP-7862) was excluded. The counterargument that parallel computation is possible after the BAL, so the state root is not a major bottleneck, prevailed, and it can be revisited in a future fork together with the binary trie work.
EIP-7807 DFI: SSZ execution blocks (EIP-7807) were excluded. The reason is that all code reading headers and blocks would have to change, so the blast radius is large while the user benefit is small.
EIP-8304 on hold: The trustless log and transaction index (EIP-8304) had its decision postponed by two weeks. Besu and Reth agreed to join the discussion asynchronously, and with no progress DFI is the default.
EIP-8094 DFI: The blob-aware mempool (EIP-8094) was excluded. The author themselves agreed to the DFI, saying most of its core features have already been absorbed into the sparse blobpool.

Discussion

Whether to include EIP-8253 in Glamsterdam

A late proposal came up to include EIP-8253, which replaces the DFI'd EIP-7610, in Glamsterdam, so the call opened by deciding how to handle it.

Outcome: Excluded from Glamsterdam; the Hegotá SFI decision deferred to the scoping block 00:20:31

Whether to keep the EIP-7979 call/return opcodes alive

EIP-7979, which adds call/return to the EVM, was rated low and landed just before DFI. The champion and some developers asked to defer the decision, saying this is a structural problem where EVM-only EIPs get pushed aside.

Outcome: Decision deferred (neither DFI nor CFI today) 00:45:03

EIP-8200 precompiles as EVM bytecode

EIP-8200, which replaces precompiles with formally verified EVM bytecode, was discussed as preparation for ZK EVMs, but the performance case is not yet mature, so whether to include it in Hegotá was weighed.

Outcome: DFI decision 01:10:35

EIP-8304 trustless log and transaction index

On EIP-8304, which opens verifiable range queries over events, the argument that there is no immediate demand but trustlessness is a core property of Ethereum clashed with the debate over benefit versus workload.

Outcome: Decision deferred (Besu and Reth to participate asynchronously, default is DFI) 01:38:10

Glossary

SFI (Scheduled For Inclusion): Scheduled for inclusion in the fork
CFI (Considered For Inclusion): Candidate under consideration for inclusion
PFI (Proposed For Inclusion): Accepted and retained as an inclusion candidate
DFI (Declined For Inclusion): Dropped from fork candidates
Headliner: A fork's flagship feature
Champion: The person responsible for the proposal who drives it forward
BAL (block access list): The list of accounts and slots a block accesses
Blast radius: The scope of impact a change has on other code

EIPs covered

Forkcast record · Recording · ← Core Dev Calls