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 adds a new automated integration test for the LSPS1 (Lightning Service Provider Specification 1) feature in the rust-lightning project. It does not change any production code, only test code. There is no security issue here.
This commit only adds new tests and a test helper for the 'manual broadcast' funding flow in a Lightning network library. It does not change production behavior, fix a bug, or alter security-critical code. The tiny code change in channelmo…
This patch fixes a logic bug in rust-lightning's channel monitor for manually-broadcast funding transactions. Previously, the monitor could try to claim outputs and watch for spending transactions before the funding transaction had actuall…
Pre-confirmation output claiming in manual-broadcast channelsPotential duplicate claim generation during block processingState consistency fix in channel monitor claim tracking
This patch fixes a logic gap in Lightning Dev Kit's channel monitoring. When a user manually chooses not to broadcast their side of a new channel immediately, the code was supposed to queue that broadcast for once the funding transaction i…
Funds-safety / liveness issue in channel state machineMissing automatic broadcast of holder commitment after funding confirmationManual-broadcast code path only
This commit adds internal bookkeeping to LDK's channel monitor so it can tell whether a channel uses 'manual' funding-transaction broadcasts and whether that funding transaction has actually appeared on-chain yet. The goal is to stop the n…
Prevents premature holder commitment broadcasts for channels whose funding transaction is not yet on-chainAdds backward-compatible persistence for new channel-monitor stateDefensive fix for LSPS2 client_trusts_lsp=true scenario where LSP may defer funding broadcast
This change fixes a logic bug in Lightning Dev Kit's channel monitor. When a user manually broadcasts their own funding transaction (rather than letting LDK do it automatically), the software could previously try to broadcast a commitment …
Prevents broadcast of unconfirmable holder commitment transactions in manual-funding modeAvoids spurious Event::BumpTransaction notifications for transactions dependent on unseen fundingAdds explicit override API with documented risk of unconfirmable broadcasts
This commit fixes a bookkeeping flag in the Lightning channel monitor. The flag `funding_seen_onchain` was not being set when the funding transaction was observed on the blockchain, even though the code already detected it. Setting the fla…
State flag not updated despite on-chain detectionChannel monitor internal consistency fixCould affect safety checks that depend on funding_seen_onchain
This commit is purely a code formatting cleanup. It removes a `#[rustfmt::skip]` annotation and lets rustfmt reformat the `broadcast_latest_holder_commitment_txn` function. There is no change to program logic, behavior, or security.
This commit adds a new LSPS2 trust model called client_trusts_lsp. In this model, a Lightning Service Provider (LSP) delays broadcasting the Bitcoin funding transaction for a new channel until the client has actually paid the channel-openi…
New manual-broadcast funding path in ChannelManager with validation but no automatic broadcastLSPS2 service defers funding broadcast until opening fee is collectedGuard that skips broadcast if ChannelManager channel is no longer ready
This commit adds a new access-control rule to the LSPS5 (webhook) service in rust-lightning. Before accepting a state-allocating LSPS5 request such as 'set webhook', the service now requires proof that the requesting peer is already 'engag…
New access-control gate for state-allocating LSPS5 requestsNew protocol error code LSPS5_NO_PRIOR_ACTIVITY_ERROR_CODE (1003) and enum variant NoPriorActivityErrorAddition of has_active_requests() on LSPS1/LSPS2 service handlers to detect active peer flows
This commit changes the LSPS5 webhook notification cooldown from 1 hour to 1 minute. The shorter cooldown means the same type of notification can be sent to a client's webhooks far more frequently. This is not a code vulnerability in itsel…
Rate-limiting threshold relaxed by 60x (1 hour -> 1 minute)Webhook notification spam now easier due to shorter cooldownNo input validation or additional throttling added to compensate
This commit changes the project's GitHub Actions build configuration for Windows only. It tells the Rust compiler to use an alternative linker (rust-lld) instead of the default Windows link.exe, because the Windows CI builds were failing t…
This commit is a small internal code cleanup. It makes a date/time wrapper type copyable by value instead of requiring an explicit clone, and removes a few now-unnecessary `.clone()` calls. There is no security-relevant change and no user-…