TECH Oct 24, 2026 · by Skills Team

Ethereum Glamsterdam Delay: A Guide for Blockchain Builders

Ethereum developers postponed the Glamsterdam testnet fork over gas risks found by ChainSecurity. This guide explains the EIP-8037 and EIP-8038 issue and gives businesses a checklist to protect their smart contracts.

Ethereum Glamsterdam Delay: A Guide for Blockchain Builders

The Short Answer

On October 22, 2026, Ethereum developers made a decision that should matter to every business building on the network: they postponed the Ethereum Glamsterdam hard fork activation on the Hoodi testnet, just days before it was scheduled to go live on October 26 at 17:42:48 UTC. The delay came after security researchers at ChainSecurity identified…

On October 22, 2026, Ethereum developers made a decision that should matter to every business building on the network: they postponed the Ethereum Glamsterdam hard fork activation on the Hoodi testnet, just days before it was scheduled to go live on October 26 at 17:42:48 UTC. The delay came after security researchers at ChainSecurity identified gas-related risks that could permanently break the way existing smart contracts handle failed transactions. No replacement date has been announced, and the upgrade's expected early-December mainnet target is now uncertain.

This is not just a story for protocol engineers. If your business runs payment flows, loyalty tokens, supply-chain tracking, or any other logic on Ethereum, a change to how the network prices operations can change how your contracts behave. This guide explains what Glamsterdam is, what went wrong, and exactly what to do about it.

What Is the Ethereum Glamsterdam Upgrade?

Ethereum Glamsterdam is the network's main scaling upgrade for 2026, the next hard fork after 2025's Pectra and Fusaka upgrades. Ethereum's upgrade history shows a steady progression: The Merge in September 2022 moved the network from proof-of-work to proof-of-stake, Dencun in March 2024 introduced EIP-4844 blob transactions that cut layer-2 data costs by roughly 90 percent, and Fusaka in December 2025 added PeerDAS to expand data availability for rollups.

Glamsterdam shifts the focus back to the layer-1 chain itself. Its headline changes include:

  • Enshrined proposer-builder separation (EIP-7732): moves the handoff between specialized block builders and validators directly into the protocol, reducing reliance on outside middleware.
  • Block-level access lists (EIP-7928): record the accounts and storage locations used during each block, opening the door to parallel transaction validation and higher throughput.
  • Gas repricing (EIP-8037 and EIP-8038): changes how the network charges for creating blockchain state and accessing existing state, so gas costs better reflect the real cost of running the network.

The upgrade already went live on the Sepolia testnet on October 6 and had activated earlier on the short-lived Plataberget testnet in August. The Hoodi testnet, which mirrors mainnet staking conditions, was the final dress rehearsal. It was also meant to test a planned increase of Hoodi's gas limit to 200 million, a jump designed to prove Ethereum can handle much larger transaction volumes. That gas-limit increase is now suspended along with the fork.

The stakes are enormous. As of October 2026, Ethereum holds about $49 billion in DeFi deposits across more than 210 protocols, more than any other blockchain, according to DeFiLlama data. Tens of billions of dollars of real value sit inside contracts whose behavior depends on gas accounting behaving exactly as developers expect.

What Went Wrong: The EIP-8037 and EIP-8038 Gas Problem Explained

To understand the risk, you need one concept: gas. Every operation on Ethereum costs gas, a fee paid to keep the network running. When a smart contract calls another contract, the caller can limit how much gas the called contract receives. If the called contract runs out of gas, that part of the transaction fails, and the failure is handled gracefully.

Many existing contracts are written to catch that failure and continue. For example, a contract might record that a claim attempt failed and then disable the claim so it cannot be retried. Developers who write this pattern sometimes rely on a subtle safety valve: after the failure, the remaining gas is so low that the follow-up logic cannot finish, so the whole transaction reverses instead. The failure never gets permanently recorded.

