Vitalik Buterin: Storing Only Merkle Roots On-Chain Won’t Fully Solve Ethereum’s State Data Problem

Ethereum co-founder Vitalik Buterin has weighed in on the ongoing debate over the blockchain’s state storage challenges, clarifying that storing only Merkle roots on-chain — while shifting actual data to users — does not eliminate the underlying scalability issue. In a recent post on X, Buterin explained that the data required for proof verification would still need to be stored and updated, and its size could eventually approach that of the entire state.

The Merkle Root Approach and Its Limitations

Buterin’s comments address a common proposal in Ethereum scaling discussions: reducing on-chain storage to just a cryptographic hash (Merkle root) of the state, with users holding the full data. While this would lower direct blockchain storage costs, Buterin noted that validators and nodes would still need to maintain verification data. Over time, the size of this auxiliary data could grow to rival the full state, undermining the efficiency gains.

“Solutions exist, but they require significant trade-offs and complex components compared to Ethereum’s current structure,” Buterin wrote, signaling that no simple fix is on the horizon.

Context: EIP-8037 and the State Cost Debate

The discussion was prompted by DeFi content creator marilyn100x.eth, who highlighted Ethereum’s long-term state storage cost problem. The creator explained that Ethereum Improvement Proposal (EIP) 8037 aims to address this by raising the cost of creating new contracts, accounts, and storage slots — rather than imposing a recurring storage fee. This approach seeks to discourage state bloat at the point of creation, without penalizing existing users.

State bloat refers to the ever-growing size of Ethereum’s ledger, which stores every account balance, contract code, and storage slot. As the network processes more transactions, the state expands, increasing hardware requirements for node operators and potentially centralizing the network.

Why This Matters for Ethereum Users and Developers

For everyday users, the state storage issue has direct implications for transaction fees and network efficiency. If left unaddressed, rising storage costs could lead to higher gas fees or force smaller nodes offline, reducing decentralization. For developers, understanding the trade-offs of different state management approaches is critical when building dApps that rely on large amounts of on-chain data.

Buterin’s remarks underscore that Ethereum’s path to scalability is not straightforward. While layer-2 solutions like rollups address transaction throughput, the base layer’s state management remains a fundamental design challenge.

Conclusion

Vitalik Buterin’s latest clarification reinforces that Ethereum’s state storage problem requires more than a simple architectural change. Storing only Merkle roots on-chain, while promising, introduces new verification data demands that could negate the benefits. As the community explores proposals like EIP-8037, the focus remains on balancing cost, security, and decentralization — a complex equation with no easy answers.

FAQs

Q1: What is a Merkle root in Ethereum?
A Merkle root is a single cryptographic hash that summarizes all the data in a block or state. It allows efficient verification of data without storing the full dataset on-chain.

Q2: How does EIP-8037 propose to reduce state bloat?
EIP-8037 increases the cost of creating new contracts, accounts, and storage slots, making it more expensive to add data to the state. This discourages unnecessary state growth without imposing ongoing storage fees.

Q3: Why is state storage a problem for Ethereum?
As more users and applications use Ethereum, the state (which stores all account balances, contract code, and data) grows larger. This increases the hardware requirements for running a node, potentially reducing network decentralization and raising transaction costs.