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 2 minutes ago

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

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

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

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

Merge pull request #10708 from jtobin/alias-perms

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

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

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

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

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

docs: describe invoice collection finality

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

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

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

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

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

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

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

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

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

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

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

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

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

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

invoices: require complete payment collection

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

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

lnwallet: reject a zero CSV delay

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

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

lnwallet+chanstate: keep persisted HTLC data readable

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

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

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

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

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

invoices: reject settled AMP set shards

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

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

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

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

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

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

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

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

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

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

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

invoices: fix test whitespace

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

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

build: pin the new lint job actions by commit

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

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

build: fix the custom linter cache wiring for CI

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

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

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

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

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

Explore captured commits

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

Lower-priorityMerge pull request #11462 from ziggie1984/sync-v0.20.7-v0.21.6-release-notesby ziggieXXX · 2f149331 · Oct 30, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11462 from ziggie1984/sync-v0.20.7-v0.21.6-release-notes

docs: add v0.20.7 and v0.21.6 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
Security candidatedocs: add v0.20.7 and v0.21.6 release notesby ziggie · 050603ed · Oct 30, 2026 · 3 filesMessage 88 · StrongHigh 79Details
Commit message · ziggie

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

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

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

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

Lower-priorityMerge pull request #11456 from ziggie1984/build-disable-mptcpby Yong · ee23b6bf · Oct 30, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11456 from ziggie1984/build-disable-mptcp

build: disable MPTCP listeners by default

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-prioritydocs: add MPTCP default release noteby ziggie · 619ea5f2 · Oct 30, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add MPTCP default release note

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-prioritybuild: disable MPTCP listeners by defaultby ziggie · a14fcb3a · Oct 30, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

build: disable MPTCP listeners by default

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
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.

Lower-prioritysweep: retry transient mempool errorsby yyforyongyu · c2da0c69 · Oct 30, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · yyforyongyu

sweep: retry transient mempool errors

Treat unrecognized mempool acceptance failures and reversible policy
rejections as retryable. Preserve the underlying backend error and
continue the existing fee trajectory, including an exhausted fee cap.

Keep recognized script and local initialization failures terminal.
Cover the public broadcast result and retain existing publication
failure coverage.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritydocs: add release notes for #11445by Olaoluwa Osuntokun · da75d3a7 · Oct 30, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

docs: add release notes for #11445

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityonionmessage: validate forwarding hop payload fieldsby Olaoluwa Osuntokun · 2c015622 · Oct 29, 2026 · 3 filesMessage 73 · AdequateTriage 8Details
Commit message · Olaoluwa Osuntokun

onionmessage: validate forwarding hop payload fields

In this commit, we enforce the BOLT 4 forwarding rules for onion messages. Intermediate hops now reject any outer TLV besides encrypted_recipient_data and any decrypted path_id, while final-hop payloads keep their existing behavior.

The checks use record presence rather than value length, so empty unknown-odd and path_id records cannot slip through.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validation
Security candidatechancloser: preserve cooperative close variantsby Olaoluwa Osuntokun · 5b8e6a15 · Oct 29, 2026 · 5 filesMessage 73 · AdequateModerate 59Details
Commit message · Olaoluwa Osuntokun

chancloser: preserve cooperative close variants

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

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

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

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

Lower-prioritykvdb/etcd: retain transaction read errorsby Olaoluwa Osuntokun · c7eb9aef · Oct 29, 2026 · 5 filesMessage 68 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

kvdb/etcd: retain transaction read errors

In this commit, we retain the first etcd read error that occurs behind a kvdb method without an error return.

Managed transactions now return that error after the callback, while manual transactions roll back instead of committing pending writes. Bucket, sequence, and cursor reads all feed the same transaction-level error slot so a later successful operation can't hide the failure.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysweep: keep fee curves within budgetby Olaoluwa Osuntokun · 16756970 · Oct 29, 2026 · 5 filesMessage 68 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

sweep: keep fee curves within budget

In this commit, we reject fee curves whose starting rate already exceeds their maximum, and cap the relay-fee fallback by the same budget.

A rejected starting hint remains retryable. We clear it before the next sweep attempt so the estimator can choose a valid rate, including the partial unknown-spend path where the fee function hasn't been initialized yet.

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

Lower-prioritywtpolicy: apply dust limits per output scriptby Olaoluwa Osuntokun · 8a31a130 · Oct 29, 2026 · 2 filesMessage 68 · AdequateTriage 8Details
Commit message · Olaoluwa Osuntokun

wtpolicy: apply dust limits per output script

In this commit, we validate each reward transaction output against the dust limit for its own script.

The old calculation checked the victim output using the tower reward script's size, which could reject a valid sweep output while accepting a dusty reward. The justice transaction builder now checks both amounts at the point where both scripts are available.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validation
Lower-prioritywtwire: bound inbound message decodingby Olaoluwa Osuntokun · 37bd12b4 · Oct 29, 2026 · 7 filesMessage 68 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

wtwire: bound inbound message decoding

In this commit, we bound watchtower message decoders by both the message type's maximum payload and the bytes left in the transport frame.

This lets variable-length fields reject impossible lengths before allocating or reading them, while the unframed reader keeps its existing sequential-message behavior. We also correct the maximum size of CreateSessionReply to include its variable-length prefix.

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

Lower-priorityMerge pull request #11427 from ziggie1984/release-notes-fold-tool-publicby Yong · 37997cd8 · Oct 29, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11427 from ziggie1984/release-notes-fold-tool-public

scripts: add tool to fold release note fragments

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-prioritychanneldb: retain on-chain HTLC outcomesby yyforyongyu · 7a28e193 · Oct 29, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · yyforyongyu

