Ethereum Protocol Update: ACDE #249

Ethereum ACDE #249 weighs Glamsterdam compatibility risks, narrows Hegotá’s scope around Frame Transactions, and advances post-quantum security plans.

Ethereum Protocol Update: ACDE #249
Ethereum Protocol Update: ACDE #249

Ethereum developers leaned toward retaining Glamsterdam's existing specifications despite smart contract compatibility concerns, narrowed Hegotá's potential scope around Frame Transactions, and advanced plans for native post-quantum signatures. Although no final decision was reached on Glamsterdam's specifications, most execution clients supported proceeding without changes.

Hegotá discussions also revealed a preference for prioritizing Frame Transactions alongside selected post-quantum improvements rather than pursuing an expansive upgrade. The meeting established several immediate priorities, including a pending Hoodi fork decision, a narrower Hegotá scope discussion, and the postponement of combined execution-consensus devnets until FOCIL's direction is settled.

Glamsterdam's Existing Specification Remains the Preferred Path

No Glamsterdam specification change received majority support. Most execution clients favored retaining the current specification, while the final go/no-go decision was deferred to the next ACDC meeting.

The central concern involves EIP-8037, which changes gas accounting for creating new Ethereum state. Although intended to improve the sustainability of state growth, the proposal has exposed compatibility risks involving contracts that depend on existing gas behavior.

Following the concerns reported during ACDE #248, the Ethereum Foundation, ChainSecurity, and Dedaub contacted more than 50 affected companies. The remediation effort targets high-severity issues by mid-December and medium-severity issues by January 10, 2027.

Developers considered modifying the specification to reduce these risks. One frequently discussed approach involved removing mid-transaction gas refunds.

However, Marius warned that eliminating those refunds could introduce additional breakages for applications relying on gas being returned during transaction execution. Consequently, even a narrowly targeted change could create an unpredictable impact across existing smart contracts.

Client positions reflected this trade-off:

  • Geth, Nethermind, Reth, and ethrex favored preserving the existing specification and schedule.
  • Erigon preferred making specification changes.
  • Besu reluctantly accepted the current specification during the discussion, despite previously advocating a narrower modification.

Besu's written position specifically emphasized Ethereum's backward compatibility and raised concerns about contracts using try/catch-style execution behavior. The broader issue is that any specification change would require another development, auditing, and testing cycle. As previously explored in ACDE #244, late-stage modifications can significantly affect upgrade readiness.

Mid-January 2027 is now the earliest estimated mainnet window if the current specification remains unchanged. Late January or early February was considered more realistic.

The Hoodi fork is tentatively targeted for the week of December 14, potentially December 16–17, subject to confirmation at the next ACDC meeting. For now, developers are prioritizing remediation and impact analysis over an immediate specification rewrite.

Hegotá Moves Toward a Frames-Centered Upgrade

Developers eliminated the option of dropping Frame Transactions to directly enshrine post-quantum functionality. The emerging preference is for a focused Frames bundle, potentially accompanied by selected additional EIPs.

Following Devcon discussions, developers revisited five possible configurations for Hegotá's execution-layer scope. The broad landing zone emerged between option 3, comprising the core Frames bundle, and option 4, allowing Frames alongside selected additional proposals.

Option 1, which would remove Frames in favor of directly enshrined post-quantum functionality, received no support. This reinforces the importance of EIP-8141: Frame Transactions, selected as Hegotá's execution-layer headliner during ACDE #245.

Frames introduce a more flexible transaction structure designed to enable native account abstraction, including programmable authorization and alternative signature verification mechanisms. Besu and ethrex favored keeping the scope close to the existing Bogotá devnet-2 implementation while introducing selected post-quantum capabilities, including leanSPHINCS and signature aggregation.

Nethermind expressed a different preference: reducing the scope would only be worthwhile if doing so meaningfully accelerated delivery. Another compatibility concern emerged around EIP-8151: Account Code Restricted ecRecover.

Preliminary analysis suggested that numerous existing contracts depend on behavior potentially affected by the proposal. Developers therefore questioned whether it could safely remain within Hegotá's scope.

Greg Colvin argued that repeatedly removing or postponing EIPs creates planning difficulties for proposal champions who have invested substantial development resources. He suggested that adjusting fork dates could sometimes be preferable to dropping proposals.

Post-Quantum Signatures Advance Without Requiring Aggregation at Launch

Developers discussed a minimal leanSPHINCS implementation for Frame Transactions that could introduce native post-quantum authentication without waiting for a complete signature aggregation system. No formal inclusion decision was recorded.

Iván from ethrex introduced a proposal for integrating leanSPHINCS signatures directly into EIP-8141. The proposed implementation would remain compatible with EIP-8288, allowing future signature aggregation mechanisms without requiring aggregation in the initial implementation.

