For nearly a decade, one constant in Ethereum development has been simple: sending native ETH from one account to another consumed exactly 21,000 gas.
That foundational rule is about to change.
With Ethereum’s upcoming 'Glamsterdam' upgrade, EVM gas accounting is shifting away from a flat execution fee model. Under the new specification, transferring ETH to a brand-new, zero-balance address will carry a different gas cost than transferring to an existing account with established state.
Why does this matter?
Many legacy smart contracts, wallet interfaces, and developer SDKs have hardcoded `21000` as a fixed gas limit for standard ETH transfers. If tools rely on this static number after Glamsterdam goes live, transactions sent to uninitialized addresses risk running out of gas and failing.
The Ethereum Foundation has urged developers and infrastructure providers to test their tools on the Plataberget testnet to ensure gas estimation routines dynamically query node RPCs rather than assuming static overhead.
For everyday users, your primary responsibility will be ensuring your self-custody apps and web3 wallets are updated ahead of mainnet activation. As ETH trades near $1,913, protocol maintenance and EVM state efficiency remain central to the network's long-term roadmap.
How do you think wallet developers should handle legacy smart contracts that hardcoded gas limits?
That foundational rule is about to change.
With Ethereum’s upcoming 'Glamsterdam' upgrade, EVM gas accounting is shifting away from a flat execution fee model. Under the new specification, transferring ETH to a brand-new, zero-balance address will carry a different gas cost than transferring to an existing account with established state.
Why does this matter?
Many legacy smart contracts, wallet interfaces, and developer SDKs have hardcoded `21000` as a fixed gas limit for standard ETH transfers. If tools rely on this static number after Glamsterdam goes live, transactions sent to uninitialized addresses risk running out of gas and failing.
The Ethereum Foundation has urged developers and infrastructure providers to test their tools on the Plataberget testnet to ensure gas estimation routines dynamically query node RPCs rather than assuming static overhead.
For everyday users, your primary responsibility will be ensuring your self-custody apps and web3 wallets are updated ahead of mainnet activation. As ETH trades near $1,913, protocol maintenance and EVM state efficiency remain central to the network's long-term roadmap.
How do you think wallet developers should handle legacy smart contracts that hardcoded gas limits?