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

net: move `privatebroadcast` logs to debug category

Public commit record

What the developer wrote

Authored by Lőrinc

73/100 · Adequate
net: move `privatebroadcast` logs to debug category

Private broadcast is a privacy feature, and users may share `debug.log` with support.
Unconditional log messages that mention private broadcast and/or include (w)txids can leak which transactions a user originated.

Move private broadcast event logging from `LogInfo()` to `LogDebug(BCLog::PRIVBROADCAST, ...)` so it is only emitted when debug logging is enabled, and drop the hardcoded "[privatebroadcast]" prefixes.
Keep warnings at the default log level without (w)txids, detailed context remains available under `-debug=privatebroadcast`.

Co-authored-by: Vasil Dimov <vd@FreeBSD.org>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This change is a privacy hardening patch for Bitcoin Core's 'private broadcast' feature, which lets users send transactions over anonymity networks like Tor or I2P. Previously, routine log messages about private broadcasts—including transaction identifiers and peer details—were written to the default debug.log file. Because users often share their logs for troubleshooting, this could accidentally reveal which transactions they created. The patch moves those detailed messages behind a special debug logging category, so they only appear when a user explicitly enables it. Warnings stay visible but no longer include sensitive identifiers.

Recommended action

No urgent action required. This is a defensive privacy improvement. Users and support workflows benefit from reduced accidental information disclosure in shared debug.log files. Operators who need detailed private broadcast diagnostics can enable -debug=privatebroadcast.

Security signals we found

01

Privacy leak mitigation: default logs no longer record private broadcast activity or transaction identifiers

02

Information disclosure reduction: txid/wtxid and peer details moved behind opt-in debug category

03

No functional change to transaction relay, disconnection logic, or private broadcast behavior

04

Warning retained at default level but sanitized of feature name and transaction identifiers

Risk score

Why this scored 49/100

Our methodology →
Potential impact 8/30
Exploitability 5/25
Stealth signal 10/15
Affected reach 12/15
Confidence 9/10
Evidence quality 5/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.