LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Repository coverage

1687 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

186security candidates236second-pass queue1372AI analyses
162commits · 30 days
277commits · 60 days
643commits · 180 days
1422commits · 365 days
Backfill bands
Aug 5 → Feb 6405 seen5 candidatesComplete
Feb 6 → Jun 6665 seen28 candidatesComplete
Jun 6 → Jul 689 seen4 candidatesComplete
Jul 6 → Aug 569 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
387Strong · 80–100
837Adequate · 60–79
432Thin · 40–59
31Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Olaoluwa Osuntokun29659235474
ziggie49922422265
Elle Mouton26832268167
Yong60926172
ziggieXXX50617170
George Tsagkarelis37335167
LNBiG111173
Jared Tobin909171
yyforyongyu1211574070
bitromortac731154071
Erick Cestari26726070
Suheb746074
Analysis record

Published AI watches

Last scanned 47 minutes ago

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

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

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

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

Merge pull request #10708 from jtobin/alias-perms

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

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

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

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

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

docs: describe invoice collection finality

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

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

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

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

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

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

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

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

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

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

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

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

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

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

invoices: require complete payment collection

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

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

lnwallet: reject a zero CSV delay

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

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

lnwallet+chanstate: keep persisted HTLC data readable

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

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

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

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

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

invoices: reject settled AMP set shards

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

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

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

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

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

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

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

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

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

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

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

invoices: fix test whitespace

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

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

build: pin the new lint job actions by commit

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

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

build: fix the custom linter cache wiring for CI

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

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

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

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

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

Explore captured commits

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

Security candidatedocs: note configurable WalletKit lease lifetimeby Andras Banki-Horvath · 37945535 · Aug 26, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · Andras Banki-Horvath

docs: note configurable WalletKit lease lifetime

Document the new LeaseOutput and FundPsbt confirmation-depth option in
the 0.22.0 release notes.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 15/100

This commit only adds documentation to the release notes describing a new WalletKit feature: output leases can now optionally stay active until a spending transaction reaches a chosen confirmation depth. There is no code change, no bug fix, and no security-related content in the commit itself.

Security candidatewalletrpc: expose configurable output leasesby Andras Banki-Horvath · 515ceaac · Aug 26, 2026 · 8 filesMessage 68 · AdequateInformational 24Details
Commit message · Andras Banki-Horvath

walletrpc: expose configurable output leases

Add optional confirmation-depth fields to LeaseOutput and FundPsbt. A
non-zero value selects a lease that ignores wall-clock expiry and
releases at the requested spend depth or by explicit owner release. Zero
preserves time-controlled leases.

Resolve wallet capability before acquiring inputs so unsupported
backends fail closed even when FundPsbt selects no new input. Echo the
accepted depth after installation, and expose persisted spend height
through ListLeases so clients can observe confirmation and reorg
progress.

Cover option forwarding, zero-depth compatibility, unsupported wallets,
partial acquisition rollback, and response marshalling.

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

This commit adds a new optional feature to LND's wallet RPC that lets callers lock a coin (a 'UTXO lease') until the transaction spending it reaches a chosen number of confirmations, instead of relying only on a clock-time expiration. It also exposes more lease information in responses and lists. The change is defensive: it checks wallet support before locking, rejects unsupported wallets, requires a caller-chosen lock ID for the new mode, and preserves the old time-based behavior when the new option is not used. There is no direct evidence in the commit of a fixed vulnerability; it reads like a capability addition with safety checks.

Security candidatebuild: pin configurable btcwallet output leasesby Andras Banki-Horvath · 6f73d73d · Aug 26, 2026 · 3 filesMessage 80 · StrongModerate 60Details
Commit message · Andras Banki-Horvath

build: pin configurable btcwallet output leases

Pin btcwallet and wtxmgr to the canonical upstream commit that
merged the configurable-lease API and its wall-clock expiry fix.

