LND

This commit removes old, unused code paths for sending Lightning payments through the main RPC server. These RPCs (SendPayment, SendPaymentSync, SendToRoute, SendToRouteSync) were already deleted from the service definition in a prior change, so this patch only cleans up the leftover server-side implementations and their macaroon permissions. There is no security vulnerability here; it is routine code deletion of dead functionality.

This commit removes three old, deprecated payment RPC methods (SendPayment, SendToRoute, and TrackPayment) from the LND Lightning node's router service. These methods were already replaced by newer V2 versions and were only thin wrappers around them. Removing them reduces the amount of code that could contain bugs and removes their access permissions, but it may also break older client software that still calls these methods.

This commit only changes integration tests for the Lightning Network Daemon (LND). It removes old test helper functions that called deprecated SendToRoute RPC methods and updates the tests to use the newer routerrpc.SendToRouteV2 API. No production code, user-facing RPC behavior, or security-sensitive logic is modified. It is a test-maintenance change with no direct security relevance.

This commit removes backward-compatible handling of an old, single outgoing channel ID field in LND's router RPC. Previously, callers could use either the old field or the newer list field; now the old field is rejected with an error. The main risk is that existing callers still using the deprecated field will see their requests fail instead of being silently treated as unrestricted. This is a hardening/cleanup change rather than a fix for an active vulnerability.

This commit only adds new integration tests for an existing feature in LND. It does not change production code, fix a bug, or alter any security-relevant behavior. The tests verify that the EstimateRouteFee API correctly handles requests that restrict the first hop to a specific outgoing channel.

This commit adds a new optional feature to LND's EstimateRouteFee API that lets callers specify which channels can be used as the first hop when estimating fees or probing payments. It is a feature enhancement, not a security fix or vulnerability. There is no indication of a security issue in the code changes.

This commit adds a new command-line option called outgoing_chan_id to the estimatefee command in LND. It lets users tell the fee estimator which payment channel(s) to consider for the first hop. There is nothing in the change that fixes a bug or addresses a security issue; it is a straightforward feature addition.

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 broadcast' before any actual closing transaction existed, which could make channels temporarily disappear from normal listings or leave a waiting-close record with an empty transaction field. The release note confirms the fix but does not itself change any code.

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 nil transaction. It does not change the actual production code that users run, so it cannot by itself fix or introduce a live bug.

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' transaction. That created a confusing in-between state in the database. The change removes those premature marks and now requires a real, non-nil closing transaction before the status is set. It also updates restart logic so the node can still recover an unfinished close from other stored information. The commit is defensive hardening rather than a fix for an active exploit.

This commit updates the database driver used by LND's key-value database module from an older, deprecated PostgreSQL library (pgx v4) to its newer version (pgx v5). It is a routine dependency migration with no direct security fix described in the commit. The change could indirectly improve reliability and future maintainability, but it does not by itself patch a known vulnerability.

This commit updates the LND project's PostgreSQL database helper library from an older version (pgx v4) to a newer one (pgx v5). The only code change is in a test file, switching to the new library's way of creating a database connection pool. There is no direct security fix or vulnerability being patched here; it is routine dependency maintenance.

This commit only adds a temporary Go module 'replace' directive so that the main lnd project uses a local copy of the kvdb package instead of a released version. It is a build/packaging convenience change with no security relevance visible in the diff or commit message.

This is a routine dependency cleanup. The project switched from a standalone PostgreSQL connection package to the version bundled inside the newer pgx v5 library. Only import paths and the dependency list changed; no program logic was modified. There is no indication this fixes or introduces a security vulnerability.

This is a routine dependency cleanup. The project was using a standalone PostgreSQL connection helper package (pgconn) that has been merged into the main pgx database driver package in version 5. The change updates two source files to import pgconn from its new location and removes the old standalone package from the module files. There is no functional code change and no security fix or vulnerability introduced.

This commit only updates the release notes document. It adds text describing two earlier changes: a switch in how LND checks Bitcoin peer health, and clearer wording for a warning about ZMQ port mismatches. There is no code change in this commit itself.

This commit only rewords two warning log messages in LND's chain registry. It changes the text from saying 'unable to subscribe to zmq ... events' to saying 'zmq ... port mismatch' when LND's configured ZMQ port differs from what the connected bitcoind reports. There is no code behavior change, no security fix, and no vulnerability addressed.

This change is a performance and reliability improvement, not a security fix. LND previously checked how many outbound peers its bitcoind backend had by calling getpeerinfo, which returns detailed information about every single peer and can be slow. The patch switches to using getnetworkinfo.connections_out, a lighter-weight RPC call that just reports the outbound peer count. The old getpeerinfo-based helper is kept for btcd because btcd does not support getnetworkinfo. There is no indication this change addresses a vulnerability or security incident.

This is a routine code cleanup in LND's chain setup code. It replaces a hand-rolled JSON call to Bitcoin's getzmqnotifications RPC with a typed library method. There is no security-relevant change visible in the diff: the same ZMQ notification checks are still performed, just with less manual parsing.

This commit is a straightforward code cleanup in LND's Bitcoin backend health check. It replaces a manual raw JSON-RPC call and hand-written JSON parsing with a typed library call that does the same thing. There is no security issue visible in the change.

This commit only adds documentation: a set of release-candidate testing guides for the upcoming LND v0.21.0 release. No source code, configuration defaults, RPC behavior, or database logic is changed. The new Markdown files describe how testers (human or automated) can verify new features such as taproot channels, onion-message rate limiting, and a payment-store migration. Because nothing executable is modified, the commit itself does not introduce a security vulnerability or fix one.

This is a routine internal code cleanup in LND's autopilot (automatic channel-opening assistant). It changes a callback to pass a node public key directly instead of wrapping it in a full Node object, and skips nodes with no channels during graph traversal. There is no security fix or externally visible behavior change.

This commit only adds a release note describing a previous performance improvement in LND's autopilot feature. It is documentation-only and makes no code changes. There is no security issue present in this commit.

This commit only updates a commented-out example value in the sample configuration file so that it matches a newer default version from an upstream dependency. It is a documentation/sample-file maintenance change with no functional or security effect on running software.