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

xpay: fix reported value of amount_sent_msat

Public commit record

What the developer wrote

Authored by Lagrang3

60/100 · Adequate
xpay: fix reported value of amount_sent_msat

Changelog-None

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit fixes a bookkeeping bug in Core Lightning's xpay plugin. Previously, when a payment was routed through the user's own node, the plugin incorrectly reported that the user had paid fees to themselves. The fix separates the amount actually injected into the network from the amount reported as sent, so self-routed payments no longer show a fake fee. This is a reporting/accounting issue, not a way for an attacker to steal funds.

Recommended action

No urgent security action required. This is a reporting correction. Operators relying on xpay's `amount_sent_msat` for accounting or fee analysis should upgrade to obtain accurate values for self-routed payments.

Security signals we found

01

Incorrect fee accounting in payment reporting

02

Self-payment overestimation of amount_sent_msat

03

Test expectation changed to reflect corrected reporting

Risk score

Why this scored 28/100

Our methodology →
Potential impact 8/30
Exploitability 0/25
Stealth signal 3/15
Affected reach 5/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.