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

Lower-priorityMerge pull request #11589 from ziggie1984/ci/macos-26-runnerby Yong · 5ffce515 · Nov 16, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Yong

Merge pull request #11589 from ziggie1984/ci/macos-26-runner

ci: migrate macOS nightly to macOS 26

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-priorityci: migrate macOS nightly to macOS 26by ziggie · 835d48e5 · Nov 16, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

ci: migrate macOS nightly to macOS 26

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 #10891 from MPins/issue-9892by Yong · 46f8dc0a · Nov 14, 2026 · 6 filesMessage 68 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #10891 from MPins/issue-9892

Remove RBF coop close staging feature bits

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #11528 from saubyk/updatechanpolicy-partialby Suheb · 28cb56b8 · Nov 14, 2026 · 14 filesMessage 73 · AdequateTriage 0Details
Commit message · Suheb

Merge pull request #11528 from saubyk/updatechanpolicy-partial

multi: allow partial channel policy updates

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 #10842 from yyforyongyu/isolate-mempool-failureby Olaoluwa Osuntokun · a0470cc3 · Nov 13, 2026 · 11 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #10842 from yyforyongyu/isolate-mempool-failure

sweep: isolate bad inputs on mempool rejection

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 #10708 from jtobin/alias-permsby Olaoluwa Osuntokun · 98dc2b44 · Nov 13, 2026 · 2 filesMessage 68 · AdequateModerate 51Details
Commit message · Olaoluwa Osuntokun

Merge pull request #10708 from jtobin/alias-perms

routerrpc: add XFindBaseLocalChanAlias to macPermissions

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

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

Lower-priorityMerge pull request #11569 from yyforyongyu/task-release-preflightby Olaoluwa Osuntokun · b21b727e · Nov 13, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11569 from yyforyongyu/task-release-preflight

ci: prepare release drafts before tagging

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 #11574 from litbot-9000/gossip-syncer-test-flakeby Yong · 955eb884 · Nov 13, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · Yong

Merge pull request #11574 from litbot-9000/gossip-syncer-test-flake

discovery: fix flaky TestGossipSyncerSyncTransitions

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
Lower-prioritydiscovery: fix flaky TestGossipSyncerSyncTransitionsby litbot-9000 · f3508c55 · Nov 12, 2026 · 2 filesMessage 81 · StrongTriage 0Details
Commit message · litbot-9000

discovery: fix flaky TestGossipSyncerSyncTransitions

The test asserted an exact FirstTimestamp for the GossipTimestampRange
message the syncer sends when (re)entering active sync. The syncer
stamps the message with its own clock while processing the start or
transition request, and the test sampled time.Now() for its expectation
only afterwards. If a wall-clock second boundary was crossed in
between, the expectation was one second ahead of the stamped value and
the test failed, as seen in CI [1]:

expected: FirstTimestamp 1794500870
got: FirstTimestamp 1794500869

Sample the time before starting the syncer and assert that the stamped
first timestamp falls within [startTime, now] instead of comparing
exact values.

[1]: https://github.com/lightningnetwork/lnd/actions/runs/42982273166/job/131243808607

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Security candidateMerge pull request #11555 from yyforyongyu/invoice-settlement-publicby Olaoluwa Osuntokun · 895118ac · Nov 12, 2026 · 48 filesMessage 73 · AdequateModerate 68Details
Commit message · Olaoluwa Osuntokun

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

invoices: settle after complete HTLC collection

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

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

Lower-priorityMerge pull request #11567 from ziggie1984/docs-port-latest-release-notesby Yong · 69ab4e9a · Nov 11, 2026 · 15 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11567 from ziggie1984/docs-port-latest-release-notes

docs: port latest 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
Lower-prioritydocs: port latest release notes to masterby ziggie · cd2b2136 · Nov 11, 2026 · 15 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: port latest release notes to master

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 #11562 from ziggie1984/release-tag-notes-preflight-prby Yong · 6734bcce · Nov 11, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11562 from ziggie1984/release-tag-notes-preflight-pr

build: validate release notes before tagging

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 validationmerge-commit duplicate discount
Lower-priorityMerge pull request #11561 from ziggie1984/fix-pr11540-nlreturnby Yong · e7106f6d · Nov 11, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Yong

Merge pull request #11561 from ziggie1984/fix-pr11540-nlreturn

peer: fix channel sync error formatting

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-prioritypeer: fix channel sync error formattingby ziggie · c4d2acd3 · Nov 11, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · ziggie

peer: fix channel sync error formatting

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #11540 from vincenzopalazzo/repro/pending-channel-reestablishby Yong · 926d903f · Nov 11, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11540 from vincenzopalazzo/repro/pending-channel-reestablish

peer: reestablish pending channels on reconnect

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 #11554 from yyforyongyu/task-lint-timeoutby Yong · abe5379a · Nov 11, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11554 from yyforyongyu/task-lint-timeout

ci: scope lint reports and allow slower analysis

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 candidatedocs: describe invoice collection finalityby yyforyongyu · 9649d9f6 · Nov 11, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · yyforyongyu

docs: describe invoice collection finality

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

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

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

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

Lower-priorityci: scope lint reports to the change baseby yyforyongyu · 623e0bb1 · Nov 11, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · yyforyongyu

ci: scope lint reports to the change base

Use the checked-out merge commit's first parent as the lint reporting
base for PR and merge-group jobs, following the release-note checks.
Pass the same optional override to root and submodule lint so existing
warnings outside the change no longer fail unrelated PRs.

Keep nightly runs on the configured baseline and preserve native
lint's existing merge-base override. Full package analysis still runs.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritylint: allow more time for CI analysisby yyforyongyu · 35bf1262 · Nov 11, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

lint: allow more time for CI analysis

Package loading can consume nine minutes of the existing ten-minute
budget on CI runners, leaving too little time for lint analysis.
Increase the total-work limit to fifteen minutes while keeping it
bounded and preserving all lint checks.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidateMerge pull request #11551 from ziggie1984/public-pr149-sanitizedby Yong · 4b7447bc · Nov 11, 2026 · 7 filesMessage 73 · AdequateModerate 64Details
Commit message · Yong

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

invoices: revalidate accepted htlc expiries at set completion

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

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

Lower-prioritydocs: add release note for htlc set expiry checkby ziggie · 9850e230 · Nov 11, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add release note for htlc set expiry check

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-prioritydocs: add release notes for #11540by Vincenzo Palazzo · 6e473970 · Nov 10, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Vincenzo Palazzo

docs: add release notes for #11540

Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Lower-prioritypeer: reestablish pending channels on reconnectby Vincenzo Palazzo · 14efa3d3 · Nov 10, 2026 · 3 filesMessage 78 · AdequateTriage 0Details
Commit message · Vincenzo Palazzo

peer: reestablish pending channels on reconnect

BOLT 2 requires a node to send channel_reestablish for every
remembered channel when a peer reconnects. Pending channels are remembered
but have no link, so lnd previously sent nothing until funding confirmed. A
peer waiting for the message could disconnect the shared connection.

Queue the message while loading pending channels and record the handoff so
the link created after confirmation still processes the remote state without
sending a duplicate.

Add regression coverage for the pending funding-node case.

Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification