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

graph/db: set policy version for cache load

Public commit record

What the developer wrote

Authored by Elle Mouton

60/100 · Adequate
graph/db: set policy version for cache load

Ensure policies loaded for graph cache reconstruction are tagged as v1.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This small code change fixes a bug where Lightning Network routing policies loaded from the database into an in-memory cache were missing a version tag. The fix explicitly marks them as version 1 policies. Without the version set, other parts of the node that rely on the version field could misinterpret the policy, potentially causing incorrect fee or time-lock calculations when routing payments through the network.

Recommended action

Apply the patch. Review all other code paths that construct GraphChannelPolicy from database rows to ensure Version is consistently set. Add regression tests or assertions verifying policy version after cache load. Monitor for any routing/fee anomalies on nodes running versions prior to this fix.

Security signals we found

01

Missing version metadata in deserialized security/routing policy

02

Potential for incorrect routing constraints (timelock/fees) due to default-zero version

03

Fix is localized and defensive, suggesting a latent correctness issue

Risk score

Why this scored 46/100

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