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
278commits · 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 35 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.

AI review queuedMerge pull request #11588 from ziggie1984/lnwallet/fix-reorg-wallet-sync-flakeby Yong · 8cdbf85c · Nov 18, 2026 · 4 filesMessage 73 · AdequateLow 43Details
Commit message · Yong

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

lnwallet: harden wallet sync checks during reorgs

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

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 replaced by another at the same height), the heights could match while the wallet was still on the wrong block. The fix now checks both the block height and the block hash. This is a correctness and reliability improvement rather than a typical remote-exploitable vulnerability, but it could lead to unsafe behavior if LND acted on a stale or inconsistent wallet view.

AI review queuedMerge pull request #11396 from yyforyongyu/task-lease-policyby Yong · 03e28a96 · Nov 10, 2026 · 9 filesMessage 73 · AdequateLow 35Details
Commit message · Yong

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

walletrpc: make no-expiry leases explicit

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 35/100

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 the removed option now get a clear error instead of silently falling back to a timed lease. The change is a deliberate API cleanup with security-relevant hardening against silent downgrade, but it is not a fix for an active vulnerability.

AI review queuedMerge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-storeby Yong · 8c251687 · Nov 10, 2026 · 26 filesMessage 73 · AdequateLow 40Details
Commit message · Yong

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

graph/db: cross-version graph Store queries

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 discountsecond-pass: unusually broad change
AI analysis · Low 40/100

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, or mixed-up records. It adds 'preferred' lookups that pick the best available version, keeps the in-memory cache consistent with those lookups, and fixes several bugs where deleting or updating one version could leave the other version invisible or inconsistent. The changes are framed as architectural groundwork for the upcoming gossip v2 feature rather than as a fix for an active security vulnerability.

AI review queuedMerge pull request #11440 from Roasbeef/fix-longstanding-correctness-bugsby Olaoluwa Osuntokun · 0123a548 · Nov 10, 2026 · 38 filesMessage 73 · AdequateModerate 61Details
Commit message · Olaoluwa Osuntokun

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

multi: tighten wire, fee and transaction invariants

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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 61/100

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 database transactions, miscalculate sweep/close transactions, or read oversized wire messages. The patch is defensive: it adds checks and tests rather than removing functionality, and the release notes describe the changes as fixing 'low-level correctness bugs.'

AI review queuedlnwallet: reject a zero CSV delayby Olaoluwa Osuntokun · 266eba7b · Nov 10, 2026 · 3 filesMessage 78 · AdequateModerate 60Details
Commit message · Olaoluwa Osuntokun

lnwallet: reject a zero CSV delay

In this commit, we reject a CSV delay of zero during constraint
verification.

The CSV delay is the time the owner of a commitment must wait before
sweeping their own output, and it is the window the other party has to
respond to a breach. A delay of zero removes that window entirely and
is never a sensible value, but VerifyConstraints only bounded the delay
from above.

VerifyConstraints is the one place every delay passes through:
CommitConstraints calls it for the delay the remote party requires of
us, in both the initiator and responder roles, and the funding manager
calls it for the delay we require of the remote party. Checking for zero
there covers every channel type and both directions.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

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 channel commitment, and it is also the time the other party has to punish a cheating attempt. A zero delay would remove that safety window, so the patch makes it impossible to accept or propose such a channel. The fix is applied at the single central checkpoint that all channel types and both sides of a channel pass through.

AI review queuedMerge pull request #11374 from bitromortac/20261016-c7e5-dispatchby bitromortac · a9d4ca3b · Nov 9, 2026 · 38 filesMessage 73 · AdequateLow 39Details
Commit message · bitromortac

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

bolt12handler+devrpc: dispatch invoice requests and add CreateOffer

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 discountsecond-pass: unusually broad change
AI analysis · Low 39/100

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. It also adds rate/inflight limits and reply-path handling to avoid obvious DoS, but the feature is gated behind dev/native-SQL builds and explicitly marked as not yet returning invoice_error replies for failed requests.

AI review queuedMerge pull request #11282 from lightningnetwork/elle-base-branch-payment-serviceby Olaoluwa Osuntokun · 11f79be0 · Nov 6, 2026 · 58 filesMessage 73 · AdequateModerate 59Details
Commit message · Olaoluwa Osuntokun

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

multi: add switchrpc external HTLC dispatch subsystem

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 discountsecond-pass: unusually broad change
AI analysis · Moderate 59/100

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 pathfinding. The change is opt-in and compiled only when the 'switchrpc' build tag is used. It also reworks how in-flight payment attempts are stored so the same attempt ID cannot be used twice, preventing accidental duplicate payments when an external caller retries after a network timeout. The release notes explicitly warn that running the local router and an external router at the same time is unsafe and can cause loss of funds.

AI review queuedMerge pull request #11472 from yyforyongyu/task-sweep-rejectionsby Yong · c5863e55 · Nov 5, 2026 · 20 filesMessage 73 · AdequateLow 44Details
Commit message · Yong

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

