Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This commit simply adds a new PGP public key for a person named 'gijswijs' to the list of keys used by LND's release verification script. It does not change any code that handles money, network connections, or cryptography beyond registeri…
This commit adds a safety valve to how LND handles 'onion messages'—a type of private Lightning Network message. Before this change, a flood of onion messages from a peer could fill up an internal queue and stall the connection handler. No…
Adds backpressure/RED-based probabilistic dropping to prevent unbounded mailbox growth for onion messagesReplaces unbounded context.TODO() with a 30-second timeout around actor Tell to avoid readHandler stallsComment frames change as preventing a blocked readHandler, indicating prior stall risk
This commit adds a new optional mailbox type and factory hooks to the actor framework. It is a feature/refactoring change: it lets callers choose a backpressure-aware mailbox that can deliberately drop messages under load. There is no indi…
No security-relevant signals: change is a feature addition, not a vulnerability fix.No bounds of trust changed; new mailbox is opt-in via factory injection.No sensitive data exposure, authentication, authorization, or cryptographic changes.
This commit adds a brand-new generic queue helper called BackpressureQueue with a Random Early Drop (RED) option. It is purely a new building block for managing overload: when a queue gets too full, some incoming items are dropped early ra…
This is a trivial code cleanup commit that adds a blank line to satisfy a Go linter rule. It does not change program behavior, fix a bug, or address any security issue.
This commit adds a separate onion-message router that deliberately skips the usual replay-protection logging used for payment routing. The change is intentional and documented: onion messages are not payments, so replay protection is consi…
New code path uses a no-op replay log for onion-message sphinx processingExisting payment sphinx processor is renamed but otherwise unchangedOnion messages are explicitly treated as non-payment traffic
This commit adds the ability for LND nodes to forward encrypted 'onion messages' through intermediate peers, rather than only sending them directly. It introduces new actor-based code for routing these messages, expands the RPC API respons…
New network-facing message forwarding path addedSphinx/onion cryptography used for decryption and routingRPC response now exposes encrypted recipient data and custom TLV records
This commit adds a small in-memory cache to speed up repeated lookups of which node public key belongs to a given short channel ID (SCID). It is a performance optimization, not a security fix. There is no evidence in the commit or supplied…
This commit adds new code to LND that handles a new kind of Lightning network message called an 'onion message payload.' It is a feature addition, not a fix. The code reads and writes message fields such as reply paths, encrypted recipient…
New network message parser added to lnwire packageTLV decode preserves unknown final-hop records (type >= 64), which could affect protocol behavior if validation is incomplete elsewhereReply path length is decoded from a single uint8 and checked against the remaining byte length via l > 67
This commit adds a new subsystem for handling 'onion messages' in the LND Lightning node. Onion messages are a way to send data through the Lightning network without a payment. The change introduces a per-peer actor that decodes, routes, a…
New network-facing message handling path added (onion messages)Use of actor framework for per-peer concurrency isolationBlinded route processing and ephemeral key derivation
This commit adds a new helper function in LND's code for constructing routing data used in a privacy-preserving messaging feature called 'blinded routes' for onion messages. It is a pure code addition with no obvious security bug, no fix o…
This commit adds a new user-configurable switch that lets an LND node operator turn off support for "onion messages" (a type of Lightning network control message). When the switch is enabled, the node stops advertising that it supports the…
Adds an opt-in denial-of-service mitigation by allowing operators to disable an optional network featureDoes not change default behavior; nodes must explicitly enable the flagNo removal of existing validation, authentication, or resource limits for nodes that do not set the flag
This commit is a documentation-only edit to the release notes for LND version 0.21.0. It rewords a bullet point about a new 'onion messaging forwarding' feature and adds a link to an additional pull request. No code, configuration, or secu…
This commit updates a core Lightning Network library (lightning-onion) to a new version that adds 'onion-messaging support.' It also adjusts LND's own code to match renamed constants and functions in that library. The change is presented a…
Dependency update of a cryptographic/onion-routing library to a new minor versionAPI rename from MaxPayloadSize to MaxRoutingPayloadSize and introduction of DecodeHopPayload with tlvGuaranteed flagCommit message frames change as feature addition ('onion-messaging support'), not a security fix
This change only adjusts internal test code to fix timing-related flakiness in two watchtower client tests. It does not modify production code, so it has no direct security impact on running LND nodes.
This commit only changes a test file, increasing a timeout from 10 seconds to 60 seconds during automated tests. It is not a security fix and does not affect the production LND software that users run.
This commit fixes a build tooling issue where running the code linter inside a git worktree failed to compare changes against git history. It is a developer-experience fix for the Makefile and does not change any runtime code, network beha…
This commit fixes a logic bug in a small helper function called FlatMap used inside the LND codebase. FlatMap is supposed to transform a successful value and pass through failures unchanged. The old code did the opposite: it left successes…
Logic inversion in error-handling primitivePotential for error values to be passed where success values are expectedPotential for successful results to bypass intended validation/transformation
This commit adds new RPC endpoints to LND that allow users to send and receive 'onion messages'—a type of privacy-preserving Lightning network message. The change is a feature addition, not a bug fix. There is no indication in the commit o…
New network-facing RPC endpoints added with offchain read/write permissionsRaw onion blobs are forwarded peer-to-subscriber without visible payload validation in this patchNo rate limiting, authentication beyond macaroons, or size bounds visible in the diff
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 incl…
New network-exposed RPC surface added (SendOnionMessage / SubscribeOnionMessages)Raw onion packet bytes accepted from API caller with no visible validation in this commitBlinded-path path_key is exposed to the API and forwarded to peer logic