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

walletrpc: release partial locks by owner ID

Public commit record

What the developer wrote

Authored by Andras Banki-Horvath

68/100 · Adequate
walletrpc: release partial locks by owner ID

Make multi-input lease acquisition all-or-nothing. A metadata lookup or
lease failure after an earlier success now triggers one guarded deferred
rollback.

Release each acquired output with its recorded lock ID. This preserves a
caller's custom owner ID instead of incorrectly using LND's internal ID.
Cover both metadata and lease failures with internal and custom owners.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This change fixes a bug in LND's wallet RPC code that handles locking multiple bitcoin inputs at once. Previously, if locking one input failed after earlier inputs were already locked, the rollback tried to unlock the earlier inputs using LND's internal lock ID instead of the caller's actual lock ID. That meant the earlier locks might not get released, leaving funds stuck or unavailable. The patch makes the rollback use the real lock ID recorded for each acquired lease, and also rolls back on metadata lookup failures, not just lease failures.

Recommended action

Treat as a bug-fix patch with moderate operational/security relevance. Review and merge. Operators using FundPsbt with custom lock IDs should upgrade to avoid stuck UTXO leases on partial failures. No emergency response is indicated absent a disclosed exploit.

Security signals we found

01

Incorrect lock ID during rollback could leave UTXO leases unreleased

02

Partial multi-input lease acquisition was not all-or-nothing

03

Metadata lookup failure did not trigger rollback of already-acquired leases

04

New rollback helper improves observability by reporting surviving leases with owner ID

Risk score

Why this scored 47/100

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