Why Vitalik Buterin Thinks Blockchain Speed Is Being Solved the Wrong Way
Vitalik Buterin argues Ethereum should scale by increasing bandwidth, not chasing lower latency, to preserve decentralization and long-term security.
As blockchain networks race to scale, the debate over speed has increasingly focused on latency, the time it takes for data to move across a network. Vitalik Buterin believes that fixation is misplaced. According to Ethereum’s co-founder, expanding bandwidth is not only more realistic but fundamentally safer than aggressively reducing latency, especially for a global, decentralized system.
In recent remarks, Buterin argued that Ethereum’s future scalability hinges on increasing how much data the network can handle, rather than shaving milliseconds off confirmation times. Technologies such as Peer-to-Peer Data Availability Sampling and Zero-Knowledge Proofs, he said, already allow Ethereum to scale “thousands of times” beyond its current capacity without undermining decentralization. His broader point was clear: scale does not have to come at the expense of resilience.
Latency, by contrast, is constrained by physics and economics. Buterin pointed out that Ethereum must support node operators in rural regions, homes, and environments far removed from professional data centers. Reducing latency too aggressively risks centralizing participation in well-connected urban hubs. If operating a node outside New York cuts staking rewards by even a small margin, he warned, economic gravity will eventually pull validators into a handful of locations.
“Ethereum itself must pass the walkaway test,” Buterin said, arguing that the network cannot rely on constant social coordination to preserve decentralization. Market incentives, in his view, must carry most of the burden. This reality places hard limits on how far latency can be pushed without tradeoffs that would quietly erode censorship resistance and anonymity.
That does not mean Ethereum is standing still. Buterin acknowledged there is room to reduce latency from today’s levels through targeted improvements, particularly in peer-to-peer networking and erasure coding. These changes can shorten message propagation times without forcing individual nodes to adopt higher bandwidth connections. He also suggested that using chains with smaller node counts per slot could eliminate costly aggregation steps, allowing latency reductions to occur within a single subnet.
Even under optimistic assumptions, however, Buterin sees latency gains as incremental. He estimated that such optimizations might yield a three- to six-fold improvement, lowering moderate latency into a two-to-four range, but not transforming Ethereum into a system designed for ultra-low-latency use cases.
This limitation, he argued, is not a failure but a design choice. Buterin described Ethereum as “the world’s heartbeat,” a base layer optimized for security, decentralization, and global consensus rather than raw speed. Applications that need to move faster than that heartbeat will continue to rely on layer-two networks and off-chain components. The rise of artificial intelligence, he added, will only reinforce this pattern, as many AI-driven applications will inevitably demand faster execution than any global base layer can safely provide.
Earlier this week, Buterin also reiterated his belief that Ethereum has effectively resolved the blockchain trilemma through the deployment of zkEVMs and PeerDAS on mainnet. Together, these technologies, he said, deliver decentralization, high bandwidth, and robust consensus at scale. The Ethereum Foundation is now focused on tightening cryptographic guarantees, with plans to require 128-bit provable security by the end of the year and further milestones in 2026.
The message behind Buterin’s comments is conservative in the best sense of the word. Ethereum’s path forward is not about chasing theoretical speed records, but about scaling in ways that preserve the network’s core promise: a system that works for everyone, everywhere, without asking users to trust that decentralization will somehow be patched back in later.



