Ethereum Was Supposed to Run on Bitcoin

The origin everyone forgets

Before Ethereum was a chain, it was a proposal to make Bitcoin programmable.

In 2013 Vitalik Buterin was deep inside the Bitcoin world, writing for Bitcoin Magazine, tinkering with colored coins, working on the Mastercoin protocol, which was trying to bolt richer financial logic onto Bitcoin. Buterin's insight was that all these one-off protocols were reinventing narrow slices of the same thing. Why hand-roll a protocol for each new asset type when you could give Bitcoin a general-purpose scripting language and let people build anything on it?

Bitcoin, conservative by design and rightly protective of its base layer, didn't take it. So Buterin did the only other thing available to him: he wrote a whitepaper for a brand-new chain that would be Turing-complete from day one, and in 2015 Ethereum went live as the "world computer."

Read that sequence again:
Ethereum exists because Bitcoin wouldn't run smart contracts. The world computer was Plan B. Plan A was Bitcoin.

What the world computer became

The pitch for Ethereum was singular and electric: one decentralized base layer where anyone's code runs, composable, unstoppable, settled by the same chain everyone shares. For a while it really was that.

Then it ran into physics. A single base layer can't be both the global execution environment and cheap and decentralized at scale. So in 2020 Ethereum formally adopted a rollup-centric roadmap: stop trying to run the world's applications on L1, and instead push computation out to Layer 2s. The base layer's job was downgraded to security and data availability, a settlement court that the actual application chains report back to.

It was a reasonable engineering decision. But it quietly retired the original promise. The "world computer" became a settlement layer for other computers. Liquidity, state, and users fragmented across dozens of L2s, each with its own bridges and its own trust assumptions. Even Buterin has recently revisited the roadmap publicly, noting that L2s have decentralized far more slowly than expected.

Whatever you think of Ethereum today, one thing is no longer true of it: you cannot point to a single base layer and say "this is where the apps live."

Plan A, ten years late

Here is the twist. The thing Buterin originally wanted, general-purpose smart contracts running directly on Bitcoin's base layer, now exists. It is called Alkanes, and it did not require changing Bitcoin at all.
And to be fair, none of this was even possible in 2013. WebAssembly did not exist yet, and neither did the Runes-style metaprotocol and indexing that now let general contracts run on Bitcoin without changing it. Buterin had the right idea, but a decade too early.

Alkanes is a smart-contract metaprotocol on Bitcoin L1. Contracts are real programs compiled to WebAssembly, a far more modern execution target than the EVM that grew out of that 2013 whitepaper, and their calldata rides inside a Runes-compatible envelope, recorded in Bitcoin's OP_RETURN data. Contract state lives on Bitcoin and is settled by Bitcoin. No separate consensus engine, no validator set to trust, no bridge to a foreign chain. The same thing Mastercoin and colored coins were groping toward in 2013, except general, expressive, and Turing-class.

The architectural punchline is exactly the one Ethereum walked away from: applications live on the base layer. Assets that would be scattered across a dozen incompatible L2s instead coexist in one shared data layer, composable in a single transaction. You don't bridge BTC to a far-off rollup to use it in a contract, you wrap and use it atomically, on Bitcoin, in one go. That is the property the world computer was supposed to have and never quite kept.

And this is not a whitepaper or a testnet. By independent measurement, Alkanes protostones are now 91% of all OP_RETURN outputs on Bitcoin, and the broader category is more than a ⅓ of all block space, a steady state held for weeks, not a spike. The base-layer smart-contract chain Buterin sketched in 2013 turned out to be possible. It just shipped on the chain he left, a decade later, built by people who never accepted that Bitcoin had to stay dumb.

Why the base layer was always the point

It's worth being honest about the trade. Bitcoin's base layer is more expensive and more constrained than a high-throughput L2. Alkanes does not pretend otherwise.

But the reason Buterin wanted this on Bitcoin in the first place is the same reason it matters now: Bitcoin is the most secure, most neutral, most widely held settlement layer that exists. Building directly on it means your application inherits that, not the security of a six-month-old rollup with a multisig escape hatch, but Bitcoin itself. Computation that has to be trust-minimized. Everything else is a convenience layer.

Ethereum's whole history is the story of starting at that base, deciding it was too hard, and spending ten years building outward from a substitute. Alkanes is the story of someone going back to the original question, can Bitcoin run smart contracts?, and answering it with code instead of a new chain.

SUBFROST is what you build once Plan A works

A programmable base layer is only interesting for what gets built on it. That's where SUBFROST comes in.

The cornerstone is frBTC, synthetic Bitcoin you can mint atomically in a single transaction, redeemable back to native BTC through a decentralized signer ring. From there: an AMM to swap native BTC into Bitcoin-native assets, and FIRE for protocol yield and bonds. DeFi primitives, the exact genre Ethereum was invented to host, running on Bitcoin's base layer.

Bitcoin-native yield, done right.

Ethereum took the scenic route. The world computer is finally booting up. It's running on Bitcoin, which is where it was always supposed to run.

Sources: the early-Ethereum history (Buterin's work around Mastercoin and colored coins, the 2013 Ethereum whitepaper, and the 2015 launch) is drawn from the public record; Ethereum's rollup-centric roadmap (2020) and Buterin's subsequent re-evaluation of it are likewise public. On-chain Alkanes figures are from Bitcoin Block Space Weekly, Issue #29 (Renaud Cuny, Jun 2026). frBTC and the synthetic-Bitcoin model are described in SUBFROST's own writing.