List of bitcoin forks explained

See 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.

According to BIP-123 specifications, there are 3 main categories of Bitcoin forks[2] :

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

Soft Forks within Bitcoin

These are consensus rule changes that did not cause a split in the network. These are the result of consensus rule changes where previously-valid blocks are now invalid in newer clients. 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.

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.[3] The upgrade adds privacy features.[4] [5] Taproot includes Bitcoin Improvement Proposal numbers BIP340, BIP341, BIP342.[6]

Advantages:

Hard Forks within Bitcoin

These are Hard Forks within Bitcoin that caused a chain split but did not create an alternative network or cryptocurrency. These are consensus rule changes where some previously-invalid blocks are now valid in newer clients.

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 Classic: In its first 8 months, Bitcoin Classic promoted a single increase of the maximum block size from one megabyte to two megabytes.[8] 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.[9]
  • Bitcoin UnlimitedAll three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.[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.[11] 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."[12] On December 27, 2014 Hearn released version 0.10 of the forked client XT, with the BIP 64 changes.[13] 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] [15]

    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.[16] The new maximum transaction rate under XT would have been 24 transactions per second.[17]

    On August 6, 2015 Andresen's BIP101 proposal was merged into the XT codebase.[18] [19] Bip 101 was reverted[20] and the 2-MB block size bump of Bitcoin Classic was applied instead.

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

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

    On August 25, 2017, Bitcoin XT published Release G, which was a Bitcoin Cash client by default.[23] 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.

    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.

    References

    Other references

    Notes and References

    1. Book: Antonopoulos. Andreas. Mastering Bitcoin: Programming the Open Blockchain. 2017. O' Reilly media, inc.. USA. 978-1491954386. Glossary. 2.
    2. Web site: Lombrozo . Eric . BIP: 123 - BIP Classification . Bitcoin BIP Github . Bitcoin . 13 December 2025.
    3. News: Sigalos. MacKenzie. 2021-06-09. Bitcoin just got its first makeover in four years. en-US. CNBC. 2021-06-15.
    4. News: Kharif. Olga. 2021-06-15. Bitcoin to get more privacy features in Taproot update, making it harder to trace payments. en-US. Bloomberg. 2021-06-23.
    5. News: Locke. Taylor. 2021-06-14. 7 key things that happened in crypto over the past week. en-US. CNBC. 2021-06-23.
    6. Web site: All Bitcoin Improvement Proposals, including BIP340 . 2021-06-01 . GitHub.
    7. https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki March 2013 Chain Fork
    8. Web site: Is Bitcoin Breaking Up?. Paul Vigna. 17 January 2016. Wall Street Journal.
    9. Web site: Classic is Back . April 28, 2017 . https://web.archive.org/web/20170202055402/https://zander.github.io/posts/Classic%20is%20Back/ . 2017-02-02 . dead.
    10. Book: Ammous, Saifedean . The Bitcoin Standard: The Decentralized Alternative to Central Banking . 2018 . John Wiley & Sons . 9781119473893 . 227, 228 . 23 April 2018.
    11. News: Inside the Fight Over Bitcoin's Future . Maria Bustillos . 7 January 2017 . 25 August 2015 . The New Yorker . Conde Naste .
    12. Web site: bips/bip-0064.mediawiki at master 路 bitcoin/bips 路 GitHub. GitHub.
    13. Web site: bitcoinxt/bitcoinxt. GitHub.
    14. News: Bitcoin's forked: chief scientist launches alternative proposal for the currency. Alex Hern. 17 August 2015. the Guardian. 20 August 2015.
    15. Web site: 2022-04-29 . A list of Bitcoin forks and how they have changed the network - CNBC TV18 . 2024-09-09 . CNBCTV18 . en.
    16. Web site: bips/bip-0101.mediawiki at master 路 bitcoin/bips 路 GitHub. GitHub.
    17. News: Bitcoin XT debate overshadowing growth opportunities . Tim Hornyak . 7 January 2017 . 21 August 2015 . PC World . IDG .
    18. Web site: Implement hard fork to allow bigger blocks 路 bitcoinxt/bitcoinxt@946e3ba. GitHub.
    19. Web site: bitcoinxt/bitcoinxt. GitHub.
    20. Web site: 2MB block size bump by dgenr8 路 Pull Request #117 路 bitcoinxt/bitcoinxt. GitHub.
    21. The Bitcoin Schism Shows the Genius of Open Source. 19 August 2015. WIRED. Cade Metz.
    22. News: Bitcoin splits: Will it break, or be better than ever? . Everett Rosenfeld . 5 January 2017 . 20 August 2015 . CNBC.
    23. Web site: Bitcoin XT Releases. . 17 June 2018.
    24. Web site: NVD - CVE-2010-5139 . NIST National Vulnerability Database . 2 December 2025.
    25. Quamara . Sidharth . Singh . Awadhesh . A systematic survey on security concerns in cryptocurrencies: State-of-the-art and perspectives . Computers & Security. 22 February 2022 . 113 . 102548 . 102548 . 10.1016/j.cose.2021.102548 . 2 December 2025. subscription .
    26. Web site: NVD - cve-2018-17144 . NIST National Vulnerability Database . 2 December 2025.