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

topology: in deterministic mode, only return one best candidate for listincoming.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
topology: in deterministic mode, only return one best candidate for listincoming.

This ensures that bolt11/bolt12 selection of routehints/blinded paths is always the same.

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

What changed, and why it matters

This change makes a Lightning node return a single, predictable incoming channel when running in deterministic mode (used for reproducible testing and invoice route hints). Previously, multiple candidate channels could be returned in a non-deterministic order, which could cause the same invoice to produce different route hints across runs. The patch selects the highest-capacity channel as the one and only candidate. This is primarily a reliability/consistency fix; it does not appear to be a direct security vulnerability, but non-deterministic route hints could theoretically leak extra topology information or cause payment routing inconsistencies.

Recommended action

Treat as a normal code-quality/reliability patch. No urgent security action required. Reviewers may want to confirm that deterministic mode cannot be enabled in production configurations and that selecting a single highest-capacity channel does not degrade payment reliability for nodes with multiple usable incoming channels.

Security signals we found

01

Non-deterministic route hint selection could expose different subsets of a node's channels across invoice generations

02

Deterministic mode is typically test-only, limiting production exposure

03

No input validation or memory safety issues visible in the diff

04

No cryptographic or authorization changes

Risk score

Why this scored 26/100

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