What changed, and why it matters
This commit only adds a release note describing a bug fix that was already merged in a previous pull request. The actual code change happened elsewhere, so this commit itself does not introduce, fix, or alter any executable software. It is purely documentation.
No action needed for this commit. Review the actual fix in PR #10895 if a security assessment of that change is required.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/release-notes/release-notes-0.21.1.md to document PR #10895, which fixed on-chain forward interceptor settlement after incoming channel force closes. The commit adds a bullet describing held forwards being tracked as off-chain or on-chain entries, and advises Go callers of htlcswitch.InterceptedPacket to use the new Deadline field or AutoFailHeight(). No source code is changed.
Changed components
docs/release-notes/release-notes-0.21.1.mdInspect captured patch +10 / −0
diff --git a/docs/release-notes/release-notes-0.21.1.md b/docs/release-notes/release-notes-0.21.1.md
index 870c5f0..efb05cd 100644
--- a/docs/release-notes/release-notes-0.21.1.md
+++ b/docs/release-notes/release-notes-0.21.1.md
@@ -35,6 +35,15 @@
non-SRV record. Non-SRV records are now skipped, and an empty `LookupHost`
result for the shim no longer triggers an out-of-bounds index.
+- [Fixed on-chain forward interceptor
+ settlement](https://github.com/lightningnetwork/lnd/pull/10895) after the
+ incoming channel force closes. Held forwards are now tracked as off-chain or
+ on-chain entries, allowing an on-chain re-offer to replace the old off-chain
+ hold so settlement reaches the witness beacon. Go callers of the exported
+ `htlcswitch.InterceptedPacket` type should use the new `Deadline` field to
+ distinguish off-chain auto-fail heights from on-chain settlement deadlines,
+ or `AutoFailHeight()` if they only need the legacy flattened value.
+
# New Features
## Functional Enhancements
@@ -88,4 +97,5 @@ rejected, and must lower the value accordingly below the specified maximum.
# Contributors (Alphabetical Order)
+* Erick Cestari
* Ziggie
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.