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

keysend: increase assumed final_cltv_expiry to 42 (to match LDK).

Public commit record

What the developer wrote

Authored by Rusty Russell

81/100 · Strong
keysend: increase assumed final_cltv_expiry to 42 (to match LDK).

Reported-by: https://github.com/tnull
Fixes: https://github.com/ElementsProject/lightning/issues/9034
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Fixed: JSON-RPC: `keysend` now assumes 42, not 22 for final CLTV (should fix sending to LDK nodes)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This change fixes a compatibility issue in the `keysend` payment feature. Core Lightning was assuming a lower safety margin (22 blocks) for the final recipient's deadline than LDK/Rust-Lightning actually requires (42 blocks). When sending spontaneous payments to LDK nodes, this mismatch could cause the payment to be rejected or fail. The patch simply raises the assumed value to match LDK, improving interoperability. It is not a vulnerability that lets an attacker steal funds, but it is a reliability/security-adjacent fix for payment routing.

Recommended action

Apply the patch. No additional hardening is required. Operators using `keysend` to pay LDK nodes should upgrade to avoid payment failures.

Security signals we found

01

Interoperability fix for final CLTV expiry mismatch

02

Could cause payment failure/rejection when sending to LDK nodes

03

No memory corruption, authentication bypass, or cryptographic weakness introduced

04

Reported by external contributor and acknowledged with Fixes tag

Risk score

Why this scored 35/100

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