Chain Future

Solidity, smart-contract development, developer tools and explained protocol engineering

Glamsterdam’s gas-pricing proposals raise smart-contract compatibility questions

Developers preparing contracts for Ethereum’s planned Glamsterdam hard fork faced an unresolved question as of November 20, 2026: whether proposed gas-pricing changes could alter how existing contracts behave. Glamsterdam aims to increase network capacity and efficiency, but its specifications and activation date had not been settled.

The concerns center on EIP-8037 and EIP-8038. In October, blockchain security firm ChainSecurity warned that the proposed changes could disrupt existing contracts and potentially expose them to exploitation. Developers postponed the Hoodi testnet fork, originally scheduled for October 26. Researchers identified 13 real-world examples of potentially affected contracts that month; a November investigation examined eight smart-contract invariants—properties expected to remain true—that the upgrade could disrupt.

Glamsterdam’s gas-pricing proposals raise smart-contract compatibility questions (1)

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 debated keeping the current specifications or changing them to reduce compatibility risks. A change that protects one contract might affect another: “Every spec change could, again, break new invariants that we are not aware of breaking yet,” one developer warned.

Glamsterdam’s gas-pricing proposals raise smart-contract compatibility questions (2)

Under the current specifications, mainnet activation could come as early as mid-January 2027. Developers said waiting until January to decide could move activation to late February or early March; adopting modifications could push it to April or May. They had not reached a decision.

The meeting also addressed Hegotá, Ethereum’s next planned hard fork. Developers considered postponing some Ethereum Improvement Proposals to prioritize post-quantum security features, though several argued that narrowing the upgrade would help little unless it shortened the rollout. A preliminary review of EIP-8151, a proposal intended to protect accounts migrating to post-quantum security, identified a potentially large number of existing contracts that could be affected. Hegotá’s scope remained undecided, with client teams expected to submit positions before further discussions in two weeks.