diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-01-24 15:19:47 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-01-24 15:25:17 +0100 |
| commit | 72bd4ab867e3be0d8410403d9641c08288d343e3 (patch) | |
| tree | aac7d5bbf05ba12d12ffd939fb937e6b5ea72041 /doc/release-notes.md | |
| parent | 5eb32d23841bbcd8eaf7ba49dc4ddfd822bd4773 (diff) | |
| parent | a36d97d866e8a11f205d07c624ace7c3d1a2ded8 (diff) | |
Merge #15193: Default -whitelistforcerelay to off
a36d97d866e8a11f205d07c624ace7c3d1a2ded8 Default -whitelistforcerelay to off (Suhas Daftuar)
Pull request description:
No one seems to use this "feature", and at any rate the behavior of relaying transactions when they violate local policy is error-prone, if we ever consider changing the ban behavior of our software from one version to the next.
Defaulting this to off means that users who use -whitelist won't be unexpectedly surprised by this interaction. If anyone is still relying on this feature, it can still be explicitly turned on.
Tree-SHA512: 52650ad464a728d1648f496751e3f713077ea3a1de7278ed03531b2e8723e63cf2f6f41b56c98c0f73ffa22c36e01d9170b409ab452c737aca35b7ecd7a6b448
Diffstat (limited to 'doc/release-notes.md')
| -rw-r--r-- | doc/release-notes.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index c21a153a25..9e04f11635 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 ------------- |