Without the follow-up fix, a slowly confirming spend can outlive its
timed lease before wtxmgr records the spend height. A later shallow
reorg can then expose the input to coin selection.

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
access control
AI analysis · Moderate 60/100

This commit updates LND's dependency versions for btcwallet and wtxmgr to a newer upstream version that fixes a timing issue with 'output leases.' In plain terms, when LND temporarily reserves a coin (UTXO) for a transaction, it sets an expiration time. The bug being fixed is that a slow-to-confirm spend could have its reservation expire before the wallet records that the coin was actually spent. If a shallow blockchain reorganization then happens, the wallet might mistakenly think the coin is still available and select it again for a new transaction. This could lead to double-spending attempts or channel failures. The commit itself only changes version pins and linter settings; the actual code fix lives in the upstream btcwallet/wtxmgr libraries.

Security candidatelnwire: preserve channel update extrasby yyforyongyu · 7afea2bd · Aug 26, 2026 · 4 filesMessage 83 · StrongModerate 59Details
Commit message · yyforyongyu

lnwire: preserve channel update extras

Canonicalize channel update TLV data without mutating the message during
encoding. This keeps unknown records intact, reconciles legacy duplicate
inbound fee representations, and makes signing match the emitted bytes.

Cover receiver immutability, legacy encoding shapes, concurrent
encoding, and signature verification across a wire round trip.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationboot or update path
AI analysis · Moderate 59/100

This change fixes how Lightning channel-update messages handle optional extra data. Previously, encoding could silently rewrite the message's internal byte slice, which could cause signature mismatches, lost unknown fields, and race conditions when the same message was encoded from multiple threads. The patch now builds a fresh canonical copy of the extra data for each encoding/signing operation without changing the original message. The tests explicitly verify that signatures still verify after a full encode-decode round trip, that unknown fields survive, and that concurrent encoders no longer race.

Security candidatepeer: test outgoing queue costsby yyforyongyu · 64645cc5 · Aug 25, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · yyforyongyu

peer: test outgoing queue costs

Cover each non-serializing queue cost rule with declarative message
shapes. Pin the retained opaque data charged for all active v1 bulk
gossip messages.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
access control
AI analysis · Informational 15/100

This commit only adds a new automated test file. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The test verifies how the outgoing message queue calculates the memory cost of different network messages, helping ensure future code changes do not accidentally under-count or over-count queue memory usage.

Security candidateMerge pull request #11008 from LNBIG-COM/fix/psbt-funding-lock-orderby Yong · a912dd69 · Aug 24, 2026 · 3 filesMessage 73 · AdequateModerate 66Details
Commit message · Yong

Merge pull request #11008 from LNBIG-COM/fix/psbt-funding-lock-order

lnwallet: fix limboMtx/intentMtx lock order inversion in PsbtFundingVerify

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

This commit fixes a classic multi-threading bug in LND's wallet code. Two functions were acquiring the same two locks in opposite orders, which could cause a deadlock. When triggered, the wallet's single request-handler goroutine would freeze, permanently stopping all channel opening on the node and preventing newly confirmed channels from being announced. Only a restart would recover. The fix reorders the lock acquisition so both functions now take the locks in the same order.

Security candidatepeer: rate limit inbound pingsby yyforyongyu · b9388cca · Aug 21, 2026 · 2 filesMessage 68 · AdequateModerate 65Details
Commit message · yyforyongyu

peer: rate limit inbound pings

Bound Pong replies with separate reply and flood token buckets.
Count every decoded Ping before generic routing. Disconnect peers that
exhaust the flood budget through a stable sentinel error.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Moderate 65/100

This commit adds rate limits on incoming ping messages in LND's peer connection handler. Without these limits, a malicious or misconfigured peer could send a flood of ping messages, forcing the node to waste CPU, memory, and bandwidth processing them and sending pong replies. The fix counts every incoming ping and disconnects peers that exceed a flood threshold, while also limiting how often pong replies are sent. This is a defensive hardening change against a potential denial-of-service attack.

