docs/release-notes: add release note for production taproot channels
What the developer wrote
Authored by Olaoluwa Osuntokun
docs/release-notes: add release note for production taproot channels
What changed, and why it matters
This commit only adds a release note describing a new feature: production-ready Taproot payment channels. It contains no code changes, no bug fixes, and no security-related statements. There is nothing for an attacker to exploit.
No action required; this is a documentation-only release-note entry. Review the actual implementation PR #9985 separately if a security assessment of the Taproot channel feature is needed.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to docs/release-notes/release-notes-0.21.0.md. It describes PR #9985, which introduces final/simple Taproot channels using feature bits 80/81, optimized scripts (OP_CHECKSIGVERIFY), and map-based nonce encoding keyed by funding TXID. No source code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect 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 2015e06..754fedc 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -95,6 +95,16 @@
non-wumbo channel size (~0.168 BTC), with wumbo channels always requiring
6 confirmations.
+* [Added support for production (final) simple taproot
+ channels](https://github.com/lightningnetwork/lnd/pull/9985) using the
+ finalized taproot channel scripts with feature bits 80/81. Production taproot
+ channels use optimized scripts (`OP_CHECKSIGVERIFY` instead of `OP_CHECKSIG` +
+ `OP_DROP`) and a map-based nonce encoding in `channel_reestablish` and
+ `revoke_and_ack` keyed by funding TXID, laying the groundwork for splice
+ support. The nonce type is now auto-detected from the negotiated channel type
+ rather than peer feature bits, ensuring correct behavior across all recovery
+ and resynchronization paths.
+
* [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
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.