Ethereum · 2013–2015
Why Vitalik Buterin wanted a programmable blockchain
A thought experiment about a savings account helps explain the leap from Bitcoin scripts to Ethereum’s shared programming environment.
One of the most revealing examples in Vitalik Buterin’s Ethereum white paper is a family savings account. Imagine an agreement allowing one key to make small daily withdrawals while a larger transfer requires a second key. The idea is easy to explain to another person. The harder question is where those rules live and who keeps track of how much has already been withdrawn.
Buterin proposed giving developers a general-purpose way to express such rules on a blockchain. A contract could remember an earlier action and use that stored state to decide what to do next. The same environment could support a registry, a currency or the family’s spending agreement. Developers could try a new rule without first persuading an entire network to build their particular application into its protocol.
A proposal still needed software and people willing to run it. Ethereum’s first public mainnet release, Frontier, arrived in July 2015. That gap between the paper and the launch matters. Buterin articulated the design, while bringing it into operation was the work of co-founders, developers and network participants. Their choice also gave users a new question to ask of any application: what do its deployed rules actually permit?