Ethereum’s Glamsterdam timetable hinges on smart-contract compatibility

Could changes meant to improve Ethereum’s capacity also disrupt contracts already running on the network? That was the question facing developers in discussions reported on November 20, 2026. Glamsterdam remained a planned hard fork, not an activated upgrade, and its specifications and launch date had not been settled.

The concern centered on EIP-8037 and EIP-8038, proposals to change gas pricing. In October, security firm ChainSecurity warned that the changes could disrupt existing smart contracts and potentially expose them to exploitation. Developers subsequently postponed the Hoodi testnet fork, which had been scheduled for October 26. Researchers identified 13 real-world examples of potentially affected contracts in October; a November investigation examined eight contract invariants that the upgrade could disrupt.

At the All Core Developers meeting covered in the report, developers said the Ethereum Foundation, ChainSecurity and Dedaub had collectively contacted at least 50 affected companies. Three projects were classified as high impact, with fixes completed or expected by mid-December. Medium-impact projects reported timelines extending to January 10.

Ethereum’s Glamsterdam timetable hinges on smart-contract compatibility

The schedule depended on a specification decision. Keeping the existing design could allow mainnet activation as early as mid-January 2027. Waiting until January to decide could shift activation to late February or early March; adopting modifications could push it to April or May. Developers had not made a decision, and they warned that changes intended to protect some contracts might disrupt others.

Separately, developers discussed whether to narrow the scope of the planned Hegotá hard fork to prioritize post-quantum security. They also raised compatibility concerns about EIP-8151, a proposal concerning accounts migrating to post-quantum security. A preliminary review suggested that many existing contracts could be affected. No decision was reached on Hegotá’s scope; client teams were expected to submit positions before further discussions in two weeks.