List of bitcoin forks
This article needs additional citations for verification. (September 2021) |
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]:
- Soft Forks within Bitcoin: These don't split the network. These are consensus rule changes where some previously-valid blocks are now invalid.
- Hard Forks within Bitcoin: These cause a permanent chain split between the 2 versions. These are consensus rule changes where some previously-invalid blocks are now valid.
- Hard Forks that created alternative blockchains and cryptocurrencies.
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.[2] 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
Segregated Witness (SegWit), formally known as Segregated Witness (Consensus layer), is an implemented soft fork change in the transaction format of bitcoin.[3]
SegWit had Bitcoin Improvement Proposal number BIP141.[3] 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.[4] 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.[5] The upgrade adds privacy features.[6][7] Taproot includes Bitcoin Improvement Proposal numbers BIP340, BIP341, BIP342.[8]
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. These are consensus rule changes where some previously-invalid blocks are now valid in newer clients.[2]
- 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.[9]
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.[10][11] 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.[12]
- Bitcoin Unlimited
All three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.[13][11]
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.[14] 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.[15][11]
- 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.[16]
- 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".[15]
- 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."[17] Developer Adam Back was critical of the 75% activation threshold being too low and that some of the changes were insecure.[18]
- 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 occurred before wxBitcoin v0.3.11 was released to fix the bug, it technically was not a hard fork.[19][20]
- 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.[21]
References
Source code
- ^ "bips/bip-0064.mediawiki at master · bitcoin/bips · GitHub". GitHub.
- ^ "bitcoinxt/bitcoinxt". GitHub.
- ^ "bips/bip-0101.mediawiki at master · bitcoin/bips · GitHub". GitHub.
- ^ "Implement hard fork to allow bigger blocks · bitcoinxt/bitcoinxt@946e3ba". GitHub.
- ^ "bitcoinxt/bitcoinxt". GitHub.
- ^ "2MB block size bump by dgenr8 · Pull Request #117 · bitcoinxt/bitcoinxt". GitHub.
- ^ "Bitcoin XT Releases". GitHub. Retrieved 17 June 2018.
Other references
- ^ Antonopoulos, Andreas (2017). Mastering Bitcoin: Programming the Open Blockchain (2 ed.). USA: O' Reilly media, inc. p. Glossary. ISBN 978-1491954386.
- ^ a b c Lombrozo, Eric. "BIP: 123 - BIP Classification". Bitcoin BIP Github. Bitcoin. Retrieved 13 December 2025.
- ^ a b bitcoin/bips, Bitcoin, 2025-09-20, retrieved 2025-09-20
- ^ Segregated Witness proposal BIP 141
- ^ Sigalos, MacKenzie (2021-06-09). "Bitcoin just got its first makeover in four years". CNBC. Retrieved 2021-06-15.
- ^ Kharif, Olga (2021-06-15). "Bitcoin to get more privacy features in Taproot update, making it harder to trace payments". Bloomberg. Retrieved 2021-06-23.
- ^ Locke, Taylor (2021-06-14). "7 key things that happened in crypto over the past week". CNBC. Retrieved 2021-06-23.
- ^ "All Bitcoin Improvement Proposals, including BIP340". 2021-06-01 – via GitHub.
- ^ March 2013 Chain Fork
- ^ Paul Vigna (17 January 2016). "Is Bitcoin Breaking Up?". Wall Street Journal.
- ^ a b c "A list of Bitcoin forks and how they have changed the network - CNBC TV18". CNBCTV18. 2022-04-29. Retrieved 2024-09-09.
- ^ "Classic is Back". Archived from the original on 2017-02-02. Retrieved April 28, 2017.
- ^ Ammous, Saifedean (2018). The Bitcoin Standard: The Decentralized Alternative to Central Banking. John Wiley & Sons. pp. 227, 228. ISBN 9781119473893. Retrieved 23 April 2018.
- ^ Maria Bustillos (25 August 2015). "Inside the Fight Over Bitcoin's Future". The New Yorker. Conde Naste. Retrieved 7 January 2017.
- ^ a b Alex Hern (17 August 2015). "Bitcoin's forked: chief scientist launches alternative proposal for the currency". the Guardian. Retrieved 20 August 2015.
- ^ Tim Hornyak (21 August 2015). "Bitcoin XT debate overshadowing growth opportunities". PC World. IDG. Retrieved 7 January 2017.
- ^ Cade Metz (19 August 2015). "The Bitcoin Schism Shows the Genius of Open Source". WIRED.
- ^ Everett Rosenfeld (20 August 2015). "Bitcoin splits: Will it break, or be better than ever?". CNBC. Retrieved 5 January 2017.
- ^ "NVD - CVE-2010-5139". NIST National Vulnerability Database. Retrieved 2 December 2025.
- ^ Quamara, Sidharth; Singh, Awadhesh (22 February 2022). "A systematic survey on security concerns in cryptocurrencies: State-of-the-art and perspectives". Science Direct. 113 (102548). Retrieved 2 December 2025.
- ^ "NVD - cve-2018-17144". NIST National Vulnerability Database. Retrieved 2 December 2025.