Add pending_changelog for async send
What changed, and why it matters
This commit only adds a pending changelog note warning that downgrading LDK after enabling a new experimental feature (`UserConfig::enable_htlc_hold`) can cause deserialization failures or HTLC timeouts. There is no code change, no vulnerability fix, and no security defect introduced in this commit.
No security action required for this commit. Treat as routine documentation. Review the referenced prior commits (#4045, #4046) separately if assessing the async-send feature's security.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff creates a single pending-changelog file describing a backwards-compatibility hazard related to the new async send / HTLC-hold feature. It documents that older LDK versions cannot deserialize ChannelManager state written after enable_htlc_hold is set, and that held HTLCs may time out if downgraded. This is a documentation-only commit; no executable code is modified.
Changed components
pending_changelog/4045-sender-lsp.txtInspect captured patch +4 / −0
diff --git a/pending_changelog/4045-sender-lsp.txt b/pending_changelog/4045-sender-lsp.txt
new file mode 100644
index 0000000..fa4243b
--- /dev/null
+++ b/pending_changelog/4045-sender-lsp.txt
@@ -0,0 +1,4 @@
+## Backwards Compat
+
+* Downgrading to prior versions of LDK after setting `UserConfig::enable_htlc_hold` may cause
+ `ChannelManager` deserialization to fail or HTLCs to time out (#4045, #4046)
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.