List of bitcoin forks: Difference between revisions

Browse history interactively ← Previous editContent deleted Content addedVisual WikitextInline

Revision as of 01:29, 2 December 2018 view sourceFresheneesz (talk \| contribs)Extended confirmed users9,055 edits Undid revision 871572651 by Retimuko (talk) If you think the sources aren't sufficient, please discuss this on the talk page before reverting.Tag: Undo ← Previous edit		Latest revision as of 01:00, 26 September 2024 view source Artem P75 (talk \| contribs)Extended confirmed users2,287 edits Change Bitcoin SV link to newly created Bitcoin Satoshi Vision page
(50 intermediate revisions by 34 users not shown)
Line 1:		Line 1:
			{{Short description\|None}}
	{{pp-semi\|small=yes}}		{{pp-semi\|small=yes}}
	{{~~broader~~\|Fork (blockchain)~~\|forks~~}}		{{main\|Fork (blockchain)}}
			{{More citations needed\|date=September 2021}}
	] forks are defined variantly as changes in the protocol of the ] or as the situations that occur "when two or more blocks have the same block height".<ref>{{cite book\|last1=Antonopoulos\|first1=Andreas\|title=Mastering Bitcoin: Programming the Open Blockchain\|date=2017\|publisher=O' Reilly media, inc.\|location=USA\|isbn=978-1491954386\|page=Glossary\|edition=2}}</ref> A fork influences the validity of the ]. Forks are typically conducted in order to add new ] to a blockchain, to reverse the effects of ] or catastrophic ]. Forks require ] to be resolved or else a permanent split emerges.		] forks are defined variantly as changes in the protocol of the ] or as the situations that occur "when two or more blocks have the same block height".<ref>{{cite book\|last1=Antonopoulos\|first1=Andreas\|title=Mastering Bitcoin: Programming the Open Blockchain\|date=2017\|publisher=O' Reilly media, inc.\|location=USA\|isbn=978-1491954386\|page=Glossary\|edition=2}}</ref> A fork influences the validity of the ]. Forks are typically conducted in order to add new ] to a blockchain, to reverse the effects of ] or catastrophic ]. Forks require consensus to be resolved or else a permanent split emerges.

	==Forks of the client software==		==Forks of the client software==
	The following are ] of the ] for the ]:		The following are ] of the ] for the ]:
			; Bitcoin XT: A fork initiated by ]. The current reference implementation for bitcoin contains a computational ].<ref name="inth">{{Cite news \|url=http://www.newyorker.com/business/currency/inside-the-fight-over-bitcoins-future \|title=Inside the Fight Over Bitcoin's Future \|author=Maria Bustillos \|access-date=7 January 2017 \|date=25 August 2015 \|newspaper=The New Yorker \|publisher=Conde Naste }}</ref> 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 ] lookups given a set of outpoints."<ref group=src>{{cite web\|url=https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki\|title=bips/bip-0064.mediawiki at master · bitcoin/bips · GitHub\|work=GitHub}}</ref> On December 27, 2014 Hearn released version 0.10 of the forked client XT, with the BIP 64 changes.<ref group=src>{{cite web\|url=https://github.com/bitcoinxt/bitcoinxt/releases/tag/v0.10\|title=bitcoinxt/bitcoinxt\|website=GitHub}}</ref> It achieved significant attention within the bitcoin community in mid-2015 amid a contentious debate among core developers over increasing the block size cap.<ref name="Hern-2015">{{cite news\|url=https://www.theguardian.com/technology/2015/aug/17/bitcoin-xt-alternative-cryptocurrency-chief-scientist\|title=Bitcoin's forked: chief scientist launches alternative proposal for the currency\|author=Alex Hern\|date=17 August 2015\|newspaper=the Guardian\|access-date=20 August 2015}}</ref><ref name=":0">{{Cite web \|date=2022-04-29 \|title=A list of Bitcoin forks and how they have changed the network - CNBC TV18 \|url=https://www.cnbctv18.com/cryptocurrency/a-list-of-bitcoin-forks-and-how-they-have-changed-the-network-13318902.htm \|access-date=2024-09-09 \|website=CNBCTV18 \|language=en}}</ref>
⚫	* ]

	* ]
			:On June 22, 2015, ] 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.<ref group=src>{{cite web\|url=https://github.com/bitcoin/bips/blob/master/bip-0101.mediawiki\|title=bips/bip-0101.mediawiki at master · bitcoin/bips · GitHub\|work=GitHub}}</ref> The new maximum transaction rate under XT would have been 24 transactions per second.<ref name="edov">{{Cite news \|url=http://www.pcworld.com/article/2974339/bitcoin-xt-debate-overshadowing-growth-opportunities.html \|title=Bitcoin XT debate overshadowing growth opportunities \|author=Tim Hornyak \|access-date=7 January 2017 \|date=21 August 2015 \|work=PC World \|publisher=IDG }}</ref>
	* ]

⚫	All three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.<ref name="tbs">{{cite book \|title=The Bitcoin Standard: The Decentralized Alternative to Central Banking \|last=Ammous \|first=Saifedean \|year=2018 \|publisher=John Wiley & Sons \|isbn=9781119473893 \|pages=227, 228 \|url=https://play.google.com/store/books/details?id=Pw5TDwAAQBAJ \|~~accessdate~~=23 April 2018}}</ref>
			:On August 6, 2015 Andresen's BIP101 proposal was merged into the XT ].<ref group=src>{{cite web\|url=https://github.com/bitcoinxt/bitcoinxt/commit/946e3ba8c7806a66c2b834d3817ff0c986c0811b\|title=Implement hard fork to allow bigger blocks · bitcoinxt/bitcoinxt@946e3ba\|website=GitHub}}</ref><ref group=src>{{cite web\|url=https://github.com/bitcoinxt/bitcoinxt/releases/tag/v0.11A\|title=bitcoinxt/bitcoinxt\|website=GitHub}}</ref> Bip 101 was reverted<ref group=src>{{cite web\|url=https://github.com/bitcoinxt/bitcoinxt/pull/117\|title=2MB block size bump by dgenr8 · Pull Request #117 · bitcoinxt/bitcoinxt\|website=GitHub}}</ref> and the 2-MB block size bump of ] was applied instead.{{cn\|date=February 2021}}

			:The August 2015 release of XT received widespread media coverage. '']'' wrote that "bitcoin is facing civil war".<ref name="Hern-2015" />

			:'']'' 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."<ref>{{cite magazine\|url=https://www.wired.com/2015/08/bitcoin-schism-shows-genius-open-source/\|title=The Bitcoin Schism Shows the Genius of Open Source\|date=19 August 2015\|magazine=WIRED\|author=Cade Metz}}</ref> Developer ] was critical of the 75% activation threshold being too low and that some of the changes were insecure.<ref name="bisp">{{Cite news \|url=https://www.cnbc.com/2015/08/20/bitcoin-splits-will-it-break-or-be-better-than-ever.html \|title=Bitcoin splits: Will it break, or be better than ever? \|author=Everett Rosenfeld \|access-date=5 January 2017 \|date=20 August 2015 \|publisher=CNBC}}</ref>

			:On August 25, 2017, Bitcoin XT published ''Release G'', which was a ] client by default.<ref name="releases" group=src>{{cite web\|url=https://github.com/bitcoinxt/bitcoinxt/releases\|title=Bitcoin XT Releases\|website=] \|access-date=17 June 2018}}</ref> 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.{{cn\|date=February 2021}}

			; Bitcoin Classic: In its first 8 months, Bitcoin Classic promoted a single increase of the maximum block size from one megabyte to two megabytes.<ref name="paulvigna">{{cite web\|url=https://www.wsj.com/articles/is-bitcoin-breaking-up-1453044493\|title=Is Bitcoin Breaking Up?\|author=Paul Vigna\|date=17 January 2016\|work=Wall Street Journal}}</ref><ref name=":0" /> 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.<ref>{{cite web \|url=https://zander.github.io/posts/Classic%20is%20Back/ \|title=Classic is Back \|access-date=April 28, 2017 \|archive-url=https://web.archive.org/web/20170202055402/https://zander.github.io/posts/Classic%20is%20Back/ \|archive-date=2017-02-02 \|url-status=dead}}</ref>
		⚫	; ]
		⚫	All three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.<ref name="tbs">{{cite book \|title=The Bitcoin Standard: The Decentralized Alternative to Central Banking \|last=Ammous \|first=Saifedean \|year=2018 \|publisher=John Wiley & Sons \|isbn=9781119473893 \|pages=227, 228 \|url=https://play.google.com/store/books/details?id=Pw5TDwAAQBAJ \|access-date=23 April 2018}}</ref><ref name=":0" />

	==Intended hard forks splitting the cryptocurrency==		==Intended hard forks splitting the cryptocurrency==
	Hard forks splitting ] (aka "split coins") are created via changes of the blockchain rules and sharing 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 ].		Hard forks splitting ] (aka "split coins") are created via changes of the blockchain rules and sharing 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 ].
⚫	The following is a list of hard forks splitting bitcoin by date and/or block:

		⚫	The following is a list of notable hard forks splitting bitcoin by date and/or block:
⚫	* ]: Forked at block 478558, ~~{{Date\|~~2017~~-08-01}}~~, for each bitcoin (BTC), an owner got 1 Bitcoin Cash (BCH)
⚫	* ]: Forked at block 491407, ~~{{Date\|2017-10-~~24}}, for each BTC, an owner got 1 Bitcoin Gold (BTG)
	* Bitcoin Diamond: Forked at Block 495866<ref name="bitcoindiamond.org about">{{Cite web\|url=https://www.bitcoindiamond.org/about/\|title=Bitcoin Diamond Website\|language=en\|access-date=2018-11-23}}</ref><ref name="coinsutra.com BCD">{{cite web\|url=https://coinsutra.com/buy-sell-bitcoin-diamond-bcd-exchanges/\|title=Bitcoin Diamond (BCD): A Full List Of Bitcoin Diamond Exchanges}}</ref><ref name="coinstalker.com BCD">{{cite web \| last = Terenzi \| first = Carlos \| title = Bitcoin Diamond: What is it and What You Should Know About it \| publisher = ] \| date=2017-11-25 \| url=https://www.coinstaker.com/bitcoin-diamond-fork/ \| accessdate = 2018-01-15}}</ref>, {{Date\|2017-11-24}}.<ref name="ethereumworldnews.com BCD">{{cite web\|url=https://ethereumworldnews.com/bitcoin-diamond-bcd-gains-105-percent-binance-listing/\|title=Bitcoin Diamond (BCD) The only Gainer Among the Top 100 Cryptos, Rises +105% In 24 Hours}}</ref><ref name="hacked.com BCD">{{cite web\|url=https://hacked.com/bitcoin-diamond-bcd-and-binance-a-256-pump-amid-the-global-dump/\|title=Bitcoin Diamond (BCD) and Binance: A 256% Pump Amid the Global Dump}}</ref><ref name="cointelegraph.com BCD">{{cite web \| last = Dhaliwal \| first = Shivdeep \| title = Is Bitcoin Diamond a Better Bitcoin? \| publisher = ] \| date = 2017-12-03 \| url=https://cointelegraph.com/news/is-bitcoin-diamond-a-better-bitcoin \| accessdate = 2018-01-15}}</ref> Holders of BTC received 10 BCD/BTC.<ref name="jimmysong BCD">{{Cite web\|url=https://medium.com/@jimmysong/bitcoin-diamond-super-bitcoin-bitcore-what-you-need-to-know-f49c35688a39\|title=Bitcoin Diamond/Super Bitcoin/BitCore: What You Need To Know
	}}</ref>
⚫	* ]: Forked at block ~~511346~~, ~~{{Date\|~~2018~~-02-28}}~~, for each Bitcoin ~~(BTC) or ZClassic~~ (~~ZCL~~), an owner got 1 Bitcoin ~~Private~~ (~~BTCP~~).
⚫	* ]: Forked at block ~~556766~~, ~~{{Date\|2018-11-~~15}}, for each Bitcoin Cash (BCH), an owner got 1 ~~Bitcoin SV~~ (~~BSV~~).

		⚫	* ]: Forked at block 478558, 1 August 2017, for each bitcoin (BTC), an owner got 1 Bitcoin Cash (BCH)
⚫	==Intended soft forks splitting from not-most-work block==
		⚫	** ]: Forked at block 556766, 15 November 2018, for each Bitcoin Cash (BCH), an owner got 1 Bitcoin SV (BSV).
⚫	* The fork fixing the value overflow incident was controversial because it was announced after the exploit was mined.
		⚫	** ]: Forked at block 661648, 15 November 2020, for each Bitcoin Cash (BCH), an owner got 1,000,000 eCash (XEC).
		⚫	* ]: Forked at block 491407, 24 October 2017, for each bitcoin (BTC), an owner got 1 Bitcoin Gold (BTG)

		⚫	==Intended soft forks splitting from a not-most-work block==
