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

Merge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-store

Public commit record

What the developer wrote

Authored by Yong

73/100 · Adequate
Merge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-store

graph/db: cross-version graph Store queries
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit refactors how the Lightning Network Daemon (LND) stores and queries channel graph data so that the same channel or node can exist under both old (v1) and new (v2) gossip protocols without the database returning stale, missing, or mixed-up records. It adds 'preferred' lookups that pick the best available version, keeps the in-memory cache consistent with those lookups, and fixes several bugs where deleting or updating one version could leave the other version invisible or inconsistent. The changes are framed as architectural groundwork for the upcoming gossip v2 feature rather than as a fix for an active security vulnerability.

Recommended action

Treat this as a correctness and forward-compatibility patch rather than an emergency security fix. Operators running LND with the SQL backend should upgrade through normal release channels to benefit from the cross-version graph consistency fixes. Reviewers should pay attention to the new preferred-mapping upsert logic during node/channel deletion to ensure no orphaned mappings remain, and monitor for any regressions in pathfinding or RPC channel visibility.

Security signals we found

01

Cross-version data consistency: prevents a v2 channel shell from shadowing a usable v1 channel, which could affect routing decisions and RPC output.

02

Cache consistency: ensures the in-memory pathfinding cache and the SQL-backed RPC reads agree on which channel version and policies are active.

03

Bug fix: zombie edge info now carries the correct channel ID instead of 0, which could have caused incorrect channel identification during resurrection.

04

Bug fix: ForEachNodeCached no longer hardcodes GossipVersion1, so v2-only channels are visible to callers requesting v2.

05

Bug fix: buffered cache updates during startup use the population context, avoiding dropped cache entries when a caller cancels early.

06

No explicit security disclosure or CVE referenced in the commit or supplied materials.

Risk score

Why this scored 40/100

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