Block Beacon Chain

A beacon is a schedule, not a mood.

Glamsterdam compatibility concerns delay Hoodi testnet deployment

As reported on November 17, 2026, Ethereum developers had not resolved compatibility concerns around the planned Glamsterdam upgrade. At a November 16 developer call, Ethereum Foundation developer Marius van der Wijden said the changes could affect up to 15,000 on-chain automated programs—far more than earlier reviews had identified. The funds associated with potentially affected contracts were estimated at hundreds of thousands of dollars.

Security firm ChainSecurity’s Tanguy Rocher reported 152 findings, about half of which overlapped with the Foundation’s internal research. Together, the reviews identified roughly 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 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 flaws through its outreach; most were being fixed.

Researchers and developers disagreed about the next step. Ansgar Dietrichs, who helped write the proposal, argued for continuing the upgrade while acknowledging 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 November 16 call ended without agreement.

Compatibility problems had delayed testing since October, forcing a postponement of the planned Hoodi public testnet deployment. Core developers planned to revisit the proposal on November 19. The Foundation said Hoodi would remain on hold until the issues were resolved, and there was no confirmed date for Glamsterdam on mainnet.