diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-07-11 10:22:44 +0200 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-07-11 10:23:09 +0200 |
| commit | ca055885c631de8ac0ffe24be6b02835dbcc039d (patch) | |
| tree | f7bd8fafc4473025ad17fc730fcee09884e14a50 /doc | |
| parent | 505b4eda55a6f1592500ec9c2b9dad9e4adf92a2 (diff) | |
| parent | fab558612278909df93bdf88f5727b04f13aef0f (diff) | |
| download | bitcoin-ca055885c631de8ac0ffe24be6b02835dbcc039d.tar.xz | |
Merge #19474: doc: Use precise permission flags where possible
fab558612278909df93bdf88f5727b04f13aef0f doc: Use precise permission flags where possible (MarcoFalke)
Pull request description:
Instead of mentioning the all-encompassing `-whitelist*` settings, change the docs to mention the exact permission flag that will influence the behaviour.
This is needed because in the future, the too-broad `-whitelist*` settings (they either include *all* permission flags or apply to *all* peers) might be deprecated to require the permission flags to be enumerated.
Alternatively, in the future there could be an RPC to set the net permission flags on an existing connection, in which case the `-whitelist*` terminology is of no help.
ACKs for top commit:
jnewbery:
reACK fab558612278909df93bdf88f5727b04f13aef0f
fjahr:
Code review ACK fab558612278909df93bdf88f5727b04f13aef0f
jonatack:
ACK fab558612278909df93bdf88f5727b04f13aef0f
Tree-SHA512: c7dea3e577d90103bb2b0ffab7b7c8640b388932a3a880f69e2b70747fc9213dc1f437085671fd54c902ec2a578458b8a2fae6dbe076642fb88efbf9fa9e679c
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/reduce-traffic.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/reduce-traffic.md b/doc/reduce-traffic.md index ea13dd5c27..86943b1f72 100644 --- a/doc/reduce-traffic.md +++ b/doc/reduce-traffic.md @@ -50,7 +50,7 @@ Be reminded of the effects of this setting. Doing so disables the automatic broadcasting of transactions from wallet. Not relaying other's transactions could hurt your privacy if used while a wallet is loaded or if you use the node to broadcast transactions. -- If a peer is whitelisted and "-whitelistforcerelay" is set to "1" (which will - also set "whitelistrelay" to "1"), we will still receive and relay their transactions. +- If a peer has the forcerelay permission, we will still receive and relay + their transactions. - It makes block propagation slower because compact block relay can only be used when transaction relay is enabled. |