diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2019-08-19 09:25:26 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2019-08-19 09:25:31 -0400 |
| commit | 1d74693e8a9670d449ebbf81eef563aafaa92283 (patch) | |
| tree | 05f1e2b103b9d3f1f4f7ffcf6be5d325ef28b173 /ci/test/00_setup_env_amd64_asan.sh | |
| parent | c79bf3277422c08ecb7305741358763f09d202ea (diff) | |
| parent | 20ea9ef6ce9228a5258b99eeeeb40e6dfae2299f (diff) | |
| download | bitcoin-1d74693e8a9670d449ebbf81eef563aafaa92283.tar.xz | |
Merge #16555: doc: mention whitelist is inbound, and applies to blocksonly
20ea9ef6ce9228a5258b99eeeeb40e6dfae2299f [doc] mention whitelist is inbound, and applies to blocksonly (Sjors Provoost)
Pull request description:
* `-whitelist` only impacts inbound nodes (see #9923). This is obvious in the context of allowing those nodes to connect to you, but there are additional whitelist features where this is less obvious, such as mempool relay behavior.
* `whitelistrelay` (on by default) explains that `-blocksonly` makes an exception for transactions from whitelisted nodes, but it wasn't documented (nor obvious imo) the other way around. See also https://github.com/bitcoin/bitcoin/pull/15984#issuecomment-490645552
Top commit has no ACKs.
Tree-SHA512: 03e363a5da5d81ad147d1c7e38bf11114df8bb89bdd66fb551520b25f810efa886ec6e649d3b435c4935e0ae4f39bb718bc7bb5778b9de6aa0b71e970a431af8
Diffstat (limited to 'ci/test/00_setup_env_amd64_asan.sh')
0 files changed, 0 insertions, 0 deletions