LND

This commit is a one-word documentation update. It adds 'Graph' to the list of subsystems that support native SQL tables in the description of a configuration option. There is no code behavior change, no bug fix, and no security relevance.

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 is a one-line documentation update to the sample configuration file. It adds 'Graph' to a comment listing which LND database subsystems support native SQL tables. There is no code change, no behavior change, and no security relevance.

This change is a build-script hardening fix, not a security vulnerability. It makes the release script prefer GNU gzip over the default macOS BSD gzip so that release tarballs are byte-for-byte identical (reproducible) across different developer machines. There is no attacker-controlled behavior or user data at risk.

This commit adds a new message type, NodeAnnouncement2, for a future Lightning protocol feature called Gossip 2 (or 1.75). It is purely a code addition that defines how the message is formatted, encoded, and decoded. There is no indication this fixes a security bug or introduces a vulnerability; it is normal feature development.

This commit adds the ability to encode and decode DNS network addresses as a new optional data field (TLV record) inside Lightning protocol messages. It is a straightforward feature addition with no security-relevant behavior change; it only prepares a data type for future use and includes tests.

This commit adds a new optional 'inbound fee' field to an experimental Lightning Network message type called ChannelUpdate2. The commit message explicitly states this message type is not used in production, and the field uses a temporary placeholder type number (55555) with a TODO to pick the correct one later. There is no security issue visible in the change itself.

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 updates LND's implementation of a Lightning network protocol message called channel_announcement2 to include the funding transaction outpoint, matching a recent specification change. It is a straightforward protocol-compliance change with no apparent security vulnerability or fix.

This commit adds a new helper data type for encoding transaction outpoints (a reference to a specific output of a Bitcoin transaction) in a special message format called TLV, which is used inside Lightning Network protocol messages. It is purely additive: it introduces a new wrapper type, its encoder/decoder, and unit tests. There is no bug fix, no change to existing logic, and no security-relevant behavior described in the commit or diff.

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 commit only creates an empty release notes template for LND version 0.21.0. It contains headings and a table of contents, but no actual content describing bug fixes, features, or any code changes. There is nothing that affects the security or functionality of the software.

This commit only adds a sentence to the release notes stating that Tor v2 onion service support is deprecated and the `--tor.v2` option will be hidden. It is a documentation-only change with no code modifications.

This commit marks the `tor.v2` configuration option in LND as deprecated. Tor v2 onion services are an older, weaker addressing format that the Tor network itself has made obsolete. The change hides the option from help text and warns users to switch to v3 onion services. It is a deprecation/cleanup patch, not a fix for an active software vulnerability in LND itself.

This commit only changes version numbers in a single source file to mark the start of a new release candidate (v0.20.0 rc1). It does not modify any program logic, network behavior, cryptography, or user-facing features. There is no security relevance in the change itself.

This commit only adds a release notes entry describing a prior code refactoring. It changes a single documentation file, adding a bullet point about making channel graph updates more memory-efficient and adding a contributor's name. There is no code change and no security relevance.

This commit is a code-quality refactor, not a security fix. It changes several database iterator functions so they return a Go 1.23-style Seq2 iterator that can carry errors, instead of returning an error separately when the iterator is first created. The practical effect is that errors that used to be silently swallowed or only logged during iteration are now surfaced to callers. There is no vulnerability being patched here; it is a defensive improvement that makes future failures easier to detect.

This is a small test-only change that adds two comment lines to a mock implementation in a test file. It does not alter any production code, network behavior, or security logic.

This commit refactors how LND's gossip syncer sends old channel updates to a peer. It switches from eagerly reading all updates into memory and launching a goroutine every time, to a lazy pull-iterator that only starts a goroutine if there is at least one update. The main benefit is lower memory and CPU usage, but the change also touches concurrency, error handling, and iterator ownership, which could hide subtle bugs.

This commit refactors an internal LND gossip method to return a lazy iterator instead of a fully built list of network messages. The goal is to reduce memory use when syncing large amounts of routing gossip. It is a code-quality/performance change, not a fix for an active security bug. There is no evidence in the commit or supplied references that it addresses a disclosed vulnerability.

This is a small internal code cleanup in the Lightning Network Daemon (LND). It switches two functions to use newer memory-efficient iterator APIs and removes some redundant filtering logic. There is no indication this fixes a security bug or introduces a vulnerability; it appears to be a refactoring change.

This commit only adds and improves unit tests for database iterator functions in LND's graph database. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit rewrites a database query method in the LND Lightning node so it returns results in smaller batches using a new iterator-style API, instead of loading everything into memory at once. It adds SQL pagination and batch caching. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a performance and memory-efficiency improvement.

This commit changes how LND's SQL database backend fetches lists of Lightning network nodes that were updated within a time window. Previously it loaded all matching nodes into memory at once; now it pages through them in batches using a database cursor. The change is mostly a performance and memory improvement, but it also slightly alters behavior: the end time is now inclusive rather than exclusive, and an optional filter for 'public nodes only' was added. There is no clear security bug, but the new SQL pagination logic is complex and could in theory skip or duplicate rows if the cursor handling has an edge-case bug.

This commit is a routine performance refactor: it changes a database query method to return results one at a time through an iterator instead of loading everything into a giant list. That reduces memory use for large results but does not fix or introduce any security vulnerability. There is no mention of security, bugs, or attacks in the commit itself.