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

chainreg: clarify zmq port-mismatch warnings

Public commit record

What the developer wrote

Authored by Boris Nagaev

86/100 · Strong
chainreg: clarify zmq port-mismatch warnings

The previous warning text ("unable to subscribe to zmq ... events") suggested
that lnd failed to create the ZMQ connection, when in reality it only means the
configured port differs from what bitcoind reports via getzmqnotifications.
Reword both messages to say "port mismatch" and tell to verify the port.

Fixes https://github.com/lightningnetwork/lnd/issues/10568
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit only rewords two warning log messages in LND's chain registry. It changes the text from saying 'unable to subscribe to zmq ... events' to saying 'zmq ... port mismatch' when LND's configured ZMQ port differs from what the connected bitcoind reports. There is no code behavior change, no security fix, and no vulnerability addressed.

Recommended action

No security action required. This is a logging/UX clarification only. Operators may benefit from the clearer warning if they misconfigure ZMQ ports, but the change does not alter security posture.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/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.