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

graph/db: remove address loading from cached node iteration

Public commit record

What the developer wrote

Authored by Elle Mouton

73/100 · Adequate
graph/db: remove address loading from cached node iteration

ForEachNodeCached is now only used for topology-oriented traversal,
so the address-loading option forced one autopilot scoring path to
bypass the in-memory graph cache for data it did not consume. Remove
the withAddrs parameter and the associated SQL/KV address plumbing
so cached node iteration can consistently use the graph cache when
it is loaded.

Autopilot still requires peer addresses before opening channels.
That filtering remains in Agent.openChans via ForEachNode, where the
selected candidates' addresses are collected for ConnectToPeer. The
trade-off is that ForEachNodesChannels no longer excludes
addressless nodes from graph-wide scoring inputs such as median
channel size or centrality, which also feed lncli getnetworkinfo
statistics like graph diameter. In practice the only addressless
nodes our local view tends to know about are nodes with no public
channels (e.g. our own node or peers we share only private channels
with), so the impact on the reported stats should be negligible.
Active channel candidates remain address-filtered before dialing.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This is a performance and code-simplification cleanup, not a security fix. It removes an optional address-loading path from a cached graph-traversal function so the cache can be used more consistently. The only behavioral change is that autopilot's graph-wide scoring now includes nodes without advertised addresses when computing statistics such as median channel size and centrality. Those nodes were previously skipped. Active channel candidates are still filtered by address before any peer connection is attempted, so the practical security impact is minimal.

Recommended action

No security action required. Treat as a normal refactoring/performance change. If desired, verify that autopilot's later address filter in Agent.openChans still prevents opening channels to unreachable peers.

Security signals we found

01

Behavioral change: addressless nodes now included in graph-wide scoring/statistics

02

No input validation, cryptographic, or authorization changes

03

No memory safety, concurrency, or resource exhaustion fixes

04

No vendor disclosure of security relevance

Risk score

Why this scored 18/100

Our methodology →
Potential impact 2/30
Exploitability 0/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.