doc: Update docs that refer to -maxconnections
What the developer wrote
Authored by Martin Zumsande
doc: Update docs that refer to -maxconnections
What changed, and why it matters
This commit only updates two documentation files to reflect that the default value for the -maxconnections setting changed from 125 to 200. It does not change any code, configuration defaults, or network behavior. There is no security issue here.
No action required. This is a documentation-only change with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies doc/reduce-memory.md and doc/reduce-traffic.md to update the documented default for -maxconnections from 125 to 200 and adjusts the derived inbound-connection arithmetic (200 - 11 = 189). No source code, defaults, or logic are altered. This is a pure documentation synchronization commit.
Changed components
doc/reduce-memory.mddoc/reduce-traffic.mdInspect captured patch +4 / −3
diff --git a/doc/reduce-memory.md b/doc/reduce-memory.md
index 44d90bcf..a69bcb7d 100644
--- a/doc/reduce-memory.md
+++ b/doc/reduce-memory.md
@@ -33,7 +33,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
index 8926a836..315de214 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.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.