What changed, and why it matters
This commit only adds a release note describing a previously merged feature. It does not change any code, configuration defaults, or security behavior. There is no security issue in this documentation update.
No action required. This is a routine documentation commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
Commit 36fb79ece5fb8f15690183e4b1e119e3f5ed561c is a documentation-only change to docs/release-notes/release-notes-0.21.0.md. It adds a bullet under ‘Functional Updates’ summarizing PR #9432, which introduced upfront-shutdown-address configuration support. The diff contains no executable code, no RPC/interface changes, and no security fixes or regressions.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +7 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 4fb4e12..e744685 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -37,6 +37,12 @@
# Improvements
## Functional Updates
+* [Added support](https://github.com/lightningnetwork/lnd/pull/9432) for the
+ `upfront-shutdown-address` configuration in `lnd.conf`, allowing users to
+ specify an address for cooperative channel closures where funds will be sent.
+ This applies to both funders and fundees, with the ability to override the
+ value during channel opening or acceptance.
+
## RPC Updates
## lncli Updates
@@ -65,3 +71,4 @@
# Contributors (Alphabetical Order)
* Elle Mouton
+* Nishant Bansal
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.