As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa... The concern is that new state gas rules could invalidate contracts’ assumptions about gas budget...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: Why are prominent developers, including Curve Finance’s founder, urging Ethereum to halt the Glamsterdam upgrade in its current form, how co. Article summary: Developers are urging a pause because Glamsterdam’s gas changes could break already-deployed contracts—not merely make transactions more expensive—and potentially leave user funds inaccessible.[11] The confirmed response. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
Ethereum’s Glamsterdam upgrade is on hold on the Hoodi testnet because proposed changes to gas accounting could make some existing smart contracts behave differently. The risk is not simply higher transaction costs: contracts that rely on specific gas assumptions may fail in ways their developers did not anticipate. The Ethereum Foundation said Hoodi will not fork until the issues are resolved.8
EIP-8037 raises the cost of creating state and introduces a separate way to account for those charges. EIP-8038 changes gas costs for accessing existing state. Together, the proposals alter how gas is charged for certain operations—rules that some deployed contracts may treat as predictable.20
23
8
That matters because contracts can use gas limits and gas measurements to decide whether an operation succeeded, failed, or should be retried. A change in the amount or accounting of gas can invalidate those assumptions, particularly around external calls that fail.6
19
gasleft(): ChainSecurity explains that gasleft() reports a frame’s execution-gas balance, while state-creation charges can also draw on that balance if the separate state-gas reservoir is exhausted. It cautions against relying on checks that infer why a call failed from the remaining gas: an intermediary revert or a gas refill can undermine that inference.The Foundation refers to eight gas-related invariants, or assumptions, that some contracts may rely on. They are not eight universal failure modes affecting every Ethereum contract. The Foundation has published examples and prompts to help teams check their own code.2
8
Ethereum.org reported that 13 mainnet examples had surfaced, while other coverage described 13 deployed contracts with potentially affected failure-handling logic.13
38 These examples show that the compatibility risk is not merely theoretical. They do not mean that 13 contracts have already failed: the concern is how they could behave if the proposed changes were activated.
8
38
The available source details do not provide a complete, independently verifiable list of all 13 contracts or their failure traces. Nor should the eight invariants be treated as a guarantee that every contract has been checked.
The Ethereum Foundation’s November 6 update says it is working with ChainSecurity and Dedaub and conducting internal audits. It also asks developers and auditors to check whether their projects rely on the affected assumptions.8 The Foundation’s published materials include examples and self-check prompts, and a report relays the address
glamsterdam@ethereum.org for affected teams.2
Those reviews are paired with a call for project-level checks. A protocol-wide audit cannot establish that every application and its failure-handling logic is safe; teams need to test their own contracts against the changed gas rules.8
33
Glamsterdam activated on the Sepolia testnet on October 6, according to reporting on the rollout.6 ChainSecurity published its gas-accounting analysis on October 13.
19 On October 22, the Foundation postponed Hoodi’s planned October 26 activation and said it had no replacement date at that time.
49 The postponement also included a planned increase of Hoodi’s gas limit to 200 million.
34
On November 6, the Foundation confirmed that developers would not fork Hoodi until the identified risks were resolved.8 The current status is therefore a security-driven pause, not a newly scheduled activation. The available updates do not establish an emergency reversal fork as a recovery plan.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa...
As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa... The concern is that new state gas rules could invalidate contracts’ assumptions about gas budgets and failure handling, potentially leaving some operations—including withdrawals—unable to complete.[19][41]
The Ethereum Foundation is coordinating audits and asking project teams to check their own contracts; the cited updates give no new Hoodi activation date.[2][8][49]
As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa... The concern is that new state gas rules could invalidate contracts’ assumptions about gas budget...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: Why are prominent developers, including Curve Finance’s founder, urging Ethereum to halt the Glamsterdam upgrade in its current form, how co. Article summary: Developers are urging a pause because Glamsterdam’s gas changes could break already-deployed contracts—not merely make transactions more expensive—and potentially leave user funds inaccessible.[11] The confirmed response. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
Ethereum’s Glamsterdam upgrade is on hold on the Hoodi testnet because proposed changes to gas accounting could make some existing smart contracts behave differently. The risk is not simply higher transaction costs: contracts that rely on specific gas assumptions may fail in ways their developers did not anticipate. The Ethereum Foundation said Hoodi will not fork until the issues are resolved.8
EIP-8037 raises the cost of creating state and introduces a separate way to account for those charges. EIP-8038 changes gas costs for accessing existing state. Together, the proposals alter how gas is charged for certain operations—rules that some deployed contracts may treat as predictable.20
23
8
That matters because contracts can use gas limits and gas measurements to decide whether an operation succeeded, failed, or should be retried. A change in the amount or accounting of gas can invalidate those assumptions, particularly around external calls that fail.6
19
gasleft(): ChainSecurity explains that gasleft() reports a frame’s execution-gas balance, while state-creation charges can also draw on that balance if the separate state-gas reservoir is exhausted. It cautions against relying on checks that infer why a call failed from the remaining gas: an intermediary revert or a gas refill can undermine that inference.The Foundation refers to eight gas-related invariants, or assumptions, that some contracts may rely on. They are not eight universal failure modes affecting every Ethereum contract. The Foundation has published examples and prompts to help teams check their own code.2
8
Ethereum.org reported that 13 mainnet examples had surfaced, while other coverage described 13 deployed contracts with potentially affected failure-handling logic.13
38 These examples show that the compatibility risk is not merely theoretical. They do not mean that 13 contracts have already failed: the concern is how they could behave if the proposed changes were activated.
8
38
The available source details do not provide a complete, independently verifiable list of all 13 contracts or their failure traces. Nor should the eight invariants be treated as a guarantee that every contract has been checked.
The Ethereum Foundation’s November 6 update says it is working with ChainSecurity and Dedaub and conducting internal audits. It also asks developers and auditors to check whether their projects rely on the affected assumptions.8 The Foundation’s published materials include examples and self-check prompts, and a report relays the address
glamsterdam@ethereum.org for affected teams.2
Those reviews are paired with a call for project-level checks. A protocol-wide audit cannot establish that every application and its failure-handling logic is safe; teams need to test their own contracts against the changed gas rules.8
33
Glamsterdam activated on the Sepolia testnet on October 6, according to reporting on the rollout.6 ChainSecurity published its gas-accounting analysis on October 13.
19 On October 22, the Foundation postponed Hoodi’s planned October 26 activation and said it had no replacement date at that time.
49 The postponement also included a planned increase of Hoodi’s gas limit to 200 million.
34
On November 6, the Foundation confirmed that developers would not fork Hoodi until the identified risks were resolved.8 The current status is therefore a security-driven pause, not a newly scheduled activation. The available updates do not establish an emergency reversal fork as a recovery plan.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa...
As of November 6, 2026, Ethereum developers had paused Glamsterdam’s Hoodi testnet activation while investigating risks to existing contracts; 13 mainnet examples were reported, but these are potential post upgrade fa... The concern is that new state gas rules could invalidate contracts’ assumptions about gas budgets and failure handling, potentially leaving some operations—including withdrawals—unable to complete.[19][41]
The Ethereum Foundation is coordinating audits and asking project teams to check their own contracts; the cited updates give no new Hoodi activation date.[2][8][49]