Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Chapter 1: The Vision Emerges

In the autumn of 2013, a nineteen-year-old programmer named Vitalik Buterin was traveling through Israel, Spain, and the United States, meeting Bitcoin enthusiasts and learning about various cryptocurrency projects. What he discovered during these travels would frustrate him enough to conceive an entirely new blockchain platform—one that would eventually process over a million transactions daily and secure hundreds of billions of dollars in value.

The frustration was simple yet profound: every project he encountered was trying to implement complex functionality on top of Bitcoin, but Bitcoin's scripting language was intentionally limited. It was like trying to build a skyscraper with tools designed for a wooden shed.

Background

To understand Ethereum's genesis, we must first understand the state of the cryptocurrency world in 2013. Bitcoin had survived its early years and was gaining legitimacy, with the price rising from under $100 to over $1,000 during that year. The community was vibrant with experimentation, but developers were running into the same walls repeatedly.

Bitcoin's scripting system was deliberately restricted—Satoshi Nakamoto had designed it this way for security reasons. While you could create simple conditions for spending coins (like requiring multiple signatures), anything more complex required awkward workarounds or entirely new blockchains.

The Bitcoin Magazine Era

Vitalik's journey into cryptocurrency began in 2011 when his father, Dmitry, first mentioned Bitcoin to him. Initially skeptical—he thought anything without physical backing was doomed to fail—Vitalik's perspective changed when he began writing for a Bitcoin blog for 5 BTC per article (worth about $3.50 at the time).

By September 2011, he co-founded Bitcoin Magazine with Mihai Alisie, becoming the publication's lead writer and a prominent voice in the Bitcoin community.1 Through his writing and research, Vitalik gained deep insights into Bitcoin's capabilities and limitations. He spent countless hours on Bitcoin forums, absorbing the community's dreams and frustrations.

His articles weren't just news—they were technical deep-dives that demonstrated an unusual ability to explain complex concepts clearly. Topics ranged from Bitcoin's economic properties to the mathematical foundations of cryptocurrency. This period of intense study and writing laid the intellectual groundwork for what was to come.

The Limits That Sparked Innovation

Throughout 2013, Vitalik observed numerous projects attempting to build new functionality on Bitcoin:

