docs: add taproot RBF coop close to 0.21.0 release notes
What the developer wrote
Authored by Olaoluwa Osuntokun
docs: add taproot RBF coop close to 0.21.0 release notes
What changed, and why it matters
This commit only updates the release notes document for version 0.21.0. It describes a new feature—taproot channel support for an RBF-based cooperative close protocol—but makes no code changes. There is no security issue in the commit itself.
No action needed; this is a documentation-only change. Review the actual implementation in PR #10063 if assessing the security of the RBF cooperative close feature.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single bullet to docs/release-notes/release-notes-0.21.0.md documenting PR #10063, which adds taproot channel support for the RBF cooperative close protocol. It mentions MuSig2 partial signatures, JIT nonce handling, and nonce invalidation across RBF rounds. No source code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +11 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index a57ca9e..35ecf6c 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -74,6 +74,17 @@
non-wumbo channel size (~0.168 BTC), with wumbo channels always requiring
6 confirmations.
+* [Added taproot channel support for RBF cooperative
+ close](https://github.com/lightningnetwork/lnd/pull/10063). The new RBF-based
+ cooperative close protocol (enabled with `--protocol.rbf-coop-close`) now
+ fully supports simple taproot channels. This includes MuSig2 partial signature
+ handling with the JIT (just-in-time) nonce pattern, where closer nonces are
+ bundled with signatures in `ClosingComplete` and closee nonces are rotated via
+ `NextCloseeNonce` in `ClosingSig` for each RBF iteration. The implementation
+ prevents nonce reuse across RBF rounds by storing the `MusigPartialSig` in the
+ protocol state machine and invalidating nonces after each signing round
+ completes.
+
## RPC Additions
* The `WaitingCloseChannel` response in `PendingChannels` now includes two
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.