docs: add release note for coop close limbo fix
What changed, and why it matters
This commit only adds a release note describing a previously fixed bug in LND's cooperative channel closing flow. The actual code fix happened in an earlier pull request. The bug caused channel status to be marked as 'cooperatively broadcast' before any actual closing transaction existed, which could make channels temporarily disappear from normal listings or leave a waiting-close record with an empty transaction field. The release note confirms the fix but does not itself change any code.
Treat this commit as documentation-only. Review PR #10782 and the actual code fix it references to assess whether the underlying bug has security implications, and verify the fix is included in the release being deployed.
Security signals we found
Release note references a bug fix in cooperative close state management
Premature channel-status flag could lead to inconsistent channel visibility during close
No code change in this commit; security relevance is second-hand from release note
Evidence from the diff
The diff adds documentation to docs/release-notes/release-notes-0.22.0.md for PR #10782. The described bug involved setting ChanStatusCoopBroadcasted prematurely during cooperative close negotiation, before the closing transaction was actually broadcast. The fix ensures channels in shutdown negotiation remain visible in ListChannels (as inactive) until the close transaction is broadcast, and that WaitingCloseChannel.ClosingTx is never empty. No source code is modified in this commit.
Changed components
docs/release-notes/release-notes-0.22.0.mdLND cooperative channel close logic (described, not modified)Inspect captured patch +8 / −0
diff --git a/docs/release-notes/release-notes-0.22.0.md b/docs/release-notes/release-notes-0.22.0.md
index fb31bad..55b0e43 100644
--- a/docs/release-notes/release-notes-0.22.0.md
+++ b/docs/release-notes/release-notes-0.22.0.md
@@ -26,6 +26,14 @@
[clarifies](https://github.com/lightningnetwork/lnd/issues/10568) the ZMQ
port-mismatch warnings so they no longer suggest that the connection failed.
+* [Fixed a bug](https://github.com/lightningnetwork/lnd/pull/10782)
+ that could be encountered during co-op closes whereby
+ `ChanStatusCoopBroadcasted` was set before a close transaction
+ actually existed. As a side effect, channels in shutdown
+ negotiation now remain in `ListChannels` (as inactive) until
+ the close transaction is actually broadcast, and
+ `WaitingCloseChannel.ClosingTx` is never empty.
+
# New Features
## Functional Enhancements
Why this scored 30/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.