Updated November 9, 2026
Ethereum’s next major protocol upgrade, Glamsterdam, has hit a new testing pause. In a November 6 update, the Ethereum Foundation said developers found that some projects may depend on gas-accounting assumptions that EIP-8037 and EIP-8038 would change. The developers decided to delay the hard-fork process and not activate Glamsterdam on the Hoodi testnet until the issues are resolved.
The announcement is a developer and test-network update. It does not announce a Glamsterdam mainnet activation date or describe a live exploit. For most ETH holders and wallet users, it does not call for an immediate transaction or wallet change.
What the Ethereum Foundation announced
The Foundation says Glamsterdam is being tested on testnets. During that work, ChainSecurity identified projects that could be vulnerable after the upgrade because they rely on certain execution assumptions. The Foundation is working with ChainSecurity and Dedaub and conducting internal audits; it also asked contract developers and auditors to check their own systems against eight identified invariants.
As of the Foundation’s November 6 notice, developers had decided not to fork Hoodi until the issues are resolved. The notice does not provide a replacement Hoodi date. It says work on the next upgrade, Hegota, continues in parallel. An earlier October 22 notice had already postponed a scheduled Hoodi activation and said no new date had been set; the November update adds the broader issue investigation.
What EIP-8037 and EIP-8038 change
| Proposal | High-level change | Why developers are reviewing it |
|---|---|---|
| EIP-8037 | Changes how state creation costs are charged and introduces a separate state-gas reservoir. | Some contracts may assume that a failed or underfunded call leaves a predictable amount of gas for the caller’s recovery code. |
| EIP-8038 | Reprices state-access operations. | Code that relies on fixed gas limits or older cost estimates may need review. |
These changes affect the economics of executing certain smart-contract operations. ChainSecurity’s technical analysis describes a specific class of concern: after a call fails, changed gas costs and accounting can leave enough gas for a contract’s failure-handling code to complete where earlier assumptions expected the whole path to run out of gas. If that handler permanently records a task as failed, a user’s operation could become difficult or impossible to retry. That is a design risk to investigate, not a claim that every contract is vulnerable.
What developers and auditors should check
- Review code that handles failed external calls, especially paths that mark a task complete or failed permanently.
- Search for fixed gas limits, gas estimates in signed messages, relayers, bots, and off-chain services.
- Check code that measures work by subtracting two
gasleft()readings. - Test first-time writes, account creation, contract creation, and retry paths under the relevant Glamsterdam rules.
- Follow the Ethereum Foundation’s invariant repository and client-team guidance; do not treat old Hoodi activation instructions as current.
The Foundation’s repository lists the assumptions it wants projects to review. A checklist is a starting point, not a security audit. Teams should test the affected paths in a controlled environment and seek qualified review for contracts that manage user funds.
What this means for ETH holders and wallet users
The current announcement concerns testing and upgrade readiness. It does not announce a mainnet fork date, require ETH holders to move funds, or tell users to install a wallet update. Users should rely on their wallet and application teams’ official notices for any later action. Avoid links or messages claiming that an urgent migration is needed because of this testnet update.
If you are learning self-custody, see our Ledger Nano X setup guide for general device setup and recovery-phrase practices. That guide is separate from the Glamsterdam testing notice.
What happens next
The next steps are further contract reviews, discussions among Ethereum’s core developers, and any specification changes needed to address the findings. The Foundation has not published a new Hoodi activation time in the November 6 notice. Treat future dates as unconfirmed until an official Ethereum Foundation or client-team announcement provides them.
Frequently asked questions
Was Glamsterdam canceled?
The Foundation describes a delay in the hard-fork process and says Hoodi will not be forked until the issues are resolved. It has not said the upgrade is canceled.
Is Ethereum mainnet affected right now?
The notice describes testing and potential post-upgrade vulnerabilities. It does not report an active mainnet exploit or set a mainnet activation date.
Do ETH holders need to do anything?
The announcement gives no immediate action for ordinary ETH holders. Follow official wallet and application notices if future upgrades require software updates.
Are all smart contracts at risk?
No. The Foundation says some projects may rely on affected assumptions and asks developers to review eight invariants. The notice does not say all contracts are vulnerable.
Sources
- Ethereum Foundation: EIP-8037/EIP-8038 Glamsterdam (November 6, 2026)
- Ethereum Foundation: Glamsterdam on Hoodi Postponed (October 22, 2026)
- ChainSecurity: Glamsterdam Hard Fork—When Spent Gas Comes Back
- EIP-8037 specification
- EIP-8038 specification
- Ethereum Foundation repository: Glamsterdam gas invariants


