LND

This commit fixes a bug in LND's cooperative channel-closing code where a peer could supply an invalid, empty, or even money-burning Bitcoin address during a close, and LND would accept it without checking. The fix makes the newer 'RBF' closer always validate the peer's payout address, matching what the older negotiation closer already did. Before, validation only happened if the peer had previously committed to a specific upfront address. Without that, a malicious or buggy peer could have caused funds to be sent to an unspendable or malformed script.

This change removes a deliberate program crash (panic) in LND's fee/dust-limit helper and replaces it with a safe fallback. Previously, if the helper received a script length it didn't explicitly recognize, it would panic and potentially crash the node. Now it treats any unrecognized length as a generic witness output and returns a dust value instead. The patch is defensive: it makes the code well-defined for future Bitcoin witness versions and arbitrary script sizes, but the commit message does not frame it as fixing a known exploitable vulnerability.

This commit fixes an internal bookkeeping bug in LND's channel-opening code. When opening a Lightning channel that uses an auxiliary (aux) funding controller, the code was previously handing the controller an incomplete view of the negotiated channel settings. The patch makes sure the controller receives the final, agreed-upon local and remote channel configuration values. There is no direct evidence in the commit that this is exploitable as a security vulnerability; it reads as a correctness/robustness fix for a feature used by custom channel types such as Taproot Assets channels.

This commit is a straightforward internal code cleanup: it changes the lnwallet package to use the OpenChannel type from a dedicated chanstate package instead of getting it indirectly through the channeldb package. There is no change to user-facing behavior, network protocol handling, cryptographic operations, or database logic. It is purely a refactoring move to make the code's type ownership clearer.

This commit only changes test helper code in LND. It swaps one internal type name (channeldb.OpenChannel) for another (chanstate.OpenChannel) inside test utilities. There is no change to production code, no user-facing behavior change, and no security fix.

This commit is a straightforward internal code cleanup in LND. It changes three places in server.go to use a new internal type name (chanstate.OpenChannel) instead of an old alias (channeldb.OpenChannel). The actual behavior of the code is unchanged; it simply updates wiring after a previous refactoring in the funding package. There is no security-relevant change visible in the diff.

This is a small internal code cleanup in LND's wallet RPC server. It changes one helper function to use a newer internal package type (chanstate.OpenChannel) instead of an older compatibility alias (channeldb.OpenChannel). There is no user-facing behavior change, no bug fix, and no security-relevant change visible in the diff.

This commit is a routine internal code cleanup in the LND Lightning node software. It removes temporary generic type parameters from channel-state database interfaces and replaces them with direct references to the concrete OpenChannel type. There are no user-facing behavior changes, no bug fixes, and no security-related modifications.

This commit is a code cleanup: it removes a forwarding-package helper object from the in-memory channel state and instead creates it on demand inside database methods. There is no direct security fix or vulnerability being patched. It mainly reduces coupling between components and updates tests to match the new structure.

This commit is a routine code reorganization: it moves two helper functions and a constant related to Taproot channels from one internal package (channeldb) to another (chanstate), and leaves aliases in the old location so existing callers keep working. There is no change to behavior, no bug fix, and no security patch.

This commit is a straightforward internal code reorganization. It moves the existing logic for saving a new remote commitment-chain update from one place in the code to another, without changing what the logic actually does. There is no user-facing behavior change and no security fix or vulnerability introduced.

This commit is a pure internal code reorganization. It moves several small channel-related data types (like channel configuration, status flags, close summaries, and helper types) from the channeldb package into a new chanstate package, then makes the chanstate.Store interface generic so callers can still use the existing channeldb.OpenChannel type. Existing code keeps compiling because channeldb now declares type aliases pointing to the new chanstate definitions. There are no behavior changes, no bug fixes, and no security-relevant logic changes.

This commit only adds a new integration test for an existing LND WalletKit RPC called SubmitPackage. It does not change production code, wallet logic, or network behavior. The test verifies that a zero-fee Bitcoin transaction can be accepted into the mempool when bundled with a fee-paying child transaction (a standard Bitcoin package-relay scenario). There is no security fix, vulnerability, or user-facing change here.

