The Ethereum ecosystem is on the brink of significant changes related to the activation of the Glamsterdam hard fork. My analysis shows that this upgrade brings not only improvements but also hidden threats to a number of critically important infrastructure components.
The core of the issue: EIP-8037 and the new gas model
At the heart of the upcoming changes lies proposal EIP-8037, which introduces a separate state-gas dimension for operations that create new blockchain state. This radically changes the approach to calculating transaction costs. While a regular ETH transfer to an existing address will retain the familiar cost of 21,000 gas units, sending funds to a new, previously unused address will result in an additional fee being charged.
Of particular concern is the fact that wallets, indexers, and fee estimation tools are in the crosshairs. Developers should immediately check their systems for the use of a "hardcoded maximum gas limit." Such solutions, as the Ethereum developer team warns, will very likely stop working correctly after the upgrade is activated and will require urgent refinement.
A critical call to developers
I strongly recommend that teams review smart contracts that rely on outdated logic where 21,000 gas units are considered universal coverage for any ETH transfer. Additionally, code that calculates fees solely based on gas volume without accounting for its type is also at risk. Testing on the public Plataberget testnet, launched on August 13, 2026, is a mandatory step for anyone who wants to avoid downtime after the upgrade.
The activation of Glamsterdam on the testnet is scheduled for August 20. This will be followed by a feedback and client software update phase that will take about a month. Only after that will the changes be tested on the Sepolia and Hoodi testnets before going live on the mainnet.
In a broader context, this upgrade is just part of a large-scale Ethereum development strategy. Recently, Vitalik Buterin outlined quantum resistance and artificial intelligence as key priorities for the network. Glamsterdam is an important step in this direction, but it requires attentiveness and readiness from the entire developer community.
My expert opinion: the market often underestimates the complexity of infrastructure upgrades. The current situation is a classic example of how protocol-level changes can create short-term volatility and technical failures. Investors and developers should factor this risk into their plans rather than relying on a "magical" upgrade without consequences.