⚫	==~~Unintended~~ hard forks==
		⚫	* The fork fixing the value overflow incident was controversial because it was announced after the exploit was mined. It was assigned .
⚫	~~Two~~ hard forks were created by "protocol change" definition:

			==Intended soft forks splitting from the most-work block==
			===Segwit===
			{{main\|Segwit}}
			===Taproot===
			Taproot is an agreed soft fork in the transaction format. The fork adds support for ]s, and improves functionality of ]s and the ]. The fork was installed in November 2021.<ref>{{Cite news\|last=Sigalos\|first=MacKenzie\|date=2021-06-09\|title=Bitcoin just got its first makeover in four years\|language=en-US\|work=CNBC\|url=https://www.cnbc.com/2021/06/12/bitcoin-taproot-upgrade-what-it-means.html\|access-date=2021-06-15\|issn=}}</ref> The upgrade adds privacy features.<ref>{{Cite news\|last= Kharif\|first=Olga\|date=2021-06-15\|title=Bitcoin to get more privacy features in Taproot update, making it harder to trace payments\|language=en-US\|work=Bloomberg\|url=https://www.bloomberg.com/news/articles/2021-06-15/bitcoin-network-approves-privacy-update-as-scrutiny-increases\|access-date=2021-06-23\|issn=}}</ref><ref>{{Cite news\|last= Locke\|first=Taylor\|date=2021-06-14\|title=7 key things that happened in crypto over the past week\|language=en-US\|work=CNBC\|url=https://www.cnbc.com/2021/06/14/7-key-things-that-happened-in-crypto-over-the-past-week.html\|access-date=2021-06-23\|issn=}}</ref> Taproot includes Bitcoin Improvement Proposal numbers BIP340, BIP341, BIP342.<ref>{{Cite web \|url=https://github.com/bitcoin/bips \|title=All Bitcoin Improvement Proposals, including BIP340 \|date=2021-06-01 \|via=GitHub}}</ref>

			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\|date=August 2021}}
			* Reduced transaction costs: The data size of complex Bitcoin transactions is reduced, which leads to lower transaction fees.{{Citation needed\|date=August 2021}}
			* Support for more complicated conditions for a transaction via Schnorr signatures.{{Citation needed\|date=August 2021}}
			* Benefits for the ]: More flexibility, privacy enhancement, lower costs.{{Citation needed\|date=August 2021}}

		⚫	==Bitcoin hard forks==
		⚫	Three hard forks were created by "protocol change" definition:
			* July 2010 Chain Fork (addition of OP_NOP functions)
	* March 2013 Chain Fork (migration from BerkeleyDB to LevelDB caused a chain split)<ref></ref>		* March 2013 Chain Fork (migration from BerkeleyDB to LevelDB caused a chain split)<ref></ref>
	* CVE-2018-17144 (Bitcoin 0.15 allowed double spending certain inputs in the same block. Not exploited)		* CVE-2018-17144 (Bitcoin 0.15 allowed double spending certain inputs in the same block. Not exploited)

	==References==		==References==
			===Source code===
			{{Reflist\|group=src}}

			===Other references===
	{{Reflist\|30em}}		{{Reflist\|30em}}

