Add pending changelog entry for PR 4687
What the developer wrote
Authored by Jeffrey Czyz
Add pending changelog entry for PR 4687
What changed, and why it matters
This commit only adds a changelog text file describing a previously merged feature (PR 4687). It does not change any source code, build scripts, tests, or documentation that affects program behavior. There is no security-relevant change to assess.
No action required. This is a documentation-only changelog entry with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff creates a single pending_changelog file documenting an API addition: a new splice_details field on ChannelDetails and a backwards-compatibility note about splicing channels upgraded from older LDK versions. No code, configuration, or cryptographic logic is modified.
Changed components
pending_changelog/4687-pending-splice-details.txtInspect captured patch +18 / −0
diff --git a/pending_changelog/4687-pending-splice-details.txt b/pending_changelog/4687-pending-splice-details.txt
new file mode 100644
index 0000000..7b1ea2c
--- /dev/null
+++ b/pending_changelog/4687-pending-splice-details.txt
@@ -0,0 +1,18 @@
+# API Updates
+
+ * `ChannelDetails` now has a `splice_details` field
+ (`Option<SpliceDetails>`) reporting any pending splice attempts on a channel.
+ Each splice or RBF round is reported as a `SpliceCandidateDetails` in
+ `SpliceDetails::candidates`, with the stage it has reached given by
+ `SpliceCandidateStatus` (spanning a contribution committed via
+ `ChannelManager::funding_contributed` but not yet negotiating, the in-flight
+ negotiation, and a negotiated candidate awaiting confirmation). `SpliceDetails`
+ also reports the confirmed candidate's progress (`ConfirmedSpliceCandidate`)
+ and the txid of any `splice_locked` received from the counterparty.
+
+# Backwards Compatibility
+
+ * A pending splice negotiated before upgrading from a prior LDK version (e.g.
+ 0.2) cannot be RBF'd, as older versions persisted neither its feerate nor our
+ contribution. Splicing such a channel instead queues a new splice that begins
+ once the inherited splice locks.
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.