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.

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

walletrpc: generate lease depth retirement

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

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

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

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

walletrpc: retire lease depth fields

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

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

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

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

walletrpc: support leases without expiry

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

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

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

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

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

walletrpc: generate lease expiry flags

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

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

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

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

walletrpc: define lease expiry flags

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

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

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

Security candidatedocs: sync the v0.21.5 release notes with the release branchby ziggie · 6cbff7a7 · Oct 21, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · ziggie

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

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

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

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

Security candidateMerge pull request #11380 from ziggie1984/fix-update-fee-floorby ziggieXXX · 732a9a0c · Oct 21, 2026 · 11 filesMessage 73 · AdequateModerate 59Details
Commit message · ziggieXXX

Merge pull request #11380 from ziggie1984/fix-update-fee-floor

lnwallet: reject fee updates below commit floor

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 update to the Lightning Network Daemon (LND) fixes several related bugs around commitment transaction fee rates for anchor-style channels. It prevents LND from accepting or sending fee updates below the protocol minimum, clamps a configuration value that could overflow and silently turn into a much lower fee, and cleans up a wallet reservation leak when an incoming channel open is rejected. The practical effect is to stop channels from being created or updated with fees so low that they cannot carry payments, and to prevent a misconfiguration from accidentally disabling the intended fee cap.

AI review queuedMerge pull request #11383 from ziggie1984/build-go-1.27.3by ziggieXXX · bfe5039f · Oct 20, 2026 · 34 filesMessage 73 · AdequateLow 28Details
Commit message · ziggieXXX

Merge pull request #11383 from ziggie1984/build-go-1.27.3

build: bump Go language to 1.26.10 and toolchain to 1.27.3

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discountsecond-pass: unusually broad change
AI analysis · Low 28/100

This commit is primarily a routine update of the Go compiler/toolchain version used to build LND (from Go 1.27.1 to 1.27.3, and the language version from 1.26.8 to 1.26.10) across many build files, Docker images, and sub-modules. It also includes a few small test-code cleanups that make error handling stricter. The change itself is not a security patch for LND logic, but it moves the project to a newer Go point release that may contain upstream fixes for compiler/runtime issues. There is no explicit vendor statement that this update fixes a security vulnerability.

AI review queuedbuild: bump Go language and toolchain versionsby ziggie · d67c9edf · Oct 20, 2026 · 30 filesMessage 80 · StrongInformational 15Details
Commit message · ziggie

build: bump Go language and toolchain versions

Keep lnd compatible with the previous stable Go release by updating the language version in every tracked go.mod file to Go 1.26.10.

Move build and release tooling to Go 1.27.3, including CI, Docker images, the Makefile, protobuf generation, the linter configuration, and mobile build documentation. Update the installation documentation and official Linux archive checksums for Go 1.26.10 as well.

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

This commit is a routine maintenance update that changes which version of the Go programming language is used to build LND. It does not change any LND source code, fix a bug, or address a security vulnerability. The only changes are version numbers in build configuration files, Docker images, CI settings, and documentation.

Security candidateMerge pull request #11164 from ViktorT-11/2026-08-sync-gossip-with-specby Yong · 26b04676 · Oct 20, 2026 · 32 filesMessage 73 · AdequateLow 40Details
Commit message · Yong

Merge pull request #11164 from ViktorT-11/2026-08-sync-gossip-with-spec

lnwire: pull gossip v2 messages in line with BOLT taproot-gossip review 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
signing or wallet pathboot or update pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 40/100

This commit updates LND's experimental gossip-v2 protocol implementation to match a newer version of the Lightning BOLT specification. It changes how several peer-to-peer messages are encoded and decoded, adds stricter checks for required fields, and fixes edge cases such as default HTLC limits and address port handling. The changes are primarily a protocol conformance and hardening patch rather than a fix for a known active vulnerability.

