That risk has already slowed the upgrade. Glamsterdam runs on one of Ethereum’s practice networks, copies of the blockchain where developers test changes before they touch real money, but a second rehearsal set for Oct. 26 was postponed after security researchers raised the alarm.
“imho Glamsterdam should not be shipped in its current form, period,” security researcher pcaversaccio wrote on X, referring to the gas increases, which he said he had flagged to Ethereum’s core developers two weeks earlier.
Pseudonymous developer banteg was blunter. “besides the already huge list of 200,000 affected contracts in ethereum/repricing-impact, i found multiple methodological issues that make it miss many more,” he wrote on X. “it affects deployment and operation of several high profile protocols, not just some random devs misusing opcodes that were given to them.”
Glisic’s draft, EIP-8488, splits Ethereum’s instruction set in two. “Existing contracts keep the legacy schedule,” it says, while “new contracts must use V2 opcodes that carry the EIP-8037/8038 gas schedule.”
Rebuffo’s draft runs two gas meters per transaction instead, one that tracks execution under the old rules and one where “billing uses the new schedule and determines the transaction fee.” It also admits “no execution-client implementation or consensus tests have been run for this design.”