sweep: retry transient mempool 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 discountsecond-pass: unusually broad change
AI analysis · Low 44/100

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 reason was unclear), LND would treat the inputs as permanently failed and stop trying to spend them. The fix makes LND retry these inputs later while preserving the intended fee increase schedule, so funds are not left stuck. It also updates the required Go version to 1.27.3 across the project.

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.

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.

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.

AI review queuedMerge pull request #11151 from Roasbeef/reject-absurd-feeratesby Yong · 5176c13c · Oct 30, 2026 · 10 filesMessage 73 · AdequateModerate 64Details
Commit message · Yong

Merge pull request #11151 from Roasbeef/reject-absurd-feerates

funding+lnwallet: reject absurdly high channel feerates

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 64/100

This commit adds two safety checks to LND's channel-opening process. When someone tries to open a Lightning channel with LND, LND now rejects the request if the proposed on-chain fee rate is absurdly high (more than 10 times LND's own fee estimate, with a minimum floor of 100 sat/vbyte), or if the initial balances are so low that neither party could actually use the channel. These checks prevent attackers or misconfigured peers from tying up LND's resources on channels that would be useless or economically harmful.

AI review queuedsweep: retry inconclusive spend checksby Olaoluwa Osuntokun · d32a9497 · Oct 29, 2026 · 5 filesMessage 68 · AdequateModerate 57Details
Commit message · Olaoluwa Osuntokun

sweep: retry inconclusive spend checks

In this commit, we distinguish a failed spend lookup from a completed
lookup that found no spender.

Notifier registration and closed-subscription errors no longer crash the
node or get treated as "not spent" by accident. When the missing input
path can't tell whether an input was spent, it now returns a retryable
result instead of a fatal one, and the sweeper keeps the input's existing
starting fee preference rather than replacing it with the result's zero
value.

During regular record processing, an inconclusive check is logged and
the record proceeds as if no input was spent. Skipping it instead would
stop fee bumps for a deadline sweep for as long as the check keeps
failing. If an input was in fact spent, the mempool rejects the attempt
for missing inputs and the missing input handling takes over.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Moderate 57/100

This commit fixes a bug in LND's transaction sweeping logic. Previously, when the node couldn't reliably check whether an input had already been spent (for example, because a notifier registration failed or a subscription closed unexpectedly), the code could either crash the node or wrongly treat the input as unspent. The patch makes these failures retryable instead of fatal, preserves the user's chosen fee rate instead of resetting it to zero, and continues fee-bumping deadline sweeps even when the spend check is inconclusive. This prevents stuck funds or incorrect fee handling during network or backend hiccups.

AI review queuedMerge pull request #11365 from saubyk/7316-listchaintxns-reverseby ziggieXXX · 730b9e55 · Oct 29, 2026 · 11 filesMessage 73 · AdequateInformational 20Details
Commit message · ziggieXXX

Merge pull request #11365 from saubyk/7316-listchaintxns-reverse

multi: add reverse ordering to listchaintxns

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 · Informational 20/100

This commit adds a new optional 'reverse' flag to the lncli listchaintxns and GetTransactions RPC that lets users list wallet transactions oldest-first instead of newest-first. It also fixes a minor ordering stability issue so transactions in the same block now appear in a predictable order. There is no security vulnerability here; it is a user-facing feature and small bug-fix for transaction listing.

AI review queuedMerge pull request #11357 from Roasbeef/zpay32-bolt11-vectorsby Olaoluwa Osuntokun · 5617ee7e · Oct 28, 2026 · 7 filesMessage 73 · AdequateLow 48Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11357 from Roasbeef/zpay32-bolt11-vectors

zpay32: enforce BOLT 11 fixed lengths, single s, low-S with n

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 48/100

This change tightens how LND reads BOLT 11 Lightning invoices. It now rejects invoices that violate the spec: fixed-length fields with wrong lengths, duplicate payment-address fields, and high-S signatures when the invoice explicitly names the payee. Previously these malformed invoices were accepted or silently skipped. The patch is defensive and brings LND into line with the BOLT 11 specification and its official test vectors.

AI review queuedzpay32: document first-wins for repeated n and h fieldsby Olaoluwa Osuntokun · b4c0fc91 · Oct 27, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

zpay32: document first-wins for repeated n and h fields

In this commit, we update the comments on repeated `n` and `h` fields.
A field with the wrong length is now an error rather than unsupported,
so "already seen a supported one" no longer describes why we skip it.
Keeping the first one is deliberate: BOLT 11 only requires exactly one
`p` and one `s` field.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes code comments in the zpay32/decode.go file. It updates the explanation for why repeated 'n' and 'h' fields in BOLT 11 invoices are ignored after the first valid one. No actual code behavior was changed, so there is no security impact.

AI review queuedMerge pull request #11354 from Roasbeef/taproot-vectors-bolts-1352by Olaoluwa Osuntokun · 4a4c9a5d · Oct 27, 2026 · 2 filesMessage 83 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11354 from Roasbeef/taproot-vectors-bolts-1352

lnwallet: sync taproot test vectors with bolts#1352

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
fuzzing or regression evidencesigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test data and test code for Taproot channel scripts in LND. It adds new test vectors that match the latest BOLT specification draft (bolts#1352), including separate keys for the remote party's commitment and a corrected distinction between the combined MuSig2 funding key and the final BIP-86 tweaked funding key. No production wallet, consensus, or networking code is changed, so this cannot directly affect live funds or node security.

AI review queuedMerge pull request #11287 from ziggie1984/fix-submodule-lintby Yong · 1a359d4a · Oct 23, 2026 · 57 filesMessage 73 · AdequateInformational 19Details
Commit message · Yong

Merge pull request #11287 from ziggie1984/fix-submodule-lint

multi: fix submodule lint issues and lint submodules in CI

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 discountsecond-pass: unusually broad change
AI analysis · Informational 19/100

This is a large housekeeping commit that fixes code-style and lint warnings across many submodules and adds a new CI step to lint those submodules. The only functional code change is a small rewrite of the retry-delay calculation to avoid integer overflow when retry settings are extremely large. There is no evidence of an exploitable vulnerability being fixed, and the commit message does not describe any security issue.

AI review queueditest: cover leases without expiryby yyforyongyu · 9dd64a3c · Oct 22, 2026 · 3 filesMessage 78 · AdequateInformational 15Details
Commit message · yyforyongyu

itest: cover leases without expiry

Verify reservation, restart, owner cancellation and first-spend cleanup
through WalletKit RPCs using a single input lifecycle.

Document the replacement flags, removed count response metadata and
explicit rejection of retired request parameters in the release notes.
Require boolean acknowledgement for callers migrating to no-expiry
leases.

78/100 · AdequateMessage clarity
✓ 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 adds integration tests and release notes for a previously implemented feature: output leases that never expire. It does not change production code, so it cannot introduce a new security vulnerability or fix one directly.

AI review queuedwalletrpc: generate lease depth retirementby yyforyongyu · e0fcd800 · Oct 22, 2026 · 2 filesMessage 68 · AdequateLow 28Details
Commit message · yyforyongyu

walletrpc: generate lease depth retirement

Regenerate WalletKit bindings and the REST schema after removing the
confirmation-count fields from requests and responses.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 28/100

This commit removes a feature called 'confirmation-count-based lease retirement' from LND's wallet RPC interface. It deletes fields that let users keep a coin locked until a spending transaction reaches a certain number of confirmations. The change only updates generated API bindings and REST documentation, not the underlying wallet logic. There is no direct evidence in the commit that this fixes a security bug; it appears to be a feature rollback or API cleanup.

AI review queuedwalletrpc: retire lease depth fieldsby yyforyongyu · 06e6c72d · Oct 22, 2026 · 1 fileMessage 68 · AdequateLow 34Details
Commit message · yyforyongyu

walletrpc: retire lease depth fields

Remove the count-based request controls and response metadata. Reserve
their protobuf numbers and names so they cannot be reused accidentally.
Document the boolean lifetime and same-owner renewal acknowledgement.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100

This commit removes several count-based lease lifetime options from LND's wallet RPC protocol definitions. It reserves the old field names and numbers so they cannot be accidentally reused. The change appears to be a deliberate API cleanup rather than a direct security fix, but it affects how long wallet outputs can be locked and how leases are renewed, which has security-relevant implications for funds availability and wallet behavior.

AI review queuedwalletrpc: support leases without expiryby yyforyongyu · e3c2d161 · Oct 22, 2026 · 4 filesMessage 78 · AdequateLow 28Details
Commit message · yyforyongyu

walletrpc: support leases without expiry

Select the existing depth-one wallet lifetime through explicit flags.
Reuse capability resolution, caller ownership and acquisition rollback,
and report the effective policy through boolean acknowledgements.

Give conflicting lifetimes and invalid owner IDs stable error
identities. Cover acquisition, validation and same-owner renewal through
the public handlers. Remove count response assignments and the obsolete
count-based RPC integration test before retiring their generated
declarations.

78/100 · AdequateMessage clarity
✓ 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 · Low 28/100

This commit changes how LND's wallet RPC lets users lock (lease) unspent bitcoin outputs. It adds a new 'no expiry' mode where a lease stays active until the output is spent and confirmed, instead of expiring after a set number of seconds. The change also removes an older confirmation-count based field from some responses and adds clearer error messages for conflicting lease settings. It is primarily a feature/API refactor, not a clear security fix or vulnerability.

AI review queuedwalletrpc: generate lease expiry flagsby yyforyongyu · 04f12489 · Oct 22, 2026 · 3 filesMessage 68 · AdequateInformational 19Details
Commit message · yyforyongyu

walletrpc: generate lease expiry flags

Regenerate WalletKit bindings and the REST schema for the explicit
no-expiry request flags and their boolean acknowledgements.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit only regenerates automatically-generated RPC bindings and REST documentation to match a new 'no-expiry' lease option that was added to the underlying protocol definition. It does not contain the actual wallet logic that enforces the new lease behavior, so it is not a security fix or vulnerability by itself. It simply exposes new API fields so callers can request leases that never time out.