LND

This commit only adds release notes describing a prior bug fix. The underlying issue was that private Taproot channels stored in an older format were incorrectly rebuilt as legacy multi-signature addresses when LND restarted. This could cause LND to watch for the wrong transaction type, potentially missing on-chain events for those channels. The commit itself does not change any code, only documentation.

This commit fixes a bug in the LND Lightning node where it could look up the wrong Bitcoin address (funding script) for certain private Taproot channels when rebuilding its chain filter after a restart. The wrong address was a legacy multisig address instead of the expected Taproot address. Because the node uses this filter to watch the blockchain for relevant transactions, using the wrong address could cause it to miss on-chain activity related to those channels. The commit makes the code check the channel's feature bits to decide which address type to reconstruct.

This commit only adds automated tests that demonstrate an existing bug in LND's handling of private taproot channels. The bug causes the wallet to watch for the wrong Bitcoin address when monitoring the blockchain for channel funding transactions. Because the commit itself does not change production code, it cannot be exploited; rather, it documents a real bug that the next commit is intended to fix. If left unfixed, the bug could prevent LND from correctly detecting on-chain activity for some taproot channels.

This commit only changes a debug log message so that ping messages show how many pong bytes were requested and how long the ping payload is. It is purely an observability/logging improvement and does not alter any behavior, protocol handling, or security logic.

This commit removes an unused error variable and widens a test generator's range. It is a cleanup/test-coverage change with no apparent security relevance.

This commit only updates the release notes document. It adds a description of a previously fixed bug where LND would disconnect peers over a specific type of ping message. There are no code changes in this commit, so it does not introduce, fix, or change any behavior by itself.

This change fixes how LND handles certain ping messages from other Lightning nodes. Previously, LND would disconnect from peers that sent pings using a special 'no-reply' range defined in the BOLT 1 protocol spec. Now LND correctly accepts and ignores those pings, keeping the connection alive. This improves compatibility with peers that use these pings as padding, especially during channel re-establishment after reconnecting.

This commit simply adds a directory named `.worktrees` to the `.gitignore` file. It tells Git to ignore that folder. There is no code change, no security fix, and no vulnerability introduced.

This commit only adds a new optional Makefile target that lets developers run the project's Go linter directly on their computer instead of inside a Docker container. It does not change any application code, network behavior, or security-sensitive logic. There is no indication this introduces a vulnerability.

This commit only adds new test code for the LND Lightning wallet. It introduces helper functions and test cases that check how taproot channels synchronize cryptographic nonces during channel re-establishment, covering both a newer 'LocalNonces' map field and the older single 'LocalNonce' field. No production code is changed, so it does not fix or introduce a live security vulnerability by itself.

This commit updates how the Lightning Network Daemon (LND) exchanges special one-time cryptographic numbers (nonces) when a Taproot payment channel reconnects after being offline. It adds support for a new 'LocalNonces' field while keeping the old 'LocalNonce' field for older peers. The change is a protocol integration/cleanup rather than a clear fix for an active security bug, but mishandling these nonces can in principle weaken the multi-signature security of Taproot channels.

This commit adds a new optional data field called LocalNonces to a Lightning Network channel-recovery message. It is a protocol-extension change designed to support multiple cryptographic nonces for in-flight channel operations (such as splices). There is no direct evidence in the commit that this fixes or introduces a security vulnerability; it appears to be a feature/backwards-compatible protocol update.

This commit adds a new data structure and wire format for exchanging groups of cryptographic nonces used in multi-signature Lightning transactions. It is purely preparatory code: it defines how to pack and unpack the data and includes unit tests. There is no actual use of this structure in message handling yet, and nothing in the commit suggests a security bug or fix.

This commit only adds a release note describing a previous documentation fix. It adds missing labels in API definitions so generated docs correctly link to command-line tool commands. There is no code change and no security issue.

This commit only updates documentation comments in protocol-buffer definitions and the generated API documentation files. It adds labels that tell readers which lncli command corresponds to three existing RPCs. No code behavior, permissions, or network logic changed.

This commit only adds a documentation hint showing which lncli command maps to the SignPsbt API. It changes comments in a .proto file, a generated swagger JSON file, and generated Go gRPC code. There is no functional code change and no security relevance.

This commit only adds documentation to the release notes. It describes a new command-line option for signing PSBTs (Partially Signed Bitcoin Transactions) that was added in a previous pull request. There is no code change and no security issue in this commit itself.

This commit adds a new command-line option to LND's wallet tool that lets users sign partially-built Bitcoin transactions (PSBTs). It is a feature addition that exposes an already-existing wallet RPC through the lncli interface. There is no indication in the commit that it fixes a bug or addresses a security vulnerability.

This change only affects internal test setup code. It adds a command-line flag to bitcoind test instances so they use an older version of the Bitcoin peer-to-peer protocol, because the test miner software (btcd) does not yet support the newer protocol. This prevents 30-second handshake timeouts that were making tests flaky. It is not a security fix and does not change production LND behavior.

This commit fixes a flaky test in LND's peer package. The test helper that creates a fake peer was missing a mock object for BestBlockView. When a background ping timer fired during tests, it tried to call a method on the nil mock, causing random test panics. The change adds a trivial mock that returns empty values and wires it into the test config. There is no production code change and no security relevance.

This commit fixes a simple but real programming bug: a logical 'and' was used where an 'or' was needed. In the LND lightning node software, when preparing a network ping message, the code asks for the latest Bitcoin block header. If that lookup fails and returns no header, the old code would try to use the missing header and crash the program with a nil pointer panic. The fix makes the code return a cached header whenever the lookup errors OR when the header hasn't changed, preventing the crash.

This commit adds a new optional command-line/configuration flag called --db.sync-graph-cache-load to the LND Lightning node software. It lets node operators choose to load the channel graph cache synchronously (blocking startup until complete) instead of the new default asynchronous loading. The change is purely an opt-out configuration addition and does not fix any vulnerability or change default behavior.

This change makes LND's in-memory channel graph cache load in the background instead of blocking startup. While the cache is loading, reads fall back to the database, and any new channel updates are buffered and replayed once loading finishes. It also lets the shutdown signal cancel a long-running cache load. The patch is a defensive reliability improvement rather than a clear security fix, but it removes a startup stall and reduces the chance of serving stale or inconsistent graph data during initialization.

This commit only updates the release notes document for version 0.21.0. It adds a description of a performance improvement (asynchronous channel graph cache loading) and fixes minor formatting/spacing in existing notes. There are no code changes, no bug fixes, and no security-related content.

This commit adds a new read-only status field to LND's GetInfo API response so users can see whether the in-memory network graph cache is disabled, still loading, fully loaded, or failed. It does not change how the cache works or how data is read; it only exposes existing internal state through the API. There is no security vulnerability here.