ETH Daily
Menu

Glamsterdam timing hinges on smart-contract compatibility review

As reported on Nov. 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 decision could determine whether mainnet activation remains possible in mid-January 2027 or slips as far as May.

Glamsterdam timing hinges on smart-contract compatibility review (1)

Gas repricing and existing contracts

The compatibility concerns center on EIP-8037 and EIP-8038, proposals to change gas pricing. In October, blockchain 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 Oct. 26.

Researchers identified 13 real-world examples of potentially affected contracts in October. A November investigation examined eight smart-contract invariants—properties that contracts rely on—that the upgrade could disrupt. At Thursday’s 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 either completed or expected by mid-December. Medium-impact projects reported timelines extending to Jan. 10.

Developers discussed retaining the current specifications or modifying 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.

Under the current specifications, mainnet activation could come as early as mid-January 2027. Developers discussed that waiting until January to decide could move activation to late February or early March; adopting modifications could push it to April or May. None of those dates was a confirmed activation date.

Glamsterdam timing hinges on smart-contract compatibility review (2)

Hegotá’s scope remains open

Developers also discussed whether to narrow the scope of Hegotá, the planned hard fork after Glamsterdam, to prioritize post-quantum security features. Some argued that postponing other EIPs would offer little benefit unless it also shortened the rollout timeline.

EIP-8151, a proposal intended to protect accounts migrating to post-quantum security, raised a separate compatibility concern. A preliminary review found that its changes could affect a potentially large number of existing smart contracts, complicating its possible inclusion in Hegotá. No decision was reached on Hegotá’s scope; client teams were expected to submit their positions before further discussions in two weeks.