CryptoDetector
Menu

Ethereum weighs Glamsterdam changes over smart contract compatibility risks

For people holding assets in smart contracts, a network upgrade raises a practical question: will those contracts still behave as intended afterward? As reported on Nov. 20, 2026, Ethereum developers had not yet decided whether to change the specifications for the planned Glamsterdam hard fork, which aims to increase network capacity and efficiency.

The concern centers on gas-pricing proposals EIP-8037 and EIP-8038. Blockchain security firm ChainSecurity warned in October that the proposed changes could disrupt existing 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 that the upgrade could disrupt. These are compatibility concerns, not reports of confirmed losses.

At the Thursday All Core Developers meeting covered in the Nov. 20 report, 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 Jan. 10.

Ethereum weighs Glamsterdam changes over smart contract compatibility risks

Developers weighed retaining the current specifications against modifying them to reduce compatibility risks. A change meant to protect one contract could affect another: “Every spec change could, again, break new invariants that we are not aware of breaking yet,” one developer said. Under the existing specifications, mainnet activation could come 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. No decision had been reached.

Separately, developers discussed narrowing the scope of the subsequent planned hard fork, Hegotá, to prioritize post-quantum security features. They also raised compatibility concerns about EIP-8151, a proposal intended to protect accounts migrating to post-quantum security: a preliminary review found that it could affect a potentially large number of existing smart contracts. No decision had been made on Hegotá’s scope, and client teams were expected to submit their positions before further discussions in two weeks.