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

docs: release-notes-0.21

LLbf473431 View source ↗
Public commit record

What the developer wrote

Authored by MPins

65/100 · Adequate
docs: release-notes-0.21

Warning message about removing the deprecated option --sat_per_byte
✓ Subject identifies a change✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit only adds a documentation note to the upcoming 0.21 release notes. It warns users that the old --sat_per_byte fee option will be removed in version 0.22 and tells them to switch to --sat_per_vbyte. No code was changed, so there is no direct security issue in this commit itself.

Recommended action

No security action needed for this commit. Users and operators should review the deprecation notice and plan migration from --sat_per_byte to --sat_per_vbyte before LND 0.22.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

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

More from LND

Related watches

Moderate 59 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11023 from ellemouton/update-fee-log

This commit hardens how LND handles Lightning channel fee updates and mailbox message admission. It enforces the protocol rule that only the channel opener can send fee updates, prevents uncommitted fee updates from piling up in the update…

BOLT 2 role validation for UpdateFee senderReplacement of uncommitted fee updates to prevent log bloat and index gapsBounded mailbox wire-message queue (count and bytes)
7f56541dby Yong+750−138 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11019 from Roasbeef/coop-close-race-public

This update fixes two related problems in LND's cooperative channel-closing code. First, it eliminates a data race where the same state machine was being advanced by two different internal goroutines at once, which could cause crashes or i…

Data race in legacy cooperative close state machine driven concurrently by link and peer goroutinesMissing or inconsistent validation of remote delivery script when no upfront shutdown script is recordedpanic() in DustLimitForSize on unrecognized script sizes replaced with safe fallback
f4ae5656by Yong+463−609 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 63 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11024 from ziggie1984/invoices-update-validation

This commit tightens how LND processes invoice payments, especially for newer multi-path (MPP) and AMP invoices, keysend payments, and replayed payments. It adds checks that ensure the right payment preimage is used for each invoice type a…

Preimage validation added for AMP and regular invoice replaysAMP invoices forced into MPP update path, preventing legacy-path processingLegacy settlement now fails when invoice-level preimage is missing
61f3b5a7by ziggieXXX+482−114 files
No security note in commit
Open full analysis →Source commit ↗