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

docs: add release-notes

Public commit record

What the developer wrote

Authored by ziggie

40/100 · Thin
docs: add release-notes
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit only adds a line to the release notes describing a prior bug fix: HTLCs (payment contracts) with a locktime of 0 were not being swept by an older legacy sweeper component called utxonursery. The actual code fix is in a separate pull request referenced by the note. Because this commit is documentation-only, it does not itself change any program behavior, but it confirms a past bug existed that could have left some funds unrecovered.

Recommended action

Review PR #10273 and the actual code fix to determine whether un-swept HTLCs with locktime 0 could lead to stuck funds or channel-force-close edge cases. Treat this documentation commit as informational only; any security response should be based on the referenced code change, not this release-note entry.

Security signals we found

01

Release note references a bug fix in legacy sweeper (utxonursery)

02

Affected condition: HTLCs with locktime of 0 not swept

03

Potential funds-recovery / liveness issue, not a direct remote exploit

04

No source code changes in this commit

Risk score

Why this scored 39/100

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