Vitalik Buterin (1994–)

In 2011, a 17-year-old Russian-Canadian named Vitalik Buterin couldn’t afford to buy or mine bitcoin, so he wrote articles for it instead — five bitcoins per article (roughly $3.50 each at the time) at Mihai Alisie’s Bitcoin Weekly. The writing led him to co-found Bitcoin Magazine in 2012 and to author dozens of long-form pieces on Bitcoin’s protocol mechanics through 2014. In late 2013 he wrote the Ethereum whitepaper, launching the network’s mainnet on July 30, 2015 at age 21.

Buterin was born January 31, 1994 in Kolomna, Russia and raised in Canada from age 6. His Bitcoin years ran to 2014, when he announced Ethereum on BitcoinTalk.

Entry into Bitcoin (2011, age 17)

According to Buterin’s own published accounts (reproduced across many interviews, e.g., the Wired and Forbes profiles in his Wikipedia entry), he first heard about Bitcoin from his father in late 2010 / early 2011 and dismissed it as a fad. After encountering the topic again later in 2011, he began to read about it seriously and concluded it was a substantive technical project. Lacking the funds to mine or buy bitcoin, he searched for ways to acquire some by writing — and found Mihai Alisie’s Bitcoin Weekly, a small early Bitcoin-focused blog that paid contributors approximately five bitcoins per article (roughly USD 3.50 each at the time).

Bitcoin Weekly and Bitcoin Magazine (2011–2014)

Buterin’s writing for Bitcoin Weekly led to a deeper collaboration with Mihai Alisie. The two co-founded Bitcoin Magazine — initially online, with the first print issue in May 2012. Buterin served as lead writer for the magazine through 2014, producing dozens of long-form articles on Bitcoin protocol mechanics, mining-economics analyses, profiles of altcoin projects (including Mastercoin and other early coloured-coin systems), commentary on the block-size question, and interviews with Bitcoin developers. The Bitcoin Magazine author archive preserves his article catalogue.

Buterin also contributed open-source Bitcoin software during this period. His most-cited contribution is pybitcointools (vbuterin/pybitcointools on GitHub) — a pure-Python library implementing Bitcoin transaction construction, ECDSA signatures, BIP32 hierarchical deterministic wallets, and Merkle-tree primitives. The BIP32 standard itself was authored by Pieter Wuille — see his biography for the standard’s origin. The library was widely used by educators and small-scale tooling builders during the 2013–2015 era and remains a reference for people learning the Bitcoin protocol.

His BitcoinTalk profile (handle vbuterin) shows posts beginning in October 2011 and concentrated activity through 2014.

The scripting-extension question (2013)

Through 2013 Buterin became increasingly focused on extending Bitcoin’s scripting language to support arbitrary computation — programmable contracts that could express arbitrary state machines rather than the limited, mostly-disabled set of Bitcoin Script opcodes. In Bitcoin Magazine articles and in conversations with the Mastercoin team (whose protocol layered metadata into Bitcoin transactions to add token-issuance and contract-like primitives), he argued that general-purpose computation belonged inside the consensus layer rather than as a metadata overlay.

The Bitcoin community did not converge on this direction. The conservative protocol-evolution culture (later codified by Bitcoin Core) treated extensions to scripting as too high-risk for inclusion via hard fork, and the Mastercoin proposal to broaden its protocol was not adopted. Buterin documented this conclusion in the preface to the Ethereum whitepaper (late 2013):

“I came to a realization that the way they were going about it was somewhat misguided… So I decided that, instead of trying to extend Bitcoin to do all sorts of things, what was actually needed was a brand new platform with a more general-purpose scripting language built from the ground up.”

The whitepaper itself — Ethereum: A Next-Generation Smart Contract and Decentralized Application Platform — was published in late 2013 and circulated initially in Bitcoin community channels.

Departure from Bitcoin (2014)

In January 2014 Buterin announced Ethereum at the North American Bitcoin Conference in Miami. Throughout 2014 he secured funding (the Ethereum crowdsale, July 2014), assembled co-founders — most of whom were also active in the Bitcoin / cypherpunk space at the time: Gavin Wood (later Polkadot), Charles Hoskinson (later Cardano), Joseph Lubin (later ConsenSys), Anthony Di Iorio, Mihai Alisie, Amir Chetrit — and led the development effort that produced the Ethereum mainnet (Frontier release) on July 30, 2015.

One thing Buterin did not carry over from Bitcoin was the supply cap. The 2014 Ethereum whitepaper states the choice against Bitcoin by name — “the existence of a permanently growing linear supply, as opposed to a capped supply as in Bitcoin” — and gives as its reason the wish to blunt what some read as excessive wealth concentration in Bitcoin and to leave people born into later eras a fair chance at acquiring units — the same reasoning the twelve-chain design comparison records as Ethereum’s stated case against a cap. Where that decision sits in the monetary-design argument that runs from b-money onward is taken up in the fixed-supply-vs-adjustable-money analysis.

Buterin’s work after 2014 is principally Ethereum’s — mainnet, the Beacon Chain merge to proof-of-stake, the layer-2 rollups — and belongs to that chain’s own record.

Bitcoin-period timeline (2011–2014)

Significance to Bitcoin

Buterin’s Bitcoin-period record matters for two reasons. First, he is the most prolific 2012–2014 Bitcoin Magazine contributor; his article archive constitutes a substantial portion of the contemporary public-facing documentation of the middle of Bitcoin’s early period (between the launch period and the block-size war). Second, the Bitcoin family-tree analysis records Ethereum as the most-cited “next-generation” chain whose origin runs through Bitcoin: the design motivation comes from Buterin’s Bitcoin-Magazine-era thinking about scripting limits, even though the codebase is independent.