rm 'received orphan channnel' log line (too verbose)
What the developer wrote
Authored by ThomasV
rm 'received orphan channnel' log line (too verbose)
What changed, and why it matters
This commit simply removes one debug log message that was considered too noisy. It does not change any program logic, data handling, or security behavior. There is no security issue here.
No action needed. This is a benign logging cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch deletes a single self.logger.debug() call in electrum/lnpeer.py that logged when an orphan channel_update gossip message was received. The surrounding code that stores orphan updates and limits the cache to 25 entries is unchanged. No functional, protocol, or security behavior is modified.
Changed components
electrum/lnpeer.pyInspect captured patch +0 / −1
diff --git a/electrum/lnpeer.py b/electrum/lnpeer.py
index fabe139..214a5d2 100644
--- a/electrum/lnpeer.py
+++ b/electrum/lnpeer.py
@@ -495,7 +495,6 @@ class Peer(Logger, EventListener):
# NOTE: The definition of gossip_queries changed
# https://github.com/lightning/bolts/commit/fce8bab931674a81a9ea895c9e9162e559e48a65
short_channel_id = ShortChannelID(payload['short_channel_id'])
- self.logger.debug(f'received orphan channel update {short_channel_id}')
self.orphan_channel_updates[short_channel_id] = payload
while len(self.orphan_channel_updates) > 25:
self.orphan_channel_updates.popitem(last=False)
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.