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

graph/db: version ChannelID lookup

Public commit record

What the developer wrote

Authored by Elle Mouton

78/100 · Adequate
graph/db: version ChannelID lookup

Add a gossip version parameter to the ChannelID method (outpoint to
short channel ID lookup) in the Store interface and both KV/SQL
implementations. Update the VersionedGraph wrapper and tests.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit changes how the Lightning Network Daemon (LND) looks up a compact channel identifier from a funding transaction outpoint. It adds a 'gossip version' parameter to the lookup so that the database can distinguish between different protocol versions when resolving channel IDs. The change is a structural/API update rather than a fix for an active security flaw. It does not, on its own, prevent or enable a known attack, but it is part of making the graph database version-aware, which can help avoid mismatches between how channels are stored and queried.

Recommended action

Treat this as a normal refactoring/API-change commit. Reviewers should verify that all callers of ChannelID have been updated to supply a correct GossipVersion and that the SQL query index/plan for GetSCIDByOutpoint remains efficient with the now-variable version parameter. No immediate security patch or incident response is indicated by the commit content.

Security signals we found

01

API signature change to include protocol version in channel ID lookup

02

KV backend explicitly rejects unsupported gossip versions

03

SQL backend stops hardcoding GossipVersion1 and uses caller-supplied version

04

No direct input validation, bounds checking, or cryptographic change present

05

No mention of vulnerability, CVE, bug bounty, or security fix in commit message

Risk score

Why this scored 19/100

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