What the developer wrote
Authored by ziggie
docs: add release-notes for LND 20.1
What changed, and why it matters
This commit only adds documentation text to the release notes for an upcoming LND version. It describes a previously merged feature that improves fee estimation for Lightning Service Provider routes. There is no code change, no bug fix, and no security-related content in the diff.
No security action needed. Treat as routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff appends a single bullet to docs/release-notes/release-notes-0.20.1.md describing PR #10396, which added an LSP-detection heuristic to the EstimateRouteFee RPC. The change is purely informational release-note text; no source code, configuration, or protocol behavior is modified.
Changed components
docs/release-notes/release-notes-0.20.1.mdInspect captured patch +8 / −0
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 59370ea..d8562a8 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -45,6 +45,14 @@
## RPC Updates
+ * The `EstimateRouteFee` RPC now implements an [LSP detection
+ heuristic](https://github.com/lightningnetwork/lnd/pull/10396) that probes up
+ to 3 unique Lightning Service Providers when route hints indicate an LSP
+ setup. The implementation returns worst-case (most expensive) fee estimates
+ for conservative budgeting and includes griefing protection by limiting the
+ number of probed LSPs. It enhances the previous LSP design by being more
+ generic and more flexible.
+
## lncli Updates
## Breaking Changes
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.