Vitalik on the "Cryptographic World Computer": The Paradigm Evolution from the Bitcoin Whitepaper to Ethereum

Written by: Vitalik Buterin

Translated by: Saoirse, Foresight News

We call Ethereum "a blockchain," as if it were fundamentally of the same technological class as the Bitcoin created by Satoshi Nakamoto in 2009. Indeed, the two share similarities in many respects; even the "minimal Ethereum" to be built in the future according to the Strawmap will retain the core characteristics of a blockchain. At the same time, however, this technology has undergone tremendous evolution over the past fifteen years and will continue to iterate over the next three. By then, it would be highly reasonable to describe Ethereum's evolving form as a system of an entirely different nature.

Today's Ethereum features general-purpose computation, proof-of-stake mechanics, on-chain applications equipped with zero-knowledge proofs, and layer-2 networks designed for scalability and privacy protection. The future Ethereum will feature computation capacity that can be flexibly tuned between maximum scalability and full generality; multiple multi-party block construction models; deeply optimized proof-of-stake; and zero-knowledge proofs built into the base layer protocol, playing a central role.

This article will outline some of the most critical fundamental differences between blockchains of the 2010s and those of 2030, both from a technical perspective and in terms of the systemic features available to users.

First, we will go through the original Bitcoin whitepaper section by section, contrasting it with Ethereum, using yellow to represent Ethereum in 2015, green for 2025, and blue for 2030.

This diagram is adapted from Satoshi's transaction principle illustration in the Bitcoin paper. It showcases the classic chain-based signature transfer model, while noting that new schemes can aggregate signatures off-chain, submit only a single record on-chain, and frequently replace traditional signatures with zero-knowledge proofs.

This figure contrasts Bitcoin's PoW mechanism with Ethereum's post-2022 PoS: originally relying on iterative nonce searching for condition-matching hashes and block production by a single participant, now shifted to validator signatures, with the future leveraging FOCIL for multi-role decentralized block co-construction, where transaction-related components such as signatures and proofs will be split and aggregated within the mempool.

This excerpt outlines the six-step network operation process from the Bitcoin whitepaper, pointing out its native design lacks capabilities such as mempool aggregation, distributed block construction, and sender anonymization. It also explains improvements brought by Ethereum PoS and PeerDAS: decoupling block construction from fork choice, requiring nodes to download only a small portion of a block, and reducing consensus latency through parallel proofs.

This diagram compares the Merkle tree pruning scheme proposed in the Bitcoin whitepaper with Ethereum's new storage strategy: Bitcoin can delete spent transactions to free up hard drive space, whereas future Ethereum will further reduce storage requirements via state-history separation and SNARK proofs, alongside introducing distributed state storage and diversified storage media optimization.

This figure interprets the privacy approach in the Bitcoin whitepaper: relying solely on public key anonymity can hide identities but leaves transaction amounts exposed, which proves insufficient under modern data analysis. In contrast, ZK‑SNARKs, FOCIL, and EIP‑8288 can build stronger programmable privacy, while challenges regarding query/read privacy and network broadcast privacy still need to be addressed.

Drastic changes will occur across almost every chapter of the whitepaper. For brevity, we have compiled them into the following table:

Nearly all core attributes encompassed by the concept of a blockchain have either already undergone fundamental shifts or are on the verge of underlying transformation:

• Verification: Downloading and re-executing → PeerDAS sampling and SNARK verification
• Consensus: Proof-of-Work → Proof-of-Stake → Deeply optimized Proof-of-Stake
• Block Construction Authority: Single miner generating blocks → Multi-party co-constructing blocks

To borrow an AI-style phrasing, the only objectively credible conclusion (well, the core thesis) is: modern encrypted networks like Ethereum after completing its minimal upgrade are called "blockchains" largely for historical reasons. In reality, it is a hybrid architecture that merges two major systems:

1. Satoshi's core concepts
2. Newly developed, powerful cryptographic tools born from fifty years of academic research, which were either non-existent or immature in 2009

How much cryptography is actually hidden within the crypto stack? A three-year comparison of 2009, 2020, and 2030.

Cryptography is not the only crucial discipline. Fields such as formal verification, database theory, improvements in P2P network theory, information theory, and economics are equally important. However, these technologies are all compatible with this foundational logic: everyone attempts to generate the next block containing a valid proof-of-work, one succeeds and broadcasts it, everyone else downloads the block and re-executes, looping endlessly. Changes at the cryptography level, on the other hand, are entirely different.