AI review queuedMerge pull request #11373 from starius/commit-fee-rate-floorby ziggieXXX · 216caf5a · Oct 20, 2026 · 8 filesMessage 73 · AdequateModerate 62Details
Commit message · ziggieXXX

Merge pull request #11373 from starius/commit-fee-rate-floor

multi: enforce the commitment fee rate floor

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

This patch fixes a bug where LND could propose or accept Lightning channel commitment transaction fees that were too low to be valid. Specifically, with a setting of max-commit-fee-rate-anchors=1, LND would propose 250 sat/kw, below the 253 sat/kw floor its own channel state machine requires. This could prevent channels from carrying payments or cause peers to reject or fail to sign updates. The fix enforces the 253 sat/kw minimum when opening channels, updating fees, and at startup configuration.

Security candidateMerge pull request #11360 from saubyk/scripts/keys-removal-policyby Yong · 88a5b0ee · Oct 20, 2026 · 1 fileMessage 73 · AdequateInformational 20Details
Commit message · Yong

Merge pull request #11360 from saubyk/scripts/keys-removal-policy

scripts: document release signing key removal policy

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 boundarydocumentation-only discountmerge-commit duplicate discount
AI analysis · Informational 20/100

This commit only adds documentation explaining when and why old release signing keys are removed from the project. It does not change any code, verification logic, or cryptographic handling. There is no security vulnerability in the commit itself.

Security candidateMerge pull request #11343 from saubyk/scripts/remove-ellemouton-keyby Yong · a1cc86d6 · Oct 19, 2026 · 6 filesMessage 73 · AdequateLow 29Details
Commit message · Yong

Merge pull request #11343 from saubyk/scripts/remove-ellemouton-key

scripts: remove expired and unused release signing keys

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 boundarymerge-commit duplicate discount
AI analysis · Low 29/100

This commit removes several expired or unused PGP public keys from the LND release verification script. It does not change any application code, wallet logic, or network behavior. The main effect is that future release signature checks will no longer trust signatures made by the removed keys, which is a routine cleanup of release-signing trust material.

AI review queuedMerge pull request #10919 from GeorgeTsagk/local-reputation-subsystemby Suheb · 3abd5967 · Oct 16, 2026 · 32 filesMessage 73 · AdequateInformational 21Details
Commit message · Suheb

Merge pull request #10919 from GeorgeTsagk/local-reputation-subsystem

[1/?] Local reputation: subsystem core, read only

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discountsecond-pass: unusually broad change
AI analysis · Informational 21/100

This commit adds a new experimental 'local reputation' feature to the Lightning Network Daemon (LND). It watches HTLC forwarding events and computes per-channel reputation scores, but only logs the results. It does not change routing decisions, alter wire messages, or write anything to disk. The feature is enabled by default but can be disabled with a config flag. The main security-relevant design is the panic boundary that prevents bugs in this new subsystem from crashing the HTLC forwarding path.

AI review queuedMerge pull request #11335 from ziggie1984/channeldb-remove-dead-v6-deserializerby ziggieXXX · a804c68c · Oct 16, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · ziggieXXX

Merge pull request #11335 from ziggie1984/channeldb-remove-dead-v6-deserializer

channeldb: remove dead v6 close summary deserializer

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit simply deletes an unused, deprecated helper function that was only kept around for old database migrations. Removing dead code does not change how the program behaves or introduce a security issue.

Security candidateMerge pull request #11307 from bitromortac/20261008-41a8-dispatchby ziggieXXX · cc6f08b8 · Oct 16, 2026 · 10 filesMessage 73 · AdequateLow 29Details
Commit message · ziggieXXX

Merge pull request #11307 from bitromortac/20261008-41a8-dispatch

bolt12handler: add BOLT 12 invoice generation and signing

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 · Low 29/100

