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

plugins: don't try to fetch max-locktime-blocks.

Public commit record

What the developer wrote

Authored by Rusty Russell

60/100 · Adequate
plugins: don't try to fetch max-locktime-blocks.

It was removed in v25.09, so this code is useless.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit removes leftover code that tried to read a configuration option called 'max-locktime-blocks' from three payment-related plugins. That option was already removed from the core software, so the code was doing nothing useful. The commit also hardcodes the fallback maximum payment delay to 2016 blocks, which was already the previous default. There is no direct security fix here; it is mostly cleanup of dead code.

Recommended action

No security action required. Treat as routine cleanup. If reviewing related code, verify that maxdelay user overrides are still honored and that 2016 blocks remains an appropriate default.

Security signals we found

01

Removal of dead configuration fallback code

02

No change to effective maxdelay default (remains 2016 blocks)

03

No bounds, type, or validation changes

04

No memory safety, auth, or crypto changes

Risk score

Why this scored 19/100

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