AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 39 Bitcoin

Merge bitcoin/bitcoin#35919: p2p: cap maxconnections at 2,000 to reduce crash risk

Public commit record

What the developer wrote

Authored by merge-script

81/100 · Strong
Merge bitcoin/bitcoin#35919: p2p: cap maxconnections at 2,000 to reduce crash risk

b30f750de56c4e510f8af5a4dbba4e821b71a9b1 p2p: cap maxconnections at 2000 (Lőrinc)

Pull request description:

**Problem:** The orphanage can abort when more than 3,000 peers have orphan announcements.
The `-maxconnections` setting currently has no explicit upper bound.

**Fix:** Cap `-maxconnections` at 2,000 with a warning before reserving file descriptors, while retaining the default of 200.

ACKs for top commit:
instagibbs:
reACK https://github.com/bitcoin/bitcoin/pull/35919/commits/b30f750de56c4e510f8af5a4dbba4e821b71a9b1
optout21:
reACK b30f750de56c4e510f8af5a4dbba4e821b71a9b1
sedited:
ACK b30f750de56c4e510f8af5a4dbba4e821b71a9b1

Tree-SHA512: 06b892a67d9031f60427d04862fb0b96b30015c93904e544b4ec083c5713e56ab8b58c8747cb14b6bbd7ee52ca6a0d1ab5c4d9607789a19987bbda89a0689afd
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This update limits how many peer connections Bitcoin Core will allow a user to request. Previously, a user could set an extremely high number of connections, which could trigger a crash when the orphan transaction cache (used for unconfirmed transactions) was shared across too many peers. Now, values above 2,000 are automatically reduced to 2,000 with a warning. It is a hardening fix, not a remote exploit.

Recommended action

No urgent action required. Operators who previously set -maxconnections above 2,000 should note the new cap and warning. Review whether the cap adequately protects nodes with very large file-descriptor limits and consider monitoring logs for the new InitWarning.

Security signals we found

01

Crash risk reduction at very high peer counts

02

Configuration input validation and clamping

03

Static assertion linking connection caps to orphanage latency budget

04

New functional test for cap behavior and warning message

Risk score

Why this scored 39/100

Our methodology →
Potential impact 12/30
Exploitability 5/25
Stealth signal 4/15
Affected reach 6/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.