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

Merge pull request #11472 from yyforyongyu/task-sweep-rejections

Public commit record

What the developer wrote

Authored by Yong

73/100 · Adequate
Merge pull request #11472 from yyforyongyu/task-sweep-rejections

sweep: retry transient mempool rejections
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes a bug in LND's transaction sweeping logic. Previously, if the Bitcoin backend rejected a sweep transaction for a temporary or unknown reason (for example, the mempool was full, a network error occurred, or the rejection reason was unclear), LND would treat the inputs as permanently failed and stop trying to spend them. The fix makes LND retry these inputs later while preserving the intended fee increase schedule, so funds are not left stuck. It also updates the required Go version to 1.27.3 across the project.

Recommended action

Reviewers should verify that the new retry cases do not accidentally retry permanently invalid transactions (e.g., double spends or consensus-invalid inputs) and that the fee cap is respected in all retry paths. Operators should upgrade to a release containing this commit to avoid stuck sweep transactions during mempool congestion or transient backend errors.

Security signals we found

01

Funds-availability / liveness fix: temporary or unknown mempool rejections could leave sweep inputs unspent.

02

Error-handling reclassification: previously fatal errors now retryable.

03

Retry metadata preservation: next fee rate and fee cap kept across attempts.

04

Go toolchain bump to 1.27.3 (build requirement, not a runtime vulnerability fix).

05

Dependency normalization: btcwallet pseudo-version replaced with tagged v0.18.1.

Risk score

Why this scored 44/100

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