Consensus versions: Difference between revisions
Jump to navigation
Jump to search
Buried deployments aren't really protocol changes? |
Contrarian (talk | contribs) 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. |
||
| 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 || | | 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> | ||
Revision as of 12:42, 31 March 2022
| TENTATIVE semantic version number | Software release | Change type | BIP(s) |
|---|---|---|---|
| 0.1.0 | wxBitcoin 0.1.0 | original | |
| 0.2.0 | wxBitcoin 0.1.6 | softfork | added nLockTime enforcement[1] |
| 0.2.1 | wxBitcoin 0.3.1 | softfork | mostly-redundant 1 MB block size limit |
| 0.2.2 | wxBitcoin 0.3.5 | softfork | fixes CVE-2010-5141 |
| 0.2.3 | wxBitcoin 0.3.6 | hardfork | OP_NOPs added[2] |
| 0.3.0 | wxBitcoin 0.3.7 | hardfork | scriptSig + scriptPubKey evaluations separated [3] |
| 0.3.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.3.3 | wxBitcoin 0.3.13 | softfork | Treat multisig with more than 20 keys invalid after block 84000 [4] |
| 1.0.0 | Bitcoin Core 0.6.0 | softfork | fixes CVE-2012-1909 |
| 1.1.0 | Bitcoin Core 0.6.0 | softfork | BIP16 |
| 1.1.1 | Bitcoin Core 0.7.0 | softfork | BIP34 |
| 1.1.2 | Bitcoin Core 0.8.1 | softfork | fixes CVE-2013-3220 by adding txid change limit |
| 2.0.0 | Bitcoin Core 0.8.1 | hardfork | removed BDB lock limit & txid change limit |
| 2.0.1 | Bitcoin Core 0.9.2 | softfork | BIP42 |
| 2.1.0 | Bitcoin Core 0.10.0 | softfork | BIP66 |
| 2.2.0 | Bitcoin Core 0.10.4 | softfork | BIP65 |
| 2.3.0 | Bitcoin Core 0.12.1 | softfork | BIP68, BIP112, BIP113 |
| 2.4.0 | Bitcoin Core 0.13.1 | softfork | BIP141, BIP143, BIP147 |
| 2.4.1 | Bitcoin Core UASF 0.14.0 | softfork | BIP148 |
| 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 |
See also
References
- ↑ Was the addition of nLockTime timelocks a hard fork?
Bitcoin StackExchange
Retrieved 2020-09-21 - ↑ https://github.com/bitcoin/bitcoin/blob/ec82517c8919f9cb7194511dc322a2575745e39e/script.cpp#L798
- ↑ https://bitcoin.stackexchange.com/questions/111673/was-bitcoin-0-3-7-actually-hard-forking
- ↑ https://github.com/bitcoin/bitcoin/commit/a790fa46f40d751307f86c37a709eb119768ce5b#diff-27496895958ca30c47bbb873299a2ad7a7ea1003a9faa96b317250e3b7aa1fef