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

Split MPP by maximizing expected delivered amount (#2792)

Public commit record

What the developer wrote

Authored by Thomas HUET

73/100 · Adequate
Split MPP by maximizing expected delivered amount (#2792)

As suggested by @renepickhardt in https://github.com/ACINQ/eclair/pull/2785
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit changes how the Eclair Lightning node splits a single large payment across multiple routes. It adds a new optional strategy that tries to maximize the expected amount that actually gets delivered, and refactors the existing random and full-capacity strategies. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a routing/performance improvement.

Recommended action

Treat as a normal feature/refactor review. Verify that the new `max-expected-amount` strategy and the rewritten `split` loop preserve fee and capacity invariants, do not over-allocate capacity, and handle edge cases (zero capacity, rounding, blinded hops) safely. Run the updated test suite, especially `RouteCalculationSpec` and `RouterSpec`.

Security signals we found

01

Refactors payment-route splitting logic, which affects how funds are allocated across HTLCs

02

Changes capacity-bounding logic in `maxEdgeAmount` (previously `maxHtlcAmount`)

03

Adjusts `updateUsedCapacity` to account for blinded final-hop fees and dummy channel IDs

04

Removes the deterministic fallback when randomized route finding fails

05

No mention of vulnerability, CVE, bug bounty, or security issue in commit message or release notes

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.