Preface: The Chain Multiverse

Bitcoin was built around the idea that thousands of independent participants could agree on a single shared history. Yet again and again, that history has split in two.

A fork happens when participants in a blockchain adopt different rules for what constitutes a valid block or transaction. Once those rules diverge, the blockchain can split into two histories, with each side continuing under its own set of rules. A soft fork tightens the rules while remaining compatible with older ones, while a hard fork introduces rules that older software cannot accept. In either case, the result can be more than a technical change: it can become a battle over what the network should be.

A fork is rarely just a software update. It is a philosophical battleground and a multi-billion-dollar experiment in human coordination. When a community fundamentally disagrees about where a protocol should go, it doesn't simply argue. It can split the network and let both visions compete for users, miners, developers, and capital.

I've been thinking about this constantly since August 8th. The temporary soft fork activated on Bitcoin that day was supposed to be a temporary change. Instead, in barely two months, it has already been followed by a hard fork and yet another soft fork. People in my community have strong, and often conflicting, views about each chain. I wanted to step back from the noise and ask a simpler question: what can history actually tell us about what comes next?

"History doesn't repeat itself, but it rhymes." That idea drives this series. I'll look at some of the most famous forks in crypto history, trace how they unfolded, examine what happened to the resulting chains, and end each one by exploring how the new fork compares with each of the two chains.

Three fractures stand out.

Each split reveals something about how decentralized governance actually works: the competing power of developers, node operators, miners, markets, and users, and the often unexpected cost of rejecting consensus.

And each one offers a potential glimpse into what is happening today.

The newest chapter is Bitcoin BLAKE2b. Emerging from the BIP-110 movement, it represents the latest attempt to reshape Bitcoin around a different set of priorities, including restricting arbitrary data such as inscriptions and replacing SHA-256 proof-of-work with BLAKE2b.

For simplicity, throughout this series we'll refer to Bitcoin with the BLAKE2b algorithm as BTCB2, and to Bitcoin on the SHA-256 algorithm as BTC.

The result is a fascinating live experiment.

By making existing Bitcoin ASICs obsolete, BLAKE2b effectively reset the mining landscape and triggered a scramble for older compatible hardware, including Sia-family ASICs. The goal is to create a more accessible and decentralized mining ecosystem. The tradeoff is a security budget that, so far, is dramatically smaller than Bitcoin's main network.

The market has been just as volatile. With thin liquidity and limited exchange support, BTCB2 has experienced enormous price swings, including an 84% drawdown after its initial surge.

BTCB2 is therefore more than another fork. It is a real-time test of ideological conviction.

Can a smaller community build a durable network around a different set of principles, especially as BLAKE2b continues to evolve and improve, or will the network effects, liquidity, and entrenched SHA-256 ecosystem of the larger network ultimately prove too difficult to overcome?

History can't answer that question for us. But it can give us a framework for asking it.

That's where this series begins. We may not agree on the conclusions, but hopefully, by the end, we'll have a sharper understanding of what these forks actually tell us about Bitcoin, consensus, and the communities built around them.

On the data: prices, transaction counts, and hashrate come from CoinMetrics' public API; exchange listing dates come from each exchange's own announcements or archived coverage; the BLAKE2b chapter also draws on a first-party block-by-block crawl of both chains and its own market data pulled directly from its one listed exchange.