What changed, and why it matters
This commit only adds a line to the release notes document describing a new RPC feature. It does not change any program code, cryptographic logic, network behavior, or access controls. There is no security issue in the commit itself.
No security action needed. This is a routine documentation update.
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 documents PR #10666, which added a DeleteForwardingHistory RPC to the router sub-server. The note mentions a 1-hour cutoff safeguard. No code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index cb5fa1a..e111409 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -82,6 +82,12 @@
## RPC Additions
+* [Added `DeleteForwardingHistory`
+ RPC](https://github.com/lightningnetwork/lnd/pull/10666) to the router
+ sub-server, allowing operators to selectively purge old forwarding events from
+ the database. Deletion requires the target cutoff timestamp to be at least 1
+ hour in the past, preventing accidental removal of recent data.
+
* The `WaitingCloseChannel` response in `PendingChannels` now includes two
new fields via [#10509](https://github.com/lightningnetwork/lnd/pull/10509):
`blocks_til_close_confirmed`, showing the remaining confirmations until a
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.