As reported on November 17, 2026, Ethereum developers had not reached agreement on how to proceed with the planned Glamsterdam upgrade after a November 16 call focused on contract compatibility. The Hoodi public testnet deployment remained on hold, and no mainnet upgrade date had been confirmed.
Ethereum Foundation developer Marius van der Wijden said the upgrade could affect as many as 15,000 on-chain automation programs. Contracts potentially affected were estimated to hold hundreds of thousands of dollars—an exposure involving far more programs than earlier reviews had identified. These were potential impacts, not confirmed losses.
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 in its external communications; most were being fixed.
Researcher Ansgar Dietrichs, who helped write the proposal, argued for continuing the upgrade but acknowledged that core engineers needed to communicate more clearly with external developers. Another participant warned that removing EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals. The call ended without consensus.
Compatibility problems had delayed testing since October and pushed back the planned Hoodi deployment. Core developers planned to revisit the proposal on November 19; the foundation said Hoodi would remain on hold until the issues were resolved.