That is where EIP-8037 changes the math. The proposal introduces a separate gas reserve for creating new blockchain state, and under the new rules, gas spent creating certain records can be restored when those changes are undone. ChainSecurity's October 13 analysis showed this can leave a contract with more gas than expected after a failure, enough to finish the failure-handling logic that previously would have reversed.

The business impact of that subtle shift is serious:

  • A failed operation can be permanently recorded, for example a user's claim right deleted or a retry function disabled, even though the original operation was perfectly valid.
  • Protections against insufficient gas griefing get weaker. In this attack, a malicious caller deliberately supplies too little gas so that a legitimate contract operation fails. Contracts that defend against this with gas-based checks may find those checks no longer work.
  • The Ethereum Foundation had already warned that the new gas model could break wallets, indexers, and gas estimators that rely on fixed gas assumptions.

ChainSecurity did not just theorize about this. The firm reported finding 13 real-world examples of affected contracts and began responsible disclosure with the affected projects. On October 21, independent security researcher pcaversaccio called the risks "serious" in a public GitHub comment and urged developers to reassess the fork. The next day, at All Core Developers Execution meeting number 248, developers chose the safe path: delay the Hoodi activation until the interaction between EIP-8037, EIP-8038, and existing mainnet contracts is fully understood.

How the Industry Reacted

The reaction was fast and coordinated. The Ethereum Foundation confirmed the postponement on October 22. Researcher Christine Kim disclosed the cancellation publicly and urged affected Hoodi node operators to revert to older software versions or install updated execution clients that remove the scheduled activation. Prysm developer Preston Van Loon said a release removing Glamsterdam from Hoodi's schedule would follow the same day.

The impact rippled into live applications. Lido DAO, the staking protocol behind stETH, prepared a community vote on October 24 to roll back smart contracts it had deployed on Hoodi in preparation for the fork. Lido reported about $23.3 billion in total value locked as of October 23 and emphasized that its mainnet contracts are unaffected and stETH and wstETH holders need take no action.

Meanwhile, ETH showed little reaction to the news, trading near $2,400, and institutional buying continued, with SharpLink deploying $400 million of its ETH treasury on-chain and BitMine adding 12,535 ETH, according to crypto press coverage. The market read the delay as the system working as designed: a security issue caught on a testnet before it could touch real money. A revised Hoodi date is expected after Devcon, which runs November 3 to 6.

What the Ethereum Glamsterdam Delay Means for Your Business

If you run a business on Ethereum or plan to, this delay is a reminder that your smart contracts live on top of a platform that changes beneath them. Hard forks can alter gas costs, execution rules, and failure behavior, and assumptions baked into your code today may not hold tomorrow. For practical background on how contracts power real companies, see our guide on smart contracts for business, and for the broader enterprise picture, our overview of blockchain use cases in 2026.

The good news: mainnet is unaffected, everyday users need do nothing, and no funds are at risk from this delay. The honest news: if you ship or maintain contracts, this is the clearest signal you will get all year to review your gas assumptions before the next mainnet upgrade lands.

Action Checklist: Prepare Your Contracts Before Glamsterdam Ships

Use this checklist to make your on-chain systems resilient to the gas-accounting changes in Glamsterdam and any future hard fork:

  1. Audit every contract for gas-dependent failure logic. Search your codebase for patterns that branch on remaining gas, catch low-level call failures, or disable retries after a failed operation. These are the patterns ChainSecurity flagged. A professional smart contract security audit should now include a gas-model review as standard.
  2. Review hardcoded gas stipends and limits. The Ethereum Foundation warned before the fork that contracts relying on fixed gas stipends or hardcoded gas limits may need changes. Replace magic numbers with values derived from the current network rules, and add margin.
  3. Test on testnets that run the new rules. Glamsterdam is live on Sepolia, which means you can deploy your contracts there and simulate failures today. Build gas-behavior tests into your release pipeline with a dedicated blockchain QA and testing process so regressions surface before mainnet.
  4. Model insufficient-gas griefing explicitly. Add test cases where callers supply minimal gas to your entry points. If an attacker can make a valid operation permanently fail or permanently recorded as failed, your contract logic needs redesigning, not just retuning.
  5. Track the Foundation's upgrade calendar. Follow the All Core Developers calls and the Ethereum Foundation's announcements. A revised Hoodi activation is expected after Devcon (November 3 to 6), and the mainnet window is still open for the fourth quarter. Treat the announcement as the start of your own upgrade sprint, not the end of it.
  6. Keep upgrade paths in your contracts. Proxies, migration functions, and admin-gated pause switches let you respond to protocol changes without stranding users. Design every new contract as if the gas rules will change, because they will.

