MSTR Cat

Blockchain/Level VII · Evolution/7.1 Ethereum: the world computer/Lesson 1

Ethereum: the power and price of programmability

The Turing trap: what happens when a ledger can run any program

MaterialsA copy of BIP-341 (Taproot)The Ethereum white paper (2014)The BitVM paper (2023)

Wonder

  1. Why does the ability to execute arbitrary code inevitably expand the surface area for theft?
  2. How did a community fork its own chain to reverse a hack, and why did Bitcoin reject that precedent?
  3. What is the precise mechanism by which Bitcoin verifies heavy computation without executing it?

Explore

  1. Ethereum launched in July 2015 with a goal distinct from Bitcoin: general-purpose programmability. While Bitcoin’s script was designed for specific, auditable financial transactions, Ethereum introduced a Turing-complete virtual machine (the EVM). This allowed developers to write and deploy any kind of program directly on the chain. The result was an explosion of tokens, decentralized finance protocols, and non-fungible tokens that were impossible to replicate on Bitcoin’s limited script environment.
  2. The power of general computation came with a price. In June 2016, a recursive bug in The DAO smart contract allowed an attacker to siphon away roughly one-third of the funds raised. The Ethereum community faced a crisis: should they let the code execute as written (‘code is law’) or intervene? They chose intervention, executing a hard fork that moved the stolen funds to a refund contract by an irregular state change. This decision split the chain into Ethereum and Ethereum Classic, proving that social consensus could override immutable code.
  3. The DAO incident highlighted a structural vulnerability: expressiveness enlarges the attack surface. Most subsequent thefts on programmable chains did not come from cryptographic breaks but from retained administrative keys, upgradeable contract logic, or simple coding errors. When a chain allows any program to run, every new feature adds complexity that can be exploited. The burden of security shifts from the protocol designers to thousands of individual developers who may lack rigorous auditing.
  4. One answer to that attack surface came from inside the language itself. Move, written at Facebook for its abandoned Libra (later Diem) project, treats tokens as resources: a value the type system will not let a program copy or silently drop, so whole classes of double-counting and lost-funds bugs fail to compile rather than fail in production. When Diem was shut down in 2022, former Diem engineers carried Move to new chains. Aptos, founded by Avery Ching and Mo Shaikh, launched its mainnet on 17 October 2022 with Block-STM, a parallel execution engine that runs transactions optimistically, checks afterwards which ones touched the same data, and re-executes only those. The engineering was cutting edge; the launch was not. Exchanges listed the APT token before its distribution was published, the figures showed roughly half the supply going to investors, core contributors and the foundation, early on-chain activity fell far short of the advertised throughput, and the team conceded it “could have gone better.” Sui, built by another group of ex-Diem engineers, followed with its own Move-based mainnet in 2023. The lesson cuts both ways: safer languages narrow the attack surface, but technology does not rescue a launch that holders cannot see into.
  5. Bitcoin’s response has been selective adoption rather than wholesale copying. Instead of general computation, Bitcoin has integrated specific, auditable capabilities. Taproot, activated in November 2021, introduced script trees that allow for complex spending conditions while maintaining privacy and efficiency. Wallets adopted PSBT (Partially Signed Bitcoin Transactions), a standard format for passing a transaction between signers. These additions enhance functionality without introducing a general-purpose virtual machine where any buggy code can compromise the entire network.
  6. For heavy computation that cannot be handled by simple scripts, the BitVM approach offers a path forward. Proposed by Robin Linus in 2023, BitVM keeps heavy computation off-chain; only a disputed step is checked on Bitcoin, and only if someone challenges. This maintains Bitcoin’s lean base layer while enabling advanced applications, ensuring that the core protocol remains simple, verifiable, and resistant to the kind of cascading failures seen in general-purpose smart contract environments.
  7. The trade-off is clear: Ethereum prioritizes flexibility at the cost of security complexity and upgradeability risks; Bitcoin prioritizes stability and explicitness by restricting computation. For any new feature added to a chain, the test is whether it introduces hidden state or admin powers that can be abused. If a capability cannot be verified through simple, transparent rules without relying on trusted third parties or complex social consensus forks, it carries inherent risk. This distinction defines the current architectural divergence between the two leading chains.

Key facts

  • Ethereum mainnet launched in July 2015 with a Turing-complete virtual machine.
  • The DAO hack occurred in June 2016, leading to a hard fork that split the chain.
  • Taproot activated on Bitcoin in November 2021 (block 709,632), introducing script trees.
  • Most smart contract thefts stem from retained admin keys or coding bugs, not cryptographic failures.
  • Move (from Facebook’s Libra/Diem project) models tokens as resources that cannot be copied or dropped; Aptos launched its Move-based mainnet on 17 October 2022 with Block-STM parallel execution.
  • BitVM enables off-chain computation with on-chain dispute resolution to maintain a lean base layer.
  • PSBT allows for multi-party transaction signing workflows with explicit accountability.

Exercise nine, six, three, one

9CollectList 9 smart contract features or protocols. Note whether each relies on general computation, specific script logic, or external oracles.
6ClusterGroup the 9 into 6 by the attack surface each creates.
3DistillReduce the 6 to 3 primary reasons why general-purpose computation increases systemic risk.
1CrystallizeWrite 1 sentence on where you would draw the line between a safe capability and a dangerous one, and why.

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