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

graph/db: add version parameter to DeleteChannelEdges

Public commit record

What the developer wrote

Authored by Elle Mouton

73/100 · Adequate
graph/db: add version parameter to DeleteChannelEdges

Thread the gossip version through DeleteChannelEdges to enable
version-aware channel deletion. The KVStore rejects non-v1 versions
while SQLStore properly passes the version to the underlying queries.
This prepares for v2 channel zombie handling (strict zombie pruning
for v2 is marked as TODO).
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes how LND deletes Lightning channel records from its graph database. It adds a 'version' parameter so the code can distinguish between older (v1) and newer (v2) channel announcement formats. Right now it mostly hard-codes v1 and explicitly rejects or errors on v2 in some paths, so it is a preparatory/refactoring change rather than a finished security fix. There is no evidence in the commit that this resolves an active vulnerability or that it was released as a security patch.

Recommended action

Treat as a normal refactoring/infrastructure commit. Monitor follow-up commits that complete v2 strict zombie pruning and remove the TODO. If this commit appears in a release note as a security fix, request the associated CVE or advisory; otherwise no immediate patching urgency is indicated by the diff alone.

Security signals we found

01

New version-gating added to channel-edge deletion paths

02

KV store explicitly rejects unsupported gossip versions

03

SQL store propagates version into channel lookup queries

04

Strict zombie pruning explicitly errors on v2 with a TODO

05

No direct bug fix, vulnerability description, or CVE reference in commit

Risk score

Why this scored 27/100

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