Ethereum charges for storing things, and that fee has failed for years to reflect what it costs to keep them on the network's nodes. Every new account created on the network takes up space on the nodes that maintain the blockchain, and that space is paid for once with a gas fee. EIP-8037 proposes multiplying that fee by more than seven, and Vitalik Buterin has come out publicly in support of it just before core developers discuss the results of the next upgrade.
The specific figure is what gives the proposal its meaning. Creating an account would go from costing 25,000 gas units to 183,600, an increase of around 634 percent in units that translates into a direct cost hike for anyone deploying contracts or opening new wallets. With ether hovering around $1,800 on the morning of November 16, the calculation in euros depends on the gas price at any given moment.
The debate is not about charging more on a whim. Ethereum has spent two years trying to raise the gas limit per block, and the same brake keeps appearing: the network's state grows and nodes need more disk. Making storage more expensive shifts that cost to whoever causes it, which is the logic of any fee.
Changes in the proposal
EIP-8037 touches the cost of creating new state, that is, of adding data the network must keep forever. A new account is the simplest case, but not the only one: contracts that are deployed and structures that are initialized also consume that resource. The proposal adjusts the fee so that it reflects the real cost of storing and maintaining that data.
The most-cited number is the account one: 183,600 gas units versus the current 25,000. The figure is not arbitrary; it comes from calculating what it costs in terms of disk and bandwidth for every node in the world to store that account for years. If the current price subsidizes that storage, the new one puts it on the balance sheet of whoever buys it.
The EIP-8037 proposal appears in the official registry and Buterin has publicly backed it. The endorsement matters because the researcher usually reserves his interventions for substantive discussions, and his position moves votes in a process where authority is earned with technical arguments.
Core developers plan to review on November 19 the audit results for Glamsterdam, the network's next upgrade. EIP-8037 is not the only piece of that conversation, and its fate depends on how it fits with the rest of the changes piling up in the same window.
Why is state the problem?
An Ethereum node stores the network's current state: balances, contract code and the data each application needs to function. That state cannot be compressed or archived without ceasing to validate, and it grows with every account and every contract someone deploys. That growth is why running a full node is expensive.
If storage is cheap, the network receives more data than it can digest. Empty accounts, abandoned contracts and structures nobody uses but every node must keep appear. The problem is not users' bad faith; it is that the price of creating state does not reflect the cost of maintaining it for years.
Raising the fee changes the incentive in two directions. Whoever truly needs to create an account pays for it, and whoever created one because it was free thinks twice. The side effect is that it makes legitimate operations more expensive, and that is where the objection from wallet and layer-two teams will come in the discussion.
The balance is not easy to find, which is why the proposal has been in the conversation for months without being resolved. Each side has a different figure in mind and all defend theirs with data.
There is a fourth category that almost never appears in the discussion and is worth keeping in mind: contracts that are deployed for testing and then abandoned without deleting anything written.
Who it makes more expensive and by how much
The most visible case is new wallets. Opening an account on Ethereum today costs a small fee paid with the first transaction, and under the proposal that fee grows. For a user who only wants to receive a payment, the change has no immediate effect; for an application that creates accounts on behalf of its customers, it does.
The second case is contract deployments. A team that creates dozens of auxiliary contracts in a single operation pays for each one, and the increase shows up in the development bill even if it later deletes half of them. That is the part infrastructure teams will negotiate, because it does not distinguish between a contract that will last years and a test one.
The third case is layer twos. Many create accounts on the mainnet when finalizing operations, and their cost model depends on that step being cheap, so the change forces them to redo their forecast. If the fee rises, they must choose between absorbing the cost or passing it on to the user.
None of the three cases breaks the system, and all three change the economics of products that today operate on thin margins and will have to decide whether to absorb the difference or pass it on to the end user.
What Buterin wants to protect
The researcher's endorsement is better understood by reading his underlying argument: Ethereum cannot grow if every node has to store state that grows without limit. Layer scalability and raising the gas limit depend on storage having a realistic price, and that price is the condition for the network to remain verifiable by anyone.
That same reasoning appears in other discussions this year. The debate over four-minute finality and the Glamsterdam delays show a network that wants to move faster without losing the property that distinguishes it: that a user with an ordinary computer can verify the full state.
The trade-off has a political cost. Making a basic operation more expensive is unpopular, and the Ethereum community has a memory for proposals that shift the cost to the small user. Defending the proposal will have to convince people that today's cost hike avoids a bigger problem tomorrow.
The other part of the argument is that storage is not free in any system. In a traditional bank, the cost of maintaining an account is paid by the deposit margin; in an open network, it is paid by all nodes or by whoever creates the state.
November 19: the key date
The first signal will be whether the proposal makes it onto the agenda of the core developers' call or stays in informal conversation. Getting on the agenda means there is a team willing to implement it and a code draft to review.
The second will be the tone of layer twos and wallet teams. If objections focus on timing rather than design, the proposal moves forward with adjustments. If an organized front appears, it gets postponed, as has happened with other state reforms.
The third will be the language of the clients. A proposal that does not reach an execution client does not exist, and the Geth and Reth teams are the ones who end up translating theory into a line of code that can be tested.
For the user, the detail has a practical consequence: if the proposal moves forward, operations that create accounts will be done before the change activates or will be done another way.
The cost of storing everything forever
Ethereum has been built on a promise of permanent availability. Anyone can consult the network's state without asking permission, and that promise has a price that until now was spread diffusely among all participants. The proposal puts it in front of whoever causes it.
That move is the same one the internet made when it stopped giving away email. At first it seemed like a service with no cost, and the cost existed behind the scenes, in servers someone paid for. The difference is that here the bill can be calculated and voted on before it arrives.
The November 19 discussion will not decide Ethereum's future, but it will say where it wants to go. A network that charges for the space it occupies is a network that takes on its own growth, and that is the condition for it to remain the layer where others build.