1 (note: this is a temporary file, to be added-to by anybody, and moved to
2 release-notes at release time)
4 Bitcoin Core version *version* is now available from:
6 <https://bitcoin.org/bin/bitcoin-core-*version*/>
8 This is a new major version release, including new features, various bugfixes
9 and performance improvements, as well as updated translations.
11 Please report bugs using the issue tracker at GitHub:
13 <https://github.com/bitcoin/bitcoin/issues>
15 To receive security and update notifications, please subscribe to:
17 <https://bitcoincore.org/en/list/announcements/join/>
22 If you are running an older version, shut it down. Wait until it has completely
23 shut down (which might take a few minutes for older versions), then run the
24 installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on Mac)
25 or `bitcoind`/`bitcoin-qt` (on Linux).
27 The first time you run version 0.15.0, your chainstate database will be converted to a
28 new format, which will take anywhere from a few minutes to half an hour,
29 depending on the speed of your machine.
31 Note that the block database format also changed in version 0.8.0 and there is no
32 automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
33 directly from 0.7.x and earlier without redownloading the blockchain is not supported.
34 However, as usual, old wallet versions are still supported.
39 The chainstate database for this release is not compatible with previous
40 releases, so if you run 0.15 and then decide to switch back to any
41 older version, you will need to run the old release with the `-reindex-chainstate`
42 option to rebuild the chainstate data structures in the old format.
44 If your node has pruning enabled, this will entail re-downloading and
45 processing the entire blockchain.
50 Bitcoin Core is extensively tested on multiple operating systems using
51 the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.
53 Bitcoin Core should also work on most other Unix-like systems but is not
54 frequently tested on them.
59 Miner block size limiting deprecated
60 ------------------------------------
62 Though blockmaxweight has been preferred for limiting the size of blocks returned by
63 getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished
64 to limit their block size directly. Using this option resulted in a few UI issues as
65 well as non-optimal fee selection and ever-so-slightly worse performance, and has thus
66 now been deprecated. Further, the blockmaxsize option is now used only to calculate an
67 implied blockmaxweight, instead of limiting block size directly. Any miners who wish
68 to limit their blocks by size, instead of by weight, will have to do so manually by
69 removing transactions from their block template directly.
73 Due to a backward-incompatible change in the wallet database, wallets created
74 with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0
75 will only create hierarchical deterministic (HD) wallets.
78 ----------------------
79 - The "currentblocksize" value in getmininginfo has been removed.
80 - The deprecated RPC `getinfo` was removed. It is recommended that the more specific RPCs are used:
86 - `dumpwallet` no longer allows overwriting files. This is a security measure
87 as well as prevents dangerous user mistakes.
92 Thanks to everyone who directly contributed to this release:
95 As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).