LND

This commit is purely a documentation housekeeping change. It moves release note entries for three already-merged changes (a logging fix, a deadlock fix, and gossip bandwidth default increases) from the v0.20.0 file to the v0.19.3 file because they are actually shipping in the earlier v0.19.3 release. No code behavior is changed.

This commit swaps out one PGP public key for another in LND's release verification script. The old key belonged to the same person (ffranr/Robyn Ffrancon) and is no longer used; the new key is the current release signing key. There is no code vulnerability here—it's a routine key rotation. However, if someone could silently replace the key with an attacker's key, they could trick users into trusting fake LND releases. The commit itself appears legitimate and matches the stated purpose.

This commit removes an expired PGP public key from the install verification script. It is a routine cleanup: keeping an expired key in the script would not let attackers take over systems, but it could cause install verification to fail or confuse users. There is no indication this is a security vulnerability fix.

This commit is a straightforward internal code cleanup in LND's channel graph code. It removes an unnecessary intermediate interface called NodeRTx and passes the underlying LightningNode object directly to callers. There is no security-relevant change here—no bug is fixed, no vulnerability is introduced, and no behavior visible to users changes.

This commit removes an unused method called ForEachChannel from the graph database interfaces and both of its implementations (one for the older key-value store and one for the newer SQL store). It also updates one integration test to use a different, already-existing method that provides the same information in a cached form. There is no indication this fixes a security bug; it appears to be routine code cleanup to simplify the interface and remove duplicated functionality.

This commit is a routine internal refactoring of LND's autopilot (automatic channel management) code. It removes an older, less efficient method for looping through channels and replaces it with a newer, more efficient one. There is no indication this fixes a security bug or introduces a vulnerability.

This commit is a routine internal refactoring in LND's autopilot (automated channel-opening) module. It adds a new method called ForEachNodesChannels to the ChannelGraph interface and implements it for database-backed and cached graph types, plus an in-memory test mock. There is no user-facing behavior change, no bug fix, and no security-sensitive logic. It simply prepares the codebase for a later removal of an older ForEachChannel method on the Node interface.

This commit is a routine performance and API improvement. It extends an internal graph database method so callers can optionally ask for each node's network addresses while iterating. When addresses are not needed, the code skips an extra database lookup, which makes operations like autopilot faster. There is no security fix or vulnerability here.

This commit only adds a new integration test to the LND project. It checks that when a Lightning channel has a maximum HTLC (payment chunk) size set, the software correctly splits a larger payment into smaller pieces that fit within that limit. There is no code fix or behavior change in the main application—only a test was added.

This commit only adds a release note describing a previously fixed bug. It does not change any code, cryptographic logic, network behavior, or configuration. There is no security issue introduced or addressed by this documentation-only change.

This commit only updates the release notes document by adding missing names to the contributors list. It does not change any code, configuration, or security behavior.

This commit changes how the Lightning Network Daemon (LND) handles 'custom HTLC' payments. Normally, LND enforces minimum and maximum amount limits on forwarded payments to prevent abuse and routing loops. For custom HTLCs—special payments that carry extra data and may use non-Bitcoin assets—these amount checks are now skipped in both the routing pathfinder and the actual forwarding switch. The change is described by the authors as intentional and needed to avoid routing loops, not as a security fix. It narrows a safety guard for a specific payment type, which could matter if the custom-channel logic has bugs or is misused.