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

graph/db: add ChanUpdateRange and NodeUpdateRange types

Public commit record

What the developer wrote

Authored by Elle Mouton

73/100 · Adequate
graph/db: add ChanUpdateRange and NodeUpdateRange types

Add version-aware range types for channel and node update horizon
queries. V1 gossip uses unix timestamps for ordering while v2 uses
block heights, so each range type validates that the correct bound
type is provided for the requested gossip version.

These types will be used in follow-up commits to version the
NodeUpdatesInHorizon and ChanUpdatesInHorizon Store methods.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds new internal data types (ChanUpdateRange and NodeUpdateRange) and validation logic for upcoming gossip protocol features. It does not change any existing behavior or fix a security issue; it is purely preparatory code with tests.

Recommended action

No security action needed. Treat as normal feature/refactoring commit. Review the follow-up commits that integrate these range types into NodeUpdatesInHorizon and ChanUpdatesInHorizon for potential security implications.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

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