docs: add release note for SIMPLE_TAPROOT_FINAL follow-ups
What the developer wrote
Authored by George Tsagkarelis
docs: add release note for SIMPLE_TAPROOT_FINAL follow-ups
See https://github.com/lightningnetwork/lnd/pull/10763.
What changed, and why it matters
This commit only adds a release-note entry describing two previously-merged fixes for taproot Lightning channels. It does not change any code. The described fixes correct how a channel-acceptor RPC reports the commitment type for final taproot channels, and prevent an RBF cooperative-close feature from being incorrectly enabled on taproot overlay channels. These are follow-up corrections to earlier production taproot work, not a new security patch in this commit.
No immediate action is required for this documentation commit. Review PR #10763 directly if assessing the actual security or correctness impact of the two described fixes.
Security signals we found
Release note references prior fixes for taproot channel commitment-type reporting and RBF cooperative-close auto-enable
No code changes in this commit; security relevance is indirect and retrospective
Potential for incorrect commitment-type reporting and premature RBF close enablement on overlay channels is described as resolved in the referenced PR
Evidence from the diff
Commit 33f623c is a documentation-only change to docs/release-notes/release-notes-0.21.0.md. It summarizes PR #10763, which fixed two follow-ups to SIMPLE_TAPROOT_FINAL support: (1) the RPC channel acceptor switch now maps SIMPLE_TAPROOT_FINAL with all scid-alias/zero-conf combinations so external acceptor clients receive the correct commitment type instead of UNKNOWN_COMMITMENT_TYPE; (2) taproot RBF cooperative-close auto-enable is restricted to skip taproot-overlay channels because the RBF close state machine does not yet propagate the AuxCloser hook needed for aux-aware close transactions. No source code is modified in this commit.
Changed components
docs/release-notes/release-notes-0.21.0.mdRPC channel acceptor (referenced, not modified)Taproot RBF cooperative-close logic (referenced, not modified)Inspect captured patch +10 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index ea6b0a3..23b93a0 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -78,6 +78,16 @@
subscriptions and the hodl queue, preventing orphaned subscriptions from
blocking invoice resolution.
+* [Fixed two follow-ups to the production taproot channels
+ work](https://github.com/lightningnetwork/lnd/pull/10763). The RPC channel
+ acceptor switch now maps `SIMPLE_TAPROOT_FINAL` (with every combination of
+ the `scid-alias` / `zero-conf` modifiers) so final-taproot opens are
+ reported to external acceptor clients with the correct commitment type
+ instead of `UNKNOWN_COMMITMENT_TYPE`. The taproot RBF cooperative-close
+ auto-enable is also narrowed to skip taproot-overlay channels, since the
+ RBF close state machine does not yet thread through the `AuxCloser` hook
+ that overlay channels rely on to build aux-aware close transactions.
+
# New Features
- [Basic Support](https://github.com/lightningnetwork/lnd/pull/9868) for onion
Why this scored 22/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.