Merge #8519: [0.13] A few small improvements to the 0.13 release notes
2f58589 Mention dump/import support for HD wallets (Pieter Wuille)
fe20b83 Remove refactors from list of changes (Pieter Wuille)
7f84015 Inline mempool RPCs and feefilter into misc sections (Pieter Wuille)
@ -54,6 +54,7 @@ For nodes on low-memory systems, the database cache can be changed back to
@@ -54,6 +54,7 @@ For nodes on low-memory systems, the database cache can be changed back to
Note that the database cache setting has the most performance impact
during initial sync of a node, and when catching up after downtime.
bitcoin-cli: arguments privacy
--------------------------------
@ -71,6 +72,7 @@ It is recommended to use this for sensitive information such as wallet
@@ -71,6 +72,7 @@ It is recommended to use this for sensitive information such as wallet
passphrases, as command-line arguments can usually be read from the process
table by any user on the system.
C++11 and Python 3
-------------------
@ -84,6 +86,7 @@ When cross-compiling for a target that doesn't have C++11 libraries, configure w
@@ -84,6 +86,7 @@ When cross-compiling for a target that doesn't have C++11 libraries, configure w
For running the functional tests in `qa/rpc-tests`, Python3.4 or higher is now
required.
Linux ARM builds
------------------
@ -104,20 +107,6 @@ possible to resolve them.
@@ -104,20 +107,6 @@ possible to resolve them.
Note that Android is not considered ARM Linux in this context. The executables
are not expected to work out of the box on Android.
New mempool information RPC calls
---------------------------------
RPC calls have been added to output detailed statistics for individual mempool
entries, as well as to calculate the in-mempool ancestors or descendants of a
transaction: see `getmempoolentry`, `getmempoolancestors`, `getmempooldescendants`.
Fee filtering of invs (BIP 133)
------------------------------------
The optional new p2p message "feefilter" is implemented and the protocol
version is bumped to 70013. Upon receiving a feefilter message from a peer,
a node will not send invs for any transactions which do not meet the filter
@ -130,6 +119,7 @@ cases it also reduces propagation delay. It is automatically enabled between
@@ -130,6 +119,7 @@ cases it also reduces propagation delay. It is automatically enabled between
Newly created wallets will use hierarchical deterministic key generation
@ -142,6 +132,10 @@ ones which haven't already been generated during the time of the backup.
@@ -142,6 +132,10 @@ ones which haven't already been generated during the time of the backup.
**Attention:** Encrypting the wallet will create a new seed which requires
a new backup!
Wallet dumps (created using the `dumpwallet` RPC) will contain the deterministic
seed. This is expected to allow future versions to import the seed and all
associated funds, but this is not yet implemented.
HD key generation for new wallets can be disabled by `-usehd=0`. Keep in
mind that this flag only has affect on newly created wallets.
You can't disable HD key generation once you have created a HD wallet.
@ -152,6 +146,7 @@ HD wallets are incompatible with older versions of Bitcoin Core.
@@ -152,6 +146,7 @@ HD wallets are incompatible with older versions of Bitcoin Core.
@ -232,6 +228,7 @@ using the command line option `-reindex-chainstate` (in addition to
@@ -232,6 +228,7 @@ using the command line option `-reindex-chainstate` (in addition to
are assumed to be fine, but the chainstate is still corrupted. It is also
useful for benchmarks.
Removal of internal miner
--------------------------
@ -246,9 +243,15 @@ For testing, the `generate` call can still be used to mine a block, and a new
@@ -246,9 +243,15 @@ For testing, the `generate` call can still be used to mine a block, and a new
RPC call `generatetoaddress` has been added to mine to a specific address. This
works with wallet disabled.
Low-level P2P changes
----------------------
- The optional new p2p message "feefilter" is implemented and the protocol
version is bumped to 70013. Upon receiving a feefilter message from a peer,
a node will not send invs for any transactions which do not meet the filter
Wladimir J. van der Laan
8 years ago