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 removes a separate CI build step that tested the project with a special 'taproot' compiler flag. It is a workflow cleanup change, not a code change. There is no indication of a security vulnerability.
This commit fixes a simple coding mistake in LND's GetNetworkInfo RPC. When building network statistics, if the code encountered a channel it had already counted, it accidentally stopped processing that node's remaining channels instead of…
No security framing in commit message or release notesBug is a logic/correctness error causing under-reported statisticsNo input validation, authorization, memory safety, or cryptographic issues evident
This commit fixes a missing length check when creating BOLT11 Lightning invoices. Before the fix, a user or attacker could supply payment metadata longer than the 639-byte BOLT11 limit, producing an invoice that violates the protocol and m…
Missing input validation on BOLT11 invoice metadata lengthProtocol compliance violation: tagged field exceeds 639-byte BOLT11 limitNew error variant CreationError::PaymentMetadataTooLong introduced
This commit only fixes a comment describing a Lightning Network routing parameter. It changes no actual code logic, so it cannot affect security or behavior.
This is a tiny code cleanup that removes two unnecessary .clone() calls in a Lightning channel implementation. It does not change behavior, fix a bug, or address any security issue. It is purely a performance/maintainability micro-optimiza…
This commit only changes where and how debug log messages are printed during peer reconnection. It moves a single log line deeper into the code and adds more detailed logging for each type of reconnection message. There is no change to pro…
This commit is a straightforward code cleanup in the project's test suite. It replaces a Rust macro used only in tests with an equivalent regular function. There is no change to the actual Lightning node logic that runs in production, and …
This commit is a straightforward code cleanup in the project's test suite. It removes a helper macro used only in tests and replaces it with direct calls to an existing function. There is no change to the actual Lightning node logic that r…
This commit is a straightforward code cleanup in the project's test suite. It replaces a Rust macro called `check_closed_broadcast!` with direct calls to an equivalent function. Macros are a shorthand in Rust; replacing them with normal fu…
This commit is a minor cleanup of internal test code. It removes redundant calls that explicitly set a default test configuration for Lightning channel managers, replacing them with simpler 'None' values that now produce the same default. …
This commit is a minor cleanup of an internal test file. It replaces a small block of test code with an existing helper function when testing the non-zero-conf path. There is no change to production code, no security fix, and no user-facin…
This is a small documentation and test cleanup commit. It removes leftover references to a 'manually_accept_inbound_channels' configuration option from two test files and a pending changelog entry. There is no code behavior change and no s…
This commit changes the default setting so that new Lightning channels will use 'anchor outputs' whenever possible. Anchor outputs are a safer, more modern channel type, but they require the user to keep some on-chain bitcoin available to …
Default channel type changed to anchor outputs, which alter fee-bumping assumptionsInbound channels now require manual acceptance to ensure user awareness of reserve requirementsDocumentation explicitly warns that users must maintain an on-chain reserve for force-close fee bumping
This commit is a pure test-code refactoring. It renames the default test channel configuration because anchor channels became the production default, and updates many tests to explicitly use a new 'legacy' configuration where they previous…
This commit removes the automatic acceptance of incoming Lightning channels in the LDK library. Previously, users could set a flag to automatically accept inbound channel requests. Now, every inbound channel request must be explicitly appr…
Removal of automatic inbound channel acceptance pathMandatory manual approval via Event::OpenChannelRequestPreparation for anchor channels default, requiring on-chain fee reserve awareness
This commit fixes a small boundary error in how Lightning Dev Kit counts peers that have unfunded channels. Previously, the software rejected new channel requests one peer too early, meaning legitimate users could be blocked from opening a…
Logic boundary error in resource-limit enforcementDenial-of-service-like effect: legitimate channel open requests rejected prematurelyFix is minimal and targeted at a single comparison operator
This commit removes a time-limited 'experiment period' for a new Lightning network signaling feature called 'accountable' (previously 'endorsement signal'). Previously, nodes would only relay this signal until a fixed date in 2026, after w…
Removal of time-based feature gatingChange to default privacy behavior of a protocol signalRenaming of experimental protocol feature
This commit is a pure rename of an experimental Lightning Network feature from 'endorsement' to 'accountable/accountability' to match a community proposal update. No security vulnerability is introduced or fixed; the underlying behavior, f…
This commit is a simple code cleanup: it turns an internal macro (a reusable code snippet) into a regular Rust method. The actual behavior of the program does not change. There is no security fix or vulnerability here.
This commit is a pure internal refactoring of the project's test code. It removes a Rust macro named `check_added_monitors!` and replaces every call with an identically-named regular function `check_added_monitors(...)`. There is no change…