LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Repository coverage

1687 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

186security candidates236second-pass queue1372AI analyses
162commits · 30 days
277commits · 60 days
643commits · 180 days
1422commits · 365 days
Backfill bands
Aug 5 → Feb 6405 seen5 candidatesComplete
Feb 6 → Jun 6665 seen28 candidatesComplete
Jun 6 → Jul 689 seen4 candidatesComplete
Jul 6 → Aug 569 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
387Strong · 80–100
837Adequate · 60–79
432Thin · 40–59
31Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Olaoluwa Osuntokun29659235474
ziggie49922422265
Elle Mouton26832268167
Yong60926172
ziggieXXX50617170
George Tsagkarelis37335167
LNBiG111173
Jared Tobin909171
yyforyongyu1211574070
bitromortac731154071
Erick Cestari26726070
Suheb746074
Analysis record

Published AI watches

Last scanned 48 minutes ago

Low 43 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11588 from ziggie1984/lnwallet/fix-reorg-wallet-sync-flake

This change fixes a wallet synchronization check in LND. Previously, the wallet only compared block heights to decide if it was fully caught up with the Bitcoin chain. During a chain reorganization (a temporary fork where one block is repl…

State synchronization check previously used height only, which is insufficient across reorgsFix adds block hash comparison to prevent false-positive sync statusCould cause LND to proceed while wallet state reflects an invalidated or not-yet-updated chain tip
8cdbf85cby Yong+224−1354 files
Vendor flagged security relevance
Moderate 51 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #10708 from jtobin/alias-perms

This commit fixes a missing permission check on a new Lightning routing RPC called XFindBaseLocalChanAlias. Without the entry, any valid macaroon could call that RPC, bypassing the normal access-control list. The patch adds the required pe…

Missing macaroon authorization entry for an RPC endpointPotential privilege escalation: any valid macaroon could invoke an unprotected RPCRegression test added to enforce macPermissions coverage
98dc2b44by Olaoluwa Osuntokun+35−02 files
No security note in commit
Moderate 68 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11555 from yyforyongyu/invoice-settlement-public

This large LND patch changes when an ordinary invoice is considered 'paid'. Previously, releasing the preimage (the secret that lets the payer claim the funds) immediately marked the invoice as settled. Now the invoice enters a new interme…

New intermediate invoice/HTLC state prevents premature settlement reportingOn-chain HTLC outcomes persisted without opt-in to support restart recoveryForwarding package marker persisted before preimage release to avoid replay rejection on restart
895118acby Olaoluwa Osuntokun+4536−32048 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

docs: describe invoice collection finality

This commit only adds documentation to the release notes. It describes a previously merged code change (PR 11555) about how LND handles invoice finality, but the commit itself contains no code, bug fixes, or behavior changes. There is noth…

9649d9f6by yyforyongyu+87−01 file
No security note in commit
Moderate 64 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11551 from ziggie1984/public-pr149-sanitized

This change fixes a bug in LND's invoice handling for multi-part payments (MPP and AMP). When a payment is split into several pieces (HTLCs), each piece is accepted individually. Previously, an old accepted piece could become too close to …

Fixes missing revalidation of accepted HTLC CLTV expiries at MPP/AMP set completionPrevents settlement of shards whose on-chain claim window has become unsafe while heldAdds new fail resolution ResultHtlcSetExpiryTooSoon and cancels the entire affected set
4b7447bcby Yong+281−347 files
Vendor flagged security relevance
Low 35 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11396 from yyforyongyu/task-lease-policy

This commit changes how LND's wallet locks (leases) unspent coins through its RPC interface. It removes a recently added 'release after N confirmations' option and replaces it with an explicit 'no expiry' flag. Old clients that still send …

Breaking API change that reserves removed protobuf fields to prevent accidental reintroductionExplicit rejection of legacy `release_after_spend_confs` parameters from old clients instead of silent fallbackValidation prevents conflicting no-expiry + duration lease settings before wallet state is touched
03e28a96by Yong+663−4029 files
Vendor flagged security relevance
Low 40 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-store

This commit refactors how the Lightning Network Daemon (LND) stores and queries channel graph data so that the same channel or node can exist under both old (v1) and new (v2) gossip protocols without the database returning stale, missing, …

Cross-version data consistency: prevents a v2 channel shell from shadowing a usable v1 channel, which could affect routing decisions and RPC output.Cache consistency: ensures the in-memory pathfinding cache and the SQL-backed RPC reads agree on which channel version and policies are active.Bug fix: zombie edge info now carries the correct channel ID instead of 0, which could have caused incorrect channel identification during resurrection.
8c251687by Yong+3752−28726 files
No security note in commit
Moderate 61 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11440 from Roasbeef/fix-longstanding-correctness-bugs

This is a large bug-fix patch for LND (a Bitcoin Lightning Network node) that tightens correctness rules across many subsystems. It prevents several ways a node could mis-handle channel data, accept bad network gossip, commit corrupted dat…

Database transaction commit now aborts on read errors (etcd) - prevents silent data corruption / inconsistent stateGossip zombie marking removed for invalid funding script - prevents denial-of-service / channel graph poisoningWire message length bounding added to watchtower protocol - prevents memory exhaustion / malformed message parsing
0123a548by Olaoluwa Osuntokun+1424−11938 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

invoices: require complete payment collection

This commit changes how LND handles multi-part Lightning payments when one part fails after the preimage was already released. Previously, the invoice could be marked as fully paid even if one shard was later reclaimed by the payer on-chai…

Changes invoice settlement semantics for released-but-failed HTLCsAdds new persisted HTLC state `HtlcStateFailed`Prevents invoice from reaching `ContractSettled` when any released shard fails
699ea930by Olaoluwa Osuntokun+492−4910 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet: reject a zero CSV delay

This change tightens the rules for opening Lightning payment channels by refusing a setting called the CSV delay when it is set to zero. The CSV delay is the waiting period a user must endure before reclaiming their own funds from a channe…

Rejects a zero CSV delay that would eliminate the breach-remedy windowCentralizes the check in VerifyConstraints so all channel types and directions are coveredAdds explicit error type and unit test for the new constraint
266eba7bby Olaoluwa Osuntokun+81−03 files
Vendor flagged security relevance
Moderate 58 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet+chanstate: keep persisted HTLC data readable

This commit fixes two bugs in how Lightning Network channel data is saved to disk. First, it stops extra 'aux' signatures meant only for advanced taproot channels from being saved on ordinary channels, where they don't belong. Second, it p…

Persisted state could become unreadable due to writer/reader size mismatchAuxiliary signatures for taproot overlay channels were persisted on plain channel HTLCsFix adds explicit serialization bound to prevent unreadable channel records
43c74723by Olaoluwa Osuntokun+101−25 files
No security note in commit
Low 39 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11374 from bitromortac/20261016-c7e5-dispatch

This commit adds the first end-to-end BOLT 12 'Offers' flow to LND: a new dev-only RPC and CLI command to create offers, plus a dispatcher that listens for incoming onion-message invoice requests and replies with signed BOLT 12 invoices. I…

New network-facing dispatcher answers invoice requests from any peer; rate and concurrency limits are appliedBlinded-path PathID check prevents reply linking to self-created paths, but TODO notes the check should move once offers can have offer_pathsCreateOffer RPC is restricted to dev builds and requires offchain:write macaroon permission
a9d4ca3bby bitromortac+3113−7838 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: reject settled AMP set shards

This change fixes a bug in LND's invoice handling for AMP (Atomic Multi-Path) payments. Previously, if someone tried to pay a fresh shard for an AMP set that was already fully paid, the invoice updater could return an internal error that w…

Denial-of-service vector: an internal updater error could force-fail a shared channel link, disrupting unrelated sibling HTLCsAMP invoice state machine edge case: reusable invoice stays open for other sets but must reject new shards for already-settled setsClean failure path introduced: ResultInvoiceNotOpen instead of error-driven link failure
99e3da37by yyforyongyu+49−02 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11282 from lightningnetwork/elle-base-branch-payment-service

This is a large feature merge for LND that adds a new optional RPC subsystem called switchrpc. It lets an external program hand a pre-built onion packet to LND for direct dispatch over a Lightning channel, instead of LND doing its own path…

New optional RPC surface (switchrpc) that accepts externally crafted onion packets and directly dispatches HTLCsIdempotency/deduplication added via InitAttempt durable write-ahead log and ErrPaymentIDAlreadyExistsStartup orphan cleanup fails half-open or pre-commit attempts to avoid hangs
11f79be0by Olaoluwa Osuntokun+11385−22458 files
Vendor flagged security relevance
Low 44 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11472 from yyforyongyu/task-sweep-rejections

This commit fixes a bug in LND's transaction sweeping logic. Previously, if the Bitcoin backend rejected a sweep transaction for a temporary or unknown reason (for example, the mempool was full, a network error occurred, or the rejection r…

Funds-availability / liveness fix: temporary or unknown mempool rejections could leave sweep inputs unspent.Error-handling reclassification: previously fatal errors now retryable.Retry metadata preservation: next fee rate and fee cap kept across attempts.
c5863e55by Yong+290−9720 files
No security note in commit
Low 32 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-op

This change is a hardening fix for LND's remote-signing feature. Previously, if a node was configured to act as an outbound remote signer but was compiled without the required 'signrpc' and 'walletrpc' sub-servers, it would silently fall b…

silent-degradation-to-no-op preventedconfiguration-misconfiguration now surfaces as fatal errorbuild-tag-dependency explicitly validated at runtime
0c538e1fby Suheb+241−125 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: fix test whitespace

This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no securit…

a67d07f4by yyforyongyu+1−11 file
No security note in commit
Low 31 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: pin the new lint job actions by commit

This change updates two GitHub Actions used in the project's automated lint workflow so they are locked to specific commit hashes instead of floating version tags. A floating tag could be silently repointed to a different, possibly malicio…

CI/CD supply-chain hardeningthird-party action pinning by commit hashprevention of tag-movement attacks
2a9f137dby Olaoluwa Osuntokun+4−21 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: fix the custom linter cache wiring for CI

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security f…

6f665663by Olaoluwa Osuntokun+30−82 files
No security note in commit
Moderate 66 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11482 from Roasbeef/pub/unsigned-acked-wrap

This patch fixes a database bug in the Lightning Network Daemon (LND) where very long lists of unsigned, acknowledged channel updates could be silently truncated when saved to disk. Because the storage format used a 16-bit counter, lists l…

Integer truncation / wrap-around in serialization format (uint16 count)Silent data loss on restart due to undersized length fieldDefensive deserialization with count-modulo validation
7431093fby Olaoluwa Osuntokun+218−127 files
Vendor flagged security relevance
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateMerge pull request #10708 from jtobin/alias-permsby Olaoluwa Osuntokun · 98dc2b44 · Nov 13, 2026 · 2 filesMessage 68 · AdequateModerate 51Details
Commit message · Olaoluwa Osuntokun

Merge pull request #10708 from jtobin/alias-perms

routerrpc: add XFindBaseLocalChanAlias to macPermissions

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege statemerge-commit duplicate discount
AI analysis · Moderate 51/100

This commit fixes a missing permission check on a new Lightning routing RPC called XFindBaseLocalChanAlias. Without the entry, any valid macaroon could call that RPC, bypassing the normal access-control list. The patch adds the required permission and a regression test that ensures every Router RPC has a matching permission entry.

Security candidateMerge pull request #11555 from yyforyongyu/invoice-settlement-publicby Olaoluwa Osuntokun · 895118ac · Nov 12, 2026 · 48 filesMessage 73 · AdequateModerate 68Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11555 from yyforyongyu/invoice-settlement-public

invoices: settle after complete HTLC collection

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 68/100

This large LND patch changes when an ordinary invoice is considered 'paid'. Previously, releasing the preimage (the secret that lets the payer claim the funds) immediately marked the invoice as settled. Now the invoice enters a new intermediate 'PENDING_SETTLE' state and only becomes 'SETTLED' once every released HTLC is finally resolved on-chain or off-chain. If a released HTLC is instead reclaimed by the payer on-chain, the invoice can become 'CANCELED' while keeping any funds that did arrive. The change also persists on-chain HTLC outcomes even when the optional final-resolution storage is disabled, so restart recovery can tell a successful claim from a reclaim. This is a defensive correctness fix: it prevents a merchant from treating a payment as complete before it is truly irreversible, which could lead to shipping goods for a payment that later fails.

Security candidatedocs: describe invoice collection finalityby yyforyongyu · 9649d9f6 · Nov 11, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · yyforyongyu

docs: describe invoice collection finality

Document final collection states, release history and retained partial
payments. Explain cancellation, RPC behavior, cleanup and upgrade and
downgrade constraints.

Signed-off-by: yyforyongyu <yong2452@gmail.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustdocumentation-only discount
AI analysis · Informational 15/100

This commit only adds documentation to the release notes. It describes a previously merged code change (PR 11555) about how LND handles invoice finality, but the commit itself contains no code, bug fixes, or behavior changes. There is nothing in this commit that introduces or fixes a security issue directly.

Security candidateMerge pull request #11551 from ziggie1984/public-pr149-sanitizedby Yong · 4b7447bc · Nov 11, 2026 · 7 filesMessage 73 · AdequateModerate 64Details
Commit message · Yong

Merge pull request #11551 from ziggie1984/public-pr149-sanitized

invoices: revalidate accepted htlc expiries at set completion

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 64/100

This change fixes a bug in LND's invoice handling for multi-part payments (MPP and AMP). When a payment is split into several pieces (HTLCs), each piece is accepted individually. Previously, an old accepted piece could become too close to its expiry while waiting for the remaining pieces to arrive. Once the final piece arrived and completed the set, LND would settle all pieces without rechecking their expiries. This could let a piece be settled on-chain with too little time left, potentially causing funds loss if the on-chain claim fails to confirm in time. The fix revalidates every accepted piece's expiry at the moment the set completes, and cancels the whole set if any piece is now too close to expiry.

Security candidateinvoices: require complete payment collectionby Olaoluwa Osuntokun · 699ea930 · Nov 10, 2026 · 10 filesMessage 80 · StrongModerate 59Details
Commit message · Olaoluwa Osuntokun

invoices: require complete payment collection

In this commit, we distinguish failed released HTLCs from attempts
canceled before preimage release. Once every released HTLC has a final
outcome, an ordinary invoice is settled only if all were collected.
Otherwise we cancel it while retaining the amount actually received.
Persisting the failed state keeps this decision independent of outcome
order and restart.

Expose failed collection and the release decision through RPC. Preserve
the first settlement index when later duplicates finish. Backend,
recovery, replay and RPC regressions cover the persisted outcome
contract. AMP settlement is unchanged.

Signed-off-by: Olaoluwa Osuntokun <laolu32@gmail.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
boot or update path
AI analysis · Moderate 59/100

This commit changes how LND handles multi-part Lightning payments when one part fails after the preimage was already released. Previously, the invoice could be marked as fully paid even if one shard was later reclaimed by the payer on-chain. Now the invoice is canceled when any released shard fails, while still keeping the funds that were successfully collected. This prevents a merchant from incorrectly believing they were paid in full and possibly shipping goods or services based on an invoice that ultimately did not fully settle.

Security candidatelnwallet+chanstate: keep persisted HTLC data readableby Olaoluwa Osuntokun · 43c74723 · Nov 10, 2026 · 5 filesMessage 73 · AdequateModerate 58Details
Commit message · Olaoluwa Osuntokun

lnwallet+chanstate: keep persisted HTLC data readable

In this commit, we tighten two invariants around the HTLC data we write
to disk.

First, we only attach aux signatures to an HTLC on taproot overlay
channels. The aux signer is configured node wide, so it also sees the
commit_sig of plain channels. Those channels never use aux signatures,
and the count check further down is already gated on the tapscript root
bit, but the attach step wasn't: any aux data unpacked for a plain
channel was copied into the HTLC's custom records and persisted with the
commitment.

Second, SerializeHtlcs now refuses to write an HTLC whose onion and extra
data exceed what ReadElement accepts for a variable length byte slice.
Before, the writer had no bound while the reader capped the field at
66,000 bytes, so an oversized HTLC was written without error but made
the whole channel unreadable on the next load. The reader's limit is now
a named constant that the writer checks against.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 58/100

This commit fixes two bugs in how Lightning Network channel data is saved to disk. First, it stops extra 'aux' signatures meant only for advanced taproot channels from being saved on ordinary channels, where they don't belong. Second, it prevents a channel from being saved with an HTLC (a routed payment slot) whose attached data is too large to be read back later, which would previously have made the whole channel unrecoverable on restart.

Security candidateinvoices: reject settled AMP set shardsby yyforyongyu · 99e3da37 · Nov 8, 2026 · 2 filesMessage 78 · AdequateModerate 60Details
Commit message · yyforyongyu

invoices: reject settled AMP set shards

Reject a fresh circuit for an already-settled AMP set through the normal
HTLC failure resolution. This avoids an updater error failing the shared
link and disturbing ordinary sibling payments.

Keep the reusable invoice open for distinct sets and verify that the
rejection changes neither stored shards nor paid value.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
boot or update path
AI analysis · Moderate 60/100

This change fixes a bug in LND's invoice handling for AMP (Atomic Multi-Path) payments. Previously, if someone tried to pay a fresh shard for an AMP set that was already fully paid, the invoice updater could return an internal error that would fail the whole channel link, disrupting other normal payments traveling over the same link. Now, that fresh shard is rejected cleanly as a normal payment failure instead, keeping the channel link and other sibling payments undisturbed. The fix also ensures the already-paid set and accounting remain unchanged.

Security candidateMerge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-opby Suheb · 0c538e1f · Nov 5, 2026 · 5 filesMessage 73 · AdequateLow 32Details
Commit message · Suheb

Merge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-op

Follow-up of #8754: Harden remote signing no op

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarydefensive validationsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 32/100

This change is a hardening fix for LND's remote-signing feature. Previously, if a node was configured to act as an outbound remote signer but was compiled without the required 'signrpc' and 'walletrpc' sub-servers, it would silently fall back to a no-op client. That left the signer node running and appearing healthy while never connecting to the watch-only node, and the watch-only node would wait indefinitely for a signer that never arrives. The patch makes this a fatal startup error with a clear message naming the missing build tags and how to rebuild. It also centralizes the 'is this a signer node?' check so future graduation out of experimental mode only needs one code change.

Security candidateinvoices: fix test whitespaceby yyforyongyu · a67d07f4 · Nov 5, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · yyforyongyu

invoices: fix test whitespace

Add the required blank line after the multiline registry test helper
signature and remove the trailing blank line in the AMP replay test.
This clears the two whitespace lint failures inherited from master.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no security implications.

Security candidatebuild: pin the new lint job actions by commitby Olaoluwa Osuntokun · 2a9f137d · Nov 5, 2026 · 1 fileMessage 92 · StrongLow 31Details
Commit message · Olaoluwa Osuntokun

build: pin the new lint job actions by commit

In this commit, we pin both actions the lint job newly uses by their
commit hash rather than by their mutable major tag, matching how the
other workflows in this repo pin third-party actions. A moved tag can
otherwise change what a lint run executes without any review.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
access controldocumentation-only discount
AI analysis · Low 31/100

This change updates two GitHub Actions used in the project's automated lint workflow so they are locked to specific commit hashes instead of floating version tags. A floating tag could be silently repointed to a different, possibly malicious commit, meaning the project's own build servers might run unexpected code. The patch is a preventive hardening measure, not a fix for an active attack.

Security candidatebuild: fix the custom linter cache wiring for CIby Olaoluwa Osuntokun · 6f665663 · Nov 5, 2026 · 2 filesMessage 92 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

build: fix the custom linter cache wiring for CI

In this commit, we fix two problems in the previous iteration of the
linter build cache.

The gha cache backend reads its credentials from the ACTIONS_RUNTIME_TOKEN
and ACTIONS_RESULTS_URL environment variables, but those are not exposed
to plain run: steps by default. We add the crazy-max/ghaction-github-runtime
step to expose them before the lint steps, otherwise the cache import or
export fails inside the manually invoked docker build.

The docker-container driver that setup-buildx-action installs doesn't
load the built image into the docker image store by default, but the lint
targets run the image with docker run. We add --load so the tagged
lnd-tools image is available to the lint steps.

We also only export the cache from the nightly run (LINT_WRITE_CACHE),
since PR-created caches aren't readable by other PRs and would only
churn the shared cache store. PR and merge queue runs still read the
cache that the nightly run exports.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
credential or privilege state
AI analysis · Informational 15/100

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security fix here; it is purely a build-infrastructure improvement.

Security candidateMerge pull request #11482 from Roasbeef/pub/unsigned-acked-wrapby Olaoluwa Osuntokun · 7431093f · Nov 5, 2026 · 7 filesMessage 73 · AdequateModerate 66Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11482 from Roasbeef/pub/unsigned-acked-wrap

lnwallet: reject oversized unsigned acked update logs

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 66/100

This patch fixes a database bug in the Lightning Network Daemon (LND) where very long lists of unsigned, acknowledged channel updates could be silently truncated when saved to disk. Because the storage format used a 16-bit counter, lists longer than 65,535 entries would have their count wrapped around to zero, causing updates to be lost after a restart. The fix rejects oversized lists before writing and also detects and rejects corrupted/truncated records when loading.

Security candidateMerge pull request #11297 from ViktorT-11/2026-10-remote-signing-renaming-and-docsby Suheb · 4553d889 · Nov 4, 2026 · 10 filesMessage 73 · AdequateInformational 18Details
Commit message · Suheb

Merge pull request #11297 from ViktorT-11/2026-10-remote-signing-renaming-and-docs

Follow-up of #8754: update docs & variable names

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 18/100

This commit is a documentation and code-comment follow-up to an earlier remote-signing feature. It renames internal variables like 'connectionTimeout' to 'startupTimeout' to make their purpose clearer, expands the user-facing docs to explain the security model, and clarifies that a remote signer protects private keys but does not stop a compromised watch-only node from getting valid signatures. There are no functional code changes that alter behavior.

Security candidateMerge pull request #11465 from Roasbeef/actor-drain-overflow-raceby Olaoluwa Osuntokun · c5eb360f · Nov 4, 2026 · 3 filesMessage 78 · AdequateLow 44Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11465 from Roasbeef/actor-drain-overflow-race

actor: hold overflowMu while Drain pops the overflow

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Low 44/100

This patch fixes a concurrency bug in LND's new actor mailbox system. When an actor was shutting down, the cleanup routine that drains leftover messages could read the internal overflow queue at the same time another goroutine was still trying to send a message or check the queue length. The fix makes the drain routine hold the same lock as senders while it pops messages, preventing a data race. The patch also adds regression tests and a release note describing the race.

Security candidateci: bump gateway to v0.7.2 and skip comments from non-membersby litbot-9000 · e46a7503 · Nov 2, 2026 · 1 fileMessage 85 · StrongLow 25Details
Commit message · litbot-9000

ci: bump gateway to v0.7.2 and skip comments from non-members

Bump the gateway-action and runtime pins to v0.7.2 together: the v0.7.2
runtime needs the job token that gateway-action v0.7.2 passes. The release
limits /gateway explain to maintainers and the PR author, authorizes every
command before any credential is loaded, and adds repeat guards for
explain (per finding) and check (per HEAD). Refused commands get no reply;
the reason is in the workflow log.

Also skip comments from anyone who is neither a repo/org member nor the PR
author, so they never boot a runner. The runtime still checks every
command's permission itself.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Low 25/100

This commit updates a GitHub Actions workflow that runs an AI code-review assistant called 'gateway' on pull request comments. It adds a pre-filter so only repository members or the pull request author can trigger the workflow, and it upgrades the gateway software to a new version that checks permissions before loading any credentials. The change is defensive: it reduces the chance that an outsider could waste compute resources or interact with the review bot, and it makes credential handling stricter. There is no direct evidence in the commit of a past security breach.

Security candidatebuild: pin btcwallet rejection mappingsby yyforyongyu · 8a69c380 · Nov 2, 2026 · 2 filesMessage 88 · StrongLow 26Details
Commit message · yyforyongyu

build: pin btcwallet rejection mappings

Use btcwallet v0.18.1 for the rejection mappings from #1464. Its
maintenance base avoids #1452's Neutrino upgrade and keeps the
existing migration library and RPC generator versions.

https://github.com/btcsuite/btcwallet/pull/1464
https://github.com/btcsuite/btcwallet/pull/1452

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access control
AI analysis · Low 26/100

This commit updates LND's dependency on btcwallet from a pre-release development snapshot to the stable v0.18.1 release. The commit message says the goal is to adopt new 'rejection mappings' from a btcwallet pull request while avoiding an unrelated Neutrino upgrade. The change itself only modifies Go module files (go.mod and go.sum); it does not contain any actual code changes. Whether this is a security fix depends entirely on what the referenced btcwallet pull request #1464 contains, which is not shown in the supplied materials.

Security candidateinvoices: reject stale shards at set completionby ziggie · 3ba74925 · Nov 1, 2026 · 4 filesMessage 68 · AdequateModerate 62Details
Commit message · ziggie

invoices: reject stale shards at set completion

Revalidate every accepted MPP or AMP shard when a completing shard
arrives. If an existing shard no longer satisfies either CLTV delta,
cancel the accepted set, keep the invoice open, and reject the
completing shard without recording it.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validationboot or update path
AI analysis · Moderate 62/100

This change fixes a bug in how Lightning Network invoices handle multi-part payments (MPP/AMP). Previously, a payment shard accepted early could sit until the rest of the payment arrived. By then, its timeout might be too close to the current blockchain height to safely settle, yet the system would still complete the payment. Now, when the final shard arrives, every previously accepted shard is re-checked for a safe timeout. If any shard is too close to expiring, the whole payment set is cancelled, the invoice stays open, and the final shard is rejected. This prevents a situation where funds could be released for a payment that can no longer be claimed on-chain in time.

Security candidatescripts: make OTS output deterministic for identical inputsby Boris Nagaev · 147e2b03 · Oct 31, 2026 · 1 fileMessage 73 · AdequateInformational 18Details
Commit message · Boris Nagaev

scripts: make OTS output deterministic for identical inputs

Keep the original CLI, dependencies, output layout and uploader behavior.
Fix the OTS subprocess hash seed, locale and timezone so identical responses
are traversed consistently. Sort proofs and replacement commands, omit local
backend details and generation times, and normalize output permissions.

Keep relative pending ages and transient diagnostics on the terminal rather
than in comparable files. Preserve the pending-age exit status.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
credential or privilege state
AI analysis · Informational 18/100

This commit changes a release-maintenance helper script so that running it twice with the same inputs produces byte-for-byte identical output files. It removes timestamps, local backend details, and non-deterministic ordering from the generated artifacts, and fixes environment settings that could make the OpenTimestamps client behave differently on different machines. These are build/reproducibility hardening changes, not a fix for an exploitable vulnerability in the Lightning node itself.

Security candidateinvoices: persist ordinary HTLC outcomesby yyforyongyu · b0a3e8ae · Oct 31, 2026 · 5 filesMessage 68 · AdequateLow 39Details
Commit message · yyforyongyu

invoices: persist ordinary HTLC outcomes

Discover pending ordinary children across parent states and apply final
outcomes inside the existing invoice transaction. Recompute successful
value and assign the first settlement index once, preserving duplicates.

Reuse the KV scan and SQL query updater. Keep AMP metadata writes on
their existing add-time path and leave ordinary producers unchanged.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Low 39/100

This commit changes how the Lightning Network Daemon (LND) records the final result of ordinary payment attempts (HTLCs) for invoices. It adds a way to find invoices whose child payments are still awaiting a final outcome, and applies those outcomes inside the existing invoice update process. The change is a correctness/robustness improvement rather than an obvious security fix, but it touches settlement accounting and state transitions, which are security-sensitive in a payment system.

Security candidatemulti: defer ordinary invoice settlementby yyforyongyu · 78c092be · Oct 31, 2026 · 15 filesMessage 68 · AdequateModerate 61Details
Commit message · yyforyongyu

multi: defer ordinary invoice settlement

Release ordinary, MPP and hold preimages into PENDING_SETTLE, then
assign final credit and the settlement index through recorded HTLC
outcomes. Recover pending children beneath terminal parents without
allocating another index; let recorded failures override channel
inference and retry channel-only completion while running.

Switch ordinary replay, preimage lookup, expiry, notifications and RPC
projection together. Preserve the parent’s AMP settlement mechanisms and
controls; AMP finality remains deferred. Reuse existing integration
invoice waits rather than adding another harness API.

Cover partial credit, all-failed cancellation, recovery races, transient
writes and pending RPC timestamps using the existing backend fixtures.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Moderate 61/100

This commit changes how LND marks invoices as 'paid.' Previously, when a payment arrived, LND immediately marked the invoice as fully settled. Now, for ordinary, multi-part, and hold invoices, LND first releases the payment preimage to the peer but keeps the invoice in a new 'pending settle' state. It only flips the invoice to 'settled' once the underlying HTLC outcomes are recorded as final. AMP invoices keep their old behavior for now. The change is designed to prevent double-counting, incorrect settlement indexes, and premature credit allocation if a payment later fails or is replayed.

Security candidatedocs: add v0.20.7 and v0.21.6 release notesby ziggie · 050603ed · Oct 30, 2026 · 3 filesMessage 88 · StrongHigh 79Details
Commit message · ziggie

docs: add v0.20.7 and v0.21.6 release notes

Port the final v0.20.7 and v0.21.6 release notes to master, including
the CVE-2026-98432 notice urging Linux operators to disable MPTCP and
install a patched kernel. Remove the MPTCP fragment, which both patch
releases now announce.

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
explicit security languagedocumentation-only discount
AI analysis · High 79/100

This commit adds release notes for LND versions 0.20.7 and 0.21.6, warning Linux users about a serious Linux kernel security flaw (CVE-2026-98432). The notes explain that recent LND versions accidentally exposed a feature called MPTCP on network ports, which attackers could use to remotely exploit the kernel. The release notes tell operators to upgrade LND, disable MPTCP on their server, and install a patched Linux kernel. The actual code change that disables MPTCP was done in a separate pull request; this commit only documents it and removes a draft release-note fragment.

Security candidatechancloser: preserve cooperative close variantsby Olaoluwa Osuntokun · 5b8e6a15 · Oct 29, 2026 · 5 filesMessage 73 · AdequateModerate 59Details
Commit message · Olaoluwa Osuntokun

chancloser: preserve cooperative close variants

In this commit, we carry the selected closing-signature variant through the cooperative close state machine instead of reducing it to a single no-closee flag.

When a peer selects the closee-only transaction, we now omit the remote output while building and completing the local proposal, then reply with the matching signature field. This keeps both peers on the same transaction for legacy and taproot channels.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 59/100

This commit fixes a bug in how the Lightning Network Daemon (LND) handles cooperative channel closes. Previously, when one peer chose a special close variant that omits the 'closee' output, the other peer would not correctly preserve that choice. This could cause both peers to build slightly different closing transactions and fail to agree on the final close. The patch makes the chosen close variant flow through the entire close process so both sides produce and sign the exact same transaction, for both older and newer taproot-style channels.

Security candidateMerge pull request #11431 from Roasbeef/actor-try-sendby Olaoluwa Osuntokun · c03d3659 · Oct 29, 2026 · 14 filesMessage 78 · AdequateLow 42Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11431 from Roasbeef/actor-try-send

actor: add non-blocking TryTell/TryAsk, in-turn overflow sends, AskThen, and a shutdown join

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Low 42/100

This commit adds new non-blocking message-sending tools and a bounded overflow queue to LND's internal actor framework. The goal is to prevent actor-to-actor message cycles from deadlocking when mailboxes are full, and to give callers a way to send messages without blocking. It also adds shutdown helpers so a caller can wait until an actor's current work finishes before cleaning up resources. The changes are defensive: they make overload and termination explicit (returning errors instead of silently blocking or dropping messages) and add hard caps so memory cannot grow without bound.

Security candidatedocs: add release notes for the actor non-blocking sendsby Olaoluwa Osuntokun · 8576d9f9 · Oct 28, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

docs: add release notes for the actor non-blocking sends

In this commit, we add a release note for the non-blocking send, overflow,
AskThen, and shutdown join additions to the actor module.

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
memory safetydocumentation-only discount
AI analysis · Informational 15/100

This commit only adds documentation (release notes) describing previously merged improvements to an internal actor messaging module. It contains no code changes and no security fixes or vulnerabilities.

Security candidateactor: add AskThen to receive an Ask reply as a later messageby Olaoluwa Osuntokun · a4eb9c7d · Oct 28, 2026 · 2 filesMessage 78 · AdequateInformational 24Details
Commit message · Olaoluwa Osuntokun

actor: add AskThen to receive an Ask reply as a later message

In this commit, we add AskThen, the pipe-to-self form of Ask. It sends
the request, returns immediately, and later delivers wrap(result) to the
caller's own ref as an ordinary message. A behavior handles the reply in
a later turn instead of calling Await inside Receive, which deadlocks
when the callee is, transitively, waiting on the caller.

AskThen never blocks its calling goroutine. Inside a receive turn the
request takes the in-turn send path, so a full target mailbox spills to
the overflow queue. From any other goroutine it is a TryAsk, so a full
mailbox is delivered to self as an ErrMailboxFull result.

Completion is best effort and detached, but never silently lost. The
result is retained and its delivery retried with TryTell while self is
alive and busy. It is dropped only when self has stopped, and then the
drop is logged, the message goes to the DLO, and an optional
WithDropHandler is called, so the caller can reconcile. A timeout
abandons the wait rather than the request, and the doc comment says that
a caller that needs a durable outcome must reconcile instead of relying
on the reply.

The design follows AskThen in wavelength's baselib/actor.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Informational 24/100

This commit adds a new helper called AskThen to LND's internal actor framework. It lets one actor send a request to another and receive the reply later as a normal message, instead of blocking and waiting. The main goal is to prevent deadlocks when two actors are waiting on each other. The change is defensive and includes tests, but it introduces new concurrency behavior that could affect reliability if misused.