What the developer wrote
Authored by yyforyongyu
docs: clarify taproot channel open defaults
What changed, and why it matters
This commit only updates release notes documentation. It clarifies that users must explicitly request Taproot channel types and keep them private for now. There is no code change and no security fix or vulnerability introduced.
No security action needed; treat as routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A four-line addition to docs/release-notes/release-notes-0.21.0.md explains default behavior for opening Taproot channels in lnd 0.21.0: they are not opened by default, require an explicit –channel_type flag, and must remain private until announced Taproot channels are supported. The diff contains no functional changes.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +4 / −1
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 392fdbc..a4aaf44 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -133,7 +133,10 @@
`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.
+ and resynchronization paths. Taproot channels must be requested explicitly
+ with `lncli openchannel --channel_type=taproot-final` (or `taproot` for
+ staging), and must remain private until announced taproot channels are
+ supported.
* [Added taproot channel support for RBF cooperative
close](https://github.com/lightningnetwork/lnd/pull/10063). The new RBF-based
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.