A repricing proposal with wider consequences
Glamsterdam is intended to improve Ethereum’s long-term performance by changing how the network charges for persistent state, the information stored by smart contracts between transactions. The proposals identified as EIP-8037 and EIP-8038 would substantially increase the cost of creating and accessing that state. They would also alter how gas is counted when contract calls fail.
In principle, repricing can be a rational response to changes in Ethereum’s technical and economic profile. Gas fees are not only a payment mechanism. They are also a way to allocate scarce computing, storage and validation resources. If certain operations consume more resources than their current prices reflect, raising their cost can discourage inefficient use and improve incentives for application developers.
The difficulty is that smart contracts are not ordinary software packages that can be routinely patched by a central operator. Many are deployed with code that cannot be changed, or can be changed only through governance mechanisms that may not be available, practical or trusted by users. Their assumptions about gas costs can therefore become part of their operating environment.
That is why a change intended to improve network economics can produce a compatibility problem. A contract that worked under existing gas rules may fail after the upgrade if it cannot complete an operation within the amount of gas supplied by a user or another contract. In applications that manage deposits, collateral or other user funds, a failure can have consequences beyond a temporary inconvenience.
CoinDesk reported on November 9 that developers are considering two competing responses to the problem. One approach would preserve legacy pricing for existing contracts. The other would introduce dual accounting, allowing older applications to continue operating under familiar rules while newer code uses the revised framework.
The dispute reflects a recurring challenge for mature blockchain networks. Ethereum must change to remain competitive and sustainable, but every change is evaluated against a large installed base of applications, financial positions and infrastructure. The network’s promise of backward compatibility is valuable precisely because users and businesses expect deployments made today to remain usable after future upgrades.
Why failed calls matter
The proposed change to failed contract calls is particularly sensitive. Smart contracts frequently call other contracts, and those calls can fail for many reasons, including invalid inputs, insufficient balances or conditions that are not met. Developers often build systems around the expectation that a failed call will consume gas in a predictable way and that the surrounding transaction can handle the failure.
Changing that accounting can affect whether a transaction completes, how much it costs and how much gas remains available for subsequent operations. A contract may be designed to attempt an action, detect failure and then execute a fallback path. If the cost of the failed attempt changes materially, the fallback may no longer have enough gas to run.
This kind of incompatibility may not be visible in simple testing. An application can appear to function under ordinary conditions while failing during unusual market activity, congested periods or specific combinations of calls. That creates a risk for contracts that hold funds because users may encounter failures precisely when they need to withdraw collateral, move assets or respond to changing conditions.
The concern is not limited to individual applications. Wallets, bridges, decentralized exchanges, lending markets and other protocols often interact through multiple layers of contracts. A change in one gas assumption can move through that chain. A wallet may need to estimate a different amount of gas. A protocol may need to update transaction construction. An automated service may need new rules for deciding whether a call is safe to submit.
Those effects also matter to institutions assessing Ethereum as financial infrastructure. Banks, asset managers and payment companies typically evaluate not only whether a network can settle transactions, but whether its upgrades can be managed with clear notice and predictable operational requirements. An upgrade that forces broad changes to established contracts may increase the cost of deployment and compliance testing, even if the underlying technical goal is sound.
Testnet delays exposed the risk
The compatibility issue became more urgent after security concerns delayed a planned test on the Hoodi network. CoinDesk reported on October 23 that developers postponed the test after security teams identified risks to existing contracts.
Testnets are designed to expose precisely these types of problems before a change reaches Ethereum’s main network. A delay does not necessarily indicate that the upgrade is failing. It can instead show that the development process is identifying risks early enough for developers to debate alternatives. In this case, however, the delay emphasizes how a change to gas rules can become a security matter rather than a narrow performance adjustment.
The episode follows another Glamsterdam-related issue involving staking deposits. CoinDesk reported on October 27 that developers fixed a bug that could have directed staking deposits to builders. That problem was different from the gas repricing dispute, but it reinforced the importance of extensive testing for an upgrade that touches core transaction and execution behavior.
For users, these incidents may look unrelated. For infrastructure operators, they share a lesson: changes at the protocol layer can produce effects far from the code being modified. A gas accounting adjustment can affect application logic, while an error in deposit handling can threaten the movement of assets. Both require developers to evaluate not just whether a new feature works, but how it interacts with assumptions embedded across the ecosystem.
Two possible paths
The first proposed solution, preserving legacy pricing for existing contracts, offers a straightforward form of protection. Contracts deployed before the upgrade could continue using the gas rules under which they were created, while new contracts would face the revised pricing. This would reduce the immediate risk to applications that cannot be upgraded.
Such a system could, however, add complexity to Ethereum’s execution environment. Nodes and developers would need to determine which pricing schedule applies to a contract. Tools for gas estimation, auditing and application development would need to account for different rules. Over time, the distinction between old and new contracts could become a permanent feature of the network.
The second option, dual accounting, could provide a more flexible transition. Instead of treating the old and new systems as entirely separate, Ethereum could track resource use under both frameworks and apply rules designed to preserve the behavior of older applications. This might make it easier to target the underlying resource problem while limiting disruption.
Dual accounting also creates its own governance and implementation questions. The system would need to define which operations qualify for protection, how the accounting interacts with nested calls and how long the legacy treatment remains available. A mechanism designed as a temporary bridge could become difficult to remove if important applications continue to depend on it.
Neither approach eliminates the central tradeoff. Protecting existing code may reduce the efficiency gains that motivated repricing. Applying new prices universally may deliver a cleaner protocol design but expose users and applications to failures that they cannot easily correct. Ethereum’s developers must decide how much technical debt the network should carry in order to preserve continuity.
A policy question for decentralized infrastructure
The Glamsterdam debate is ultimately about more than gas. It concerns how decentralized systems make policy when they have millions of users, independent developers and assets distributed across jurisdictions.
Traditional financial infrastructure generally handles major technical changes through controlled migrations, contractual notices and coordinated upgrades. Blockchain networks operate differently. A protocol change can be approved through a public development process, but implementation is distributed among node operators, application teams, wallet providers and users. Agreement among core developers is necessary, but it is not sufficient to guarantee a smooth transition.
That makes advance testing and transparent communication central to Ethereum’s institutional credibility. Developers need to establish which contracts could be affected, give application teams tools to test their deployments and explain what users must do before the upgrade. Wallets and protocols may need to publish updates, while custodians and other regulated participants may need to review operational and risk controls.
The issue also has international implications. Ethereum is used across markets with different rules for custody, payments, securities and consumer protection. An upgrade that requires applications to change how they handle funds can become relevant to compliance teams and supervisors, even when the underlying change is purely technical. The more Ethereum is used for tokenized assets and financial services, the more important predictable upgrade procedures become.
Glamsterdam therefore presents a test of institutional maturity. Ethereum must balance the need to price resources accurately against the obligation to avoid surprising users who rely on contracts deployed under earlier rules. Preserving compatibility may slow or complicate the upgrade, but failing to manage the transition could impose larger costs through broken applications, emergency fixes and loss of confidence.
The final design will determine whether the network can improve its capacity while maintaining continuity across its existing ecosystem. If developers find a solution that protects older contracts without permanently undermining the purpose of repricing, Glamsterdam could demonstrate that Ethereum can evolve without abandoning its installed base. If not, the debate may establish a more difficult precedent: that future upgrades require users to choose between the benefits of new infrastructure and the reliability of applications they already use.
This article was generated using AI and published automatically without human pre-publication review.
Read and checked by admin on 11/16/2026
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.