Ethereum Glamsterdam: Lessons for Enterprise Blockchain Upgrades

Step back from the technical details and this episode is a masterclass in how responsible infrastructure behaves, and a template for how enterprises should manage their own upgrades:

What Ethereum didWhat your business should copy
Caught the issue on a testnet, before mainnetNever ship contract upgrades without a full testnet rehearsal under realistic conditions
An independent security firm reviewed the proposalsBudget for third-party audits on every major release, not just the first one
Responsible disclosure with 13 affected projectsMaintain an incident-response list of every integration partner your contracts touch
Node operators got clear rollback instructions within a dayWrite rollback runbooks before you deploy, not after something breaks
Delay chosen over shipping a known riskMake "pause and investigate" an acceptable, pre-approved outcome of your release gates

The deeper lesson is that Ethereum's security culture treats a testnet delay as a success, not an embarrassment. Thirteen real-world contract patterns were at risk, and the network chose caution over a timeline. Businesses building on any blockchain should apply the same bar to their own blockchain and Web3 development: the upgrade that ships late but safe is the one that protects your users and your balance sheet.

Frequently Asked Questions

Is Ethereum Glamsterdam cancelled?

No. Only the Hoodi testnet activation, scheduled for October 26, 2026, was postponed. Glamsterdam remains live on the Sepolia testnet, and developers intend to reschedule Hoodi after further investigation, with a mainnet window still open in the fourth quarter of 2026.

Are my ETH holdings or DeFi positions affected by the delay?

No. Mainnet is completely unaffected. The Ethereum Foundation confirmed that the network's existing transaction history is unchanged, and Lido DAO confirmed that stETH and wstETH holders on mainnet need take no action.

What are EIP-8037 and EIP-8038 in plain language?

EIP-8037 introduces a separate gas reserve for creating new blockchain state, intended to slow state growth as Ethereum scales. EIP-8038 reprices the cost of accessing and modifying existing state. Together they make gas pricing more accurate, but they also change how much gas a contract has left after failed operations, which can alter contract behavior.

Why does a testnet delay matter for my business?

Because the contracts you run on mainnet contain gas assumptions that Glamsterdam will eventually change. The delay gives you a window, likely weeks, to audit failure-handling logic, test on Sepolia, and fix anything that depends on today's gas rules before the mainnet fork arrives.

What is insufficient gas griefing?

It is an attack where a malicious caller deliberately provides too little gas for a legitimate contract operation to complete. Contracts often include gas-based checks to defend against this. ChainSecurity warned that the new Glamsterdam gas rules could weaken those defenses and let failed operations become permanently recorded.

When will Glamsterdam reach mainnet?

Developers had been eyeing early December 2026, but the timeline is now uncertain pending the Hoodi rescheduling. A revised Hoodi date is expected after Devcon (November 3 to 6), and mainnet timing will follow successful Hoodi testing.

The Ethereum Glamsterdam delay is exactly how healthy infrastructure evolves: a real risk found early, responsible disclosure, and a pause instead of a gamble. Your contracts deserve the same discipline. If you need help auditing your smart contracts, testing them against the new gas rules, or planning your own blockchain roadmap, talk to our blockchain team and we will make sure your systems are ready before Glamsterdam ships.

#Ethereum, blockchain, smart contracts, Glamsterdam