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

init: make inbound tx relay percentage configurable

Public commit record

What the developer wrote

Authored by Amiti Uttarwar

85/100 · Strong
init: make inbound tx relay percentage configurable

Permit users to change the amount of inbounds that are permitted to relay
transactions. This is particularly relevant to ensure that superusers that are
not concerned with resource usage are not artificially restricted from offering
many transaction relay slots to the network.

Co-authored-by: Martin Zumsande <mzumsande@gmail.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit adds a new user-configurable setting called -inboundrelaypercent to Bitcoin Core. It lets node operators choose what percentage of incoming peer connections are allowed to relay transactions, instead of being hard-coded to 50%. The change itself is a feature/configuration tweak, not a fix for an active security bug. It could indirectly affect resource usage or network behavior if set unwisely, but it does not introduce a clear vulnerability.

Recommended action

No immediate security action required. Reviewers may want to confirm that edge cases (e.g., very low -maxconnections combined with high -inboundrelaypercent) behave sensibly and that the clamping prevents negative or >100 values as intended.

Security signals we found

01

New configuration option affecting P2P connection slot allocation

02

Input clamped to 0-100 via std::clamp, preventing out-of-range values

03

No validation, cryptography, or consensus code modified

04

No privilege escalation, remote code execution, or denial-of-service primitive introduced by the diff

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 2/25
Stealth signal 1/15
Affected reach 3/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.