doc: Update docs that refer to -maxconnections

mzumsande · Sep 17, 2024 · dd2721f · dd2721f
1 parent d5fd2af
commit dd2721f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git 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=<n>` - the maximum number of connections, which defaults to 125. Each active connection takes up some
+- `-maxconnections=<n>` - 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
@@ -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.