Consensus versions - Revision history

Luke-jr: Renumber

2022-04-02T16:13:38Z

Renumber

← Older revision		Revision as of 16:13, 2 April 2022
Line 10:		Line 10:
	\| 0.2.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141		\| 0.2.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141
	\|-		\|-
	\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| hardfork \|\| OP_NOPs added<ref>https://github.com/bitcoin/bitcoin/blob/ec82517c8919f9cb7194511dc322a2575745e39e/script.cpp#L798</ref>		\| 0.3.0 \|\| wxBitcoin 0.3.6 \|\| hardfork \|\| OP_NOPs added<ref>https://github.com/bitcoin/bitcoin/blob/ec82517c8919f9cb7194511dc322a2575745e39e/script.cpp#L798</ref>
	\|-		\|-
	\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated <ref>https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking</ref>		\| 0.4.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated <ref>https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking</ref>
	\|-		\|-
	\| 0.3.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139		\| 0.4.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139
	\|-		\|-
	\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138		\| 0.4.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138
	\|-		\|-
	\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Treat multisig with more than 20 keys invalid after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>		\| 0.4.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Treat multisig with more than 20 keys invalid after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-		\|-
	\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909		\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909

Contrarian: Changed 0.3.6 to correctly reflect it being a hardfork. The previous behavior was to have the opcode switch statement default to return false for unknown opcodes.

2022-03-31T12:42:04Z

Changed 0.3.6 to correctly reflect it being a hardfork. The previous behavior was to have the opcode switch statement default to return false for unknown opcodes.

← Older revision		Revision as of 12:42, 31 March 2022
Line 10:		Line 10:
	\| 0.2.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141		\| 0.2.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141
	\|-		\|-
	\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| ~~softfork~~ \|\| OP_NOPs ~~made explicit~~		\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| hardfork \|\| OP_NOPs added<ref>https://github.com/bitcoin/bitcoin/blob/ec82517c8919f9cb7194511dc322a2575745e39e/script.cpp#L798</ref>
	\|-		\|-
	\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated <ref>https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking</ref>		\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated <ref>https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking</ref>

Luke-jr: Buried deployments aren't really protocol changes?

2022-02-07T22:12:35Z

Buried deployments aren't really protocol changes?

← Older revision		Revision as of 22:12, 7 February 2022
Line 19:		Line 19:
	\|-		\|-
	\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Treat multisig with more than 20 keys invalid after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>		\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Treat multisig with more than 20 keys invalid after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-
	\| 0.3.4 \|\| wxBitcoin 0.3.14 \|\| softfork \|\| Multisig with more than 20 keys invalid for all blocks <ref>https://github.com/bitcoin/bitcoin/commit/5cbf75324d1509a1262b65c5073314a4da3f6d77#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-		\|-
	\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909		\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909

Shesek: Add SE reference for the v0.3.7 change

2022-01-26T21:50:55Z

Add SE reference for the v0.3.7 change

← Older revision		Revision as of 21:50, 26 January 2022
Line 12:		Line 12:
	\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| softfork \|\| OP_NOPs made explicit		\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| softfork \|\| OP_NOPs made explicit
	\|-		\|-
	\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated		\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated <ref>https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking</ref>
	\|-		\|-
	\| 0.3.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139		\| 0.3.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139

934: See also https://blog.bitmex.com/bitcoins-consensus-forks/

2022-01-25T12:19:19Z

See also https://blog.bitmex.com/bitcoins-consensus-forks/

← Older revision		Revision as of 12:19, 25 January 2022
Line 48:		Line 48:
	\| 2.5.0 \|\| Bitcoin Core-based Taproot Client 0.21.0 \|\| softfork \|\| BIP341, BIP342, BIP343		\| 2.5.0 \|\| Bitcoin Core-based Taproot Client 0.21.0 \|\| softfork \|\| BIP341, BIP342, BIP343
	\|}		\|}

			== See also ==

			* https://blog.bitmex.com/bitcoins-consensus-forks/

			== References ==

934: opcode limit existed before, so clarify multisig limit

2022-01-25T10:55:50Z

opcode limit existed before, so clarify multisig limit

← Older revision		Revision as of 10:55, 25 January 2022
Line 18:		Line 18:
	\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138		\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138
	\|-		\|-
	\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| ~~Adding a 201 opcode limit, enforced~~ after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>		\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Treat multisig with more than 20 keys invalid after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-		\|-
	\| 0.3.4 \|\| wxBitcoin 0.3.14 \|\| softfork \|\| ~~Enforcing the 201 opcode limit~~ for all blocks <ref>https://github.com/bitcoin/bitcoin/commit/5cbf75324d1509a1262b65c5073314a4da3f6d77#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>		\| 0.3.4 \|\| wxBitcoin 0.3.14 \|\| softfork \|\| Multisig with more than 20 keys invalid for all blocks <ref>https://github.com/bitcoin/bitcoin/commit/5cbf75324d1509a1262b65c5073314a4da3f6d77#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-		\|-
	\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909		\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909

934: Undo revision https://en.bitcoin.it/w/index.php?title=Consensus_versions&diff=67454&oldid=67451

