CASABLANCA, Nov. 20, 2026
Ethereum developers tentatively targeted the week of December 14 for Glamsterdam’s Hoodi testnet upgrade Thursday, putting mainnet activation no earlier than January 2027 as application fixes determine the next step in the network’s scaling plans.
The November 19 review produced new remediation deadlines and a provisional testing window, rather than a final mainnet schedule. That advances the story beyond the earlier review of potentially affected contracts: teams now have repair targets, while developers still have to decide whether the underlying specifications should change.
Ether closed November 19 at $1,755.38 on Coinbase Exchange, down 1.09% for the day and 27.0% from October 19. Venue volume was about 161,290 ETH. Those figures describe the broader market without establishing a reaction to the call.
Ethereum
ETHSampled completed Coinbase ETH/USD daily closes in UTC; November 20’s incomplete session is excluded.
Glamsterdam fixes set January’s earliest window
During AllCoreDevs Execution 249, the Ethereum Foundation’s Rahul reported that the Foundation, ChainSecurity and Dedaub had contacted at least 50 companies affected by gas repricing. The three projects categorized as high severity had either completed fixes or expected to finish by mid-December. Medium-severity projects gave readiness dates extending to January 10.
Mid-January was therefore presented as the earliest reasonable mainnet window if developers retain the current specifications. Late January or early February was considered more realistic. Lido representatives requested at least late January to accommodate governance voting and the holiday period.
The distinction is practical: an application can require approval, deployment and operational checks after engineers finish a fix. A tentative network target does not establish that every affected service will be ready.
The discussion follows the October postponement of Hoodi testing. The Foundation’s compatibility-review notice said testing would wait until the issues were resolved and asked application teams to examine assumptions about gas, Ethereum’s measure of transaction work.
ChainSecurity finds 24 cases needing upgrades
ChainSecurity’s public impact assessment, completed November 18, covers 200 findings alongside Foundation-coordinated investigations: three high, 30 medium and 167 low, with none critical. These are findings, not a count of hacked wallets or separate victims.
Most problems can be addressed through configuration changes; 24 require contract upgrades or migration. Potential effects include interrupted operations, locked funds and reward-accounting errors. The public version withholds affected systems’ names and exploitable detail, limiting independent exposure calculations.
As of November 20 at 00:11 UTC, the primary disclosures and targeted exploitation searches reviewed for this article did not establish observed mainnet thefts, victim-wallet counts, stolen-fund transactions, attack waves or a realized loss total attributable to these proposed rules. Ethlabs’ assessment explicitly describes risks dependent on possible deployment, rather than current exploitability.
EIP-8037 changes the charging and accounting for persistent data creation. EIP-8038 reprices access to existing data. Contracts built around fixed gas budgets or assumptions about failed internal calls may behave differently even though their own code stays unchanged.
Hoodi’s December test remains conditional
Developers penciled in Hoodi for the week of December 14, potentially December 16 or 17, while deferring the go/no-go discussion to the November 26 consensus-layer call. Supporters of specification changes were asked to bring a concrete alternative and impact analysis before that meeting.
Geth, Nethermind, Reth and ethrex favored proceeding with the current specification. Erigon preferred changes, while Besu reluctantly accepted proceeding as-is. That preference poll did not finalize the fork.
Changing the rules could require renewed audits and testing and introduce different compatibility problems. Call chair Ansgar Dietrichs outlined a conditional scenario in which waiting until January could move mainnet to late February or early March; adopting changes then could push it to April or May. Those were planning scenarios, not approved dates.
Alternative.me’s Crypto Fear & Greed Index read 12 on November 20, up from 10, remaining in extreme fear.
Fear & Greed Index
Nov. 20, 2026The next checkpoint is the November 26 decision discussion, followed by application readiness and a confirmed Hoodi schedule. No final mainnet activation time or complete public list of affected services was available in the reviewed materials.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | November 19 AllCoreDevs Execution 249 recording and notes |
| | ChainSecurity November 18 impact assessment |
| | Ethereum Foundation compatibility review |
| | Ethlabs assessment of deployment-dependent risks |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
When will Ethereum's Glamsterdam upgrade launch?
There is no confirmed mainnet date. Developers discussed mid-January 2027 as the earliest estimate without specification changes, with late January or early February considered more realistic.
Is the December Hoodi fork confirmed?
No. The week of December 14 was penciled in, potentially December 16 or 17, subject to a go/no-go discussion at the next consensus-layer call.
Has Glamsterdam caused confirmed crypto losses?
The sources reviewed as of November 20 at 00:11 UTC did not establish mainnet thefts, victim-wallet counts or realized losses from the proposed rules. Audit findings describe potential post-upgrade effects.
Could Glamsterdam slip to May 2027?
April or May was discussed as a conditional scenario if developers wait until January and then adopt specification changes, rather than an approved launch date.