This commit adds new code to LND that lets a node create and cryptographically sign BOLT 12 invoices. It also changes how invoice signing works so that signing can be done by a remote signer that never sees the node's private key. The change is a feature addition, not a fix for a known bug or vulnerability. There is no evidence in the commit message or diff that the project treats this as a security patch.

AI review queuedMerge pull request #11334 from gijswijs/fee-ceiling-clampby Yong · 65c3263c · Oct 15, 2026 · 6 filesMessage 73 · AdequateModerate 60Details
Commit message · Yong

Merge pull request #11334 from gijswijs/fee-ceiling-clamp

lnwallet/chainfee: clamp web API fee estimates to a ceiling

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

This commit adds an upper limit (ceiling) to fee estimates that LND pulls from an external web API. Previously, only a lower bound existed, so a malicious or malfunctioning fee API could return extremely high fee rates. Those inflated rates could then flow into wallet operations and cause users to overpay transaction fees. The patch clamps both per-block fee estimates and the minimum relay fee rate to a maximum of 10,000 sat/vbyte. It also ties the sweeper's maximum allowed fee rate to the same ceiling so the two limits stay consistent.

AI review queuedMerge pull request #11330 from Roasbeef/remote-next-rev-optionby ziggieXXX · 6052d0bc · Oct 15, 2026 · 21 filesMessage 73 · AdequateModerate 61Details
Commit message · ziggieXXX

Merge pull request #11330 from Roasbeef/remote-next-rev-option

lnwallet+chanstate: reject unexpected revocations, make RemoteNextRevocation an fn.Option

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 61/100

This commit hardens how LND handles revocation messages during Lightning channel state updates. Previously, parts of the code treated a missing 'next revocation point' as a nil pointer, which could lead to state updates being applied in the wrong order or to invalid revocations partially updating the channel state. The change makes the optional nature of that point explicit, validates the revocation before touching stored secrets, and rejects unexpected revocations cleanly. It is a defensive bug-fix rather than a confirmed exploited vulnerability.

Security candidateMerge pull request #11311 from ziggie1984/fix-sql-graph-empty-signaturesby Olaoluwa Osuntokun · 4ea5f814 · Oct 12, 2026 · 4 filesMessage 73 · AdequateLow 30Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11311 from ziggie1984/fix-sql-graph-empty-signatures

graph/db: normalize empty policy signatures

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 boundarymerge-commit duplicate discount
AI analysis · Low 30/100

This is a bug-fix patch for LND's native SQLite graph migration. When moving channel data from the older key-value (KV) database format to the new SQLite format, empty routing-policy signatures were stored differently: KV used an empty-but-non-nil byte slice, while SQLite returned nil. The migration validation treated these as unequal, causing the migration to fail. The fix normalizes empty signatures to nil before comparison so the migration succeeds. It is a correctness/reliability fix rather than an exploitable vulnerability.

Security candidategraph/db: normalize empty policy signaturesby ziggie · 4eec0af2 · Oct 9, 2026 · 2 filesMessage 45 · ThinInformational 24Details
Commit message · ziggie

graph/db: normalize empty policy signatures

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 24/100

This commit fixes a test-only data comparison mismatch during a database migration. When moving channel policy data to SQLite, empty signature fields were stored differently (nil vs empty slice), causing validation comparisons to fail. The fix normalizes empty signatures to nil before comparison, and adds a test case covering this scenario. It does not appear to affect live node behavior or introduce a security vulnerability.

AI review queuedMerge pull request #11246 from Roasbeef/fix-musig2-session-lifecycleby Olaoluwa Osuntokun · 7542f418 · Oct 9, 2026 · 13 filesMessage 73 · AdequateModerate 51Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11246 from Roasbeef/fix-musig2-session-lifecycle

lnwallet: clean up transient MuSig2 sessions

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

