Published Nov. 19, 2026. This update summarizes a protocol developers’ discussion; agenda comments and reported meeting outcomes are not a finalized network upgrade specification.
Ethereum’s All Core Developers Execution call (ACDE #249) met on Nov. 19 with Glamsterdam, Hegotá, and development-network next steps on its agenda. The official public issue records the meeting time and topics, including EIP-8037 feedback, a Besu team position, Hoodi fork timing, and a discussion of Hegotá scope.
Glamsterdam: compatibility questions remain
The Ethereum Foundation’s Nov. 6 update explains that EIP-8037 and EIP-8038 would change gas charges for certain operations and state, and that compatibility risks prompted additional review before Hoodi testing. That is the background to the current discussion; it does not by itself establish a final specification change or activation date.
In the official ACDE #249 agenda and comments, the Besu team’s written position raises concerns about compatibility and describes a narrow specification adjustment as one option. Those comments are a team position in the public issue, not a vote or binding decision by all client teams.
EtherWorld’s same-day meeting report says most execution clients favored keeping the current Glamsterdam specification, while the final go/no-go call was deferred to a later ACDC meeting. That is a secondary account; readers should compare it with the primary agenda and developer comments.
Hegotá: scope is still being discussed
The ACDE agenda also lists a revisit of Hegotá execution-layer scope after Devcon discussions, Frame Transactions, and devnet next steps. The agenda points to consensus-layer FOCIL decisions being handled through ACDC, so the Nov. 19 execution-layer agenda alone does not settle the full fork scope.
The Ethereum Foundation’s Glamsterdam update and the public issue are the best places to follow the technical status. No immediate mainnet action follows from an agenda item or a team comment; builders should wait for published specifications and confirmed test-network dates before making changes.
For earlier context, read our explainer on the Glamsterdam delay and EIP-8037/EIP-8038.


