docs: add release notes for offline peer uptime fix
What the developer wrote
Authored by Erick Cestari
docs: add release notes for offline peer uptime fix
What changed, and why it matters
This commit only adds a release note describing a previously fixed bug. The actual code fix is in a separate pull request. The bug caused LND's ListChannels report to incorrectly show 100% uptime for peers that were actually offline, because the channel fitness store wrongly assumed peers were online when it first started tracking them. The release note explains uptime is now seeded from the peer's real connection state. There is no new code change here, so this commit itself does not introduce or fix a security vulnerability.
No security action required for this documentation commit. Review PR #10890 separately if assessing the actual code fix. Consider whether inaccurate uptime reporting could mislead monitoring or automation that relies on ListChannels uptime, but treat that as operational risk rather than a direct security vulnerability.
Security signals we found
No executable code changed
Documentation-only release note
Referenced bug is a reporting/data accuracy issue, not a security flaw
No mention of CVE, security researcher, or security advisory in commit or references
Evidence from the diff
Commit 09f38dac is a documentation-only change adding a bullet to docs/release-notes/release-notes-0.22.0.md. It references PR #10890, which fixed a logic error in the channel fitness store: the store initialized peer uptime as online by default, even though channels are loaded at startup before peer connectivity is known. The fix seeds uptime from the actual peer connection state. This commit does not modify any executable code, RPC behavior, or cryptographic logic. The underlying issue is a data-quality/reporting bug, not a memory-safety, authentication, authorization, or funds-loss vulnerability.
Changed components
docs/release-notes/release-notes-0.22.0.mdInspect captured patch +7 / −0
diff --git a/docs/release-notes/release-notes-0.22.0.md b/docs/release-notes/release-notes-0.22.0.md
index 45e7605..22ec010 100644
--- a/docs/release-notes/release-notes-0.22.0.md
+++ b/docs/release-notes/release-notes-0.22.0.md
@@ -34,6 +34,13 @@
the close transaction is actually broadcast, and
`WaitingCloseChannel.ClosingTx` is never empty.
+* [Fixed a bug](https://github.com/lightningnetwork/lnd/pull/10890)
+ where `ListChannels` reported 100% `uptime` for channels whose peer
+ was offline. The channel fitness store assumed a peer was online when
+ it first started tracking it, but channels are loaded on startup
+ regardless of peer connectivity. Uptime is now seeded from the peer's
+ actual connection state.
+
# New Features
## Functional Enhancements
Why this scored 18/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.