The proposal, tracked through Ethereum EIPs PR #12672, is targeting Proposed for Inclusion consideration at the next ACDE meeting. Two significant Frames specification questions remain unresolved, i.e., compatibility with EIP-8288's signature-list architecture and the tree-root hashing scheme.

These design decisions matter because Ethereum is attempting to introduce post-quantum security without locking the protocol into a single authentication mechanism. The cryptographic discussion centered on hash-based leanSPHINCS versus lattice-based ML-DSA.

The Ethereum Foundation cryptography team considered hash-based cryptography the more conservative approach. However, lightclient questioned whether leaning heavily on a non-standardized scheme could create long-term adoption challenges, drawing comparisons with Ethereum's historical reliance on the K1 elliptic curve.

ML-DSA offers a standardized alternative, but verification remains expensive under current implementations. Developers discussed estimated verification costs of approximately 800,000 gas with Keccak-based optimizations and 1.6 million gas using NIST SHAKE.

As explored in Vitalik Endorses LeanPCS for EIP-8288, aggregation technologies could eventually help reduce the on-chain burden of post-quantum signature verification. The topic also builds on Vitalik Buterin Backs EIP-8288 for Ethereum, which examined the proposal's broader cryptographic flexibility.

Combined Hegotá Devnets Remain Paused Pending FOCIL Decision

No combined execution-consensus Hegotá devnet will proceed until ACDC determines the direction of FOCIL. Execution-layer-only devnets can continue independently, with their scope frozen by default.

The decision establishes a dependency between Hegotá's execution-layer development and its consensus-layer priorities. EIP-7805: Fork Choice Enforced Inclusion Lists (FOCIL) aims to strengthen Ethereum's censorship resistance through transaction inclusion guarantees enforced by fork-choice rules.

Because FOCIL affects consensus-layer behavior, developers agreed that combined testing should not advance before its direction is resolved. FOCIL's importance was established during ACDC #175, when it was selected as Hegotá's consensus-layer headliner.

For the execution layer, developers agreed to pause expansion beyond the current devnet scope by default. The All Core Devs Testing group may approve cleanup EIPs if sufficient consensus emerges, but broader additions remain discouraged until the upgrade's scope becomes clearer.

This approach builds on the phased testing strategy described in ACDC #190. Several responsibilities now follow directly from the meeting:

  • Erigon and Besu: Submit concrete Glamsterdam specification-change proposals with impact analysis.
  • Execution client teams: Provide concise positions on Hegotá scope options 2–5.
  • Spencer: Prepare quantitative impact assessments for proposed Glamsterdam specification changes.
  • Frames contributors: Aim to finalize major Frames specification changes before the holiday break.
  • Consensus developers: Resolve the FOCIL question before combined Hegotá devnet testing advances.

The immediate priority remains Glamsterdam's specification and Hoodi activation decision. The recent ACDC #191 discussion similarly highlighted the increasing importance of post-quantum readiness in Ethereum's roadmap.


If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.

Join the EtherWorld & Avarch Internship Program and build your career in blockchain, content, social media, video, podcast editing, or operations. Send your resume and brief introduction to contact@etherworld.co.


Disclaimer: The information contained in this website is for general informational purposes only. The content provided on this website, including articles, blog posts, opinions, & analysis related to blockchain technology & cryptocurrencies, is not intended as financial or investment advice. The website & its content should not be relied upon for making financial decisions. Read full disclaimer & privacy policy.

To stay updated on blockchain news, Ethereum protocol progress, and our latest stories, subscribe to our weekly digest and YouTube channel for ELI5 content.

To promote your Web3 articles, events, project updates, and Press Releases, reach out anytime via EtherWorld PR for submissions and collaboration. For other queries, email contact@etherworld.co.

If you’d like to support our work, share the content and consider donating at avarch.eth.

Join our community on Discord and follow us on Twitter, Facebook, LinkedIn & Instagram.

Sponsored
ETHShala

Understand Ethereum. Shape the Future — learn EIPs with ETHShala.

Inviting Web3 projects to partner with EtherWorld and increase visibility across the Ethereum ecosystem.

EIPs Insight

Track Ethereum protocol upgrades, EIPs & governance — all in one place.

EtherWorld.co × Avarch

Gain hands-on Web3 experience with our internship program.

Subscribe to join the discussion.

Please create an account to become a member and join the discussion.

Already have an account? Sign in

Sign up for EtherWorld.co newsletters.

Stay up to date with curated collection of our top stories.

Please check your inbox and confirm. Something went wrong. Please try again.
0/5 free articles read this week
Sign up free