Security candidatepeer: test outgoing queue boundsby yyforyongyu · d65c97cf · Aug 19, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · yyforyongyu

peer: test outgoing queue bounds

Exercise prospective admission through the direct queue and public
sending API. Pin inclusive count and byte limits and preserve the
overflow cause across synchronous batches.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
access controlmemory safety
AI analysis · Informational 15/100

This commit only adds new unit tests for the outgoing message queue in LND's peer connection code. It does not change any production logic, fix a bug, or alter behavior that an attacker could exploit. The tests verify that queue size limits are enforced correctly.

Security candidateMerge pull request #11075 from ziggie1984/agent/fix-transaction-pagination-overflowby ziggieXXX · cfde18d9 · Aug 14, 2026 · 4 filesMessage 78 · AdequateLow 44Details
Commit message · ziggieXXX

Merge pull request #11075 from ziggie1984/agent/fix-transaction-pagination-overflow

lnwallet: prevent transaction pagination overflow

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

This update fixes a crash bug in LND's transaction history viewer. When a user or program asked for transactions using very large offset and limit numbers, the old code could add those numbers together in a way that wrapped around to a tiny value, then try to slice a list with that bad value and panic. The new code checks the bounds safely before slicing, preventing the crash. It is a denial-of-service-style bug rather than a theft or remote-code-execution issue.

Security candidatelnwallet: prevent transaction pagination overflowby Ziggie · 62aeca57 · Aug 14, 2026 · 2 filesMessage 50 · ThinLow 40Details
Commit message · Ziggie

lnwallet: prevent transaction pagination overflow

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safetysigning or wallet path
AI analysis · Low 40/100

This commit fixes a pagination bug in LND's wallet transaction listing. Previously, adding a user-controlled 'offset' and 'limit' together as 32-bit unsigned integers could wrap around to a tiny number, causing the code to slice transaction data using an unexpectedly small 'end' index and potentially return wrong results or behave inconsistently. The fix performs pagination using 64-bit arithmetic and compares the limit against the remaining items before deciding where to stop, preventing the overflow.

Security candidatelnwallet: require an aux sig per HTLC on taproot overlay channelsby George Tsagkarelis · 4b564f1f · Aug 13, 2026 · 2 filesMessage 88 · StrongHigh 74Details
Commit message · George Tsagkarelis

lnwallet: require an aux sig per HTLC on taproot overlay channels

The aux signature blob is peer supplied and carries no count of its own.
Verification jobs were only built for HTLCs an entry was received for,
so a peer could withhold the aux signature for an HTLC simply by
omitting it: no job was produced, nothing reported the omission, and the
commitment became our state carrying a signature we never received. At
force close the resolver then reads an empty signature out of that
HTLC's custom records, and the second level HTLC cannot be swept.

An aux signer emits exactly one entry per non-dust HTLC, in lockstep
with the BTC level signatures, so the count is now checked the same way
those already are, right beside them.

The check is gated on the tapscript root bit rather than merely on an
aux signer being configured. The signer is attached node wide, so it is
also present on plain channels, whose peers correctly send no aux
signatures at all, and requiring them there would force close those
channels. That bit is set at funding time if and only if the negotiated
commitment type is a taproot overlay, so it names exactly the channels
whose peers owe us aux signatures.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · High 74/100

This commit fixes a bug in LND's taproot overlay Lightning channels where a peer could deliberately leave out an extra signature (aux sig) for one or more HTLCs. Because the code only checked the main Bitcoin signatures, the missing aux signature went unnoticed. Later, if the channel was force-closed, the affected HTLC could not be swept on-chain, potentially locking up funds. The fix adds a count check so that every non-dust HTLC must have a matching aux signature on taproot overlay channels.

Security candidatelnwallet: model the aux sig blob faithfully in testsby George Tsagkarelis · 80f7fd88 · Aug 13, 2026 · 3 filesMessage 88 · StrongLow 26Details
Commit message · George Tsagkarelis

