channelmanager: upgrade best_block_updated log from trace to info
What the developer wrote
Authored by Alkamal01
channelmanager: upgrade best_block_updated log from trace to info
What changed, and why it matters
This commit simply changes one diagnostic log message from the lowest detail level ('trace') to a more visible level ('info'). It does not alter program behavior, fix a bug, or change any security-sensitive logic. It is a routine observability improvement with no security relevance.
No security action needed. Review as a normal logging-level change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is a one-line edit in lightning/src/ln/channelmanager.rs that switches log_trace! to log_info! for the ‘New best block’ message emitted when the channel manager processes a new best block. The arguments, formatting, and surrounding code are unchanged. There is no functional or security impact.
Changed components
lightning/src/ln/channelmanager.rs logging onlyInspect captured patch +1 / −1
diff --git a/lightning/src/ln/channelmanager.rs b/lightning/src/ln/channelmanager.rs
index a3c33b8..f6ec581 100644
--- a/lightning/src/ln/channelmanager.rs
+++ b/lightning/src/ln/channelmanager.rs
@@ -15999,7 +15999,7 @@ impl<
// See the docs for `ChannelManagerReadArgs` for more.
let block_hash = header.block_hash();
- log_trace!(self.logger, "New best block: {} at height {}", block_hash, height);
+ log_info!(self.logger, "New best block: {} at height {}", block_hash, height);
let _persistence_guard =
PersistenceNotifierGuard::optionally_notify_skipping_background_events(
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.