Ethereum’s Glamsterdam timing hinges on smart-contract compatibility review

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. The choice could move mainnet activation from as early as mid-January 2027 to as late as May 2027.

The concern is whether proposed gas-pricing changes, EIP-8037 and EIP-8038, could disrupt existing smart contracts. Blockchain security firm ChainSecurity warned in October that some contracts might become exploitable, prompting developers to postpone a Hoodi testnet fork originally scheduled for October 26. Researchers identified 13 real-world examples of potentially affected contracts in October; a November investigation examined eight smart-contract invariants that the upgrade could disrupt.

At the November 19 All Core Developers meeting, developers said the Ethereum Foundation, ChainSecurity and security firm 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 modifying them to reduce compatibility risks. They cautioned that a change protecting one set of contracts could affect others. Under the current specifications, mainnet activation could happen as early as mid-January 2027. Waiting until January to decide could move it to late February or early March; adopting modifications could push it to April or May. Neither a specification change nor an activation date had been agreed.

Separately, developers discussed narrowing the scope of the subsequent planned hard fork, Hegotá, to prioritize post-quantum security. A preliminary review found that EIP-8151, a proposal intended to protect accounts migrating to post-quantum security, could affect a potentially large number of existing contracts. Developers had not decided Hegotá’s scope; client teams were expected to submit their positions before further discussions in two weeks.

Further reading