Merge bitcoin/bitcoin#29052: doc/reduce-traffic: update/clarify max outbound connection count

d58f89d355 doc: update/clarify max outbound connection count (Marnix)

Pull request description:

  closes https://github.com/bitcoin/bitcoin/issues/29046

ACKs for top commit:
  amitiuttarwar:
    ACK d58f89d355
  brunoerg:
    ACK d58f89d355

Tree-SHA512: 4f6e8596ceea0b655338b3fc90a465e319d81e2a006f22a98cd9acada9316e7eb2340e2f66b1b4dde4e63ae94f57efddec50478715608e1be3212b8e2d1c3a1a
This commit is contained in:
fanquake 2023-12-12 11:04:29 +00:00
commit 7a283836eb
No known key found for this signature in database
GPG key ID: 2EEB9F5CC09526C1

View file

@ -3,10 +3,10 @@ Reduce Traffic
Some node operators need to deal with bandwidth caps imposed by their ISPs.
By default, Bitcoin Core allows up to 125 connections to different peers, 10 of
which are outbound. You can therefore, have at most 115 inbound connections.
Of the 10 outbound peers, there can be 8 full-relay connections and 2
block-relay-only ones.
By default, Bitcoin Core allows up to 125 connections to different peers, 11 of
which are outbound. You can therefore, have at most 114 inbound connections.
Of the 11 outbound peers, there can be 8 full-relay connections, 2
block-relay-only ones and occasionally 1 short-lived feeler or an extra block-relay-only connection.
The default settings can result in relatively significant traffic consumption.
@ -28,7 +28,7 @@ calculating the target.
## 2. Disable "listening" (`-listen=0`)
Disabling listening will result in fewer nodes connected (remember the maximum of 10
Disabling listening will result in fewer nodes connected (remember the maximum of 11
outbound peers). Fewer nodes will result in less traffic usage as you are relaying
blocks and transactions to fewer nodes.