ETH Glamsterdam Test Eyed for Week of Dec. 14 Despite 200 Findings

By CoinPaladin Editorial Desk · Ethereum ·

ETH Glamsterdam Test Eyed for Week of Dec. 14 Despite 200 Findings

Ethereum developers target the week of Dec. 14 for a Glamsterdam Hoodi test despite 200 compatibility findings, with a Nov. 26 decision and a mid-January mai…

Ethereum developers are leaning toward keeping the Glamsterdam upgrade's current gas specifications and targeting the week of Dec. 14 for a Hoodi testnet fork, even after a ChainSecurity assessment surfaced 200 compatibility findings across wallets, bridges and exchanges. A final go/no-go decision is expected at the Nov. 26 All Core Developers Consensus call, with mid-January 2027 the earliest viable mainnet window if no specification changes are made.

Primary Sources & Key Developments

During the Nov. 19, 2026 All Core Developers Execution call, participants expressed broad support for proceeding with the existing specification rather than introducing changes that could push the Glamsterdam upgrade into April or May 2027, as CryptoSlate reported. Developers tentatively targeted the week of Dec. 14 for testing on Ethereum's Hoodi network, with Dec. 16 or 17 mentioned as possible dates. The Hoodi fork was originally scheduled for Oct. 26 but was postponed over compatibility concerns.

The compatibility picture comes from a ChainSecurity assessment coordinated with the Ethereum Foundation. Of the 200 findings, three were classified as high severity, 30 as medium and 167 as low. None was rated critical. Most can be resolved through configuration changes, but 24 require smart contract upgrades or migrations, with potential consequences including interrupted operations, locked funds and errors in reward accounting.

Rahul of the Ethereum Foundation reported outreach to more than 50 affected companies and said mid-January 2027 was the earliest viable mainnet date without specification changes, according to the ACDE #249 notes. Some affected projects reported remediation schedules extending to Jan. 10, and late January or early February was described as a more realistic activation window.

Matte black steel calibration shims and sandstone block representing smart contract gas allowance audits
Auditors found 24 contracts that require migration before activation.

What Do the 200 Findings Actually Break?

The root problem is fixed gas allowances. Applications that hard-code a gas budget for a specific operation may find that budget insufficient under Glamsterdam's proposed pricing, so a transaction can complete at the outer layer while internal payments fail or are skipped. Juicebox V6 simulations demonstrated exactly that behavior under the tested rules. Ethlabs drew a line between changing gas prices, which it called necessary to support expansion, and accounting modifications that introduced unexpected behavior.

Independent review widened the scope. A Dedaub examination of roughly 25,000 contracts with unusual gas usage flagged 70 medium- and high-risk issues, including 22 that the Ethereum Foundation had missed. That gap matters because the affected surface spans bridges, exchanges, wallets, staking platforms and governance systems, not a narrow set of experimental contracts.

By the Numbers: Market Comparison

The verified figures below frame the trade-off between shipping on schedule and shipping with modified rules.

Key Benchmark Comparison (Metric | Verified detail | Source)

  • Compatibility findings: Verified detail: 200 total: 3 high, 30 medium, 167 low, 0 critical | Source: ChainSecurity
  • Contracts needing migration: Verified detail: 24 require upgrades or migrations | Source: ChainSecurity
  • Hoodi testnet fork: Verified detail: Week of Dec. 14, with Dec. 16 or 17 floated | Source: ACDE #249
  • Go/no-go decision: Verified detail: Nov. 26 All Core Developers Consensus call | Source: ACDE #249
  • Earliest mainnet window: Verified detail: Mid-January 2027 without spec changes | Source: Ethereum Foundation
  • Block gas limit target: Verified detail: 60 million to 200 million, a more than threefold increase | Source: Ethlabs
  • Dedaub contract review: Verified detail: About 25,000 contracts, 70 issues, 22 missed by EF | Source: Dedaub
  • Companies contacted: Verified detail: More than 50 affected projects | Source: Ethereum Foundation
  • Crypto Fear & Greed Index: Verified detail: 12/100, Extreme Fear, as of Nov. 20, 2026 | Source: Alternative.me
Dark walnut and smoked bronze data hall interior representing exchange and bridge infrastructure risk
Bridges, exchanges and staking platforms carry the operational exposure.

Regulatory & Counterparty Implications

For exchanges and bridge operators, the exposure is operational rather than legal. A bridge that under-provisions gas can strand user funds in a pending state, and a staking platform that misprices reward accounting can misstate payouts. Those are counterparty risks that compliance teams typically treat as availability incidents, and they arrive while the Crypto Fear & Greed Index sits at 12/100, an Extreme Fear reading that leaves little appetite for unplanned downtime.

The precedent is familiar to anyone tracking Ethereum's capacity roadmap, where the Glamsterdam upgrade and its DeFi impact have been debated for months. What is different here is the audit trail: a named assessor, a severity distribution and a count of 24 contracts that must migrate before activation.

Will Glamsterdam Slip to May 2027?

No specification change received majority support. Most execution clients favored retaining the current specification, Erigon preferred making changes, and Besu reluctantly accepted the current specification despite previously advocating a narrower modification. That split explains why the May 2027 scenario remains live: any rule change reopens testing, and reopening testing pushes the fork past the December window and into the second quarter.

What Analysts Expect Next

The near-term catalyst is procedural. The Nov. 26 call determines whether December testing proceeds, and a confirmed Hoodi fork would put mainnet activation in mid-January at the earliest. Ethlabs acknowledged that gas price changes are necessary for expansion but argued that protocol developers must convince application developers of the upgrade's safety. Until that persuasion is complete, the 24 migration-dependent contracts and the remediation schedules running to Jan. 10 remain the binding constraint, not the block gas limit target of 200 million.

Frequently Asked Questions

When is the Glamsterdam upgrade testnet fork scheduled?

Developers tentatively targeted the week of Dec. 14 for a Hoodi testnet fork, with Dec. 16 or 17 mentioned as possible dates. The original Oct. 26 fork was postponed over compatibility concerns, and a final decision is expected at the Nov. 26 All Core Developers Consensus call.

What are the 200 compatibility findings in the Glamsterdam upgrade?

A ChainSecurity assessment identified 200 findings across wallets, bridges and exchanges: 3 high severity, 30 medium and 167 low, with none rated critical. Most can be fixed through configuration changes, but 24 require smart contract upgrades or migrations.

When could Glamsterdam reach Ethereum mainnet?

Rahul of the Ethereum Foundation said mid-January 2027 was the earliest viable mainnet date without specification changes, while late January or early February was described as more realistic. Introducing rule changes could push activation into April or May 2027.

Primary Sources

Disclosure: This market analysis is provided for informational and educational purposes only and does not constitute financial or investment advice.