Vitalik Buterin just dropped a new Ethereum L1 scaling roadmap – EIP-4444 + Stateless Clients = leaner nodes, massive throughput, and no more datacenter flexing

Cryptocurrency News and Public Mining Pools

Vitalik Buterin just dropped a new Ethereum L1 scaling roadmap – EIP-4444 + Stateless Clients = leaner nodes, massive throughput, and no more datacenter flexing

Vitalik Buterin just dropped a new Ethereum L1 scaling roadmap - EIP-4444 + Stateless Clients = leaner nodes, massive throughput, and no more datacenter flexing

Just crossed this morning with a few Tweets claiming something Vitalik proposed and after a research I found it here

https://preview.redd.it/en0dk3j7ko1f1.png?width=776&format=png&auto=webp&s=2a41b1d9afff79df249af996f24898f7d789a1d8

Vitalik Buterin just dropped a new and fresh L1 scaling roadmap for Ethereum and it comes with spicy upgrades that looks to supercharge performance without making it hell to for nodes.

The plan centers around EIP-4444 and Stateless clients but giving another think about what full nodes should be doing in the first place.

According to the proposal, EIP-4444 will allow nodes to prune old historical data (down to approximately 36 days). This will massively reduce the disk space needed. Long term data will live in a distributed storage network meaning that running a node won't need a datacenter anymore.

Regarding the Stateless clients, it aims to let nodes verify blocks without keeping the whole state. This will also slash storage more and open a door to a new best called "partially stateless nodes". These nodes basically will keep only the parts of the state you care about like active EOAs, ERC20/721 contracts or DeFi apps and can still respond to local RPCs. I like thinking of them like little substations or satellites.

This proposal comes because Vitalik is worried about only increasing the L1 gas limit that can compromise node usability but with this new approach Ethereum could 10-100x throughput without centralizing around mega nodes or third party RCPs.

Some will ask, why not rely on ZK-EVMs, etc? Well, this proposal removes the need of depending on third parties and still scale. This is a common practice in software engineering, trying to rely the less in third parties to have full control of what you have.

What do you think? Are you excited to see it running?

Source:

submitted by /u/kirtash93
[link] [comments]