aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSuhas Daftuar <sdaftuar@gmail.com>2019-01-17 16:50:50 -0500
committerSuhas Daftuar <sdaftuar@gmail.com>2019-01-22 12:18:45 -0500
commita36d97d866e8a11f205d07c624ace7c3d1a2ded8 (patch)
treea1baad5b3e19d631367a04469e9a40099c10dac6 /doc
parent19c60ca4975d5cf3847d5ba43c65eb02462c2d0f (diff)
Default -whitelistforcerelay to off
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 53b5a2119f..89206bb219 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -111,6 +111,14 @@ Configuration option changes
ambiguous whether the hash character is meant for the password or as a
comment.
+- The `whitelistforcerelay` option is used to relay transactions from
+ whitelisted peers even when not accepted to the mempool. This option now
+ defaults to being off, so that changes in policy and disconnect/ban behavior
+ will not cause a node that is whitelisting another to be dropped by peers.
+ Users can still explicitly enable this behavior with the command line option
+ (and may want to consider letting the Bitcoin Core project know about their
+ use-case, as this feature could be deprecated in the future).
+
Documentation
-------------