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

lnwallet: add configurable output lease capability

Public commit record

What the developer wrote

Authored by Andras Banki-Horvath

73/100 · Adequate
lnwallet: add configurable output lease capability

Define an optional interface for confirmation-controlled output leases
without widening WalletController or changing existing callers.

Resolve that capability through adapter chains before applying a
non-zero depth. LightningWallet and RPCKeyRing expose their wrapped
controller, so local and remote-signer nodes reach the concrete
btcwallet backend. Unsupported controllers fail closed.

Map the accepted depth to btcwallet's persisted option and retain the
legacy LeaseOutput path for zero-depth callers.
✓ 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 a new optional wallet feature that lets LND lock a coin (UTXO) until the transaction spending it reaches a chosen number of confirmations. It is purely additive: it defines a new interface, routes calls through wallet adapter wrappers, and keeps the old zero-confirmation lease path unchanged. There is no bug fix, no reported vulnerability, and no evidence this change itself introduces a security issue.

Recommended action

No security action required. Treat as a normal feature review; verify downstream callers use ResolveOutputLeaser and handle the unsupported false case correctly when adopting the new lease option.

Security signals we found

01

New optional capability interface added without widening WalletController

02

Adapter-chain unwrapping exposes concrete backend for local and remote-signer wallets

03

Legacy LeaseOutput path preserved for zero-depth callers

04

Unsupported controllers fail closed via ResolveOutputLeaser returning false

05

No vulnerability disclosure, CVE, or security-relevant commit message present

Risk score

Why this scored 12/100

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