Vitalik Buterin wants Ethereum data storage to cost more
Vitalik Buterin backs EIP-8037, which would raise the gas cost of adding new data to Ethereum, according to BeInCrypto, while normal transfers stay largely unaffected.

The facts
- According to BeInCrypto, Vitalik Buterin backs EIP-8037, a proposal in the Glamsterdam upgrade that raises the cost of adding new entries to Ethereum.
- Buterin modelled a tenfold capacity increase without the change: stored data would grow by roughly 1,100 GiB a year, against about 110 GiB today.
- In the current draft, a new storage entry needs about five times more gas than today, sending ETH to a brand-new address about seven times more, and deploying a large smart contract about eight times more.
- Older apps with fixed gas amounts in their code could see transactions fail if costs rise, and core developers and auditors are gathering evidence on deployed contracts.
Case notes · Danny's take
Why it matters
Scaling is not only about speed. Every new piece of data has to be stored by every node operator, for good. Buterin's argument is that the person who creates that burden should pay for it. That's a trade-off, not a free lunch: a bigger network, but a pricier one for anyone adding new data. Airdrops and launchpads are the ones to watch.
For traders
Don't trade the headline. This is a draft proposal, and the final fee also depends on network demand. Watch how the Glamsterdam discussions develop, and whether activity in airdrop and launchpad-heavy corners of the chain changes as the costs become clearer.
For builders
Avoid hardcoded assumptions about gas rules, block timing or transaction formats, as Buterin advises. Audit older contracts that rely on fixed gas amounts. Design to store less data, for example by posting one summary for an airdrop and letting users claim and pay their own gas.
Not financial advice. Do your own investigation.
This story was summarised with AI from BeInCrypto's reporting and checked against our editorial policy. Danny's take reflects his views. Disclaimer.
