Vitalik Buterin Says Ethereum Has Finally Solved the Blockchain Trilemma

Ethereum co-founder Vitalik Buterin says the network has finally cracked one of crypto’s longest-standing challenges: the blockchain trilemma. 

In a post on X over the weekend, Buterin argued that recent and upcoming upgrades mean Ethereum can now achieve decentralization, security and scalability simultaneously — not as theory, but through live, production-ready code.

According to Buterin, the combination of peer data availability sampling (PeerDAS) and Zero-Knowledge Ethereum Virtual Machines (ZK-EVMs) represents a structural shift in what Ethereum is capable of as a decentralized network.

“Now, Ethereum with PeerDAS (2025) and ZK-EVMs (expect small portions of the network using it in 2026), we get: decentralized, consensus and high bandwidth,” Buterin wrote. “The trilemma has been solved — not on paper, but with live running code.”

PeerDAS Moves Scalability On-Chain

PeerDAS is a data-availability technique that allows Ethereum nodes to verify large amounts of data without downloading it in full. The feature was introduced as part of the Fusaka upgrade in December and is already live on the mainnet.

The improvement directly targets Ethereum’s ability to scale without sacrificing decentralization. Instead of forcing validators to handle ever-growing data loads, PeerDAS enables lightweight verification, making it easier for a broader set of participants to run nodes.

ZK-EVMs Still Early, But Performance-Ready

While PeerDAS is live, ZK-EVMs remain in what Buterin described as an “alpha stage.” ZK-EVMs allow Ethereum blocks to be validated using zero-knowledge proofs, dramatically reducing the computational burden required to verify transactions while maintaining cryptographic security.

Although the technology has existed for some time, Buterin said ZK-EVMs are only now reaching production-quality performance. Security hardening, however, remains the main hurdle before they can be widely deployed at the base layer.

He outlined a roughly four-year timeline for full integration. Initial use cases could emerge as early as 2026, with ZK-EVMs gradually becoming the primary method for block validation toward the end of the decade.

A Multi-Year Rollout Plan

Buterin provided a detailed roadmap for how Ethereum’s scalability gains are expected to unfold. 

In 2026, the network could see significant gas-limit increases that do not rely on ZK-EVMs, enabled by mechanisms such as block access lists (BALs) and enhanced proposer-builder separation (ePBS). This year may also mark the first opportunities to run a ZK-EVM node on Ethereum.

Between 2026 and 2028, Ethereum developers are expected to implement gas repricings, changes to state structure, and shifts in execution payloads into blobs — all aimed at making higher gas limits safe. 

From 2027 to 2030, Buterin expects further large gas-limit increases as ZK-EVMs mature into the network’s dominant validation method.

A Decade-Long Effort

Buterin said Ethereum’s current position is the result of nearly ten years of continuous research and development. He traced the journey back to his first writings on data-availability challenges in April 2017, describing the process as slow, iterative, and technically demanding.

“This was a 10-year journey,” he wrote. “But it’s finally here.”

The blockchain trilemma — the idea that decentralization, security and scalability cannot be fully achieved at the same time — has long shaped design trade-offs across the industry. Many blockchains prioritize speed and low fees early on, often at the expense of decentralization.

Buterin pointed to Bitcoin as a contrasting example, describing it as highly decentralized and secure, but limited in scalability by design. Ethereum’s approach, he argues, has been to methodically expand capacity without compromising its core principles.

If the roadmap unfolds as planned, Ethereum may offer the clearest real-world example yet of a blockchain escaping the trilemma — not through shortcuts, but through years of incremental engineering.