Ethereum developers halt Glamsterdam upgrade over smart contract security risks
Ethereum developers have pulled Glamsterdam, the next major network upgrade, from its scheduled Hoodi testnet slot over security risks to deployed smart contracts. For institutions running tokenized assets, stablecoins or bank-issued tokens on Ethereum, the delay shows that backward compatibility with live contracts is being weighed before the upgrade reaches mainnet.
- The Ethereum Foundation confirmed on October 22 that the Hoodi testnet upgrade would not proceed as planned.
- Glamsterdam had been scheduled for Hoodi on October 26, four days after the confirmation.
- Developers agreed to investigate how a proposed protocol change affects existing contracts; no replacement date was reported.
- Oct. 26 planned Hoodi activation date, now off as originally scheduled
- Oct. 22 date of the Foundation’s confirmation, four days before activation
Ethereum developers have postponed Glamsterdam on the Hoodi test network after identifying potential security risks affecting existing smart contracts, CryptoSlate reported. Hoodi is a public testnet where client teams rehearse upgrades before they reach the live network.
The Ethereum Foundation confirmed on Thursday (October 22) that the Monday (October 26) activation would not go ahead.
Ethereum Foundation Cancels the October 26 Hoodi Date Four Days Out
Developers agreed to investigate how a proposed change to Ethereum’s protocol interacts with contracts already deployed on the network.
The excerpt of the CryptoSlate report we reviewed cuts off before naming that change. It also does not list the individual risks, so they cannot be broken down here.
Risks to Deployed Contracts Matter Most to Token Issuers
The exposure described is to existing smart contracts, not to the testnet itself. Any upgrade that alters how the virtual machine treats live code is a concern for issuers of tokenized funds, stablecoins and bank products.
Nothing in the report says any specific protocol or product is affected.
No Replacement Hoodi Date Leaves Glamsterdam’s Mainnet Timing Open
The report gives no new Hoodi date and no revised mainnet schedule. A testnet run is the final public rehearsal before mainnet, so each slip on Hoodi pushes the live activation back by at least the time needed to resolve the flagged risks.
The testnet is where problems of this kind are meant to surface.
The CCS read. We read the delay as the process working, not failing. Catching contract-compatibility risks on Hoodi costs a few weeks, while catching them on mainnet would cost live balances. Holders have no direct exposure from a testnet postponement, and institutions with deployed contracts should treat a conservative upgrade path as a feature of Ethereum’s governance.
The open question is whether developers drop or rework the proposed change, or keep it and ship fixes alongside. The Ethereum Foundation and client teams have yet to publish a revised Hoodi date. Until they do, the October 26 slot is the last confirmed marker and mainnet timing stays unset.