Add pending changelog for splice negotiation event changes
What changed, and why it matters
This commit only adds a pending changelog file describing upcoming API renames and additions for splicing-related events. It contains no code changes, no bug fixes, and no security-sensitive behavior changes.
No security action needed; treat as routine documentation/changelog maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single pending_changelog entry documenting four API updates: renaming Event::SplicePending to Event::SpliceNegotiated, renaming Event::SpliceFailed to Event::SpliceNegotiationFailed, adding reason and contribution fields to Event::SpliceNegotiationFailed, and adding feerate() and inputs() accessors on FundingContribution. These are public API surface changes, not runtime security fixes.
Changed components
pending_changelog/4514-splice-negotiation-failed.txtInspect captured patch +11 / −0
diff --git a/pending_changelog/4514-splice-negotiation-failed.txt b/pending_changelog/4514-splice-negotiation-failed.txt
new file mode 100644
index 0000000..809bf7c
--- /dev/null
+++ b/pending_changelog/4514-splice-negotiation-failed.txt
@@ -0,0 +1,11 @@
+# API Updates
+
+ * `Event::SplicePending` has been renamed to `Event::SpliceNegotiated`.
+
+ * `Event::SpliceFailed` has been renamed to `Event::SpliceNegotiationFailed`.
+
+ * `Event::SpliceNegotiationFailed` now includes a `reason` field
+ (`NegotiationFailureReason`) indicating why the negotiation round failed,
+ and a `contribution` field returning the `FundingContribution` for retry.
+
+ * `FundingContribution` now exposes `feerate()` and `inputs()` accessor methods.
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.