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

askrene: all remove_small_channel_layer when maxparts=1.

Public commit record

What the developer wrote

Authored by Rusty Russell

65/100 · Adequate
askrene: all remove_small_channel_layer when maxparts=1.

We were doing it for "auto.no_mpp_support", but not maxparts=1.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This change adjusts how the Core Lightning routing plugin (askrene) decides to ignore very small payment channels. Previously it only removed small channels when the payer did not support multi-part payments. Now it also does so when the caller explicitly requests a single payment part (maxparts=1). The effect is to make single-part route searches faster and more reliable, but it could also change which routes are chosen or whether any route is found at all.

Recommended action

Review whether removing small channels for maxparts=1 can cause route failure or fee/liquidity disclosure changes that affect privacy or liveness. Treat as a normal code review item; no immediate security patch is indicated by the diff alone.

Security signals we found

01

Routing behavior change in payment pathfinding

02

Single-part payment path selection altered

03

No explicit bounds check or input validation added

Risk score

Why this scored 26/100

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