2022-01-25T10:45:46Z

Undo revision https://en.bitcoin.it/w/index.php?title=Consensus_versions&diff=67454&oldid=67451

← Older revision		Revision as of 10:45, 25 January 2022
Line 17:		Line 17:
	\|-		\|-
	\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138		\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138
			\|-
			\| 0.3.3 \|\| wxBitcoin 0.3.13 \|\| softfork \|\| Adding a 201 opcode limit, enforced after block 84000 <ref>https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
			\|-
			\| 0.3.4 \|\| wxBitcoin 0.3.14 \|\| softfork \|\| Enforcing the 201 opcode limit for all blocks <ref>https://github.com/bitcoin/bitcoin/commit/5cbf75324d1509a1262b65c5073314a4da3f6d77#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef</ref>
	\|-		\|-
	\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909		\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909

Luke-jr: Taproot

2021-05-31T20:51:46Z

Taproot

← Older revision		Revision as of 20:51, 31 May 2021
Line 41:		Line 41:
	\|-		\|-
	\| 2.4.2 \|\| Bitcoin Core 0.16.3 \|\| softfork \|\| fixes CVE-2018-17144		\| 2.4.2 \|\| Bitcoin Core 0.16.3 \|\| softfork \|\| fixes CVE-2018-17144
			\|-
			\| 2.5.0 \|\| Bitcoin Core-based Taproot Client 0.21.0 \|\| softfork \|\| BIP341, BIP342, BIP343
	\|}		\|}

Luke-jr: Bump minor versions for locktime enforcement

2020-09-21T12:35:54Z

Bump minor versions for locktime enforcement

← Older revision		Revision as of 12:35, 21 September 2020
Line 4:		Line 4:
	\| 0.1.0 \|\| wxBitcoin 0.1.0 \|\| original		\| 0.1.0 \|\| wxBitcoin 0.1.0 \|\| original
	\|-		\|-
	\| ~~???~~ \|\| wxBitcoin 0.1.6 \|\| softfork \|\| added nLockTime enforcement<ref>[https://bitcoin.stackexchange.com/a/99104/21052 Was the addition of nLockTime timelocks a hard fork?]<br>Bitcoin StackExchange<br>Retrieved 2020-09-21</ref>		\| 0.2.0 \|\| wxBitcoin 0.1.6 \|\| softfork \|\| added nLockTime enforcement<ref>[https://bitcoin.stackexchange.com/a/99104/21052 Was the addition of nLockTime timelocks a hard fork?]<br>Bitcoin StackExchange<br>Retrieved 2020-09-21</ref>
	\|-		\|-
	\| 0.1.1 \|\| wxBitcoin 0.3.1 \|\| softfork \|\| mostly-redundant 1 MB block size limit		\| 0.2.1 \|\| wxBitcoin 0.3.1 \|\| softfork \|\| mostly-redundant 1 MB block size limit
	\|-		\|-
	\| 0.1.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141		\| 0.2.2 \|\| wxBitcoin 0.3.5 \|\| softfork \|\| fixes CVE-2010-5141
	\|-		\|-
	\| 0.1.3 \|\| wxBitcoin 0.3.6 \|\| softfork \|\| OP_NOPs made explicit		\| 0.2.3 \|\| wxBitcoin 0.3.6 \|\| softfork \|\| OP_NOPs made explicit
	\|-		\|-
	\| 0.2.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated		\| 0.3.0 \|\| wxBitcoin 0.3.7 \|\| hardfork \|\| scriptSig + scriptPubKey evaluations separated
	\|-		\|-
	\| 0.2.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139		\| 0.3.1 \|\| wxBitcoin 0.3.10 \|\| softfork \|\| fixes CVE-2010-5137 and CVE-2010-5139
	\|-		\|-
	\| 0.2.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138		\| 0.3.2 \|\| wxBitcoin 0.3.12 \|\| softfork \|\| fixes CVE-2010-5138
	\|-		\|-
	\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909		\| 1.0.0 \|\| Bitcoin Core 0.6.0 \|\| softfork \|\| fixes CVE-2012-1909

Harding: Add nLockTime fork

2020-09-21T12:02:20Z

Add nLockTime fork

← Older revision		Revision as of 12:02, 21 September 2020
Line 3:		Line 3:
	\|-		\|-
	\| 0.1.0 \|\| wxBitcoin 0.1.0 \|\| original		\| 0.1.0 \|\| wxBitcoin 0.1.0 \|\| original
			\|-
			\| ??? \|\| wxBitcoin 0.1.6 \|\| softfork \|\| added nLockTime enforcement<ref>[https://bitcoin.stackexchange.com/a/99104/21052 Was the addition of nLockTime timelocks a hard fork?]<br>Bitcoin StackExchange<br>Retrieved 2020-09-21</ref>
	\|-		\|-
	\| 0.1.1 \|\| wxBitcoin 0.3.1 \|\| softfork \|\| mostly-redundant 1 MB block size limit		\| 0.1.1 \|\| wxBitcoin 0.3.1 \|\| softfork \|\| mostly-redundant 1 MB block size limit