So, what does all this mean for users? The most critical conclusion is that the dimensions of trade-offs users must navigate are undergoing earth-shattering changes:

When developing applications, computational structure becomes crucial. In simple blockchains, a byte is a byte, and a unit of Gas is a unit of Gas. But in future architectures: if you cram all computation into a single, indivisible, sequentially executed transaction, the cost for equivalent compute will be significantly higher; whereas if you break computation down into well-encapsulated, independently scheduled tasks that support parallelism or early pruning, preferably completing preprocessing before the transaction enters the finalized block, costs will drop substantially. This will shift developer incentive structures, and over time, the architecture of all Ethereum applications will evolve accordingly: In the long run, we may develop a new programming paradigm — only the core metadata describing non-commutative state transitions and execution order goes on-chain, while all other data is aggregated before being incorporated into the block.

Rational organization of computation allows blockchains to focus more intently on their core tasks.

Perhaps the most profound shift lies in this: the decentralized nature of networks is no longer merely a performance burden endured in exchange for security and robustness; in certain limited scenarios, decentralization itself can even become a performance advantage. Decentralized networks can store massive amounts of data in parallel; vast amounts of computation can be executed concurrently, with much of it completed directly within the transaction mempool. In some cases, decentralization can also enhance privacy, as only decentralized networks can effectively hide metadata (such as the origins of data and requests).

As early as the mid-2010s, this was Ethereum's initial vision: decentralization is not just for enhancing robustness, but also meant to boost scalability. Centralized systems can improve performance by splitting tasks among multiple participants, and blockchains can do the same. Back then, this concept failed to materialize, primarily due to flaws in the verification mechanism. Once tasks are split, you must verify that every subtask is executed correctly. Early solutions attempted to address this via randomly sampled committees but hit the same bottleneck: first, committee deployment was complex, costly, and significantly increased latency; second, there was no fallback mechanism if a committee failed. Today, backed by modern cryptography, this challenge has been resolved, and the extra overhead introduced by this approach continues to decline monthly.

Another promising direction where decentralization could improve performance is latency. While Ethereum's inherent latency will never match centralized servers, infrastructure built atop Ethereum can achieve it.

Overall, building a powerful decentralized middleware layer between users and the main chain (which itself is not a blockchain) can vastly enhance Ethereum's capabilities without compromising the core attributes of the underlying blockchain.

Looking further ahead, Ethereum could undergo another round of transformation — program obfuscation (iO) may rise. The ultimate goal in this field: mature and usable obfuscation technology can eliminate the trade-off between privacy and generality. You can achieve fully general-purpose computation involving an unlimited number (asynchronous) of participants in a completely securely encrypted form. Even weakened versions of obfuscation technology have numerous practical use cases, such as encrypted transaction mempools. But all the conclusions drawn in this article stand true prior to the maturation of this technology.

This is the cryptographic world computer: Ethereum is no longer just a ledger, letting developers arbitrarily write computational tasks and data for execution; the new architecture fuses blockchains, cryptographic privacy, cryptographic verification, paired with powerful decentralized off-chain components into a cohesive whole.

Fully implementing this design still faces significant challenges. Making zero-knowledge proofs sufficiently efficient and secure is not easy, but it constitutes an encapsulated complex problem, which has already been massively optimized with the aid of AI tools. More thorny and systematically complex issues likely lie in the management and parallel access of massive states. Numerous solution concepts have already emerged, but they require continuous refinement, especially as we better understand which applications will run in the future.

Reviewing the Strawmap roadmap reveals that the Hegota hard fork planned for launch next year will likely be Ethereum's last "routine hard fork"; its functionalities and technologies will remain familiar to developers from 2015. All upgrades following Hegota will incorporate recursive STARKs, automated formal verification, highly optimized consensus algorithms, and system-wide post-quantum migration. The implementation of PeerDAS marks Ethereum's transition: evolving from a mere blockchain into a far more capable system. After the Hegota upgrade, this transformation will become the main thread of Ethereum's development. The ultimate goal: to realize a high-security computing framework that is cheaper, more scalable, and offers better privacy protection compared to previous-generation technologies. This is, precisely, the cryptographic world computer.