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

multi: add omit_hops option to ListPayments RPC

Public commit record

What the developer wrote

Authored by ziggie

68/100 · Adequate
multi: add omit_hops option to ListPayments RPC

Add a new omit_hops field to ListPaymentsRequest that allows clients
to skip loading hop-level route data for HTLC attempts, reducing both
query cost and response size. When set, the route is returned with
only route-level fields (TotalTimeLock, TotalAmount, SourcePubKey)
and no individual hop data or hop-level custom records.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new optional flag called omit_hops to the ListPayments RPC in the LND Lightning node. When enabled, the node skips loading detailed per-hop route information for each payment attempt, returning only summary route fields. This is a performance and data-reduction feature, not a security fix or vulnerability. There is no indication in the commit that it addresses a security issue.

Recommended action

No security action required. Review as a normal feature addition. Operators may choose to use omit_hops when large payment histories cause slow ListPayments responses.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 19/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 9/10
Evidence quality 5/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.