Glamsterdam compatibility review leaves Hoodi deployment on hold

As reported on November 17, 2026, developers had not resolved compatibility concerns around Ethereum’s planned Glamsterdam upgrade. At a November 16 developer call, Ethereum Foundation developer Marius van der Wijden said the changes could affect as many as 15,000 on-chain automation programs—far more than earlier reviews had identified. Funds associated with potentially affected contracts were estimated in the hundreds of thousands of dollars, according to the CoinDesk report cited in the original account.

Security firm ChainSecurity’s Tanguy Rocher reported 152 findings, roughly half of which overlapped with the Foundation’s internal research. Together, the reviews identified about 200 potential issues. In a separate review of approximately 25,000 contracts with unusual gas usage, Dedaub flagged 70 medium- or high-risk issues, including 22 the Foundation had previously missed. Most issues stemmed from two of the eight core technical assumptions about which the Foundation had warned developers on November 6. The Foundation also identified three high-severity and at least 25 medium-severity defects through its external communications; most were being fixed.

The November 16 call ended without agreement. Researcher Ansgar Dietrichs, who helped write the proposal, argued that the upgrade should proceed but acknowledged that core engineers needed to communicate more clearly with external developers. Other participants warned that dropping EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals.

Compatibility problems had delayed testing since October, pushing back the planned deployment on the Hoodi public testnet. Core developers planned to revisit the proposal on November 19. The Foundation said Hoodi would remain on hold until the issues were resolved; no Glamsterdam mainnet date had been confirmed.

Further reading