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

pyln-client: adapt for modern plugin notifications.

Public commit record

What the developer wrote

Authored by Rusty Russell

83/100 · Strong
pyln-client: adapt for modern plugin notifications.

For older lightningd, we copy field into the raw dict, for newer we recreate the old
"payload" member.

We do fix up the custom_notification test which set params to a string instead of a dict:
that's just weird!

We also change the hacky parsing to proper dict extraction.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Changed: pyln-client: plugin notifications parameters now exposed directly, not wrapped in `params` object.
✓ Specific, 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 updates the Python plugin client library (pyln-client) so it understands both old and new styles of plugin notification messages from the lightningd daemon. It adds backward/forward compatibility shims so plugins written for either format still receive their expected 'payload' and 'origin' fields. The changes are in the client library and its tests; there is no direct fix for an exploitable vulnerability.

Recommended action

No immediate security action required. Treat as a normal compatibility update. If you maintain a pyln-client-based plugin, verify notification parameter handling against the new direct-params style described in the changelog.

Security signals we found

01

No security-relevant keywords in commit title or message

02

No bounds/overflow, auth, crypto, or permission changes

03

Change is compatibility/deprecation handling in plugin RPC client

04

Test-only fix: custom notification params changed from string to dict

Risk score

Why this scored 19/100

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