aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2019-06-16 12:44:55 -0400
committerMarcoFalke <falke.marco@gmail.com>2019-06-16 12:44:57 -0400
commitf3855781fdc52382b7ccfd0060623fa8ab1541b5 (patch)
treefde8db5ce4c15904bd56f372770b9f15a4e1fb8f /doc
parent2ea8ebd211edea9bf222ec3b7786f1d21d247aa7 (diff)
parentfa55dd89cbfababb400624d6c2081487ee6b176f (diff)
Merge #16196: doc: Add release notes for 14897 & 15834
fa55dd89cb doc: Add release notes for 14897 & 15834 (MarcoFalke) Pull request description: #14897 & #15834 ACKs for commit fa55dd: fanquake: ACK fa55dd89cbfababb400624d6c2081487ee6b176f Tree-SHA512: 301742191f3d0e9383c6fe455d18d1e153168728e75dd29b7d0a0246af1cf024cc8199e82a42d74b3e6f5b556831763e0170ed0cb7b3082c7e0c57b05a5776db
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md15
1 files changed, 13 insertions, 2 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 4a86469ccf..9efb6cbabb 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -90,7 +90,7 @@ Updated RPCs
Note: some low-level RPC changes mainly useful for testing are described in the
Low-level Changes section below.
-* The `sendmany` RPC had an argument `minconf` that was not well specified and
+- The `sendmany` RPC had an argument `minconf` that was not well specified and
would lead to RPC errors even when the wallet's coin selection would succeed.
The `sendtoaddress` RPC never had this check, so to normalize the behavior,
`minconf` is now ignored in `sendmany`. If the coin selection does not
@@ -106,11 +106,22 @@ Low-level changes
Configuration
------------
-* An error is issued where previously a warning was issued when a setting in
+- An error is issued where previously a warning was issued when a setting in
the config file was specified in the default section, but not overridden for
the selected network. This change takes only effect if the selected network
is not mainnet.
+Network
+-------
+
+- When fetching a transaction announced by multiple peers, previous versions of
+ Bitcoin Core would sequentially attempt to download the transaction from each
+ announcing peer until the transaction is received, in the order that those
+ peers' announcements were received. In this release, the download logic has
+ changed to randomize the fetch order across peers and to prefer sending
+ download requests to outbound peers over inbound peers. This fixes an issue
+ where inbound peers can prevent a node from getting a transaction.
+
Wallet
------