From dd2721f7ad410eb15940157eeb771bffbeb5d46a Mon Sep 17 00:00:00 2001 From: Martin Zumsande Date: Mon, 5 Aug 2024 13:57:12 -0400 Subject: [PATCH] doc: Update docs that refer to -maxconnections --- doc/reduce-memory.md | 2 +- doc/reduce-traffic.md | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/reduce-memory.md b/doc/reduce-memory.md index 2710797ef3abb..c69f4c4d0cc36 100644 --- a/doc/reduce-memory.md +++ b/doc/reduce-memory.md @@ -24,7 +24,7 @@ The size of some in-memory caches can be reduced. As caches trade off memory usa ## Number of peers -- `-maxconnections=` - the maximum number of connections, which defaults to 125. Each active connection takes up some +- `-maxconnections=` - the maximum number of connections, which defaults to 200. Each active connection takes up some memory. This option applies only if inbound connections are enabled; otherwise, the number of connections will not be more than 11. Of the 11 outbound peers, there can be 8 full-relay connections, 2 block-relay-only ones, and occasionally 1 short-lived feeler or extra outbound block-relay-only connection. diff --git a/doc/reduce-traffic.md b/doc/reduce-traffic.md index 8926a8361aa3e..315de21450595 100644 --- a/doc/reduce-traffic.md +++ b/doc/reduce-traffic.md @@ -3,8 +3,9 @@ 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, 11 of -which are outbound. You can therefore, have at most 114 inbound connections. +By default, Bitcoin Core allows up to 200 connections to different peers, 11 of +which are outbound. You can therefore, have at most 189 inbound connections, half of +which can only be taken up by low-traffic block-relay-only peers. 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.