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 10 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 #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.

Lower-priorityzpay32: fail TestBOLT11Vectors if an expected-error key matches no vectorby Olaoluwa Osuntokun · 949dc278 · Oct 27, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

zpay32: fail TestBOLT11Vectors if an expected-error key matches no vector

In this commit, we make TestBOLT11Vectors assert that every key in
expectedVectorErrors and paymentLayerVectors names one of the loaded
vectors. Before, a key that matched nothing, due to a typo or a reworded
description after a resync from the spec repository, quietly dropped the
vector back to a bare require.Error check.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
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.

Security candidatezpay32: resync BOLT 11 vectors with bolts#1368by Olaoluwa Osuntokun · 8f72c8f0 · Oct 27, 2026 · 2 filesMessage 81 · StrongInformational 20Details
Commit message · Olaoluwa Osuntokun

zpay32: resync BOLT 11 vectors with bolts#1368

In this commit, we pick up the corrected high-S vector from
lightning/bolts#1368, which drops the duplicate `s` field it used to
carry. The vector now reaches the signature check, so we expect
`ErrHighSSignature` for it rather than `ErrDuplicatePaymentAddr`.

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 20/100

This commit updates LND's test data and test expectations to match a corrected official BOLT 11 specification test vector. The invoice string used to exercise 'high-S' signature rejection was changed so it no longer contains a duplicate 's' field. The test now expects the code to reject it specifically for the high-S signature, not for a duplicate field. It is a test-only alignment with the spec, not a functional code change.

Security candidatezpay32: assert why each fixed BOLT 11 vector is rejectedby Olaoluwa Osuntokun · 79c123b0 · Oct 27, 2026 · 3 filesMessage 100 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

zpay32: assert why each fixed BOLT 11 vector is rejected

In this commit, we make the tests show that each of the new decoder
rules is what rejects its invalid invoice, rather than any error.

The vector test only checked that an invalid vector failed, so a vector
rejected for the wrong reason still passed. That hid a real gap: the
spec's high-S vector also repeats its `s` field, so it's rejected as a
duplicate payment address before the signature is ever checked, and no
test exercised `ErrHighSSignature` at all.

We now map each vector this PR fixes to the sentinel error it must
produce, and add `TestDecodeHighSWithDestination`, which decodes the
same invoice (with a single `s` field) once with a high-S and once with
a low-S signature. A duplicate `s` case joins `TestParseTaggedFields`.
Dropping or breaking any of the three new checks now fails a test aimed
at it.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only improves and expands test code for the BOLT 11 invoice decoder. It makes existing tests verify the exact reason each invalid test invoice is rejected, and adds a new test specifically for high-S signature rejection. No production code is changed, so it cannot introduce or fix a runtime security vulnerability on its own.

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.

Lower-priorityMerge pull request #11421 from ziggie1984/ci-remove-master-push-runby Olaoluwa Osuntokun · 2b4701e8 · Oct 27, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11421 from ziggie1984/ci-remove-master-push-run

ci: avoid duplicate master push runs

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
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11425 from ziggie1984/sync-v0.20.6-v0.21.5-release-notesby Olaoluwa Osuntokun · 1b9b099f · Oct 27, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11425 from ziggie1984/sync-v0.20.6-v0.21.5-release-notes

docs: sync final v0.20.6 and v0.21.5 release notes

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
documentation-only discountmerge-commit duplicate discount
Lower-prioritydocs: sync final v0.20.6 and v0.21.5 release notesby ziggie · e506ab5e · Oct 27, 2026 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · ziggie

docs: sync final v0.20.6 and v0.21.5 release notes

62/100 · AdequateMessage clarity
✓ Specific, 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-priorityci: avoid duplicate master push runsby ziggie · 76cde065 · Oct 26, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

ci: avoid duplicate master push runs

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 #11413 from ziggie1984/fix-network-result-prune-v2by Olaoluwa Osuntokun · 85db2f58 · Oct 26, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11413 from ziggie1984/fix-network-result-prune-v2

htlcswitch: avoid per-row queries when pruning network result store

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-priorityhtlcswitch: avoid per-row queries when pruning network result storeby ZZiigguurraatt · e092b728 · Oct 26, 2026 · 3 filesMessage 81 · StrongTriage 0Details
Commit message · ZZiigguurraatt

htlcswitch: avoid per-row queries when pruning network result store

The network result store is pruned at startup, keeping only results for
payments that are still in flight. Previously, cleanStore iterated over
the bucket and deleted each stale key individually.

On SQL backends, each iteration step and deletion requires separate
database queries. A store with N entries therefore incurred O(N)
sequential client/server round trips and could make startup take hours
when using remote PostgreSQL.

Read retained results with one streaming query, drop and recreate the
bucket, then restore the retained entries. PostgreSQL still processes
O(N) rows internally, but the operation no longer performs a round trip
for every stored result.

Exercise cleanup across the supported kvdb backends, including partial,
empty, and unchanged result sets. Add PostgreSQL benchmarks covering
1,000 and 10,000 entries with fully stale and partially retained stores.

