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

Lower-priorityMerge pull request #11326 from ziggie1984/docs/v022-release-note-fragmentsby ziggieXXX · bbad0489 · Oct 15, 2026 · 9 filesMessage 58 · ThinTriage 0Details
Commit message · ziggieXXX

Merge pull request #11326 from ziggie1984/docs/v022-release-note-fragments

docs: add per-PR release note fragments

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityscripts: check release notes consistency in CIby ziggie · d4480547 · Oct 15, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · ziggie

scripts: check release notes consistency in CI

The release note fragments in docs/release-notes/unreleased are only
consistent as long as the fragments are deleted once their change is
released, and a release is only cut after its fragments were folded into
its release note document. Nothing enforced either, so a forgotten step
would either announce a change twice or ship a release with incomplete
notes.

Add check-release-notes-consistency.sh with two modes. On pull requests, it
fails if a fragment belongs to a PR that is already announced in a
version-wide release note document, which catches both the fold and the
port of a patch release's notes to master. If the pull request bumps
build/version.go to a release version, release candidate or final, it also
requires the release note document of that version to exist and all
fragments to be folded into it. A final release additionally requires a
non-empty contributors section. The release mode runs the same readiness
check in the release build against the tagged commit.

The check runs in its own CI job that ignores the no-changelog label, since
the pull requests that fold fragments or bump the version carry that label.
Release branches keep their release version between releases, so the
readiness check only runs for the pull request that changes the version.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydocs: add per-PR release note fragmentsby ziggie · ed24eb97 · Oct 15, 2026 · 6 filesMessage 80 · StrongTriage 0Details
Commit message · ziggie

docs: add per-PR release note fragments

Every PR currently edits the release note document of the next release and
its shared contributor list, so concurrent PRs keep conflicting on the same
lines. Following Bitcoin Core's release note process, new entries are
instead added as one fragment file per PR in docs/release-notes/unreleased.

The fragments are not tied to a release. Each one is folded into the release
note document of the first release that ships the change when that release
is prepared, and the contributor list is generated from Git history. This
means a contributor doesn't need to know whether the change will be
backported: the automated backport workflow cherry-picks the fragment along
with the change, so a backported fix ends up in the next patch release, and
the port of the patch release notes to master deletes the released
fragments there.

The existing release-notes-0.22.0.md and release-notes-0.21.5.md stay as the
baseline for the entries written before this change.

The guide lives in docs/release-notes/README.md. The pull request template,
contribution guidelines, backport workflow documentation and release note CI
failure message point contributors at it.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityscripts: match exact PR number in release note checkby ziggie · 3dfc5d67 · Oct 15, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ziggie

scripts: match exact PR number in release note check

The release note check used a plain substring match, so a PR whose number
is a prefix of another PR's number (e.g. 1132 and 11326) passed as soon as
the longer number was referenced. Require that the PR number isn't followed
by another digit.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityscripts: validate release note fragments in CIby ziggie · 776b1580 · Oct 15, 2026 · 3 filesMessage 80 · StrongTriage 8Details
Commit message · ziggie

scripts: validate release note fragments in CI

The release note check only verified that the PR's link shows up somewhere
under docs/release-notes, so a fragment with the wrong filename, a missing
link or misspelled headings passed. Since the fragments are consolidated at
release time, such mistakes would only surface then.

Validate every file that a PR adds or modifies in a subdirectory of the
release notes against its base: it must live in unreleased/, start with a
top-level heading and only use the headings of the template or of the
newest version-wide release note document, without the document title or a
contributors section. A newly added fragment must additionally be named
after the PR and link to it. Modified fragments are exempt from that, so
that a follow-up PR can extend the entry of an earlier one.

The existing recursive link check is kept so that version-wide release note
files of older release lines continue to pass. The CI checkout now fetches
two commits so that the base of the PR's merge commit is available.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
defensive validation
Lower-priorityMerge pull request #11308 from saubyk/gateway-v0.7.1by ziggieXXX · 1f67d1ff · Oct 15, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11308 from saubyk/gateway-v0.7.1

