docs: move coop close confirmation scaling note to 0.21.0
What changed, and why it matters
This commit only moves text between two release note documents. It removes two entries from the 0.20.1 release notes and adds the same entries to the 0.21.0 release notes, because the related code change actually shipped in version 0.21.0 rather than 0.20.1. No program code was changed, so there is no direct security impact from this commit itself.
No security action needed for this documentation-only commit. If reviewing the referenced PR #10331 separately, assess the confirmation-scaling and MinCLTVDelta changes directly.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only relocation of release notes for PR #10331. It transfers the ‘Improved confirmation scaling for cooperative closes’ and ‘Increased MinCLTVDelta from 18 to 24’ notes from docs/release-notes/release-notes-0.20.1.md to docs/release-notes/release-notes-0.21.0.md. The underlying code changes referenced by the notes are not part of this commit and are not reviewed here.
Changed components
docs/release-notes/release-notes-0.20.1.mddocs/release-notes/release-notes-0.21.0.mdInspect captured patch +16 / −16
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 2d40781..81b9ed3 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -87,13 +87,6 @@
ensures dependencies are properly freed and logs the panic trace for
debugging.
-* [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).
-
## RPC Updates
* The `EstimateRouteFee` RPC now implements an [LSP detection
@@ -108,15 +101,6 @@
## Breaking Changes
-* [Increased MinCLTVDelta from 18 to
- 24](https://github.com/lightningnetwork/lnd/pull/10331) to provide a larger
- safety margin above the `DefaultFinalCltvRejectDelta` (19 blocks). This
- affects users who create invoices with custom `cltv_expiry_delta` values
- between 18-23, which will now require a minimum of 24. The default value of
- 80 blocks for invoice creation remains unchanged, so most users will not be
- affected. Existing invoices created before the upgrade will continue to work
- normally.
-
## Performance Improvements
* [Added new Postgres configuration
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index f4c0155..083f644 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -85,6 +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).
+
## RPC Additions
* [Added support for coordinator-based MuSig2 signing
@@ -150,6 +157,15 @@
## Breaking Changes
+* [Increased MinCLTVDelta from 18 to
+ 24](https://github.com/lightningnetwork/lnd/pull/10331) to provide a larger
+ safety margin above the `DefaultFinalCltvRejectDelta` (19 blocks). This
+ affects users who create invoices with custom `cltv_expiry_delta` values
+ between 18-23, which will now require a minimum of 24. The default value of
+ 80 blocks for invoice creation remains unchanged, so most users will not be
+ affected. Existing invoices created before the upgrade will continue to work
+ normally.
+
* The [`GetDebugInfo`](https://github.com/lightningnetwork/lnd/pull/10613) RPC
no longer returns log file content by default. Clients that rely on the `log`
field must now explicitly set `include_log` to `true` in the request. The
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.