Ethereum’s next major protocol upgrade, Glamsterdam, has hit a testing delay after developers identified potential compatibility and security problems linked to proposed changes in how the network charges for computation and long-term data storage. In a November 6 update, Ethereum Foundation researcher Marius van der Wijden said testing had revealed projects that could become vulnerable because they rely on assumptions that two proposals, EIP-8037 and EIP-8038, are designed to change. Ethereum’s All Core Developers group decided not to proceed with the planned Hoodi testnet fork until the issues are understood and resolved.
The development is an important reminder that blockchain upgrades are not simply software releases. Changes to transaction fees can affect smart-contract behavior, developer tooling and the assumptions applications make about the network. Glamsterdam remains in development; it has not been activated on Ethereum mainnet.
What happened to the Glamsterdam upgrade?
Glamsterdam is Ethereum’s planned upgrade following Fusaka. It combines changes to the execution layer and consensus layer, with a broader goal of improving how Ethereum builds, propagates and verifies blocks. The upgrade is being tested on public test networks before any mainnet activation date is finalized.
The immediate issue concerns EIP-8037 and EIP-8038. According to the Ethereum Foundation, security firm ChainSecurity identified projects that could be vulnerable after the changes because they depend on existing gas-accounting invariants. Developers have paused the Hoodi testnet fork process while they investigate which projects are affected and whether the specifications need adjustments.
This is a test-stage issue, not evidence that Ethereum mainnet has been compromised. The Foundation’s update says work on the separate Hegotá upgrade continues in parallel.
Why EIP-8037 and EIP-8038 matter
EIP-8037: pricing permanent data more accurately
Ethereum nodes maintain a shared record of accounts, balances and smart-contract storage. Adding data to this record can create a lasting burden because nodes must preserve and serve that state over time. EIP-8037 proposes changing how the network accounts for the cost of creating this permanent state.
The proposal introduces a dedicated state-gas accounting model, separating the cost of computation from the cost of creating persistent data. In principle, this can make fees better reflect the storage burden of an operation and help the network grow without placing unlimited demands on node operators.
However, a change to gas accounting can affect contracts and applications that make assumptions about how much gas remains available during execution. Code that was safe under the old rules may need review if the meaning or timing of gas charges changes.
EIP-8038: updating the cost of reading network state
EIP-8038 focuses on state-access operations: instructions that read account or contract information from Ethereum’s database. Some operations may require more database work than their current gas price reflects. The proposal aims to align their cost more closely with the resources nodes use.
More accurate pricing can discourage abusive workloads and make denial-of-service attacks more expensive. Yet changing gas costs can also expose fragile assumptions in smart contracts, infrastructure and developer tools. That is why compatibility testing is essential before a network-wide activation.
How Glamsterdam is intended to improve Ethereum
The two gas proposals are only part of a wider technical plan. Glamsterdam also includes work intended to make block production more efficient and prepare Ethereum for greater transaction capacity.
Enshrined proposer-builder separation
Enshrined proposer-builder separation, associated with EIP-7732, is designed to formalize the division between validators that propose blocks and specialized builders that assemble transaction payloads. Today, parts of this arrangement rely on software and relays outside Ethereum’s core protocol. Bringing more of the process into the protocol could reduce some trust assumptions and give the network more flexibility when propagating block data.
Block-level access lists
Block-level access lists, associated with EIP-7928, provide an upfront description of which parts of the network state a block’s transactions will touch. That information can help clients identify transactions that do not depend on the same data and prepare for more parallel processing. It may also make some node synchronization tasks more efficient.
These mechanisms are intended to improve the base layer, or Layer 1. They do not mean every application will immediately become faster or cheaper, and the final effects will depend on the features that make it into the activated upgrade and how clients implement them.
What the delay means for smart contracts and dApps
For decentralized application teams, the most practical response is to treat the delay as a reason to test, not as a reason to assume their software is already affected. Teams should review contracts that depend on exact gas behavior, state-access costs, contract deployment routines or execution traces. They should follow the updated specifications and test against the relevant client releases when available.
Wallets, exchanges, bridges, staking services and infrastructure providers also need to monitor changes that affect transaction estimation, event indexing and node compatibility. An upgrade can alter how clients account for work even when the user-facing application appears unchanged.
Ordinary ETH holders do not need to migrate tokens because a protocol upgrade is being tested. Users should be cautious of anyone claiming they must send ETH to a special address or pay a fee to “upgrade” their coins. Official upgrade instructions come from Ethereum’s developer channels and client teams.
Why the pause is significant for blockchain security
Ethereum’s decision to pause the Hoodi step demonstrates the value of staged deployments. Testnets allow developers and independent researchers to identify unexpected effects before a change reaches the network that holds real user funds and supports live applications.
Gas schedules are part of a blockchain’s security model. If an operation is priced too cheaply, an attacker may be able to force nodes to perform expensive work at a relatively low cost. If costs are changed without accounting for existing contract behavior, applications may encounter unexpected failures. The challenge is to improve economic security without breaking legitimate software.
The episode also highlights why open-source protocol development requires coordination among researchers, client teams, infrastructure operators and application developers. A technically sound proposal still needs compatibility analysis, test coverage and a safe rollout plan.
What happens next?
Ethereum’s developers must determine which projects depend on the affected gas assumptions, assess the severity of those dependencies and decide whether code changes, specification revisions or developer guidance are needed. The Hoodi testnet activation date has not been reset in the November 6 update. A mainnet activation date should therefore not be treated as confirmed.
For now, Glamsterdam remains a work in progress. Its broader goals—more efficient block construction, better preparation for parallel processing and more sustainable state growth—remain part of Ethereum’s scaling discussion, but the precise feature set and schedule can change as testing continues.
Conclusion
The Glamsterdam delay is a cautious engineering decision rather than a failure of Ethereum’s live network. EIP-8037 and EIP-8038 seek to make gas charges better reflect the real costs of storing and accessing blockchain data, but those changes can affect applications built around today’s rules. By stopping the next Hoodi testnet step while researchers investigate, Ethereum’s developers are prioritizing compatibility and security over a rushed timetable.
The key takeaway for the wider blockchain industry is straightforward: scaling is not only about processing more transactions. It also requires sustainable data costs, predictable execution and careful testing across the software ecosystem.
Image assets and publishing details
Featured image prompt: Create an original editorial technology illustration, 16:9 landscape. A luminous Ethereum-inspired crystalline network structure at the center, branching validator nodes and subtle circuit pathways, a restrained dark navy and violet palette, a small visual motif suggesting a software upgrade being carefully paused for inspection. No logos, no text, no coins, no financial chart imagery.
Featured image title: Ethereum Glamsterdam Upgrade Testing Delay
Featured image ALT: Abstract Ethereum blockchain network illustration representing the delayed Glamsterdam protocol upgrade.
Featured image caption: Ethereum developers are reviewing potential gas-accounting compatibility issues before advancing Glamsterdam testing.
First in-article image prompt: Original clean technical infographic-style illustration, 16:9 landscape, showing two connected layers of a blockchain database: computational execution on one side and permanent state storage on the other, with clear visual separation and simple unlabeled icons. Professional editorial design, dark background with restrained cyan accents, no words or logos.
Image title: Ethereum Gas Accounting and State Storage
ALT: Conceptual diagram showing Ethereum transaction computation separated from permanent blockchain state storage.
Caption: EIP-8037 proposes a separate accounting model for the long-term cost of creating blockchain state.
Second in-article image prompt: Original 16:9 editorial technology illustration of a blockchain test network under review: validator nodes connected in a distributed mesh, a central software update represented by modular blocks, and a magnifying-glass inspection motif. Modern realistic 3D rendering, professional newsroom style, navy and teal palette, no text, no logos.
Image title: Ethereum Glamsterdam Testnet Security Review
ALT: Distributed blockchain validator network undergoing a software upgrade and security review.
Caption: Testnet validation gives developers and security researchers a chance to identify compatibility problems before mainnet activation.