MSTR Cat

Blockchain/Level VI · After bitcoin/6.3 Ethereum and smart contracts/Lesson 1

The Ethereum whitepaper and the EVM

A state machine that runs on every node, fueled by gas

MaterialsA copy of the Ethereum white paper (2014)The Ethereum Yellow Paper (Gavin Wood, 2014)Access to a block explorer like Etherscan

Wonder

  1. Why does a computer replicated across thousands of machines need to charge for every single instruction?
  2. What breaks if the code running on those machines can loop forever without penalty?
  3. How can two different account models—UTXOs and in-place balances—represent the same wealth differently?

Explore

  1. Vitalik Buterin, then nineteen, drafted the Ethereum white paper in late 2013, proposing a general-purpose computation platform rather than a specific currency. The project, announced publicly in January 2014, gathered co-founders including Gavin Wood, Joseph Lubin, Charles Hoskinson, Anthony Di Iorio, and Mihai Alisie. A crowdsale ran from July to August 2014, raising approximately 31,500 BTC for the venture. The network officially launched on 30 July 2015, marking a shift from bitcoin’s limited scripting to a fully programmable environment where developers could build complex applications directly on-chain.
  2. The core of this architecture is the Ethereum Virtual Machine (EVM), a Turing-complete state machine replicated across every full node. Unlike bitcoin’s UTXO model, which tracks individual unspent outputs, Ethereum employs an account model where balances update in place. Each account—whether controlled by a private key or by code—maintains a nonce and a balance. When a transaction executes, the EVM processes it deterministically; every node computes the same result on its own, ensuring consensus without requiring trust between participants.
  3. Smart contracts are programs written in high-level languages like Solidity that compile to low-level opcodes executed by the EVM. These contracts hold value and logic simultaneously. A contract can retain ether, execute conditional trades, or manage governance votes based on inputs from other accounts. Because execution is deterministic and many contracts publish their source code, anyone can check the logic before interacting with it. This transparency removes the need for trusted intermediaries in many financial applications, as the rules are enforced by software rather than human discretion.
  4. To prevent infinite loops and denial-of-service attacks, every EVM operation consumes ‘gas,’ a unit of computation paid in ether. The sender specifies a gas limit upfront; if execution exhausts this fuel, state changes revert, but the consumed gas is still deducted. This economic constraint forces developers to write efficient code and shields the network from malicious or buggy contracts that could otherwise freeze the chain. Gas prices rise and fall with demand; originally users simply bid, and since 2021 a protocol-set base fee adjusts automatically, with tips on top (a later lesson).
  5. The design choices in the EVM reflect a trade-off between expressiveness and security. Turing completeness allows for arbitrary computation but introduces complexity that can harbor vulnerabilities. The account model makes some programs simpler than UTXOs do, but contracts that call each other must be written carefully to avoid bugs such as reentrancy, the flaw behind The DAO hack (a later lesson). The EVM’s standardization enables a vast ecosystem of tools and auditors familiar with the specific instruction set.
  6. Open a block explorer such as Etherscan and inspect any recent transaction that deployed a smart contract. Observe the ‘Contract Creation’ status and the gas used compared to the gas limit. Note how the transaction’s input data contains the compiled bytecode being stored at the new address. This concrete step reveals the mechanical reality of deployment: code is uploaded, verified by every node, and locked into the chain’s state machine, ready for execution upon future interaction.

Key facts

  • Vitalik Buterin wrote the Ethereum white paper in late 2013; the project was announced in January 2014.
  • The July-August 2014 crowdsale raised approximately 31,500 BTC for the Ethereum development fund.
  • Ethereum’s mainnet launched on 30 July 2015, introducing a Turing-complete virtual machine.
  • Every EVM operation consumes gas, paid in ether, to prevent infinite loops and ensure termination.
  • Ethereum uses an account model with in-place balance updates, distinct from bitcoin’s UTXO system.
  • Smart contracts are typically written in Solidity, which compiles to deterministic EVM bytecode.

Exercise nine, six, three, one

9CollectList 9 technical constraints or design decisions in the Ethereum white paper that differ from Bitcoin’s protocol.
6ClusterGroup these 9 items into 6 categories based on their impact: state management, security, execution cost, language support, consensus, and governance.
3DistillReduce the 6 clusters to 3 core reasons why Turing completeness requires a gas mechanism.
1CrystallizeWrite 1 sentence explaining how the EVM’s deterministic nature ensures global consensus on state transitions.

Fact check

Dates, figures and claims checked against the published sources listed below.

Open in the interactive academy →

PT ES ZH JA KO RU DE FR MS