Buterin says post-Hegotá Ethereum shifts to proof-based verification by 2030
He framed Hegotá next year as the last “normal” fork and put wallet-metadata privacy and faster finality on the roadmap.
Vitalik Buterin laid out a 2030 Ethereum vision that moves the network away from universal re-execution and toward proof-based verification with more computation pushed off-chain. He framed next year’s planned Hegotá upgrade as the last “normal” fork before that proof-centric era becomes Ethereum’s primary roadmap story.
Buterin’s ‘Cryptographic World Computer’ Puts Proofs at the Center of Ethereum’s 2030 Plan
Vitalik Buterin published a post titled “The cryptographic world computer” on Sep. 27 describing an Ethereum end-state in 2030 that may still be called a blockchain, but would function differently by pairing the chain with cryptographic proofs and networks of computers working outside it.
The market-relevant part is the sequencing he attached to it. Buterin said Ethereum’s transformation would accelerate after the planned Hegotá upgrade next year, and he characterized Hegotá as Ethereum’s last “normal” fork, built with technology that would look familiar to someone working on Ethereum in 2015. After that, he wrote, upgrades would increasingly lean on mathematical proofs, tools that check software for errors, and security designed to withstand future quantum computers.
Buterin also framed the post-Hegotá period as a regime change in what counts as “core” work on Ethereum. “Starting after Hegota, this transformation becomes Ethereum's primary story,” he wrote, describing the intended outcome as “much more cheap, scalable and private high-security computation than anything that could be done with the previous era's technology alone.”
From Everyone Re-Executing to Many Verifying: The Proof-Based Verification Pitch
Ethereum’s current security model gets its assurance from repetition. A computer fully checking Ethereum repeats the calculations behind transactions, verifying that a sender had enough funds and that an application followed its rules. That redundancy keeps the network honest, but it also caps scaling because adding more computers does not automatically increase throughput when each is busy checking much of the same activity.
Buterin’s proposed shift is to make verification cheaper than execution by default. In his framing, a computer could process transactions and produce a short mathematical proof that it followed the rules, and other computers could check that proof far faster than re-running the original computation. He also described “separate spot checks” as a way to establish that transaction records remain available for inspection, even as different machines tackle different jobs and cross-check one another’s results.
He positioned this as the missing ingredient that made older “split the work” ideas impractical. “Back then, this was not viable for one primary reason: the missing ingredient was verification,” Buterin wrote, referring to what Ethereum developers wanted to do a decade ago.
The catch is that parallelism does not remove ordering problems, it just changes where they get resolved. Buterin noted Ethereum would still need to settle questions where order matters, such as deciding which of two payments spending the same funds came first, and he suggested more of the work behind payments could be completed beforehand, with proofs combined to reduce the information recorded on-chain. The post describes that combination conceptually, without a concrete deployment path.
Post-Hegotá Priorities: Wallet-Metadata Privacy and the 8–32 Second Finality Target
Buterin put privacy on the same tier as scaling, and he defined it more broadly than private transfers. His privacy goals include hiding wallet activity metadata, including balance-check requests that can reveal which addresses a user monitors when a wallet queries an outside server.
In his example, even if payments are private, the operator of the server answering balance queries can learn which accounts a person follows. Buterin envisaged hiding those requests alongside payment details and the rules an account uses to approve spending, so a business could keep payments confidential without revealing its accounts whenever an employee checks a balance.
On performance, Buterin’s 2030 comparison envisioned payments becoming final, meaning treated as irreversible by the network under normal conditions, in roughly eight to 32 seconds. He did not attach an implementation schedule beyond saying the broader transformation accelerates after Hegotá, and he listed prerequisites that remain open engineering constraints: proofs need to become efficient enough for widespread use, and computers handling separate jobs must coordinate updates to the same balances and application records without interfering with one another.
My read: Hegotá as a narrative inflection point, not a dated catalyst
Hegotá is being framed as a fork you can calendar, but the more important signal is the way Buterin is trying to re-label what comes after it. Calling it the last “normal” fork is less about Hegotá’s EIP set, which is still unspecified, and more about telling the market that proofs and formal methods are meant to become the default substrate for future upgrades rather than a bolt-on scaling theme.
The threshold that matters is whether proof costs fall enough that core developers can credibly treat proof-based verification as the baseline security and scaling path, and whether the parallel off-chain worker model can be made to coordinate shared state without introducing new failure modes. If those two constraints start getting resolved in concrete proposals after Hegotá, the setup starts to look structural rather than narrative-driven, because Ethereum’s throughput ceiling becomes a verification-cost problem instead of a universal re-execution problem.