Latest revision as of 01:00, 26 September 2024

Main article: Fork (blockchain)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "List of bitcoin forks" – news · newspapers · books · scholar · JSTOR (September 2021) (Learn how and when to remove this message)

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

Forks of the client software

The following are forks of the software client for the bitcoin network:

Bitcoin XT: A fork initiated by Mike Hearn. The current reference implementation for bitcoin contains a computational bottleneck. 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." On December 27, 2014 Hearn released version 0.10 of the forked client XT, with the BIP 64 changes. It achieved significant attention within the bitcoin community in mid-2015 amid a contentious debate among core developers over increasing the block size cap.

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

On August 6, 2015 Andresen's BIP101 proposal was merged into the XT codebase. Bip 101 was reverted 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—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." Developer Adam Back was critical of the 75% activation threshold being too low and that some of the changes were insecure.

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

Bitcoin Classic: In its first 8 months, Bitcoin Classic promoted a single increase of the maximum block size from one megabyte to two megabytes. 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.
Bitcoin Unlimited

All three software clients attempt to increase transaction capacity of the network. None achieved a majority of the hash power.

Intended hard forks splitting the cryptocurrency

Hard forks splitting bitcoin (aka "split coins") are created via changes of the blockchain rules and sharing 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)

Intended soft forks splitting from a not-most-work block

The fork fixing the value overflow incident was controversial because it was announced after the exploit was mined. It was assigned CVE-2010-5139.

Intended soft forks splitting from the most-work block

Segwit

Main article: Segwit

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

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.
Reduced transaction costs: The data size of complex Bitcoin transactions is reduced, which leads to lower transaction fees.
Support for more complicated conditions for a transaction via Schnorr signatures.
Benefits for the Lightning Network: More flexibility, privacy enhancement, lower costs.

Bitcoin hard forks

Three hard forks were created by "protocol change" definition:

July 2010 Chain Fork (addition of OP_NOP functions)
March 2013 Chain Fork (migration from BerkeleyDB to LevelDB caused a chain split)
CVE-2018-17144 (Bitcoin 0.15 allowed double spending certain inputs in the same block. Not exploited)