This commit fixes how LND manages temporary MuSig2 signing sessions for Taproot Lightning channels. Previously, these sessions could be left alive longer than necessary or leak if a signing round failed or was aborted. The patch releases the backing signer session as soon as the local node no longer needs it, and adds regression tests to confirm sessions are cleaned up. It also fixes a related error-handling bug where an invalid MuSig2 partial commitment signature was rejected without including the commitment height and transaction details that the remote peer needs for debugging.

Security candidateMerge pull request #11068 from GeorgeTsagk/auxsig-requiredby ziggieXXX · a8970c6e · Oct 9, 2026 · 5 filesMessage 73 · AdequateHigh 70Details
Commit message · ziggieXXX

Merge pull request #11068 from GeorgeTsagk/auxsig-required

lnwallet: reject commitments missing aux HTLC signatures

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 · High 70/100

This commit fixes a security gap in LND's taproot overlay channels. Previously, a channel peer could send a commitment transaction with missing or mismatched auxiliary HTLC signatures, and LND would still accept it. Those signatures are needed to safely recover funds if the channel is later force-closed. Without them, HTLCs could be left on disk with empty signatures, making them unsweepable at force-close time and potentially locking up funds. The patch now rejects such commitments, causing a force close instead of silently accepting a dangerous state. It also fixes a test helper so that restarting a channel does not drop the auxiliary signer configuration.

Security candidateMerge pull request #11290 from allenpiscitello/fix/blinded-path-fee-overflowby ziggieXXX · d9a52264 · Oct 7, 2026 · 3 filesMessage 78 · AdequateModerate 56Details
Commit message · ziggieXXX

Merge pull request #11290 from allenpiscitello/fix/blinded-path-fee-overflow

blindedpath: avoid uint32 overflow in accumulated fee calc

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 · Moderate 56/100

This commit fixes a math overflow bug in LND's blinded payment paths. When building a private (blinded) route for an invoice, the node adds up per-hop fees using 32-bit unsigned integers. If the total base fee or fee rate exceeded about 4295, the sum would wrap around to a tiny number. The invoice would then advertise fees that were too low, so any payer sending through that path would underpay and the payment would fail. The fix uses checked 64-bit arithmetic and simply skips any route whose true fees don't fit in the invoice's 32-bit fields, rather than advertising incorrect fees.

Security candidatesqldb: prevent retry backoff overflowby ziggie · 34b0d4ef · Oct 1, 2026 · 4 filesMessage 50 · ThinLow 36Details
Commit message · ziggie

sqldb: prevent retry backoff 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 safety
AI analysis · Low 36/100

This commit fixes a math overflow bug in the database retry logic of LND, a Bitcoin Lightning Network node. When retrying failed database operations, the code could calculate a wait time so large that it wrapped around to a negative number, potentially causing immediate retries, unexpected behavior, or node instability. The fix caps each step of the calculation and uses safer integer math. It is a defensive hardening change rather than a directly exploitable remote vulnerability.

AI review queuedMerge pull request #11191 from bitromortac/2604-bolt12-1hby ziggieXXX · f3a8f4e8 · Oct 1, 2026 · 21 filesMessage 58 · ThinLow 37Details
Commit message · ziggieXXX

Merge pull request #11191 from bitromortac/2604-bolt12-1h

bolt12: finalize the codec package

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
signing or wallet pathparser or protocol pathmerge-commit duplicate discountsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 37/100

This commit finalizes LND's new BOLT 12 codec package. It is mostly a refactor: public Encode/Decode helpers are renamed to internal encodeBech32/decodeBech32, validation helpers are unexported, and new helpers such as EncodeSigned and OfferHash are added. The most user-visible change is that the bech32 decoder no longer rejects very long strings on its own; it now expects the caller (onion-message envelope, RPC, or CLI) to enforce size limits. The commit also adds a display-only DecodeInvoiceStringUnvalidated entry point and tightens signing so that SignInvoice/SignInvoiceRequest run writer validation before producing a signature. There is no explicit bug fix or security patch in the diff; the changes are defensive API hardening.