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 38 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 #11281 from ziggie1984/lint-intrange-cleanupby Olaoluwa Osuntokun · 95c56eeb · Sep 30, 2026 · 49 filesMessage 58 · ThinInformational 15Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11281 from ziggie1984/lint-intrange-cleanup

lnd: use Go integer ranges

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

This commit is a large but purely cosmetic code cleanup. It replaces old-style Go for loops like 'for i := 0; i < N; i++' with the newer 'for i := range N' syntax introduced in Go 1.22. No logic, behavior, or security properties of the code are changed.

Lower-priorityMerge pull request #11264 from djkazic/kvdb-bucket-id-cacheby ziggieXXX · afcea30d · Sep 30, 2026 · 11 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11264 from djkazic/kvdb-bucket-id-cache

kvdb/sqlbase: cache nested bucket ids within a transaction

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: enable intrange linterby ziggie · 1bb35fd5 · Sep 29, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · ziggie

build: enable intrange linter

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityMerge pull request #11276 from Roasbeef/sec-key-updateby Olaoluwa Osuntokun · f9872e3a · Sep 29, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11276 from Roasbeef/sec-key-update

docs: update security key link in SECURITY.md

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
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11250 from ziggie1984/ci-live-label-checkby Olaoluwa Osuntokun · 8d12806b · Sep 29, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11250 from ziggie1984/ci-live-label-check

build: reduce CI pressure (live labels, docs-only/draft gating, cancel on merge)

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: update security key link in SECURITY.mdby Olaoluwa Osuntokun · 28ed93ae · Sep 29, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

docs: update security key link in SECURITY.md

The gist revision previously linked in SECURITY.md serves an export of
the security@lightning.engineering key that is now shown as expired
(expiry 2026-09-13). The key itself is unchanged; its expiry has been
extended to 2027-09-13. This updates the link to point at the new
export of the same key. The key fingerprint is unchanged:

91FE 464C D751 01DA 6B6B AB60 555C 6465 E5BC B3AF

85/100 · StrongMessage clarity
✓ 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
documentation-only discount
Lower-prioritydocs: add release note for the offer storeby bitromortac · 9449605d · Sep 28, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · bitromortac

docs: add release note for the offer store

Add the offer store to the BOLT 12 section of the 0.22.0 release notes.
The PR link holds a placeholder until the PR number is known.

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
documentation-only discount
Lower-priorityscripts: add upgrade-ots.pyby Boris Nagaev · 4ad9e2bf · Sep 26, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Boris Nagaev

scripts: add upgrade-ots.py

The OpenTimestamps proofs attached to releases are uploaded right after
stamping, when they still depend on the calendar servers. Once a
calendar has committed the stamp to Bitcoin, `ots upgrade` makes the
proof verifiable with a Bitcoin node alone.

upgrade-ots.py upgrades the proofs of the published releases that
aren't complete yet, verifies each upgraded proof against the release
file it timestamps, and writes the results to a new directory. It only
reads from GitHub. The directory holds upload.sh, which replaces the
proofs on the releases using gh, a summary, the upgraded proofs, the
originals as .ots.bak and the files they timestamp.

Proofs are verified with the local bitcoind by default. For testing
without a node, --esplora verifies them against block headers from an
Esplora API, and warns that this trusts that server.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritykvdb: run shared backend tests against sqliteby djkazic · 9f0020e8 · Sep 25, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · djkazic

kvdb: run shared backend tests against sqlite

The shared kvdb tests ran against bolt, etcd and postgres, but not
sqlite, even though sqlite shares the sqlbase implementation with
postgres. The two differ in ways that matter to it, for example sqlite
hands out the ids of deleted buckets again.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritykvdb/sqlbase: cache nested bucket ids within a transactionby djkazic · 47e48ac3 · Sep 25, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · djkazic

kvdb/sqlbase: cache nested bucket ids within a transaction

Every nested bucket lookup in the SQL kvdb backend is a query, whereas
with bbolt it's an in-memory lookup. Callers are written with the bbolt
cost in mind and resolve the same bucket path over and over within a
transaction. btcwallet's address manager for example resolves its scope
bucket for every address and account it reads, so the majority of the
queries issued by wallet calls such as WalletBalance are lookups of
bucket ids that were already looked up in the same transaction.

We now cache bucket ids, including buckets that were found not to
exist, for the lifetime of a transaction. As a transaction reads from a
single snapshot, a bucket id can only change through the transaction's
own writes. Creating a bucket updates the cache. Deleting a bucket
clears it, as the delete cascades to an unknown set of sub-buckets and
sqlite may hand out the ids of deleted buckets again. The cache is
bounded, as transactions that walk a large number of buckets don't
benefit from it.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritykvdb: test bucket lookups after create and deleteby djkazic · 0a6688bd · Sep 25, 2026 · 5 filesMessage 78 · AdequateTriage 0Details
Commit message · djkazic

