Fix 0.2 CHANGELOG to note that offers will break on downgrade
What changed, and why it matters
This commit is a documentation-only update to the 0.2 release CHANGELOG. It adds a note warning users that if they upgrade to LDK 0.2, create BOLT 12 offers, and then downgrade to an older LDK version, those offers will not be accepted. This is a compatibility/operational issue, not a security vulnerability, and no code behavior is changed.
No immediate security action required. Users planning to downgrade from LDK 0.2 should be aware that BOLT 12 offers created on 0.2 will not be accepted by older versions. If downgrade compatibility is needed, avoid creating offers on 0.2 or regenerate them after downgrade.
Security signals we found
No code change—documentation-only changelog edit
Relates to BOLT 12 offer authentication key compatibility
Could affect payment/receive workflows after downgrade, but is a known operational limitation rather than an exploit
No mention of vulnerability, CVE, attacker, or exploit in commit or diff
Evidence from the diff
The commit updates CHANGELOG.md to disclose a backward-compatibility break: LDK 0.2 changed the key used to authenticate newly created BOLT 12 offers, so offers created on 0.2 are rejected by prior LDK versions after a downgrade. The change is purely informational; no logic is patched. The underlying behavior was already present in the released 0.2 code.
Changed components
CHANGELOG.mdBOLT 12 Offers compatibility noteInspect captured patch +2 / −0
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6e83ef2..12f926c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -201,6 +201,8 @@
generated for inclusion in BOLT 12 `Offer`s will no longer be accepted. As
most blinded message paths are ephemeral, this should only invalidate issued
BOLT 12 `Refund`s in practice (#3917).
+ * Blinded message paths included in BOLT 12 `Offer`s generated by LDK 0.2 will
+ not be accepted by prior versions of LDK after downgrade (#3917).
* Once a channel has been spliced, LDK can no longer be downgraded.
`UserConfig::reject_inbound_splices` can be set to block inbound ones (#4150)
* Downgrading after setting `UserConfig::enable_htlc_hold` is not supported
Why this scored 18/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.