Fixes #11353.

Co-authored-by: ziggie <ziggie1984@protonmail.com>

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-prioritychanneldb: scope confirmation hints by scriptby Olaoluwa Osuntokun · 22a68df7 · Oct 23, 2026 · 6 filesMessage 78 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

channeldb: scope confirmation hints by script

In this commit, we key confirmation hints by the same txid and output
script that a confirmation request uses to match a transaction. Two
pending requests can share a txid while watching different scripts,
and the txid-only cache key let one request's scan advance the other's
hint, so the request could resume from its caller-provided height
instead of the block where its transaction confirmed.

We add a cache regression for requests with the same txid and different
scripts, plus an integration case that runs the breach confirmation
with bitcoind without txindex and requires the justice transaction to
sweep the revoked outputs while the funding request remains pending.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
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.

Security candidatewalletrpc: reject retired lease requestsby yyforyongyu · e0269ab2 · Oct 22, 2026 · 2 filesMessage 68 · AdequateLow 48Details
Commit message · yyforyongyu

walletrpc: reject retired lease requests

Reject retired confirmation-count protobuf fields before lease
acquisition or PSBT funding so older clients cannot silently create
timed leases. Use preserved unknown fields and the existing protobuf
wire parser to keep the retired fields out of the public request schema.

Cover both public handlers with decoded old requests and stable error
identity assertions. Keep the existing wallet lifetime implementation.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 48/100

This change is a hardening patch, not an active exploit fix. LND removed two protobuf fields that let callers request timed output leases. Older clients still send those field numbers over the wire as 'unknown' protobuf data, so the server would silently ignore them and create a different kind of lease than the client expected. The patch now detects those retired field numbers in LeaseOutput and FundPsbt and returns an explicit error instead of silently falling through. The main risk is operational: an old client or script that relied on the removed fields will now fail fast rather than silently changing behavior.

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.

AI review queuedwalletrpc: define lease expiry flagsby yyforyongyu · 1b9c6fbb · Oct 22, 2026 · 1 fileMessage 78 · AdequateInformational 19Details
Commit message · yyforyongyu

walletrpc: define lease expiry flags

Expose the no-timeout lifetime explicitly for unused output leases.
Document owner cancellation and first-confirmed-spend cleanup, and add
boolean acknowledgement fields so clients can verify the selected mode.

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

This commit only changes the API definition file (a .proto file) for LND's wallet RPC. It adds new boolean flags and documentation describing how long-term output leases work. There is no actual code logic change here—just the interface and comments—so it does not by itself fix or introduce a security vulnerability. It is a design/documentation/API surface change that may be related to a larger feature around lease lifetimes.

Lower-priorityitest: cover link failure force closeby Olaoluwa Osuntokun · 123094db · Oct 22, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

itest: cover link failure force close

In this commit, we add real-node coverage for link failures that overlap legacy cooperative-close handling. The test holds a forwarded HTLC, fails a separate close link and the HTLC link with unknown settles, then mines to the outgoing deadline.

We assert that the node broadcasts its commitment, publishes the outgoing HTLC timeout transaction after confirmation, and continues processing later blocks. This covers the on-chain path that the focused peer and link tests can't exercise.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritypeer: decouple link failure deliveryby Olaoluwa Osuntokun · 0a4f3ce9 · Oct 21, 2026 · 8 filesMessage 80 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

peer: decouple link failure delivery

In this commit, we decouple link failure reporting from the peer's channel manager with a typed concurrent queue. A link can otherwise report its terminal failure while the channel manager is waiting for that same link to accept a close hook, which leaves both goroutines waiting on each other.

We also make hook registration observe the link event-loop lifetime and the caller's context. This lets close negotiation stop cleanly when the receiver exits, while preserving the existing hook ordering when registration succeeds.

The failure queue starts before active links are loaded, so a link that fails during peer startup also has a live receiver.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityMerge pull request #11394 from ziggie1984/port-0.20.6-0.21.5-release-notesby ziggieXXX · 0d9c9d3a · Oct 21, 2026 · 7 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11394 from ziggie1984/port-0.20.6-0.21.5-release-notes

docs: add 0.20.6 and 0.21.5 release notes to master

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
documentation-only discountmerge-commit duplicate discount
Security candidatedocs: sync the v0.21.5 release notes with the release branchby ziggie · 6cbff7a7 · Oct 21, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · ziggie

docs: sync the v0.21.5 release notes with the release branch

The MuSig2 session cleanup and aux HTLC signature validation entries of
release-notes-0.21.5.md were in a different order on master than on
v0.21.x-branch. Use the release branch's order, so both documents are
identical.

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
signing boundarydocumentation-only discount
AI analysis · Informational 15/100

This commit only reorders two existing entries in the release notes document for version 0.21.5. No code, configuration, or behavior of the LND software is changed. It is a documentation-only edit to keep two copies of the release notes in the same order.