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

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

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

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

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

Merge pull request #10708 from jtobin/alias-perms

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

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

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

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

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

docs: describe invoice collection finality

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

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

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

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

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

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

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

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

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

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

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

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

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

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

invoices: require complete payment collection

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

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

lnwallet: reject a zero CSV delay

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

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

lnwallet+chanstate: keep persisted HTLC data readable

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

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

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

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

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

invoices: reject settled AMP set shards

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

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

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

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

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

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

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

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

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

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

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

invoices: fix test whitespace

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

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

build: pin the new lint job actions by commit

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

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

build: fix the custom linter cache wiring for CI

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

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

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

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

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

Explore captured commits

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

AI review queuedMerge pull request #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.

Lower-prioritybolt12handler: add BOLT 12 invoice generationby bitromortac · a8aca702 · Oct 9, 2026 · 5 filesMessage 68 · AdequateTriage 8Details
Commit message · bitromortac

bolt12handler: add BOLT 12 invoice generation

Build a signed BOLT 12 invoice from a validated invoice request: mirror
the request fields, compute the amount, construct the blinded payment
paths carrying the path_id, and sign the Merkle root. An optional
PaymentPathBuilder supplies multi-hop paths. A single-hop path is the
fallback when there is no builder or the builder fails.

The invoice is signed under the node identity key, so an offer without
offer_issuer_id is refused for now.

The package logs under the B12H sub logger.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validation
Lower-priorityMerge pull request #11302 from saubyk/docs/release-notes-0.22-syncby Olaoluwa Osuntokun · 4ab78a0e · Oct 8, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11302 from saubyk/docs/release-notes-0.22-sync

docs: sync 0.22.0 release notes with unreleased work

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11278 from bitromortac/20260924-6dc2-dispatchby ziggieXXX · a27ead09 · Oct 8, 2026 · 16 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11278 from bitromortac/20260924-6dc2-dispatch

offers: add a SQL-backed store for BOLT 12 offers

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-prioritydocs: sync 0.22.0 release notes with unreleased workby saubyk · f6132dc4 · Oct 8, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · saubyk

docs: sync 0.22.0 release notes with unreleased work

Drop entries for #10900 and #11173, which already shipped in 0.21.x,
and add the missing entries for unreleased master changes, including
the outbound remote signer (#8754). PRs labeled no-changelog are left
out.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11219 from bitromortac/2609-fix-node-announcementby ziggieXXX · c58148dd · Oct 7, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11219 from bitromortac/2609-fix-node-announcement

lnwire: fix NodeAnnouncement2 address decoding

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Security candidateMerge pull request #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.

Lower-priorityMerge pull request #11267 from bitromortac/20260928-35de-messageby ziggieXXX · ff38b9cb · Oct 6, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11267 from bitromortac/20260928-35de-message

sqldb: close the Postgres migrate driver after use

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-prioritydocs: add release notes for migrate driver fixby bitromortac · 99eaf853 · Oct 2, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · bitromortac

docs: add release notes for migrate driver fix

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

Lower-prioritysqldb/v2: close the Postgres migrate driver after useby bitromortac · 720f5010 · Oct 1, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · bitromortac

sqldb/v2: close the Postgres migrate driver after use

The sqldb/v2 Postgres store has the same leak as sqldb. The pgx migrate
driver takes one connection from the pool it gets, and it keeps that
connection until the driver is closed. executeMigrations,
GetSchemaVersion and SetSchemaVersion used the shared pool and never
closed the driver, so each call held one connection for the life of the
store.

Each driver now gets its own database handle from the same DSN, and the
caller closes the driver. Closing the driver closes that handle and
leaves the shared pool open. A failed close is logged.

TestPostgresMigrateDriverReleasesConns is the same test as in sqldb.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritygithub: lint submodules in CIby ziggie · 3db832c2 · Sep 30, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · ziggie

github: lint submodules in CI

Now that all submodules pass make lint-module, run it as part of the
lint job so new lint issues in the submodules are caught on every PR
instead of only when the command is run by hand.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritybuild: allow golang-migrate replace directiveby ziggie · e3f1dafb · Sep 30, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · ziggie

build: allow golang-migrate replace directive

The sqldb/v2 module replaces golang-migrate with the lightninglabs fork
to get custom functionality that is not yet available upstream. Add it
to the gomoddirectives allow list so the submodule linter accepts the
replace directive.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritysqldb/v2: fix lint issuesby ziggie · 9beb5ee1 · Sep 30, 2026 · 11 filesMessage 78 · AdequateTriage 0Details
Commit message · ziggie

sqldb/v2: fix lint issues

Fix the issues reported by the linter for the sqldb/v2 submodule so it
passes make lint-module.

Test helpers now use t.Context() instead of context.Background(), the
redundant copies of loop variables are removed, counter loops use
range-over-int, long lines are wrapped, and the whitespace around
returns follows the nlreturn and whitespace linters. The unused
defaultMigrateOptions helper is removed.

The retry backoff multiplies the initial delay with a factor that is
typed as a duration but is a plain multiplier, so the multiplication is
annotated with a nolint directive for durationcheck.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritysqldb: fix lint issuesby ziggie · f28ca612 · Sep 30, 2026 · 9 filesMessage 61 · AdequateTriage 0Details
Commit message · ziggie

sqldb: fix lint issues

Fix the issues reported by the linter for the sqldb submodule so it
passes make lint-module.

Tests now use t.Context() instead of context.Background(), counter
loops use range-over-int, long lines are wrapped, and the whitespace
around returns follows the nlreturn and whitespace linters. The
migration tests use errors.Is to compare against ErrNilVersion, and a
duplicated word in a comment is removed. The migration file prefix check
uses strings.HasPrefix to keep the line within the limit.

ApplyMigrations no longer assigns an initial value to currentVersion
that is always overwritten. The isSQLite test constant is only used by
tests built with the test_db_sqlite or test_db_postgres tags, so it is
annotated with a nolint directive for the default build.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityfn: fix lint issuesby ziggie · 08912fea · Sep 30, 2026 · 5 filesMessage 51 · ThinTriage 0Details
Commit message · ziggie

fn: fix lint issues

Fix the issues reported by the linter for the fn submodule so it passes
make lint-module. Counter loops now use range-over-int, and the
whitespace around returns and function bodies follows the nlreturn and
whitespace linters.

51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context
Lower-prioritytor: fix lint issuesby ziggie · 9ff076da · Sep 30, 2026 · 2 filesMessage 61 · AdequateTriage 0Details
Commit message · ziggie

tor: fix lint issues

Fix the issues reported by the linter for the tor submodule so it
passes make lint-module by wrapping a long test case line and adding
the missing newline after a multi-line if statement.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritykvdb: fix lint issuesby ziggie · e69f6af9 · Sep 30, 2026 · 6 filesMessage 61 · AdequateTriage 0Details
Commit message · ziggie

kvdb: fix lint issues

Fix the issues reported by the linter for the kvdb submodule so it
passes make lint-module.

The type assertions in the bucket id cache test are now checked, the
redundant copy of the loop variable in the sqlite test is removed,
benchmark loops use range-over-int, and a long comment is rewrapped.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityqueue: fix lint issuesby ziggie · 325dbedb · Sep 30, 2026 · 3 filesMessage 61 · AdequateTriage 0Details
Commit message · ziggie

queue: fix lint issues

Fix the issues reported by the linter for the queue submodule so it
passes make lint-module.

Tests now use t.Context() instead of context.Background(), counter
loops use range-over-int, long lines are wrapped, and the whitespace
around returns and select blocks follows the nlreturn and whitespace
linters.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityactor: fix lint issuesby ziggie · 85f0c9c5 · Sep 30, 2026 · 15 filesMessage 61 · AdequateTriage 0Details
Commit message · ziggie

actor: fix lint issues

Fix the issues reported by the linter for the actor submodule so it
passes make lint-module.

Most of the changes are mechanical: tests now use t.Context() instead of
context.Background(), counter loops use range-over-int, and lines are
wrapped to the 80 character limit. The examples now check the error
returned by Shutdown, and the unused blockingBehavior and
deadLetterTestMsg test helpers are removed.

The context fields held by the actor, the mailboxes and the actor
system are intentional as they govern the lifecycle of those types, so
they are annotated with nolint directives. The same applies to the
cancel func created in NewActor, which is stored on the actor and
invoked by Stop.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedMerge pull request #11277 from GeorgeTsagk/maxfeeratio-ceilingby ziggieXXX · 69e35917 · Sep 30, 2026 · 4 filesMessage 73 · AdequateLow 36Details
Commit message · ziggieXXX

Merge pull request #11277 from GeorgeTsagk/maxfeeratio-ceiling

[1.5/3] aux revocation: allow maxFeeRatio above 1.0

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

This change loosens a safety cap on Bitcoin transaction fees for a specific LND wallet RPC. Previously, callers could not allow fees larger than the transaction's total output value. Now they can opt in to a ratio up to 5x the output value, with a hard ceiling and an audit log warning. The intended use is legitimate: sweeping or re-creating tiny 'asset carrier' outputs that hold only about 1000 satoshis of Bitcoin but carry valuable off-chain assets. Without the higher cap, those operations could be blocked when on-chain fees spike. The change is defensive rather than a vulnerability fix, but it does increase the damage a compromised caller or malicious user with RPC access could do by overpaying fees.

Lower-priorityMerge pull request #10452 from ziggie1984/add-submodule-linter-optionby Olaoluwa Osuntokun · dcc6ffd7 · Sep 30, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #10452 from ziggie1984/add-submodule-linter-option

scripts: add make command to lint submodules

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #11280 from ziggie1984/lint-enable-intrangeby ziggieXXX · f0f23ef3 · Sep 30, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · ziggieXXX

Merge pull request #11280 from ziggie1984/lint-enable-intrange

build: enable intrange linter

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount