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 47 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.

Lower-priorityMerge pull request #11478 from Roasbeef/pub/alias-collision-validationby Olaoluwa Osuntokun · e08866c5 · Nov 5, 2026 · 7 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11478 from Roasbeef/pub/alias-collision-validation

scidalias: reject peer aliases for other channels

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
merge-commit duplicate discount
Lower-prioritydocs: add release note for #11499by litbot-9000 · fb8c14d5 · Nov 5, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · litbot-9000

docs: add release note for #11499

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritygithub: move Go's temporary build dir off /tmpby litbot-9000 · ea965dcf · Nov 5, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · litbot-9000

github: move Go's temporary build dir off /tmp

On the ubuntu-26.04 runner image /tmp is a RAM backed tmpfs capped at
about 7.7G. Go creates its temporary build directory ($WORK) there by
default, so builds that link many binaries can run it out of space even
though the root disk still has plenty free. The "Check commits" job,
which builds every unit test binary for each commit, failed this way
with "write /tmp/go-build.../...: disk quota exceeded" while / had 45G
available.

Point GOTMPDIR at a directory under RUNNER_TEMP in the shared setup-go
action. RUNNER_TEMP lives on the runner's disk, exists on Linux, macOS
and Windows runners, and is cleaned up after every job.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification! Contains work-in-progress language
Why it was queued
documentation-only discount
Lower-prioritydocs: add release note for #11498by litbot-9000 · dc43954e · Nov 5, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · litbot-9000

docs: add release note for #11498

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityci: hold CI on new pull requests until the ci-hold label is removedby litbot-9000 · 5668a503 · Nov 5, 2026 · 3 filesMessage 97 · StrongTriage 0Details
Commit message · litbot-9000

ci: hold CI on new pull requests until the ci-hold label is removed

Every new pull request starts a CI run right away, including draft PRs
that are still being worked on and PRs that will need substantial rework
or are closed without being merged. Together with the merge queue this
keeps the shared runners busy, and the runs of PRs that are actually
ready wait in line behind them.

Hold CI on new pull requests instead:

- The new ci-hold.yml adds the ci-hold label to every new PR. It runs
on pull_request_target, so it can label PRs opened from forks, and
never checks out or executes PR code.
- The CI gate of main.yml selects a new held tier while the label is
present. All jobs skip (the required matrix legs stay instantiated
and only skip their steps) and the CI result job fails, so a held PR
can't enter the merge queue. Merge group and nightly runs are never
held. Because the run for a newly opened PR starts at the same time
as ci-hold.yml, the first attempt of an opened run is held even if
the label isn't visible yet, unless it has already been removed again
or the PR was opened with the GITHUB_TOKEN.
- Removing the label makes ci-hold.yml re-run the PR's latest CI run
for its current head commit. The gate reads the labels from the API,
so the re-run runs the pr tier, and its results are reported on the
PR like those of the original run. Adding the full-ci label re-runs CI
the same way. main.yml doesn't listen to label events itself, as
every unrelated label change would cancel the run in progress.

The commit checks and the release notes checks now wait for the gate
job, as they have to know whether CI is held.

97/100 · StrongMessage clarity
✓ Specific, 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
documentation-only discount
Lower-priorityci: track nightly failures in an issueby litbot-9000 · 5b2e8817 · Nov 5, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · litbot-9000

ci: track nightly failures in an issue

GitHub only notifies the user who last changed the schedule of a workflow
about failed scheduled runs. Report the result of each scheduled nightly
run in an issue labeled nightly-failure instead: a failing run opens one,
or comments on the open one, listing the failed jobs, and the next passing
run closes it.

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
documentation-only discount
Lower-priorityMerge pull request #11497 from ziggie1984/fix-chainntnfs-hint-lintby Olaoluwa Osuntokun · ae8b82bb · Nov 5, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11497 from ziggie1984/fix-chainntnfs-hint-lint

chainntnfs: wrap ConfirmHintCache comments at 80 columns

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
merge-commit duplicate discount
Lower-prioritychainntnfs: wrap ConfirmHintCache comments at 80 columnsby ziggie · 45c3896b · Nov 5, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · ziggie

chainntnfs: wrap ConfirmHintCache comments at 80 columns

The ConfirmHintCache doc comments updated in #11481 exceed the
80-character line limit, which fails the ll linter on master and on
every open PR that is linted against it.

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #11479 from Roasbeef/pub/batch-publish-stateby Olaoluwa Osuntokun · 37936c11 · Nov 5, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11479 from Roasbeef/pub/batch-publish-state

funding: preserve batch state after publish errors

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
merge-commit duplicate discount
Lower-priorityMerge pull request #11484 from Roasbeef/pub/commit-replacement-handlingby Olaoluwa Osuntokun · 3447e4cc · Nov 5, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11484 from Roasbeef/pub/commit-replacement-handling

contractcourt: handle replacement fee rejections

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
merge-commit duplicate discount
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.

Lower-priorityMerge pull request #11483 from Roasbeef/pub/peer-link-event-deliveryby Olaoluwa Osuntokun · e503de7a · Nov 4, 2026 · 10 filesMessage 58 · ThinTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11483 from Roasbeef/pub/peer-link-event-delivery

peer: decouple link failure delivery

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-prioritydocs: add release note for #11489by litbot-9000 · 20c09e3c · Nov 4, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · litbot-9000

docs: add release note for #11489

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityci: split CI into pr, merge queue and nightly tiersby litbot-9000 · d140b6c5 · Nov 4, 2026 · 2 filesMessage 95 · StrongTriage 0Details
Commit message · litbot-9000

ci: split CI into pr, merge queue and nightly tiers

Required status checks apply to both the pull_request and the merge_group
context, so the complete CI ran twice for every PR: once to enter the merge
queue and once in it. Together with up to five concurrently built merge
groups this exhausts the available runners, and jobs regularly wait for
hours before they start.

Split the jobs into three tiers selected by the CI gate job:

- pr: the fast checks only. The required unit test and basic itest legs
that aren't part of it stay instantiated and skip their steps, so the
per-leg checks are still reported. The full-ci label selects the merge
tier for a PR.
- merge: the real gate, adding the full unit test matrix, the basic
itests, the etcd, sqlite and postgres itests, the arm cross compilation
and the backwards compatibility test.
- nightly: the new nightly.yml runs the complete set on master every day,
including the remaining itests, the Windows and macOS itests and the
coverage report.

A new CI result job aggregates all gating jobs into a single check that
fails if a job failed, was cancelled or was skipped although it belongs to
the selected tier. Requiring it lets the merge queue gate on jobs that
aren't required individually.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11481 from Roasbeef/pub/conf-hint-scriptby Olaoluwa Osuntokun · 86670056 · Nov 4, 2026 · 6 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11481 from Roasbeef/pub/conf-hint-script

channeldb: scope confirmation hints by script

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
merge-commit duplicate discount
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.

AI review queuedMerge pull request #11480 from Roasbeef/pub/restored-force-closeby Olaoluwa Osuntokun · e1604c85 · Nov 4, 2026 · 6 filesMessage 73 · AdequateModerate 58Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11480 from Roasbeef/pub/restored-force-close

lnwallet: reject force close for restored channels

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 pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 58/100

This change fixes a bug where LND could try to force-close a Lightning channel that had been restored from a Static Channel Backup (SCB) even though the local node does not actually have a current commitment transaction to broadcast. In Bitcoin Lightning, force-closing without the right transaction can lead to broadcasting an outdated state, which the remote party could punish as a protocol violation (a 'justice transaction'), potentially causing loss of funds. The patch now rejects force-close requests for restored channels and logs the situation clearly instead of pretending a close transaction was published.

AI review queuedMerge pull request #11304 from saubyk/fix/shutdown-exit-codesby Olaoluwa Osuntokun · a2b76a94 · Nov 4, 2026 · 13 filesMessage 73 · AdequateLow 34Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11304 from saubyk/fix/shutdown-exit-codes

multi: exit with a non-zero code when lnd shuts itself down on failure

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 pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 34/100

This change makes the LND Bitcoin Lightning node return a non-zero exit code when it shuts itself down because of an internal failure, such as a failed health check. Previously, LND often exited with code 0 even on failure, which made process managers like systemd think the stop was intentional and not restart the node. The patch also assigns specific exit codes to different health-check failures (chain backend, disk space, TLS, Tor, remote signer, leader status). This is a reliability/operational fix, not a vulnerability that an attacker can exploit.

Lower-prioritybuild: require Go 1.27.3by yyforyongyu · aab1e466 · Nov 4, 2026 · 16 filesMessage 81 · StrongTriage 0Details
Commit message · yyforyongyu

build: require Go 1.27.3

The upstream wallet revision requires Go 1.27.3. Keep our modules and
installation instructions consistent.

https://github.com/btcsuite/btcwallet/pull/1439

81/100 · StrongMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedMerge pull request #11340 from bitromortac/20261012-b57b-dispatchby Yong · 25b25d0f · Nov 4, 2026 · 19 filesMessage 73 · AdequateLow 25Details
Commit message · Yong

Merge pull request #11340 from bitromortac/20261012-b57b-dispatch

bolt12handler: add the invoice request handler behind a protocol flag

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
parser or protocol pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 25/100

This commit adds a new, experimental BOLT 12 invoice-request handler to LND. It is gated behind a build flag and a protocol option, requires native SQL, and is described in release notes as not yet routing real invoice requests to the handler. The change is a feature addition with defensive validation and tests, not a fix for an active vulnerability.

Lower-prioritydocs: rename release note fragment to PR numberby Olaoluwa Osuntokun · 3e4c79fa · Nov 4, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Olaoluwa Osuntokun

docs: rename release note fragment to PR number

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11471 from yyforyongyu/task-itest-stabilityby Yong · 5590f4a2 · Nov 4, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · Yong

Merge pull request #11471 from yyforyongyu/task-itest-stability

itest: stabilize close and backup recovery tests

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
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.

AI review queuedMerge pull request #11474 from ziggie1984/itest-fix-outbound-rs-macaroon-flakeby Yong · 03b2b8d4 · Nov 3, 2026 · 1 fileMessage 83 · StrongInformational 14Details
Commit message · Yong

Merge pull request #11474 from ziggie1984/itest-fix-outbound-rs-macaroon-flake

itest: deflake outbound remote signer macaroon test

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 14/100

This commit only adjusts timing settings in an integration test to reduce flaky failures on slow CI systems. It is not a security fix and does not change production code.

AI review queueditest: deflake outbound remote signer macaroon testby ziggie · 06a97396 · Nov 3, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · ziggie

itest: deflake outbound remote signer macaroon test

testOutboundRSMacaroonEnforcement waits a fixed 15 seconds for the
watch-only node to write its invoice macaroon. On slow CI runners with a
remote database backend, opening the database can take longer than that,
and the test fails with a missing macaroon file.

Wait for the macaroon with the default timeout, which already accounts
for remote database backends.

The watch-only node starts waiting for the signer after writing its
macaroons, and the test still has to open a stream and start the signer
node before the signer connects. Raise the watch-only node's signer
connection timeout to the default timeout as well, so a slow runner
doesn't move the flake to that step.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes an integration test. It replaces hard-coded 15-second waits with longer default timeouts so the test doesn't randomly fail on slow CI machines. There is no change to production code or user-facing behavior, and no security issue is being fixed or introduced.