github: bump gateway code-review to v0.7.1

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

Lower-priorityMerge pull request #11325 from Roasbeef/graph-kv-validation-cleanupby Yong · b0347689 · Oct 14, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11325 from Roasbeef/graph-kv-validation-cleanup

graph/db: keep KV graph records readable

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 revocation validation release noteby Olaoluwa Osuntokun · b2496ee9 · Oct 14, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

docs: add revocation validation release note

In this commit, we add the release note for the revocation validation and optional next revocation point updates.

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
documentation-only discount
Lower-prioritygraph/db: fix lint line lengthsby Olaoluwa Osuntokun · 28dd1a7d · Oct 14, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

graph/db: fix lint line lengths

In this commit, we wrap the four lines reported by the public CI lint job. We also shorten the KV-only test skip message so the pruning regression stays within the 80-column limit.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityMerge pull request #11328 from ziggie1984/dev-docker-release-tagsby Olaoluwa Osuntokun · 5520f556 · Oct 14, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11328 from ziggie1984/dev-docker-release-tags

build: use release tags in dev Docker image

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-prioritybuild: remove ineffective cgo DNS settingby ziggie · 479e0f7e · Oct 13, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

build: remove ineffective cgo DNS setting

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybuild: use release tags in dev Docker imageby ziggie · e69112e1 · Oct 13, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

build: use release tags in dev Docker image

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityMerge pull request #11320 from ziggie1984/docs-move-kvdb-cache-note-to-v0215by ziggieXXX · a3756272 · Oct 13, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · ziggieXXX

Merge pull request #11320 from ziggie1984/docs-move-kvdb-cache-note-to-v0215

docs: move kvdb cache note to v0.21.5

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11318 from ziggie1984/docs/aux-sig-v0215-release-noteby ziggieXXX · dfc69821 · Oct 13, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11318 from ziggie1984/docs/aux-sig-v0215-release-note

docs: move aux sig validation note to v0.21.5

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 #11322 from ziggie1984/docs-move-11246-release-notesby Olaoluwa Osuntokun · 318292e2 · Oct 12, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11322 from ziggie1984/docs-move-11246-release-notes

docs: move MuSig2 session cleanup release note to 0.21.5 and 0.20.6

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

Lower-prioritydocs: move the MuSig2 session cleanup release note to 0.21.5 and 0.20.6by ziggie · 16989265 · Oct 12, 2026 · 3 filesMessage 93 · StrongTriage 0Details
Commit message · ziggie

docs: move the MuSig2 session cleanup release note to 0.21.5 and 0.20.6

In this commit, we move the release notes for #11246 out of the 0.22.0
notes and into the 0.21.5 and 0.20.6 notes, since the change is being
backported to both release branches (#11310, #11309). The separate
its commits landed through #11246. The text matches the backport PRs:
the 0.20.6 entry leaves out the cooperative-close round wording, as that
part of the change is not backported to 0.20.x.

We also drop the "Pins" contributor entry from 0.22.0, which was only
there for this change, and the "Nishant Bansal" entry, which was moved
to 0.21.4 in e4be20ead and re-added by mistake in 0a03890e9.

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-prioritydocs: move kvdb cache note to v0.21.5by ziggie · af8e7a6b · Oct 12, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: move kvdb cache note to v0.21.5

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11313 from ziggie1984/docs-empty-release-notes-0.21.5-0.20.6by Olaoluwa Osuntokun · eb30b24d · Oct 9, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11313 from ziggie1984/docs-empty-release-notes-0.21.5-0.20.6

docs: add empty v0.21.5 and v0.20.6 release notes

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-prioritydocs: add empty patch release notesby ziggie · 00658ae2 · Oct 9, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add empty patch release notes

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydocs: add release note for graph migration fixby ziggie · 7513eb04 · Oct 9, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add release note for graph migration 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 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.