AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 29 Bitcoin

lightningd: remove deprecations due in v26.12

Public commit record

What the developer wrote

Authored by daywalker90

78/100 · Adequate
lightningd: remove deprecations due in v26.12

These were deprecated in v25.05 or v25.09 and last supported in v26.06
or v26.09:

- `coin_movement` notification: `tags`, `txid`, `utxo_txid` and `vout`.
- `channel_state_changed` notification: `short_channel_id` was `null`
when unconfirmed. It is now omitted.
- Plugin notifications: the legacy `payload` object and flat unwrapped fields.
- `pay_notifications.raw_fields`: `channel_hint_update`, `pay_failure`
and `pay_success` already wrap their members in an object of the same
name.
- `wait.details`: the subsystem-specific object is used instead.

The shared coin movement serializer no longer takes the legacy flags.
The Python plugin client no longer recreates `payload` for old plugins.
The Rust plugin client sends custom notifications in the modern shape
only, without the deprecated flat copy of the fields.

The test harness still skips `channel_state_changed` when `message` is
`null`: it is deprecated since v25.12 and still supported until v26.12,
unlike the removed `short_channel_id` null.

Changelog-Removed: Plugins: `coin_movement` notification `tags`, `txid`, `utxo_txid` and `vout` fields (use `primary_tag`, `extra_tags`, `spending_txid` and `utxo`).
Changelog-Removed: Plugins: `channel_state_changed` notification omits `short_channel_id` when the channel is unconfirmed, instead of `null`.
Changelog-Removed: Plugins: notifications no longer include the legacy `payload` object or flat unwrapped fields; use the object named after the method instead.
Changelog-Removed: JSON-RPC: `wait` no longer returns the `details` object for `invoices`, `forwards` and `sendpays`; use the subsystem-specific object instead.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit removes old, previously-announced deprecated API fields and shapes from Core Lightning. It is a planned cleanup, not a security fix. Plugins or clients that still relied on the old fields will break or need to be updated, but there is no new vulnerability introduced.

Recommended action

Treat as a normal API-cleanup commit. Operators and plugin authors should verify their integrations no longer depend on the removed deprecated fields. No urgent security patch is required.

Security signals we found

01

Removal of deprecated API surface reduces attack surface and maintenance burden

02

No new memory safety, cryptographic, or authorization issue visible in diff

03

Changes are cleanup of previously announced deprecations with explicit version lifetimes

04

Potential compatibility breakage for downstream plugins/clients still using removed fields

Risk score

Why this scored 29/100

Our methodology →
Potential impact 5/30
Exploitability 0/25
Stealth signal 2/15
Affected reach 8/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.