build: Bump version to 0.16.99
Also clean out release notes. Tree-SHA512: c4d5b52c089e14438be37381e1b0dab3711cc72aa8d345d1024169fff0055f3d021c8ca9d46fb794110694ebcbf7cbca0a12619f650873c9d381530adea7100e
This commit is contained in:
Wladimir J. van der Laan
parent
8d57319863
commit
4602dc704a
2 changed files with 2 additions and 67 deletions
|
|
@ -1,7 +1,7 @@
|
||||||
dnl require autoconf 2.60 (AS_ECHO/AS_ECHO_N)
|
dnl require autoconf 2.60 (AS_ECHO/AS_ECHO_N)
|
||||||
AC_PREREQ([2.60])
|
AC_PREREQ([2.60])
|
||||||
define(_CLIENT_VERSION_MAJOR, 0)
|
define(_CLIENT_VERSION_MAJOR, 0)
|
||||||
define(_CLIENT_VERSION_MINOR, 15)
|
define(_CLIENT_VERSION_MINOR, 16)
|
||||||
define(_CLIENT_VERSION_REVISION, 99)
|
define(_CLIENT_VERSION_REVISION, 99)
|
||||||
define(_CLIENT_VERSION_BUILD, 0)
|
define(_CLIENT_VERSION_BUILD, 0)
|
||||||
define(_CLIENT_VERSION_IS_RELEASE, false)
|
define(_CLIENT_VERSION_IS_RELEASE, false)
|
||||||
|
|
|
||||||
|
|
@ -3,7 +3,7 @@ release-notes at release time)
|
||||||
|
|
||||||
Bitcoin Core version *version* is now available from:
|
Bitcoin Core version *version* is now available from:
|
||||||
|
|
||||||
<https://bitcoin.org/bin/bitcoin-core-*version*/>
|
<https://bitcoincore.org/bin/bitcoin-core-*version*/>
|
||||||
|
|
||||||
This is a new major version release, including new features, various bugfixes
|
This is a new major version release, including new features, various bugfixes
|
||||||
and performance improvements, as well as updated translations.
|
and performance improvements, as well as updated translations.
|
||||||
|
|
@ -56,71 +56,6 @@ frequently tested on them.
|
||||||
Notable changes
|
Notable changes
|
||||||
===============
|
===============
|
||||||
|
|
||||||
GCC 4.8.x
|
|
||||||
--------------
|
|
||||||
The minimum version of GCC required to compile Bitcoin Core is now 4.8. No effort will be
|
|
||||||
made to support older versions of GCC. See discussion in issue #11732 for more information.
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
Replace-By-Fee by default in GUI
|
|
||||||
--------------------------------
|
|
||||||
The send screen now uses BIP-125 RBF by default, regardless of `-walletrbf`.
|
|
||||||
There is a checkbox to mark the transaction as final.
|
|
||||||
|
|
||||||
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` or
|
|
||||||
use the `replaceable` argument for individual transactions.
|
|
||||||
|
|
||||||
Wallets directory configuration (`-walletdir`)
|
|
||||||
----------------------------------------------
|
|
||||||
|
|
||||||
Bitcoin Core now has more flexibility in where the wallets directory can be
|
|
||||||
located. Previously wallet database files were stored at the top level of the
|
|
||||||
bitcoin data directory. The behavior is now:
|
|
||||||
|
|
||||||
- For new installations (where the data directory doesn't already exist),
|
|
||||||
wallets will now be stored in a new `wallets/` subdirectory inside the data
|
|
||||||
directory by default.
|
|
||||||
- For existing nodes (where the data directory already exists), wallets will be
|
|
||||||
stored in the data directory root by default. If a `wallets/` subdirectory
|
|
||||||
already exists in the data directory root, then wallets will be stored in the
|
|
||||||
`wallets/` subdirectory by default.
|
|
||||||
- The location of the wallets directory can be overridden by specifying a
|
|
||||||
`-walletdir=<path>` option where `<path>` can be an absolute path to a
|
|
||||||
directory or directory symlink.
|
|
||||||
|
|
||||||
Care should be taken when choosing the wallets directory location, as if it
|
|
||||||
becomes unavailable during operation, funds may be lost.
|
|
||||||
|
|
||||||
Low-level RPC changes
|
|
||||||
----------------------
|
|
||||||
- The deprecated RPC `getinfo` was removed. It is recommended that the more specific RPCs are used:
|
|
||||||
* `getblockchaininfo`
|
|
||||||
* `getnetworkinfo`
|
|
||||||
* `getwalletinfo`
|
|
||||||
* `getmininginfo`
|
|
||||||
- The wallet RPC `getreceivedbyaddress` will return an error if called with an address not in the wallet.
|
|
||||||
- The wallet RPC `addwitnessaddress` was deprecated and will be removed in version 0.17,
|
|
||||||
set the `address_type` argument of `getnewaddress`, or option `-addresstype=[bech32|p2sh-segwit]` instead.
|
|
||||||
|
|
||||||
Changed command-line options
|
|
||||||
-----------------------------
|
|
||||||
- `-debuglogfile=<file>` can be used to specify an alternative debug logging file.
|
|
||||||
|
|
||||||
Renamed script for creating JSON-RPC credentials
|
|
||||||
-----------------------------
|
|
||||||
The `share/rpcuser/rpcuser.py` script was renamed to `share/rpcauth/rpcauth.py`. This script can be
|
|
||||||
used to create `rpcauth` credentials for a JSON-RPC user.
|
|
||||||
|
|
||||||
|
|
||||||
- `dumpwallet` now includes hex-encoded scripts from the wallet in the dumpfile, and
|
|
||||||
`importwallet` now imports these scripts, but corresponding addresses may not be added
|
|
||||||
correctly or a manual rescan may be required to find relevant transactions.
|
|
||||||
|
|
||||||
Credits
|
Credits
|
||||||
=======
|
=======
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue