diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-07-21 16:04:31 +0200 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-07-21 16:04:33 +0200 |
| commit | 2c0c3f8e8ca6c64234b1861583f55da2bb385446 (patch) | |
| tree | 49e59cf45083d42c4a324a05b003b5695c5877aa /src/sync.cpp | |
| parent | edfeaf6836f1fcaacf1445001e1f58e1d09087ba (diff) | |
| parent | ec4c6a17e82a6726d95075b43ebd2525c50b37cd (diff) | |
Merge #19217: p2p: disambiguate block-relay-only variable names from blocksonly variables
ec4c6a17e82a6726d95075b43ebd2525c50b37cd scripted-diff: replace MAX_BLOCKS_ONLY_CONNECTIONS with MAX_BLOCK_RELAY_ONLY_CONNECTIONS (glowang)
Pull request description:
We have two different concepts that have similar names: `-blocksonly` and `block-relay-only`, and the similarity of names could lead to confusion. `-blocksonly` disables all local receiving & relaying of transactions (with a few exceptions), while `block-relay-only`means that bitcoind will make 2 additional outbound connections that are only used for block relay.
In net.h and init.cpp, `MAX_BLOCKS_ONLY_CONNECTIONS` is used to represent the maximum number of `block-relay-only` outbound peers, which is 2. But this name sounds ambiguous, and I proposed a better name, `MAX_BLOCK_RELAY_ONLY_CONNECTION`.
ACKs for top commit:
jnewbery:
ACK ec4c6a17e82a6726d95075b43ebd2525c50b37cd
Tree-SHA512: cfa592a7ff936f14d10cfc1e926a51b82bc0feaf104885a41ca8111b906cb3d1ec5536bab143a3cfca70aa49e9575c6995941eb6d3d7f4018d4535712342f155
Diffstat (limited to 'src/sync.cpp')
0 files changed, 0 insertions, 0 deletions