Ethereum co-founder Vitalik Buterin has backed EIP-8037, a proposal that would sharply increase the gas charged when transactions create permanent blockchain state while separating those costs from ordinary execution. In his November 16 explanation, Buterin argued that Ethereum can expand execution capacity much faster than it can safely expand the database every node must maintain. The objective is to let Ethereum process more computation without allowing state storage requirements to grow at the same rate.
The official EIP-8037 specification introduces a cost-per-state-byte mechanism currently set at 1,530 gas and a separate state-gas accounting model. Buterin’s examples put total new-account creation at about 197,900 gas versus 36,600 today, a fresh storage slot at 110,020 versus 22,100, and deployment of a 24 KiB contract at roughly 37.8 million versus 4.95 million. These figures are gas units rather than fixed transaction fees, so the actual ETH cost still depends on the prevailing gas price.
My views on EIP-8037:https://t.co/WUeR5lxJiC pic.twitter.com/eUnHJiUsgk
— vitalik.eth (@VitalikButerin) November 16, 2026
Higher State Costs Create Compatibility Risks
The repricing addresses a growing infrastructure constraint. EIP-8037 estimates that Ethereum state currently expands by roughly 116 GiB annually and targets approximately 120 GiB per year at a reference 150 million block gas limit. Buterin has framed state growth as harder to scale than execution because larger databases increase storage, synchronization and state-access requirements for node operators. Charging more for permanent data is intended to preserve room for higher throughput without shifting excessive hardware costs onto validators and independent nodes.
The trade-off is backward compatibility. Ethereum developers have documented eight EVM assumptions that can change under EIP-8037 and companion proposal EIP-8038, including hardcoded gas limits, gas stipends and logic based on gasleft(). The Ethereum Foundation had already urged developers to conduct Glamsterdam gas-repricing compatibility testing before broader rollout. Most applications are not expected to break, but contracts whose correctness depends on specific gas behavior require additional review.
One example raised by Buterin involves an OP Stack bridge path with a hardcoded 40,000-gas allowance. Under the proposed schedule, operations that create new state could exceed that amount and fail in ways the surrounding application was not designed to handle. Merkle-tree distributions are one alternative Buterin suggested for airdrops, while UTXO-like structures and privacy-preserving keyed nonces could eventually reduce dependence on conventional storage slots. The issue is therefore not simply higher fees but whether existing applications embed assumptions that the new accounting model invalidates.
Glamsterdam Remains Under Review
Those concerns have already changed Ethereum’s deployment schedule. Glamsterdam successfully reached Sepolia on October 6, but developers later postponed the Hoodi activation while EIP-8037 and EIP-8038 underwent additional audits. The current Glamsterdam upgrade status still shows no replacement Hoodi date and no announced mainnet activation. A testnet deployment therefore should not be confused with final specification approval or mainnet activation.
The Ethereum Foundation said four reports of potentially affected deployed contracts had already been received by November 9, prompting audits from ChainSecurity and Dedaub and a dedicated November 16 testing call. Financial publication AD HOC NEWS also noted on November 17 that compatibility findings were moving into the next core-developer review. The current process is assessing whether the risks can be mitigated operationally or whether the specifications themselves need revision.
ACDE #249 is scheduled for November 19 at 14:00 UTC, with Glamsterdam formally on the agenda. Ethereum Foundation guidance says developers will discuss the audit findings and possible next steps without a pre-committed outcome. Vitalik’s support strengthens the technical case for EIP-8037, but the proposal’s final parameters and Glamsterdam deployment schedule remain subject to the core-development process.