kvdb: test bucket lookups after create and delete

Add tests covering lookups of buckets that are created, deleted and
re-created within the same transaction, and lookups across committed and
rolled back transactions. These run against all backends to make sure
the SQL backend's bucket id cache behaves like bbolt and etcd.

We also test the cache itself, making sure that a repeated lookup isn't
sent to the database and that the cache stays bounded.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritykvdb: add nested bucket lookup benchmark for postgresby djkazic · 2ef8c6e8 · Sep 25, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · djkazic

kvdb: add nested bucket lookup benchmark for postgres

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritydocs: add release noteby djkazic · 37984d4a · Sep 25, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · djkazic

docs: add release note

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritysqldb: close the Postgres migrate driver after useby bitromortac · 8a2e35d5 · Sep 25, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · bitromortac

sqldb: close the Postgres migrate driver after use

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. Each schema migration therefore held one connection
for the life of the store.

A fresh database runs 18 schema migration steps plus one schema version
read, so the store keeps 19 connections after startup. With the default
pool of 25, only 6 connections stay free. If db.postgres.maxconnections
is lower than 20, the migrations wait forever for a free connection,
and lnd does not start.

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 checks that the schema version
calls leave no connection in use, both in the pool and on the server.
The server count is necessary because each driver uses its own handle,
which the pool stats do not include. TestPostgresMigrationSmallConnPool
runs all migrations on a fresh database with a pool of two connections,
under a one minute deadline. It reproduces the startup hang from #11007.

Co-authored-by: Vandit Singh <vanditsinghkv@gmail.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #11258 from ziggie1984/htlcswitch/forwarding-response-lifecycleby ziggieXXX · f2963ce1 · Sep 25, 2026 · 19 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11258 from ziggie1984/htlcswitch/forwarding-response-lifecycle

htlcswitch: align forwarding response and circuit lifetimes

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
AI review queuedbuild: skip CI for docs-only changes and run a fast subset on draftsby ziggie · 098f8445 · Sep 24, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · ziggie

build: skip CI for docs-only changes and run a fast subset on drafts

Every push to a PR currently runs the full CI matrix regardless of what
changed or whether the PR is still being iterated on. Introduce two
measures to cut down on wasted runners while keeping all jobs in
parallel, so a single run still reports as many failures as possible:

1. A ci-gate job runs first and detects documentation-only PRs, i.e.
PRs that only touch files under docs/ or markdown files. Renamed
files are checked under both their old and new name so that moving
a source file into docs/ doesn't count as a documentation change.
The cheap commit and release notes checks always run. The way the
other jobs are skipped depends on whether they have a matrix:

- Non-matrix jobs (static checks, lint) and non-required jobs are
skipped at the job level. A skipped job still reports its status,
so the required checks in branch protection are satisfied.
- Matrix jobs with required legs (unit tests, cross compilation,
pinned dependencies, basic itests) are kept instantiated and skip
their steps instead, in the same way the no-itest label already
works. A job-level condition is evaluated before the matrix is
expanded, so a skipped matrix job would never report the per-leg
check names that branch protection requires and the PR would
stay blocked.

All job-level conditions use !cancelled() so that a failure of the
gate job itself results in the full CI running rather than
everything being skipped.

2. Draft PRs only run a fast subset: static checks, lint, the pinned
dependency check, the non-race unit test legs and the basic itests
(18-22 min per leg). The large itests (up to 86 min per leg),
Windows and macOS itests, cross compilation, the race unit legs
(47-56 min) and the backwards compatibility test are skipped until
the PR is marked ready for review. ready_for_review and
converted_to_draft are added to the pull_request trigger types so
that changing the draft state triggers a run with the right subset;
the concurrency group cancels the previous one.

Push and merge_group runs carry no PR and always run everything.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit only changes how the project's automated GitHub test pipeline is organized. It adds a 'gate' job that decides whether a pull request only touches documentation, and if so, skips the heavy code tests. It also makes draft pull requests run a smaller, faster set of tests. There is no change to the actual Lightning Network software, wallet logic, cryptography, or network handling, so it does not create a security vulnerability in the product users run.

Lower-prioritybuild: cancel unfinished CI runs when a PR is closedby ziggie · b92ce2a5 · Sep 24, 2026 · 1 fileMessage 97 · StrongTriage 0Details
Commit message · ziggie

build: cancel unfinished CI runs when a PR is closed

