List of bitcoin forks

Main article: Fork (blockchain)

Bitcoin forks are defined variantly as changes in the protocol of the Bitcoin network or as the situations that occur "when two or more blocks have the same block height".^[1] A fork influences the validity of the rules. Forks are typically conducted in order to add new features to a blockchain, to reverse the effects of hacking or catastrophic bugs. Forks require consensus to be resolved or else a permanent split emerges.

There are 3 categories of Bitcoin forks:

• Soft Forks within Bitcoin: These don't split the network.
• Hard Forks within Bitcoin: These cause a permanent chain split between the 2 versions.
• Hard Forks that created alternative blockchains and cryptocurrencies.

There is also another category of consensus rule changes that had a chance to cause a hard fork and chain split. However, because they were never exploited, they are technically not a hard fork.

Soft Forks within Bitcoin

These are consensus rule changes that did not cause a split in the network. Client nodes both with and without the update can still build on the same chain. Two of the most well-known Bitcoin soft forks are Segwit and Taproot.

Segwit

These paragraphs are an excerpt from SegWit.[edit]

Segregated Witness (SegWit), formally known as Segregated Witness (Consensus layer), is an implemented soft fork change in the transaction format of bitcoin.^[2]

SegWit had Bitcoin Improvement Proposal number BIP141.^[2] The declared purpose was to prevent nonintentional bitcoin transaction malleability, allow optional data transmission, and to bypass certain protocol restrictions (such as the block size limit) with a soft fork.^[3] Segregated Witness was activated on 24 August 2017.

Taproot

Taproot is an agreed soft fork in the transaction format. The fork adds support for Schnorr signatures, and improves functionality of smart contracts and the Lightning Network. The fork was installed in November 2021.^[4] The upgrade adds privacy features.^[5][6] Taproot includes Bitcoin Improvement Proposal numbers BIP340, BIP341, BIP342.^[7]

Advantages:

• Complex transactions, such as those requiring multiple signatures or those with delayed release, are indistinguishable from simple transactions in terms of on-chain data.^{[citation needed]}
• Reduced transaction costs: The data size of complex Bitcoin transactions is reduced, which leads to lower transaction fees.^{[citation needed]}
• Support for more complicated conditions for a transaction via Schnorr signatures.^{[citation needed]}
• Benefits for the Lightning Network: More flexibility, privacy enhancement, lower costs.^{[citation needed]}

Hard Forks within Bitcoin

These are Hard Forks within Bitcoin that caused a chain split but did not create an alternative network or cryptocurrency.

• v0.3.6: The addition of OP_NOP functions eventually caused a chain split. Clients prior to 0.3.6 can no longer sync with the current Bitcoin blockchain after block 163,685.^{[citation needed]}
• March 2013 Chain Fork. The migration from BerkeleyDB to LevelDB in v0.8 caused a chain split. Miners reorged 24-blocks by switching back to v0.7.2. At least one double-spend occurred during this event. This bug was later fixed in v0.8.1.^[8]

Hard Forks that created alternative blockchains and cryptocurrencies

These are Hard Forks created via consensus rule changes that created an alternative blockchain and cryptocurrency. They share a transaction history with Bitcoin up to a certain time and date. The first hard fork splitting bitcoin happened on 1 August 2017, resulting in the creation of Bitcoin Cash.

The following is a list of notable hard forks splitting bitcoin by date and/or block:

• Bitcoin Cash: Forked at block 478558, 1 August 2017, for each bitcoin (BTC), an owner got 1 Bitcoin Cash (BCH)
• Bitcoin Satoshi Vision: Forked at block 556766, 15 November 2018, for each Bitcoin Cash (BCH), an owner got 1 Bitcoin SV (BSV).
• eCash: Forked at block 661648, 15 November 2020, for each Bitcoin Cash (BCH), an owner got 1,000,000 eCash (XEC).
• Bitcoin Gold: Forked at block 491407, 24 October 2017, for each bitcoin (BTC), an owner got 1 Bitcoin Gold (BTG)

Bitcoin Classic

In its first 8 months, Bitcoin Classic promoted a single increase of the maximum block size from one megabyte to two megabytes.^[9][10] In November 2016 this changed and the project moved to a solution that moved the limit out of the software rules into the hands of the miners and nodes.^[11]

Bitcoin Unlimited

All three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.^[12][10]

Software forks of Bitcoin Core without a blockchain

The following are proposed software forks of the Bitcoin Core software client that did not successfully launch a blockchain:

Bitcoin XT

A fork initiated by Mike Hearn. The current reference implementation for bitcoin contains a computational bottleneck.^[13] The actual fork was preceded by Mike Hearn publishing a Bitcoin Improvement Proposal (BIP 64) on June 10, 2014, calling for the addition of "a small P2P protocol extension that performs UTXO lookups given a set of outpoints."^{[src 1]} On December 27, 2014 Hearn released version 0.10 of the forked client XT, with the BIP 64 changes.^{[src 2]} It achieved significant attention within the bitcoin community in mid-2015 amid a contentious debate among core developers over increasing the block size cap.^[14][10]

On June 22, 2015, Gavin Andresen published BIP 101 calling for an increase in the maximum block size. The changes would activate a fork allowing eight MB blocks (doubling in size every two years) once 75% of a stretch of 1,000 mined blocks is achieved after the beginning of 2016.^{[src 3]} The new maximum transaction rate under XT would have been 24 transactions per second.^[15]

On August 6, 2015 Andresen's BIP101 proposal was merged into the XT codebase.^{[src 4][src 5]} Bip 101 was reverted^{[src 6]} and the 2-MB block size bump of Bitcoin Classic was applied instead.^{[citation needed]}

The August 2015 release of XT received widespread media coverage. The Guardian wrote that "bitcoin is facing civil war".^[14]

Wired wrote that "Bitcoin XT exposes the extremely social—extremely democratic—underpinnings of the open source idea, an approach that makes open source so much more powerful than technology controlled by any one person or organization."^[16] Developer Adam Back was critical of the 75% activation threshold being too low and that some of the changes were insecure.^[17]

On August 25, 2017, Bitcoin XT published Release G, which was a Bitcoin Cash client by default.^{[src 7]} Subsequently, Release H was published, which supported the November 2017 Bitcoin Cash protocol upgrade, followed by Release I, which supported the May 2018 Bitcoin Cash protocol upgrade.^{[citation needed]}

Potential hard forks that were never exploited

These are client consensus updates that could have potentially caused a hard fork. They were either never exploited before being patched, or were reverted by a reorg before they were patched.

• CVE-2010-5139: There was a value overflow bug that was exploited when a transaction minted 184B bitcoins. Miners reorged the blockchain to remove the minting transaction, causing a chain split. Because the reorg occured before wxBitcoin v0.3.11 was released to fix the bug, it technically was not a hard fork.^[18][19]
• CVE-2018-17144: Bitcoin 0.15 had a critical inflation bug that allowed double spending certain inputs in the same block. This was not exploited before being patched.^[20]