bitcoin-change history study
change history
2014-03-19 Bitcoin Core version 0.9.0 released
- OP_RETURN feature
这个特性不是认可在区块中存储数据,而是创建一个可证明,可裁剪的 output,避免已经提交的一些存储模式,
例如:在 unspendable TX outputs 中保存图片等任意数据。避免 UTXO database 膨胀影响使用。
在区块中存储非交易数据现在仍然是个坏主意,保存在其他地方更有效率并且成本也更低。
- Autotools build system
- Bitcoin-cli
- Transaction Fees
2014-04-08 Bitcoin Core version 0.9.1 released
No code change, just dependencies
2014-06-16 Bitcoin Core version 0.9.2 released
- Gitian OSX build
- GUI
2014-06-19 Bitcoin Core version 0.9.2.1 released
not found potential fork feature
2014-09-27 Bitcoin Core version 0.9.3 released
not found potential fork feature
2015-02-16 Bitcoin Core version 0.10.0 released
BIP 66: strict DER encoding for signatures
2015-04-27 Bitcoin Core version 0.10.1 released
not found potential fork feature
2015-05-19 Bitcoin Core version 0.10.2 released
not found potential fork feature
2015-07-12 Bitcoin Core version 0.11.0 released
- Change the default maximum OP_RETURN size to 80 bytes
- Implement BIP62 rule 6
- Implement BIP66
2015-10-14 Bitcoin Core version 0.10.3 released
2015-10-15 Bitcoin Core version 0.11.1 released
2015-11-13 Bitcoin Core version 0.11.2 released
BIP113 specifies a soft fork
2016-02-23 Bitcoin Core version 0.12.0 released
2016-04-15 Bitcoin Core version 0.12.1 released
This release includes a soft fork deployment to enforce BIP68, BIP112 and BIP113 using the BIP9 deployment mechanism.
2016-08-23 Bitcoin Core version 0.13.0 released
- From 0.13.0 on, Windows XP is no longer supported.
- C++11 and Python 3
- Newly created wallets will use hierarchical deterministic key generation according to BIP32 (keypath m/0’/0’/k’). Existing wallets will still use traditional key generation.
- Segregated Witness not activate yet
- Removal of internal miner
2016-10-27 Bitcoin Core version 0.13.1 released
Implement NULLDUMMY softfork (BIP147) (jl2012)
2017-01-03 Bitcoin Core version 0.13.2 released
2017-03-08 Bitcoin Core version 0.14.0 released
2017-04-22 Bitcoin Core version 0.14.1 released
2017-06-17 Bitcoin Core version 0.14.2 released
2017-09-14 Bitcoin Core version 0.15.0 released
2017-09-19 Bitcoin Core version 0.15.0.1 released
fix gui bug
2017-11-11 Bitcoin Core version 0.15.1 released
2018-02-26 Bitcoin Core version 0.16.0 released
- Segwit Wallet
- HD-wallets by default
Due to a backward-incompatible change in the wallet database, wallets created with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.2018-06-15 Bitcoin Core version 0.16.1 released
2018-07-29 Bitcoin Core version 0.16.2 released
List of Bitcoin consensus fork
ref.
after 0.8.6 version there is six soft fork has been done
| Date | Activation Block Number | BIP Number or Software Version | Description | Type | Outcome |
|---|---|---|---|---|---|
| 4 July 2015 | 363,731 | BIP66 | Strict DER signature upgrade means Bitcoin is no longer dependent on OpenSSL’s signature parsing. | Softfork | 95% threshold over a 1,000-block period. A chainsplit occurred, lasting six blocks, as some miners signaled support for BIP66 but had not upgraded and were SPY mining. The new softfork rules chain eventually took the lead. |
| 14 Dec 2015 | 388,380 | BIP65 | Check Lock Time Verify enables funds to be locked until a specific time in the future. This is Bitcoin’s first new function. | Softfork | Successful rollout using a 95% threshold. |
| 4 July 2016 | 419,328 | BIP68,BIP112,BIP113 | Relative lock-time enables a transaction output to be banned for a relative amount of time after the transaction.CheckSequenceVerify.Median time-past removes the incentive for a miner to use a future block timestamp to grab more transaction fees. | Softfork | Successful rollout using 95% versionbits signaling. |
| 23 July 2017 | 477,800 | BIP91 | This temporary softfork makes signaling for the SegWit upgrade mandatory. | Softfork | Softfork successfully activated with an 80% miner threshold over a 336-block period, although only a tiny minority of users enforced BIP91 rules, which have since expired. Therefore, the risk of a chainsplit was elevated in this period. |
| 01 Aug 2017 | 478,479 | BIP148 | This temporary softfork makes signaling for the SegWit upgrade mandatory for a two week period following 1 August 2017. | Softfork | Flag-day softfork appeared to succeed with no issues, although only a minority of users enforced BIP148 rules, which have since expired. Therefore, the risk of a chainsplit was elevated in this period. |
| 24 Aug 2017 | 481,824 | BIP141,BIP143,BIP147 | The segregated-witness (SegWit) upgrade. | Softfork | Rollout using 95% versionbits signaling. |