@@ -3,7 +3,7 @@ release-notes at release time)
3
3
4
4
Bitcoin Core version * version* is now available from:
5
5
6
- < https://bitcoin .org/bin/bitcoin-core-*version*/ >
6
+ < https://bitcoincore .org/bin/bitcoin-core-*version*/ >
7
7
8
8
This is a new major version release, including new features, various bugfixes
9
9
and performance improvements, as well as updated translations.
@@ -56,71 +56,6 @@ frequently tested on them.
56
56
Notable changes
57
57
===============
58
58
59
- GCC 4.8.x
60
- --------------
61
- The minimum version of GCC required to compile Bitcoin Core is now 4.8. No effort will be
62
- made to support older versions of GCC. See discussion in issue #11732 for more information.
63
-
64
- HD-wallets by default
65
- ---------------------
66
- Due to a backward-incompatible change in the wallet database, wallets created
67
- with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0
68
- will only create hierarchical deterministic (HD) wallets.
69
-
70
- Replace-By-Fee by default in GUI
71
- --------------------------------
72
- The send screen now uses BIP-125 RBF by default, regardless of ` -walletrbf ` .
73
- There is a checkbox to mark the transaction as final.
74
-
75
- The RPC default remains unchanged: to use RBF, launch with ` -walletrbf=1 ` or
76
- use the ` replaceable ` argument for individual transactions.
77
-
78
- Wallets directory configuration (` -walletdir ` )
79
- ----------------------------------------------
80
-
81
- Bitcoin Core now has more flexibility in where the wallets directory can be
82
- located. Previously wallet database files were stored at the top level of the
83
- bitcoin data directory. The behavior is now:
84
-
85
- - For new installations (where the data directory doesn't already exist),
86
- wallets will now be stored in a new ` wallets/ ` subdirectory inside the data
87
- directory by default.
88
- - For existing nodes (where the data directory already exists), wallets will be
89
- stored in the data directory root by default. If a ` wallets/ ` subdirectory
90
- already exists in the data directory root, then wallets will be stored in the
91
- ` wallets/ ` subdirectory by default.
92
- - The location of the wallets directory can be overridden by specifying a
93
- ` -walletdir=<path> ` option where ` <path> ` can be an absolute path to a
94
- directory or directory symlink.
95
-
96
- Care should be taken when choosing the wallets directory location, as if it
97
- becomes unavailable during operation, funds may be lost.
98
-
99
- Low-level RPC changes
100
- ----------------------
101
- - The deprecated RPC ` getinfo ` was removed. It is recommended that the more specific RPCs are used:
102
- * ` getblockchaininfo `
103
- * ` getnetworkinfo `
104
- * ` getwalletinfo `
105
- * ` getmininginfo `
106
- - The wallet RPC ` getreceivedbyaddress ` will return an error if called with an address not in the wallet.
107
- - The wallet RPC ` addwitnessaddress ` was deprecated and will be removed in version 0.17,
108
- set the ` address_type ` argument of ` getnewaddress ` , or option ` -addresstype=[bech32|p2sh-segwit] ` instead.
109
-
110
- Changed command-line options
111
- -----------------------------
112
- - ` -debuglogfile=<file> ` can be used to specify an alternative debug logging file.
113
-
114
- Renamed script for creating JSON-RPC credentials
115
- -----------------------------
116
- The ` share/rpcuser/rpcuser.py ` script was renamed to ` share/rpcauth/rpcauth.py ` . This script can be
117
- used to create ` rpcauth ` credentials for a JSON-RPC user.
118
-
119
-
120
- - ` dumpwallet ` now includes hex-encoded scripts from the wallet in the dumpfile, and
121
- ` importwallet ` now imports these scripts, but corresponding addresses may not be added
122
- correctly or a manual rescan may be required to find relevant transactions.
123
-
124
59
Credits
125
60
=======
126
61
0 commit comments