lnwallet: model the aux sig blob faithfully in tests

Three places modelled the aux signature blob less faithfully than
production does, in ways that hid whether the blob was carried at all.

MockAuxSigner.UnpackSigs returned a single slot no matter how many HTLCs
were packed. A real aux signer emits exactly one slot per HTLC, and code
that pairs the unpacked slots with HTLCs by index depends on that. The
default mock now records the slot count in the packed blob and hands
back that many slots. Since the blob is parsed into custom records, it
has to stay a canonical TLV stream, so the count travels in the dummy
record's value. Registering a function rather than a fixed value is what
lets the result depend on the input.

restartChannel rebuilt the channel with no channel options, so a restart
silently dropped the aux signer and the restarted side stopped producing
aux signatures while its peer still expected them. Production re-applies
the aux components every time a channel is loaded.

Two chan sync tests rebuilt CommitSigs from a retransmitted wire message
without its aux signature blob, which the link carries across.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 26/100

This commit fixes test code in LND's Lightning wallet so that mock auxiliary (taproot/asset channel) signatures behave more like the real production code. The changes make tests correctly preserve the aux signer across channel restarts and carry the aux signature blob through retransmitted commitment messages. There is no direct production code change; it is a test-harness hardening patch that prevents future bugs in the aux-signature protocol from being hidden by inaccurate test mocks.

Security candidatedocs: update release notesby bitromortac · 9cfd5a66 · Aug 11, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · bitromortac

docs: update release notes

Add changes for the Merkle tree and BIP-340 signature work in bolt12.

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 15/100

This commit only updates the release notes document. It adds two bullet points describing earlier work on BOLT 12 Merkle trees and BIP-340 signatures, plus related test vectors. No code, logic, or configuration was changed, so it cannot introduce or fix a security issue by itself.

Security candidateMerge pull request #11023 from ellemouton/update-fee-logby Yong · 7f56541d · Aug 7, 2026 · 8 filesMessage 73 · AdequateModerate 59Details
Commit message · Yong

Merge pull request #11023 from ellemouton/update-fee-log

lnwallet+htlcswitch: align update_fee handling with BOLT 2

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

This commit hardens how LND handles Lightning channel fee updates and mailbox message admission. It enforces the protocol rule that only the channel opener can send fee updates, prevents uncommitted fee updates from piling up in the update log, limits how many queued messages a peer can stuff into a channel's mailbox, and makes the link disconnect if the mailbox is full so messages are not silently dropped. These changes reduce ways a misbehaving or buggy peer could disrupt a channel or waste resources.

Security candidatebolt12: add BIP-340 message signaturesby bitromortac · dfdcd507 · Aug 6, 2026 · 3 filesMessage 83 · StrongInformational 14Details
Commit message · bitromortac

bolt12: add BIP-340 message signatures

SignMessage and VerifySignature wrap btcec's Schnorr API around the
Merkle root with the spec's tagged-hash domain separator. Typed
helpers bind the construction to invoice requests and invoices, so
callers sign and verify messages rather than raw roots.

The signed vectors in signature-test.json verify the construction
against the spec, and a tamper matrix pins rejection of modified
roots, signatures, keys, and tags.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 14/100

This commit adds new code for creating and checking digital signatures on BOLT 12 lightning invoices and invoice requests. It is a feature addition with extensive tests, not a fix for a known security bug. There is no evidence in the commit or supplied references that it addresses a vulnerability.

Security candidatecontractcourt: match second-level outputsby yyforyongyu · dd24c85c · Aug 6, 2026 · 2 filesMessage 73 · AdequateModerate 57Details
Commit message · yyforyongyu

contractcourt: match second-level outputs

A re-signed success transaction can move its committed output to another
index while preserving the HTLC input signature.

Match the indexed output against the sweep descriptor and return the
confirmed outpoint. Keep malformed resolver and notifier state distinct
from complete non-matches.

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 boundary
AI analysis · Moderate 57/100

This commit adds logic to LND's contract court so that when an incoming HTLC is claimed on-chain via a re-signed success transaction, the resolver correctly identifies which output of that transaction it should sweep next. Previously, the code may have relied on a fixed output index; now it checks the actual output at the same index as the HTLC input and verifies it matches the expected sweep descriptor. The change is defensive and includes tests, but the commit message frames it as fixing a real correctness issue that could affect fund recovery.

Security candidateMerge pull request #11024 from ziggie1984/invoices-update-validationby ziggieXXX · 61f3b5a7 · Aug 5, 2026 · 4 filesMessage 58 · ThinModerate 63Details
Commit message · ziggieXXX

Merge pull request #11024 from ziggie1984/invoices-update-validation

invoices: refine update handling

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
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 63/100

This commit tightens how LND processes invoice payments, especially for newer multi-path (MPP) and AMP invoices, keysend payments, and replayed payments. It adds checks that ensure the right payment preimage is used for each invoice type and that AMP invoices cannot be processed through the older legacy path. The changes are defensive hardening rather than a single obvious exploit fix, but they close several paths where an attacker might trick LND into settling an invoice incorrectly or using the wrong secret.

Security candidateinvoices: refine update handlingby ziggie · 6be6350e · Aug 5, 2026 · 3 filesMessage 35 · OpaqueModerate 59Details
Commit message · ziggie

invoices: refine update handling

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Moderate 59/100

This commit tightens how LND handles invoice payment updates, especially for newer 'AMP' invoices and old-style 'keysend' payments. It adds checks so that the wrong kind of payment cannot be processed against the wrong kind of invoice, and it verifies that stored payment secrets actually match the expected hash. The changes are defensive: they reject mismatched or malformed payments instead of allowing them to proceed. The commit does not say it fixes a known exploit, but the new checks close paths where a payment might have been accepted incorrectly.

Security candidatepeer+lnwallet/chancloser: advance the legacy closer from one goroutineby Olaoluwa Osuntokun · e5e134dd · Aug 4, 2026 · 4 filesMessage 88 · StrongModerate 60Details
Commit message · Olaoluwa Osuntokun

peer+lnwallet/chancloser: advance the legacy closer from one goroutine

In this commit, we give the legacy ChanCloser a single owner, rather than
letting two goroutines advance it. The peer's channelManager drives the state
machine for the Shutdown and ClosingSigned messages that come off the wire, and
for local close requests. The link drives it as well: while we wait for the
channel to drain we register a flush hook, and the link invokes that hook from
its own goroutine, where it called BeginNegotiation directly. Nothing kept the
two apart, so the state field, the priorFeeOffers map, and the signing step
could all be touched at once. Under `go test -race` this shows up as a data race
on the state field.

Rather than reach for a lock, we route the flush through the channelManager. The
hook now only reports the channel ID over a new chanCloseFlushed channel, and
handleChanFlushed picks it up next to the close messages. Every transition, the
cached offer processing, the fee map, and the signing then happen on the one
goroutine, so the closer needs no synchronization of its own. We spell that out
on the type, since it's an invariant a new caller can break from the outside.

The report goes out from a fresh goroutine, which matters more than it looks.
The link may well be holding its own lock while it invokes the hook, and
channelManager reaches for that same lock in DisableAdds, so blocking on the
handoff would trade the race for a deadlock. The `go` in front of RemoveLink
just above it is there for the same reason.

We look the closer up with a plain map load rather than through
fetchActiveChanCloser, as that one builds a fresh closer when it doesn't find
an existing one, and a flush that lands after the negotiation was torn down has
no business starting a new negotiation.

One behavior change falls out of the move: the flush path now runs the same
finalization tail as the message path. It skipped that before, so a responder
that drained a cached offer would reach closeFinished and broadcast, but nothing
ran finalizeChanClosure until the next close message showed up, and having
already sent its final signature, there may not be one. The link == nil path
already ran the tail, so this makes all three paths agree.

The new test drives a close with a link that hands us the flush hook instead of
running it inline, so we can check that negotiation waits on the report, and
that a report for a channel we have no closer for is dropped.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 60/100

This commit fixes a concurrency bug in how LND negotiates cooperative channel closures. Previously, two different goroutines could update the same channel-closing state machine at the same time, which could corrupt internal data or cause a crash. The fix routes all updates through a single goroutine and adds a test to confirm the behavior.

Security candidatehtlcswitch: bound peer-controlled channel ingressby Elle Mouton · ef24f2c5 · Aug 4, 2026 · 4 filesMessage 68 · AdequateHigh 72Details
Commit message · Elle Mouton

htlcswitch: bound peer-controlled channel ingress

In this commit, we bound the channel mailbox by message count and by the
encoded size of non-commitment control messages. Commitment updates retain
their full custom-record allowance and remain protected by the count bound.
If either budget fills, we disconnect the peer instead of silently dropping
an ordered channel message.

We also reject unauthorized fee updates before fee-exposure evaluation,
return the exposure error used to fail the link, and emit peer-controlled
warning classes only once per link lifetime.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · High 72/100

This commit hardens LND's channel message handling against a peer that tries to overwhelm the node. It adds limits on how many ordered messages and how much data a peer can queue up for a channel, and it disconnects the peer if either limit is exceeded instead of silently dropping messages. It also fixes a protocol rule: only the channel initiator is allowed to send fee updates, so the node now rejects fee updates from the wrong side before doing any math on them. Finally, it reduces log spam by recording certain peer warnings and unknown messages only once per channel lifetime.

Security candidatelnwallet: fix limboMtx/intentMtx lock order inversion in PsbtFundingVerifyby LNBiG · a9c794e0 · Jul 30, 2026 · 3 filesMessage 73 · AdequateCritical 85Details
Commit message · LNBiG

lnwallet: fix limboMtx/intentMtx lock order inversion in PsbtFundingVerify

PsbtFundingVerify acquired intentMtx and then limboMtx, while
handleFundingCancelRequest, which runs in the wallet's single requestHandler
goroutine, acquires the two in the opposite order. With PSBT or batch funding
both paths run concurrently, so the two goroutines can deadlock.

The consequences are severe and node wide: requestHandler is the only executor
of every ChannelReservation method, and those methods are unconditional round
trips with neither a timeout nor a quit escape. Once it is stuck, a peer
disconnect parks funding.Manager's resMtx forever in CancelPeerReservations,
and the next zombie sweeper tick kills reservationCoordinator on resMtx.RLock.
From that moment the node can neither open nor accept channels, freshly
confirmed channels are stuck in the channelReadySent opening state and are
never added to the graph nor announced, and no log line is emitted about any of
it. Only a restart recovers.

Look the channel reservation up, and release limboMtx, before acquiring
intentMtx, and document the required order on the mutex declaration.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Critical 85/100

This commit fixes a classic deadlock bug in LND's wallet code. Two different code paths were acquiring the same two locks in opposite orders, which could cause the wallet's single request handler goroutine to freeze permanently. Once frozen, the node could no longer open or accept any Lightning channels, and newly confirmed channels would get stuck without being announced to the network. Only restarting the node would recover. The fix reorders the lock acquisition so both paths use the same order, and documents the rule.

Security candidatebolt12: test invoice request decodeby bitromortac · fa39cd74 · Jul 28, 2026 · 1 fileMessage 95 · StrongInformational 12Details
Commit message · bitromortac

bolt12: test invoice request decode

The invoice_request codec has round-trip coverage against locally-
constructed messages only, so a canonical-encoding bug would go
unnoticed until a real peer rejected a signature. Drive the decoder from
the spec's signature-test invoice_request and assert that re-encoding is
byte-identical to the wire bytes, because the signature commits to the
Merkle root of that exact encoding.

95/100 · StrongMessage clarity
✓ 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 12/100

This commit only adds a new test. It does not change any production code. The test decodes a standard BOLT12 invoice request from the official specification's test vectors and checks that re-encoding it produces exactly the same bytes. This is a defensive quality-improvement change meant to catch canonical-encoding bugs before they reach real peers.

Security candidatebolt12: add bech32 lno/lnr/lni codecby bitromortac · 81d31862 · Jul 28, 2026 · 8 filesMessage 85 · StrongInformational 23Details
Commit message · bitromortac

bolt12: add bech32 lno/lnr/lni codec

The bolt12 package can already encode and decode the TLV layer but has
no way to carry an offer as a human-transportable string, which is the
form the spec specifies for QR codes, URLs and email signatures. BOLT
12's envelope is subtractive relative to BIP-173: there is no BCH
checksum, because the BIP-340 signature over the Merkle root already
secures the payload, and a '+' continuation marker may split the string
across lines. btcutil/bech32's public API always wraps the checksum, so
the alphabet layer is duplicated here rather than reused. Enforce a
whitelist of BOLT 12 prefixes (lno, lnr, lni) on both Encode and Decode.

85/100 · StrongMessage clarity
✓ 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
signing boundary
AI analysis · Informational 23/100

This commit adds a new encoder/decoder that turns BOLT 12 Lightning payment data (offers, invoice requests, invoices) into human-readable strings like 'lno1...' and back again. It is a feature addition, not a fix for a known vulnerability. The code includes careful input checks for length, character set, case rules, allowed prefixes, and line-continuation markers, plus extensive tests. There is no indication in the commit that this resolves a security incident or was reported by an outside researcher.

Security candidatebolt12: add InvoiceError onion message repliesby bitromortac · e279cdf1 · Jul 21, 2026 · 4 filesMessage 73 · AdequateInformational 21Details
Commit message · bitromortac

bolt12: add InvoiceError onion message replies

InvoiceError is the negative-reply counterpart to an invoice, sent over
onion messages at namespace type 68 when the receiver rejects an invoice
request or the sender rejects a returned invoice. All three fields are
odd (informational): erroneous_field (TLV 1, the offending TLV type),
suggested_value (TLV 3, a valid replacement), and error (TLV 5, a UTF-8
explanation). Unlike Offer/InvoiceRequest/Invoice this type has no
bech32 form and no Merkle signature — it travels only inside onion
message payloads.

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 boundary
AI analysis · Informational 21/100

This commit adds support in LND for a new Lightning protocol message called InvoiceError. It is used to politely tell another node why their payment invoice or invoice request was rejected, sent privately through an onion-routed message. The change is mostly a feature addition with built-in validation to make sure the error message is well-formed before it is sent.

Security candidatebolt12: validate Invoice messagesby bitromortac · e0f04f17 · Jul 9, 2026 · 4 filesMessage 73 · AdequateLow 36Details
Commit message · bitromortac

bolt12: validate Invoice messages

Implement the structural validators for the BOLT 12 invoice, adding
ValidateInvoiceWrite, ValidateInvoiceRead, ValidateInvoiceExpiry, and
ValidateInvoiceAgainstRequest.

The validators implement the spec writer and reader requirements in the
order the spec lists them. The reader confirms the signature TLV is
present but defers actual Schnorr verification until the merkle and
signing primitives land, mirroring the ValidateInvoiceRequestRead
precedent.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validation
AI analysis · Low 36/100

This commit adds validation checks for BOLT 12 invoices in the LND Lightning node software. It ensures invoices contain required fields (creation time, amount, payment hash, node ID, payment paths), match their originating invoice requests, and aren't expired or malformed before being encoded or accepted. The change is defensive: it rejects invalid invoices rather than letting them propagate, which helps prevent payment failures, confusion, or minor abuse. Signature verification is explicitly left for a future patch, so this is not a complete security fix on its own.