This commit adds a new command-line tool called `lncli wallet submitpackage` that lets users hand one or more raw Bitcoin transactions to LND's wallet service so they can be submitted to the network as a group (a "package"). The change only wires up an existing backend RPC to the command-line interface; it does not change how transactions are validated or accepted by the node. There is no indication in the commit that this fixes a security bug.

This commit is just a documentation update adding a release note for a previously fixed bug. The actual bug was a crash (panic) in LND's DNS fallback code: when looking up network routing information, the program assumed every answer from a DNS server would be a specific record type (SRV). If a DNS server returned a different kind of record, the program would crash. The fix also handled an empty lookup result safely. This release note describes that earlier code fix; the commit itself does not change any program code.

This commit only removes a sentence from the release notes document for version 0.22.0. It does not change any program code, so it cannot by itself introduce, fix, or alter a security vulnerability. The deleted text described a previously documented bug fix (a daemon crash caused by mishandling DNS records), but the actual code change was made elsewhere and is not present in this commit.

This commit is mostly a cleanup patch: it wraps long lines caused by a recent library rename and, importantly, adds a missing error check around a call that loads a Bitcoin transaction filter. The error check prevents a silent failure where the node might continue without realizing its filter was not updated, which could affect routing/chain monitoring. There is no direct evidence this is exploitable as a security vulnerability.

This commit only adds a release note describing a previously fixed bug in LND's DNS fallback code. The actual code fix is not shown in this commit. The bug could crash the LND daemon (a panic) if a DNS response contained unexpected record types during a special service-location lookup, or if a host lookup returned no results. Because this is just documentation, the immediate code risk is low, but the described underlying issue was a real crash bug.

This commit updates the software's dependency list for the Tor-related sub-package, bumping the btcd library from version 0.24.2 to a newer pre-release (0.26.0-beta.rc1) along with several supporting libraries. There are no actual code changes shown—only the files that record which library versions are used. Because the commit message says only 'use latest btcd' and no security issue is described, this looks like a routine dependency refresh rather than a confirmed security fix. However, dependency updates can sometimes include security patches from the upstream libraries, so it is worth monitoring the release notes for btcd and the related Go packages.

This commit simply updates a database helper library (pgx) used by LND's key-value database module from version 5.7.4 to 5.9.2. Only version numbers in dependency files changed; no actual code was modified. There is no information in the commit itself saying this fixes a security problem, and no verified references were supplied.

This commit simply updates the version of a third-party PostgreSQL database driver library (pgx) used by LND from version 5.7.4 to 5.9.2. The change only affects dependency files (go.mod and go.sum). There is no direct code change shown, and the commit message does not say why the update was made or whether it fixes any security issue. It could be a routine maintenance update, or it could be pulling in bug or security fixes from the upstream library, but that is not stated in the materials provided.

This commit updates the Prometheus monitoring library and related dependencies inside a developer tools module. It is a routine maintenance change with no direct security fix or code change to the main LND application. The update removes some old, unused dependency entries and refreshes checksums, which is normal housekeeping.

This commit removes a now-unnecessary dependency override in a Go module file. The override was forcing the use of a newer, fixed version of the gogo/protobuf library, but the project's dependency graph now naturally selects that same fixed version, so the override is redundant. There is no functional code change and no security regression.

This commit updates the Prometheus monitoring library used inside the kvdb sub-module of LND. It is a routine dependency refresh that removes an old transitive dependency on an outdated version of gogo/protobuf. There is no direct code change, no disclosed vulnerability being fixed, and no indication this patch itself introduces a security problem.

This commit updates the Prometheus metrics library and several related Go module dependencies to newer versions. It is a routine dependency maintenance change, not a code-level security fix. The commit message does not describe any specific vulnerability being patched, and the diff only changes dependency version pins in go.mod and go.sum. While newer dependency versions can indirectly improve security by removing old, potentially vulnerable transitive packages, there is no direct evidence in the commit that this fixes a known security issue.