As reported on November 20, 2026, Ethereum developers had not decided whether to change the specifications for Glamsterdam, a planned hard fork intended to increase network capacity and efficiency. Smart-contract compatibility concerns could move its mainnet activation from as early as mid-January 2027 to as late as May 2027.
The concern centers on gas-repricing proposals EIP-8037 and EIP-8038. In October, security firm ChainSecurity warned that the proposed changes could disrupt existing contracts and potentially expose them to exploitation. Developers postponed the Hoodi testnet fork, which had been scheduled for October 26. Researchers identified 13 real-world examples of potentially affected contracts that month; a November investigation examined eight contract invariants that the upgrade could disrupt.

At Thursday’s All Core Developers meeting, 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.

Developers weighed keeping the current specifications against changing them to reduce compatibility risks. A change that protects some contracts could affect others. “Every spec change could, again, break new invariants that we are not aware of breaking yet,” one developer warned. Developers said waiting until January to decide could shift activation to late February or early March; adopting modifications could move it to April or May. Neither a specification change nor an activation date had been settled.
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 intended to protect accounts migrating to post-quantum security: a preliminary review found that potentially many existing contracts could be affected. No decision was reached on Hegotá’s scope. Client teams were expected to submit their positions before further discussion in two weeks.




