Ethereum developers have proposed two competing solutions aimed at preventing the upcoming Glamsterdam upgrade from disrupting existing smart contracts due to changes in gas pricing rules. As concerns grow over adjustments to the network’s gas billing rules, this issue is attracting increased attention.
Developers Leo Glisic and Giulio Rebuffo submitted separate proposals on Sunday, November 8, outlining two different approaches to introducing a new gas fee structure while minimizing disruption to applications already running on Ethereum.
These proposals appeared after a security warning that forced developers to postpone parts of the Glamsterdam test schedule. Some existing smart contracts rely on fixed gas costs, and changes to these costs could cause transactions to fail or disrupt applications that cannot be updated after deployment.
Ethereum developers propose two gas pricing models
Glisic's proposal, EIP-8488, introduces a separate set of instructions for newly deployed smart contracts while allowing existing contracts to continue using their current gas rules.
Under this proposal, new contracts will use V2 opcodes with pricing revised according to EIP-8037 and EIP-8038. Existing contracts will retain their original pricing structure, allowing developers to introduce these changes without forcing legacy applications to adapt.
Rebuffo proposed a different approach in another draft: introducing two separate gas accounting systems for each transaction.
One set will calculate how much gas the contract consumed under the old rules, to preserve the conditions expected during execution; the other set will calculate the actual transaction fees based on the revised pricing schedule.
He acknowledged in the proposal that this design has not yet been implemented in any execution client or tested for consensus. Neither proposal has been approved for inclusion in Glamsterdam.
Why Glamsterdam's gas adjustment has raised security concerns
Compatibility concerns stem from EIP-8037 and EIP-8038, which alter how Ethereum charges for creating and accessing blockchain state.
EIP-8037 will increase the base gas cost for creating smart contracts from 32,000 to 183,600, excluding additional execution and code storage costs.
Although these changes aim to reflect the resources consumed by blockchain activity, security researchers warn that existing applications may not yet be prepared for the revised fees.
As previously reported by crypto.news, the security firm ChainSecurity identified that eight assumptions in existing smart contracts could fail under the proposed gas rules.
Some contracts reserve a fixed amount of gas for external calls, while others rely on specific behaviors when a transaction fails. Unexpected changes in gas consumption may disrupt these operations.
Anonymous developer banteg warned on X that analyses have indicated approximately 200,000 contracts may be affected, and methodological issues could mean the actual number is higher.
The developer stated that these concerns extend beyond isolated coding errors to the deployment and operation of multiple well-known protocols.
The Ethereum community is divided on the risks of Glamsterdam.
The proposed changes have drawn criticism from developers and DeFi industry professionals, who argue that Ethereum should address compatibility issues before moving forward.
Curve Finance founder Michael Egorov warned on X that Glamsterdam could cause serious issues if developers proceed without addressing these risks.
Dear @ethereum—please don’t break this chain. It appears that proceeding with Glamsterdam in its current form could lead to another emergency hard fork rollback, accompanied by significant controversy,” Egorov wrote.
Ryan Berckmans, a member and investor in the Ethereum community, initially supported proceeding with the upgrade, arguing that Ethereum cannot guarantee that gas pricing for all existing applications will remain unchanged.
However, after reconsidering compatibility concerns, Berckmans changed his position.
“We clearly shouldn’t continue pushing forward with the Glam activation as quickly as possible. I was wrong earlier,” he wrote on X.
Security researcher pcaversaccio takes a stronger stance, arguing that Glamsterdam should not be deployed in its current form.
“In my opinion, Glamsterdam should never be released in its current form, absolutely not,” the researcher wrote, noting that these gas changes were allegedly submitted to Ethereum core developers weeks ago.
The Glamsterdam test is still postponed.
Ethereum developers have postponed the scheduled October 26 activation of Hodai due to concerns about how the revised gas rules might affect contracts already deployed on the mainnet.
This extension involves the Amsterdam executive layer update, the Gloas consensus change, and the plan to increase Hoodi’s gas limit to 200 million.
On November 6, Ethereum Foundation developer Marius van der Wijden stated that the organization is collaborating with ChainSecurity and Dedaub to review affected applications and gather developer feedback.
At a developer meeting on October 29, an initial discussion took place regarding a subsequent private Glamsterdam test as early as November 16–20. However, this timeline was established before two competing proposals were submitted.


