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

lightningd: make notifications from plugins just like native ones.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
lightningd: make notifications from plugins just like native ones.

Rather than forcing them to wrap their parameters in a "payload"
sub-object, copy in params directly. We include the "origin" field
one level up, if they care.

The next patch restores compatibility for the one place we currently use
them, which is the pay plugin.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Deprecated: pyln-client: plugin custom notifications origins and payload (use parameters directly)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes how Core Lightning forwards notifications between plugins. Previously, plugin notifications wrapped their data in a 'payload' sub-object. Now the data is placed directly in 'params', matching how native notifications work. This is a deliberate API cleanup with a deprecation period, not a security fix. It could break older plugins that still expect the old 'payload' wrapping, but there is no direct evidence of a vulnerability being patched.

Recommended action

Treat as a routine API-change commit, not an emergency security patch. Operators and plugin authors should review custom plugins that subscribe to plugin-originated notifications and update parsing from 'payload' to direct parameters before the v26.09 removal. Monitor the follow-up commit referenced in the message for pay-plugin compatibility.

Security signals we found

01

API deprecation with backward-compatibility shim in channel_hint.c

02

Behavioral change in notification serialization could affect plugins relying on 'payload' field

03

No explicit security relevance stated by vendor

04

No CVE or advisory references present in commit or supplied materials

Risk score

Why this scored 21/100

Our methodology →
Potential impact 3/30
Exploitability 2/25
Stealth signal 2/15
Affected reach 4/15
Confidence 7/10
Evidence quality 3/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.