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

xpay: remove internal "disable_mpp" flag.

Public commit record

What the developer wrote

Authored by Rusty Russell

68/100 · Adequate
xpay: remove internal "disable_mpp" flag.

We already have `maxparts`: simply set that to 1 for the same effect.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This is a small internal cleanup in Core Lightning's xpay plugin. It removes a redundant 'disable_mpp' flag and instead uses the existing 'maxparts' setting (set to 1) to achieve the same effect of disabling multi-part payments. The behavior appears functionally equivalent.

Recommended action

No immediate action required. Reviewers may want to confirm that setting maxparts=1 provides equivalent routing behavior to the removed `auto.no_mpp_support` layer, particularly for invoices that do not advertise MPP support.

Security signals we found

01

Refactoring of payment routing logic

02

Removal of explicit MPP disabling layer ('auto.no_mpp_support')

03

Behavioral equivalence claim in commit message

Risk score

Why this scored 18/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/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.