Once a PR is merged (or closed) its CI result no longer matters, but
a run that is still in progress keeps occupying runners, often for the
better part of an hour due to the itests.

Add a workflow triggered on pull_request_target closed that cancels
every unfinished run of the main CI workflow triggered by the PR's head
commit. pull_request_target is used so the token has actions: write
even for PRs opened from forks. No PR code is checked out or executed.

A PR that is closed and quickly reopened gets a fresh run for the same
head commit. To never cancel it, the handler bails out if the PR is
open again by the time it runs and only considers runs that were
created before the close event.

Only main.yml runs are targeted on purpose: the backport workflow is
triggered by the very same closed event and shares the head commit, so
a broader match would cancel it.

97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11257 from ziggie1984/move-11064-release-noteby ziggieXXX · 5649468c · Sep 24, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11257 from ziggie1984/move-11064-release-note

docs: move the explicit channel type release note to 0.21.4

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 #11212 from ziggie1984/disable-legacy-channelsby ziggieXXX · 112cb5f3 · Sep 24, 2026 · 16 filesMessage 58 · ThinModerate 62Details
Commit message · ziggieXXX

Merge pull request #11212 from ziggie1984/disable-legacy-channels

multi: stop opening legacy channels

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: security-sensitive path
AI analysis · Moderate 62/100

This change stops LND from opening new Lightning channels using the old 'legacy' commitment format. The legacy format makes it harder to recover funds if something goes wrong, because the money owed to you is tied to a secret key that changes with each channel state. From now on, LND will either use a safer default or refuse the channel open. Existing legacy channels keep working normally; only brand-new legacy channels are blocked.

Lower-priorityMerge pull request #11249 from saubyk/gateway-v0.7.0by Yong · ef1ac2bb · Sep 24, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11249 from saubyk/gateway-v0.7.0

github: bump gateway code-review to v0.7.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
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11243 from ziggie1984/build/sqlite-pgx-upgradesby Yong · 33034fb0 · Sep 24, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Yong

Merge pull request #11243 from ziggie1984/build/sqlite-pgx-upgrades

build: update SQLite and pgx drivers

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
Security candidatebuild: read live PR labels in check-label actionby ziggie · 45c9cfff · Sep 24, 2026 · 2 filesMessage 92 · StrongInformational 21Details
Commit message · ziggie

build: read live PR labels in check-label action

The check-label composite action evaluated
github.event.pull_request.labels, which is a snapshot captured when the
pull_request event fired. A label such as no-changelog or no-itest added
after the run kicked off was therefore never seen, not even when
re-running the failed job, because a re-run reuses the original event
payload. The only workaround was pushing a new commit.

Query the current label set through the API instead and only fall back
to the event payload when there is no PR number (push and merge_group
runs) or the API call fails. Re-running a failed job now picks up labels
added after the run started.

The workflow declares explicit permissions, so grant pull-requests: read
for the API call.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Informational 21/100

This is a GitHub Actions workflow fix, not a vulnerability in the LND lightning node software itself. It changes how a CI check reads pull-request labels so that re-running a failed job sees labels added after the run started. The change adds a GitHub API call and grants the workflow read-only access to pull-request metadata. There is no direct security risk to LND users or funds.

Lower-prioritygithub: bump gateway code-review to v0.7.0by saubyk · cc34f3b4 · Sep 24, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · saubyk

github: bump gateway code-review to v0.7.0

Repin the gateway shim from v0.6.0 to v0.7.0: both the gateway-action
SHA and runtime_ref move together. Also raise the job's timeout-minutes
from 15 to 30: a GitHub job timeout cancels the run before gateway can
post an error, and real multi reviews have run past 15 minutes.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Lower-priorityhtlcswitch: run every TestChannelLinkFail case as a subtestby Olaoluwa Osuntokun · 75d660a8 · Sep 23, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

htlcswitch: run every TestChannelLinkFail case as a subtest

In this commit, we fix TestChannelLinkFail so it actually runs all of
its cases. The loop over the table would `return` as soon as it hit a
case that expects the link to stay up, which ended the whole test. As
the very first case (a warning message from the remote) is one of
those, none of the cases after it had been running, including the ones
that assert we force close on an invalid commit_sig.

We now run each case as a subtest, so the early return only ends that
case. All of the existing cases pass.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityhtlcswitch: test unexpected revocation handlingby Olaoluwa Osuntokun · b29d0e09 · Sep 23, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

htlcswitch: test unexpected revocation handling

In this commit, we add link-level coverage for the ReceiveRevocation
validation. The test verifies that the link reports ErrInvalidRevocation,
disconnects the peer, and leaves the channel open.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification