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

wallet: we can assume local_alias field is non-null.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
wallet: we can assume local_alias field is non-null.

We have a migration which ensures this, but then I discovered that did
*not* address channels without an SCID yet. So fixed the migration, and
simpligied the code.

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 commit fixes a database migration in Core Lightning that was supposed to ensure every channel has a local alias (a routing identifier), but it missed channels that didn't yet have a stable channel ID (SCID). The patch moves and broadens the migration so all channels without a local alias get one, and then simplifies the code to always expect the field to be present. It is a data-integrity bug fix rather than an obvious remote exploit, but if a channel lacked a local alias it could lead to inconsistent routing behavior or crashes in later code paths that assume the alias exists.

Recommended action

Treat as a low-severity data-integrity fix. Users running versions between the original migration and this fix should ensure the updated migration runs and backfills alias_local for all channels, especially those without an SCID. Monitor for any crashes or routing anomalies related to missing local aliases. No immediate emergency response is warranted absent evidence of remote exploitability.

Security signals we found

01

Incomplete database migration that left some rows with a NULL field the code later assumes is non-null

02

Code simplification removes NULL handling for alias_local, increasing reliance on the migration's completeness

03

Potential data-integrity / availability issue if a channel without local_alias is loaded or saved

04

No explicit security framing by the vendor; appears as a correctness/robustness fix

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.