What the developer wrote
Authored by ziggie
docs: update release notes
The previous release-note entry was not super accurrate so we
update it to reflect the change in more detail.
What changed, and why it matters
This commit only edits a release notes markdown file to make an earlier description more accurate. It does not change any code, configuration, or behavior of the LND software. There is no security issue in the commit itself.
No action needed. This is a documentation-only commit. If reviewing the underlying PR #10331 for security relevance, examine that commit or PR separately.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates the release notes entry for PR #10331. The old text described the change as ‘improved confirmation scaling for cooperative closes’ with a 1-confirmation minimum for small channels. The new text describes it as ‘added reorg protection for channel closes’ requiring 3-6 confirmations scaled by channel capacity. This is purely documentation wording; no code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +7 / −6
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 083f644..5a3968e 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -85,12 +85,13 @@
## Functional Enhancements
-* [Improved confirmation scaling for cooperative
- closes](https://github.com/lightningnetwork/lnd/pull/10331) to provide better
- reorg protection. Previously, cooperative closes required a minimum of 3
- confirmations. Now, small channels only require 1 confirmation, while larger
- channels scale proportionally using the standard 0.16 BTC threshold (matching
- funding confirmation scaling).
+* [Added reorg protection for channel
+ closes](https://github.com/lightningnetwork/lnd/pull/10331). Previously,
+ channel closes were considered final immediately on spend detection with no
+ confirmation waiting. Now, all channel closes require between 3 and 6
+ confirmations, scaled linearly with channel capacity up to the maximum
+ non-wumbo channel size (~0.168 BTC), with wumbo channels always requiring
+ 6 confirmations.
## RPC Additions
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.