LND

This commit fixes a subtle multi-threading bug in how LND retrieves a node's public key. Multiple parts of the program could call the same method at the same time, and because the method cached the parsed key in a shared field, several threads could try to write that cache simultaneously. That kind of race can corrupt memory or cause crashes in Go. The fix removes the cache entirely and simply parses the key on demand, which is fast enough that caching isn't worth the risk.

This commit moves a finalization step for special auxiliary channel closes from the interactive negotiation phase to the point where the closing transaction is confirmed on-chain. The goal is to make the process more reliable by not depending on the remote party staying online and sending a message. The change itself is a refactor of when and where finalization happens, not a fix for a known exploit.

This commit is a straightforward internal code reorganization. It moves some data type definitions related to channel closing from one package to a new shared package so other parts of the program can use them without creating circular imports. No behavior changes, bug fixes, or security-sensitive logic changes are visible in the diff.

This commit fixes a race condition in LND's graph database code. During startup, multiple internal routines could try to update the node's own information at the same time, using the same timestamp. The old SQL upsert required a strictly newer timestamp, so these concurrent updates sometimes failed with 'sql: no rows in result set'. The fix uses a more lenient upsert for the local node so that last-write-wins and parameter changes persist even when timestamps collide. It is a reliability/availability fix rather than a vulnerability that external attackers can exploit.

This change makes LND's routing memory (mission control) more resilient: if the database contains damaged or unreadable entries, the node now starts up anyway instead of crashing, and it cleans out the bad entries. The patch itself is defensive and does not introduce an obvious vulnerability, but it silently deletes data, which could hide underlying corruption or, in theory, allow a subtle attacker to manipulate routing history if they could already write corrupt records to the database.

This small change fixes a logic bug in how LND decides whether to create its TLS certificate and private key. Previously, if either the certificate or the key file existed, the program skipped creating a new pair and tried to handle encryption settings instead. After the fix, it only skips creation when both files exist. The old behavior could leave LND running with a mismatched certificate/key pair (for example, a new certificate paired with an old key, or vice versa), which can break TLS connections to the node or, in rare cases, affect how private keys are protected on disk.

This commit only adds a new test file that reproduces a bug: when LND's TLS manager finds only one of its two TLS files (either the certificate or the private key) on disk, it wrongly assumes the other file also exists and skips generating a fresh pair. That leaves the node unable to start or serve TLS correctly. The commit does not include the actual fix, only the failing/regression test.

This commit adds a new piece of information—the block height at which a commitment transaction was confirmed—to the data structures used when resolving Lightning Network channel closes. It does not change any security-critical logic by itself; it is a data plumbing change that makes the confirmation height available to auxiliary contract resolvers. There is no direct vulnerability visible in the diff, but it could be a prerequisite for a future fix or feature that depends on knowing this height accurately.

This commit changes only a single line of code comment text in the contractcourt package. It rewords a comment to more accurately describe that a report field is being updated with a calculated maturity height, rather than a confirmation height. No executable code, logic, or data flow was modified.

This commit is a routine code cleanup: it removes an unused Go interface called DB from the graph package and replaces its one remaining use with a direct pointer to the concrete ChannelGraph type. There is no change to program logic, data handling, or security behavior.

This commit adds a new gRPC API endpoint called SendOnionMessage to the LND Lightning node, along with a matching subscription stream for incoming onion messages. It only changes the protocol definition and generated code; it does not include the actual server-side implementation that would process these messages. Because the implementation is missing, the change by itself does not create or fix a security vulnerability, but it does expose a new network-facing capability that will need careful review once the backend logic lands.

This commit fixes a single-character typo in the user documentation. The command example showed '-multi_file' instead of the correct '--multi_file'. It does not change any code, commands, or security behavior.

This commit fixes a broken hyperlink in a documentation file. The old URL was missing a slash between 'master' and 'docs', making it invalid. The fix replaces it with a proper relative link. There is no code change and no security impact.

This is a one-character logging fix. The developer changed a debug log message from using %x (which prints data as hexadecimal) to %s (which prints as a regular string). It does not change program behavior, fix a crash, or address any security issue. It is purely a cosmetic/log readability correction.

This commit is a straightforward code cleanup that renames the existing `lnwire.NodeAnnouncement` struct to `lnwire.NodeAnnouncement1` across the LND codebase. The commit message explicitly states this is preparation for adding a new `NodeAnnouncement2` struct and a shared interface. No security behavior is changed, no bug is fixed, and no vulnerability is introduced or patched.

This commit simply renames an internal helper method from a longer name to a shorter one (allNonSignatureRecordProducers -> nonSignatureRecordProducers) and updates the three places that call it. There is no change to program logic, data handling, or security behavior.

This change is a routine performance optimization, not a security fix. The developer replaced a temporary 12-byte nonce buffer that was repeatedly created on the fly with a fixed buffer stored inside the encryption state struct. This removes almost all memory allocations during message encryption/decryption and makes the code faster, but it does not change what data is encrypted or how keys are managed.

This commit adds the remote peer's public key to an internal data structure (AuxChanState) used by external components to look up custom channel records. Public keys are not secrets, and the change only exposes information that was already available elsewhere in the channel state. There is no indication this fixes a vulnerability or changes security behavior.

This commit only adds a new Go interface definition with no actual implementation or logic. It defines hooks that future code could use to inject custom data during Lightning channel setup and to react when a channel becomes ready. There is no executable code, no change to existing behavior, and no security issue visible in this patch.

This patch teaches LND to recognize a second type of Bitcoin network fee-rejection error ('minimum relay fee not met') alongside the one it already handled ('mempool minimum fee not met'). Without the change, transactions rejected for the new reason would not be retried or fee-bumped automatically, potentially leaving channel-closing or penalty transactions stuck instead of being rebroadcast with a higher fee.

This commit adds support for a new type of Bitcoin fallback address (P2TR, also known as Taproot) when encoding and decoding Lightning Network payment invoices. Previously, LND could not include or read Taproot fallback addresses in invoices. This is a feature addition rather than a clear security fix, but missing support could have caused payment failures or forced users onto older address types when Taproot was preferred.

This commit is a small internal code cleanup in the LND lightning node software. It changes several functions so they receive a short channel identifier (SCID) directly by value instead of by pointer. There is no user-facing behavior change, no bug fix, and no security-relevant change visible in the diff.

This commit refactors how one Lightning network message type (AnnounceSignatures2) is encoded and decoded, switching it from a fixed-field format to a more flexible Type-Length-Value (TLV) format. The change is primarily a code modernization and protocol-alignment refactor. There is no direct evidence in the commit or supplied references that this fixes an active security vulnerability.

This commit only fixes code style issues flagged by a linter. It adds punctuation to comments and reformats a test function call to fit line-length rules. There are no changes to program logic, security behavior, or how payments are processed.

This commit only renames a test helper function from `assertPaymentstatus` to `assertDBPaymentstatus` and updates all call sites in test files. It makes no changes to production code, user-facing behavior, or security logic. There is no security relevance.