Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This commit only adds a line to the release notes document for version 0.21.2. It mentions that a bug was fixed where a feature called the 'RBF closer' could be used with incompatible auxiliary channels. The commit itself does not change a…
This commit fixes a bug in LND where a new cooperative channel-closing mechanism (RBF coop close) was being used for special 'aux' channels that carry Taproot Assets. Those aux channels need extra steps to safely move the assets out, but t…
Loss-of-funds / asset-destruction bug for aux (taproot asset overlay) channelsChannel-stuck / denial-of-service side effect (waiting-close state)Feature-bit selection bypassed per-channel safety checks
This commit fixes a bug in LND's transaction sweeping logic that could permanently strand certain custom-channel (asset) outputs. The sweeper's budget filter was ignoring extra funds contributed by an optional 'aux sweeper' helper, so it w…
Denial-of-service / fund stranding: custom-channel outputs could be silently excluded from all future sweepsFee-ratchet interaction: non-fee failures (wallet UTXO collisions) could raise startingFeeRate and trigger the filterMissing budget accounting: filter did not mirror set-construction logic that already used aux extra budget
This commit only adds a release note describing a previously fixed bug in LND's sweeper logic. It does not change any code, so it cannot introduce or fix a security issue by itself. The described bug relates to fee budgeting for sweeping c…
No code changesDocumentation-only commitReferences a prior bug fix (PR #10897) in release notes
This commit removes an unused data field called FreshFlush from the cooperative channel-closing logic. The field was always set to true and never actually checked by any code, so deleting it is a cleanup change with no security effect.
This commit only adds a release note describing a previously fixed bug in LND's cooperative channel closing flow. The actual code fix happened in an earlier pull request. The bug caused channel status to be marked as 'cooperatively broadca…
Release note references a bug fix in cooperative close state managementPremature channel-status flag could lead to inconsistent channel visibility during closeNo code change in this commit; security relevance is second-hand from release note
This commit only changes a test file. It adds a safety check to make sure a function called during cooperative channel closes is always given a real transaction, not a blank one. The test now records every call and fails if any call has a …
Test-only regression guard for nil transaction in cooperative close pathReferences external issue about a 'limbo state' when ChanStatusCoopBroadcasted is set without a stored transactionNo production code change; no patch to the actual MarkCoopBroadcasted caller or channel state machine
This commit cleans up how LND records that a Lightning channel is being closed cooperatively. Previously, the code would mark a channel as 'cooperatively closed' before an actual closing transaction existed, storing a placeholder 'nil' tra…
Eliminates a 'limbo' channel status where ChanStatusCoopBroadcasted is set without a stored close transactionAdds an explicit non-nil guard in markBroadcasted to prevent future nil close-tx persistenceReduces risk of incorrect state recovery/restart behavior after a crash during cooperative close
This commit only changes the wording of an error message. It does not alter any logic, permissions, or security behavior. The new message more accurately tells standalone lnd users that taproot overlay channels are not supported in their b…