channeldb: retain on-chain HTLC outcomes

Keep on-chain final outcomes without requiring the optional off-chain
resolution history. Invoice recovery needs durable success and failure
evidence if a final notification is missed during shutdown.

Retain the existing storage transaction and verify both on-chain
outcomes with resolution history disabled.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Security candidateMerge pull request #11431 from Roasbeef/actor-try-sendby Olaoluwa Osuntokun · c03d3659 · Oct 29, 2026 · 14 filesMessage 78 · AdequateLow 42Details
Commit message · Olaoluwa Osuntokun

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

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

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

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

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

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

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

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

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

Lower-priorityactor: require lnd/queue v1.2.1by Olaoluwa Osuntokun · 3f5ad1cf · Oct 28, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

actor: require lnd/queue v1.2.1

In this commit, we bump the queue requirement from v1.1.1 to v1.2.1.
backpressure_mailbox.go uses queue.BackpressureQueue, DropCheckFunc,
AsDropPredicate and NewBackpressureQueue, which v1.1.1 doesn't have. The
module only built because of the replace directive pointing at ../queue,
and replace directives are not inherited, so a module importing actor
failed with undefined: queue.BackpressureQueue unless it bumped queue
itself. The module now also builds with the replace directives removed.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityactor: add Done, StopAndWait and ShutdownAndWait to join Receiveby Olaoluwa Osuntokun · 63354e3e · Oct 28, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

actor: add Done, StopAndWait and ShutdownAndWait to join Receive

In this commit, we let an owner stop an actor and know that no Receive
is still running. Stop and ActorSystem.Shutdown only cancel the actor's
context, so a caller that closes the stores a behavior uses right after
them can race with a Receive that is mid-flight, and an abandoned or
timed-out Future proves nothing about that.

Actor.Done is closed once the processing goroutine has exited, after
the loop and the drain of undelivered messages. StopAndWait stops the
actor and blocks until Done or the caller's context expires, and
ActorSystem.ShutdownAndWait does the same for every managed actor. A nil
return is a join: the last Receive has returned and none will start. An
actor that was never started has nothing to join, so Stop closes Done
for it directly.

The join only holds for a behavior that returns when the context it is
passed is cancelled, which the doc comments state.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidateactor: add AskThen to receive an Ask reply as a later messageby Olaoluwa Osuntokun · a4eb9c7d · Oct 28, 2026 · 2 filesMessage 78 · AdequateInformational 24Details
Commit message · Olaoluwa Osuntokun

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

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

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

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

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

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

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

Security candidateactor: never park sends made from inside a receive turnby Olaoluwa Osuntokun · db6106a3 · Oct 28, 2026 · 4 filesMessage 90 · StrongModerate 53Details
Commit message · Olaoluwa Osuntokun

actor: never park sends made from inside a receive turn

In this commit, we make a send issued from an actor's own receive turn
non-blocking. Parking an actor on a full mailbox stalls its whole
mailbox, and a cycle of actors that do so deadlocks.

The actor loop now stamps the context handed to the behavior with a
turn marker, which is cleared when the turn returns. A Tell or Ask made
with such a context goes through a new in-turn path on the default
ChannelMailbox: it uses the channel when there is room and nothing is
queued ahead of it, and otherwise spills into a bounded overflow queue
that the receive loop refills the channel from, oldest first.

The queue is capped at ActorConfig.MailboxOverflowLimit, defaulting to
DefaultMailboxOverflowLimit. A send at the cap fails with
ErrMailboxOverflow, which an Ask surfaces on its Future. Tell can't
return an error, so it logs the drop. A context that outlives its turn,
in a goroutine the behavior spawned, parks like any other producer.
WithoutTurn clears the marker explicitly.

Delivery order is acceptance order. TrySend reports full while the
overflow is non-empty, and an ordinary blocking Send from outside the
actor first waits for the overflow to drain instead of writing to the
channel ahead of it. An owner can therefore enqueue a shutdown or
barrier message and know it runs after everything already accepted.
Drain yields the overflow after the channel.

The Mailbox interface is unchanged: the in-turn path is an optional
interface that ChannelMailbox implements.

This is ported from the in-turn send design in wavelength's
baselib/actor, with the Send ordering added.

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Moderate 53/100

This commit fixes a design flaw in LND's internal actor framework where an actor could freeze itself by sending a message to another actor whose mailbox was full. If several actors did this in a circle, the whole group could deadlock. The fix marks messages sent during an actor's own processing turn as 'in-turn' and routes them through a special non-blocking overflow queue, so the actor never stops moving. It also preserves message order and adds a hard cap so runaway message floods fail loudly instead of consuming unlimited memory.

Lower-priorityactor: add non-blocking TryTell and TryAskby Olaoluwa Osuntokun · 4c30fe41 · Oct 28, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

actor: add non-blocking TryTell and TryAsk

In this commit, we add TryTell and TryAsk to the actor reference
interfaces. Tell and Ask park the caller when the target's mailbox is
full, which is unsafe for a plain goroutine, such as an event loop, that
must keep servicing other work.

TryTell returns ErrMailboxFull instead of waiting for room. TryAsk
returns a Future that is already completed with the failure, so the
caller learns of it without parking. Neither blocks from any goroutine,
whether or not it is an actor. A stopped actor is reported as
ErrActorTerminated, with a TryTell routed to the DLO, and a closed
mailbox as the new ErrMailboxClosed.

The mailbox's existing TrySend already provides the primitive; this
commit exposes it on the refs and the router.

The design follows the non-parking sends in wavelength's baselib/actor.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context