Sign in

Bitcoin-specific forks

Suggest an edit

Bitcoin's rules can change, but the way they change is unusual. Nobody is in charge of them. The protocol moves when enough people running nodes voluntarily upgrade their software. If consensus breaks, the network splits. This lesson walks through three real upgrade stories from Bitcoin's history to show what that looks like in practice.

Soft fork, hard fork

The forks lesson introduced two kinds of rule change. A soft fork makes the rules stricter, so anything that's valid under the new rules is still valid under the old ones, and the network stays one chain. A hard fork is a change that the old rules don't accept, and if miners keep working under both sets of rules, the chain splits into two.

Take the limit on how big a block can be. Lowering the limit is a soft fork, because a block that fits the smaller limit also fits the old one, and old nodes accept it without noticing the upgrade. Raising the limit is a hard fork, because old nodes reject any block bigger than the limit they know. Most Bitcoin changes are made as soft forks because they don't risk a chain split.

The next three stories are: two successful soft forks, SegWit and Taproot, and one hard fork, Bitcoin Cash, that split the network in two.

Bitcoin timeline: SegWit and Taproot soft forks, Bitcoin Cash hard forkA timeline runs from Bitcoin's launch in 2009 to 2021. Soft forks, SegWit (2017) and Taproot (2021), sit above the line, while the Bitcoin Cash hard fork (2017) sits below, showing where the chain split Three real Bitcoin upgrades soft forks (everyone stays on one chain) sit above hard forks (the chain can split) sit below 2009 Bitcoin launches SegWit 2017 · soft fork Bitcoin Cash split 2017 · hard fork Taproot 2021 · soft fork

SegWit (2017): the upgrade that almost didn't happen

By 2016, Bitcoin had a known bug. Anyone watching the network could grab a signed transaction and slightly rewrite the signature in a way that kept it valid but changed the transaction's ID. The coins still went to the right place, but downstream software that tracked transactions by ID got confused. The Lightning Network, a payment system on top of Bitcoin that was being designed around the same time, depended on stable transaction IDs and couldn't work until this bug was fixed.

The fix was an upgrade called SegWit. It restructured how signatures were stored so that they no longer affected the transaction ID. It also made room for more transactions per block as a side benefit, without producing blocks that old nodes reject. That made the change a soft fork, and old nodes kept working without trouble.

Some of the biggest mining operations didn't want SegWit to activate. They wanted Bitcoin to scale by allowing bigger blocks instead, a dispute the next section returns to. The activation mechanism required a supermajority of miners to signal support, and they refused. For most of 2017, SegWit was ready to activate and miners blocked it.

Then a movement of regular users acted on their own. They started running modified software that promised to reject any block that didn't signal support for SegWit, starting on a specific date. If miners kept blocking SegWit past that date, those miners' blocks would be ignored by a large part of the network, including most exchanges and big businesses. Their freshly mined bitcoin would be worth nothing to the people they wanted to sell to.

Within weeks of the deadline being announced, miner signaling jumped from a fraction to nearly all of them, and SegWit activated in August 2017.

Miners produce blocks, but they don't decide what counts as a valid block. That's decided by the people running nodes, especially the ones connected to exchanges, custodians, and big merchants. When miners and nodes disagree, miners eventually have to give in, because they need someone to buy their bitcoin.

Bitcoin Cash (2017): when consensus breaks

Not everyone wanted SegWit. A group of miners and developers thought Bitcoin should scale differently, by allowing bigger blocks. SegWit gave a modest capacity increase as a side effect. They wanted a much larger one as the main feature.

That disagreement was deep enough that no compromise emerged. So on the same day SegWit's user-imposed deadline was scheduled, the group that disagreed launched their own version of Bitcoin with bigger blocks. They called it Bitcoin Cash. Bigger blocks are a change the old rules don't accept, so this was a hard fork.

Bitcoin hard fork splitting into Bitcoin (BTC) and Bitcoin Cash (BCH)A shared history box leads to a last shared point, which then splits into two paths: Bitcoin (BTC), where old rules continue, and Bitcoin Cash (BCH), a new chain with new rules. Notes explain that both chains share the same history up to the split and diverge forever after, and anyone holding 1 BTC at the split also held 1 BCH on the new chain. A chain splits in two shared history last shared Bitcoin (BTC) old rules continue Bitcoin Cash (BCH) new chain, new rules Up to the split, both chains share the same history. After, they diverge forever. Anyone holding 1 BTC at the split moment also held 1 BCH on the new chain.

Up to the split moment, both chains are the same chain, with the same blocks, the same balances, and the same transaction history. After the split, the two networks operate independently and never reconnect. Both still produce blocks today.

When a hard fork creates a new chain, everyone who owned coins on the original chain at the split moment also owns coins on the new chain. The same private key that controlled your BTC now also controls an equal amount of BCH, because both chains inherited the same state. This is where "fork airdrops" come from. They are the automatic consequence of two chains sharing history up to the split, not a gift from anyone.

Years later, Bitcoin's market value is roughly a hundred times bigger than Bitcoin Cash's, but the BCH chain is still running and still has users. In a decentralized system, you can't force people to agree. If they don't, they can leave with a copy.

Taproot (2021): a smooth upgrade that still took four years

After the SegWit fight, many people predicted Bitcoin would never be able to upgrade itself again without another community split. Taproot, an upgrade that improved Bitcoin's privacy and made certain advanced spending conditions cheaper, proved them wrong. The community broadly agreed it was a good idea, miners signaled support without a fight, and it went live in November 2021 with no drama. Even so, from the first proposal to deployment took roughly four years. Other software platforms release comparable features in months. Bitcoin's slowness is a deliberate trade. The protocol settles hundreds of billions of dollars of value, and if it could be changed quickly, it could be broken quickly too.

A rule change needs the people who can reject blocks

When someone proposes a change to the rules of a chain, ask two questions. Who can refuse to accept a block that follows the new rules? And who do the block producers have to sell their reward to? In Bitcoin both answers point at the people running nodes, including the exchanges and merchants who buy what miners mine. If they don't adopt a change, it either fails or its supporters split off with a copy of the chain.