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

routerrpc: remove deprecated outgoing_chan_id field handling

Public commit record

What the developer wrote

Authored by Erick Cestari

73/100 · Adequate
routerrpc: remove deprecated outgoing_chan_id field handling

Remove the compatibility fallback in QueryRoutes and ExtractPaymentIntent
that accepted the deprecated single outgoing_chan_id field alongside the
replacement outgoing_chan_ids. Callers must now use outgoing_chan_ids.

Update TestQueryRoutes and TestExtractPaymentIntent accordingly.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit removes backward-compatible handling of an old, single outgoing channel ID field in LND's router RPC. Previously, callers could use either the old field or the newer list field; now the old field is rejected with an error. The main risk is that existing callers still using the deprecated field will see their requests fail instead of being silently treated as unrestricted. This is a hardening/cleanup change rather than a fix for an active vulnerability.

Recommended action

Review release notes and RPC documentation to warn users that OutgoingChanId is now rejected. Ensure client SDKs and integrations have migrated to OutgoingChanIds. No immediate patch is required, but operators should monitor for broken integrations after upgrade.

Security signals we found

01

Removal of deprecated RPC field fallback

02

Explicit rejection of deprecated field to avoid silent loss of outgoing channel restrictions

03

Behavior change from fallback/error-on-both to always-error-on-deprecated-field

04

Test updates reflect new strict rejection behavior

Risk score

Why this scored 32/100

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