Hoodi Upgrade 2.2.1 Removes Glamsterdam Fork
Ethereum Hoodi node operators must upgrade to version 2.2.1 before 26 October 2026 at 17:42:48 UTC. The patch removes the planned Glamsterdam fork from Hoodi, which is on hold following security concerns discussed at ACDE #248. Nodes still running version 2.2.0 would activate the fork at the scheduled time and split from the network. The Hoodi upgrade keeps the testnet on BPO2, with no next fork date announced. Operators can upgrade in place from any 2.2.x version; no database or configuration changes are required. The release affects Hoodi only, not other networks. The Hoodi upgrade is a testnet maintenance change and does not directly alter Ethereum’s mainnet.
Neutral
This is a Hoodi testnet client update, not a change to Ethereum mainnet consensus or ETH economics, so its direct effect on ETH trading and broader market stability is likely limited. In the short term, node operators need to upgrade before the scheduled fork time to avoid network divergence; the deadline may prompt operational attention but is unlikely by itself to drive substantial spot or derivatives activity. The release removes the planned Glamsterdam fork after security concerns, while leaving Hoodi on BPO2 and announcing no replacement date. As with past testnet fork postponements, traders may monitor developer communications and subsequent releases for signals about the upgrade’s readiness, but a testnet delay alone is not necessarily a bearish signal. Longer term, addressing security concerns before deploying a fork may support confidence in Ethereum’s upgrade process. Market impact could change if the pause leads to wider delays or affects a mainnet schedule, but the article provides no indication of that. Overall, the news is operationally important for Hoodi participants but neutral for the market.