Yes

>>News

>>Vitalik Buterin contends that limiting on-chain storage to Merkle roots alone is insufficient to fully solve Ethereum's state data problem.

Vitalik Buterin contends that limiting on-chain storage to Merkle roots alone is insufficient to fully solve Ethereum's state data problem.

crypthub

about 1 hour ago

Merkle Root Proposal Limits

Storing only the Merkle root of Ethereum’s state on‑chain shifts the full data to users. Vitalik Buterin warns that validators still need verification data, which must be stored and updated. This auxiliary data can eventually approach the size of the complete state, eroding the expected savings. He notes that viable solutions involve complex trade‑offs beyond the simple root approach.

EIP‑8037 and State Cost

EIP‑8037 tackles state bloat by raising the creation cost of contracts, accounts, and storage slots instead of imposing recurring fees. The higher upfront cost discourages unnecessary additions to the state. This method targets growth at the source while leaving existing data untouched. It emerged after concerns raised by the community about ever‑increasing ledger size.

Impact on Users and Developers

A growing state raises hardware requirements for node operators, threatening decentralization. Higher storage demands can translate into increased gas fees for everyday transactions. Developers must weigh trade‑offs when designing dApps that rely on large on‑chain datasets. Understanding these dynamics is crucial for sustainable ecosystem growth.

Broader Scalability Outlook

Buterin emphasizes that Ethereum’s scalability challenge remains unsolved by a single architectural tweak. While roll‑up layer‑2 solutions improve throughput, base‑layer state management still demands careful design. The community continues to explore proposals like EIP‑8037, balancing cost, security, and decentralization. No easy answer exists yet.