Colored Coins aimed to represent real-world assets on the Bitcoin blockchain by "coloring" certain bitcoins to represent shares, bonds, or property. The project included notable figures like Yoni Assia (eToro's CEO), Lior Hakim, and Meni Rosenfeld. Vitalik himself contributed to the project, but he grew frustrated with its limitations.2

Mastercoin (later Omni) created a protocol layer on top of Bitcoin for smart contracts and custom currencies. While more ambitious than Colored Coins, it still felt constrained by Bitcoin's architecture.

Namecoin took a different approach, creating an entirely new blockchain for decentralized domain names. This demonstrated the potential for blockchain applications beyond currency but required massive duplication of effort.

Each project revealed the same pattern: developers were either cramming functionality into Bitcoin's limited scripting language or creating entirely new blockchains for each use case. Neither approach was sustainable.

The Whitepaper

In late October 2013, Vitalik had an epiphany. Instead of creating blockchains with built-in functionality, why not create a blockchain with a built-in programming language? This would allow developers to write any kind of decentralized application without needing to create new blockchains.

He began drafting what would become the Ethereum whitepaper, initially sharing it with a small group of close contacts on November 27, 2013. The response was immediate and enthusiastic. Within weeks, over 30 people had reached out wanting to help with the project.

The whitepaper, titled "Ethereum: A Next Generation Smart Contract & Decentralized Application Platform,"3 introduced several revolutionary concepts:

Smart Contracts

While the term "smart contract" was coined by Nick Szabo in the 1990s,4 Ethereum would be the first platform to make them practical. The whitepaper described smart contracts as "systems which automatically move digital assets according to arbitrary pre-specified rules."

// A simple example from the whitepaper concept
contract NameRegistry {
    mapping(bytes32 => address) public registry;
    
    function register(bytes32 name) {
        if (registry[name] == 0) {
            registry[name] = msg.sender;
        }
    }
}

The Ethereum Virtual Machine

The whitepaper introduced the concept of a Turing-complete virtual machine that would run on every node in the network. This was radical—Bitcoin was deliberately not Turing-complete to avoid infinite loops and complexity. Ethereum would embrace this complexity while solving the halting problem through its gas mechanism.

Gas: The Fuel of Computation

Perhaps the most elegant innovation was the gas system. Every operation in the EVM would cost a certain amount of gas, paid for in ether. This simultaneously:

  • Prevented infinite loops (programs halt when gas runs out)
  • Compensated miners for computation
  • Created a market for computational resources
  • Defended against denial-of-service attacks

The gas concept was inspired by the idea of cloud computing services where users pay for computation time, but implemented in a decentralized manner.

State and Accounts

Unlike Bitcoin's UTXO model, Ethereum would use an account-based system with two types:

  • Externally Owned Accounts (EOAs): Controlled by private keys
  • Contract Accounts: Controlled by contract code

Each account would have a balance and (for contracts) associated code and storage. This made it much easier to implement complex logic compared to Bitcoin's stateless design.

Key Technical Concepts

The whitepaper laid out several fundamental principles that would guide Ethereum's development:

Simplicity

The protocol should be as simple as possible, even at the cost of data storage or time inefficiency. This would make it easier to understand, implement, and secure.

Universality

Ethereum would not have "features." Instead, it would provide a simple, universal scripting language that developers could use to build any feature through smart contracts.

Modularity

Different parts of the protocol should be designed as separate, interchangeable modules when possible.

Non-discrimination

The protocol should not actively restrict or prevent specific categories of usage. This was a direct response to Bitcoin's limited scripting capabilities.

Early Reactions and Refinements

As the whitepaper circulated in December 2013 and early 2014, feedback poured in. Some were skeptical—was Turing-completeness really necessary? Others were excited by specific use cases:

  • Decentralized exchanges: Trading tokens without intermediaries
  • Prediction markets: Betting on future events with automatic settlement
  • Decentralized autonomous organizations (DAOs): Organizations governed by code
  • Identity systems: Self-sovereign identity management
  • Decentralized file storage: Incentivized distributed storage networks

Vitalik refined the whitepaper based on this feedback, clarifying technical details and expanding on potential applications. The vision was crystallizing: Ethereum would be the "world computer"—a decentralized platform where anyone could deploy unstoppable applications.

The Philosophy Takes Shape

Beyond the technical innovations, a philosophy was emerging. Ethereum wouldn't just be about moving money—it would be about programming money, creating new forms of economic interaction, and building systems that no single entity could control or shut down.

This vision attracted a different crowd than Bitcoin. While Bitcoin drew libertarians focused on monetary freedom, Ethereum attracted developers, entrepreneurs, and futurists who saw the potential for entirely new types of applications and organizations.

Why This Mattered

The Ethereum whitepaper represented a paradigm shift in blockchain thinking. Rather than viewing blockchains as application-specific databases (Bitcoin for currency, Namecoin for domains), Ethereum proposed a general-purpose computational platform.

This shift would have profound implications:

  1. Developer Accessibility: Instead of learning blockchain-specific languages, developers could use familiar programming concepts
  2. Innovation Velocity: New applications could be deployed in days rather than requiring new blockchains
  3. Composability: Applications could interact with each other, creating complex ecosystems
  4. Reduced Redundancy: One blockchain could host thousands of applications

The technical elegance of solutions like gas pricing showed this wasn't just ambitious—it was carefully thought through. The combination of vision and practical solutions would attract the team needed to make it reality.

Looking Ahead

By January 2014, the Ethereum project was gaining momentum. The whitepaper had attracted talented developers and thinkers from around the world. The next challenge would be assembling this distributed group into a cohesive team and turning the theoretical framework into working code.

The vision was clear: create a blockchain that could execute arbitrary programs in a trustless environment. The implications were staggering—everything from financial systems to governance structures could be rebuilt on this new foundation. But first, they would need to build the foundation itself.5

References

  1. Bitcoin Magazine Archives. (2011-2013). Various articles by Vitalik Buterin ↩

  2. Colored Coins Whitepaper. (2013). Assia, Y., Buterin, V., Hakim, L., Rosenfeld, M., & Lev, R. ↩

  3. Buterin, V. (2013). "Ethereum White Paper: A Next Generation Smart Contract & Decentralized Application Platform" ↩

  4. Szabo, N. (1994). "Smart Contracts" ↩

  5. Wood, G. (2014). "Ethereum: A Secure Decentralised Generalised Transaction Ledger" (Yellow Paper) ↩