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

Validate CLTV somewhat in `Route::debug_assert_route_meets_params`

Public commit record

What the developer wrote

Authored by Matt Corallo

73/100 · Adequate
Validate CLTV somewhat in `Route::debug_assert_route_meets_params`

Now that we've cleaned up trampoline CLTV building and added
`Path::total_cltv_expiry_delta`, we can use both to do some basic
validation of CLTV values on blinded tails in
`Route::debug_assert_route_meets_params`
✓ 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 extra sanity checks inside a Lightning payment routing library to catch cases where time-lock (CLTV) values on payment paths are internally inconsistent. The checks live in a debug-only assertion helper, so they do not change normal runtime behavior; they mainly help developers detect bugs during testing. The patch also fixes one unit test that previously relied on an unrealistic CLTV value and adjusts how the first-hop CLTV is computed when building onion payloads for trampoline/blinded routes.

Recommended action

Treat as a defensive hardening/debug-assertion improvement rather than an active vulnerability fix. Review whether these checks should eventually be promoted from debug_assert to runtime errors, especially for blinded/trampoline paths where CLTV inconsistencies could affect payment safety. No urgent patch or incident response is indicated by the commit alone.

Security signals we found

01

New CLTV consistency assertions in route validation

02

Blinded path / trampoline CLTV delta checks

03

Addition of max_total_cltv_expiry_delta enforcement in debug assertion

04

Unit test adjustment to accommodate new validation

05

Onion payload CLTV computation refactor for first hop only

Risk score

Why this scored 36/100

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