CommitWatch RSS
LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Source repository ↗
Repository coverage

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

141security candidates194second-pass queue1285AI analyses
78commits · 30 days
173commits · 60 days
599commits · 180 days
1237commits · 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.

67/100 average clarity
318Strong · 80–100
646Adequate · 60–79
391Thin · 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 Osuntokun20942204474
Elle Mouton26832268167
ziggie44416413165
Yong28513171
LNBiG111173
Jared Tobin909171
bitromortac531051069
yyforyongyu83861068
Erick Cestari26726070
Andras Banki-Horvath11311072
Gijs van Dam33230073
ziggieXXX2026070
Analysis record

Published AI watches

Last scanned 4 minutes ago

Moderate 62 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

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

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 chan…

Prevents opening new channels with the legacy commitment type, whose tweaked to_remote output complicates data-loss recoveryCloses a negotiation path where an empty channel_type TLV bypassed feature checks and forced a legacy channelAdds explicit RPC and wire rejection with a dedicated error code
112cb5f3by ziggieXXX+265−4716 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 56 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11223 from gijswijs/legacy-dust-retribution-fix

This update fixes a bug in how LND handles old-style punishment transactions when a channel partner tries to cheat. Previously, tiny (dust) HTLCs were left as blank placeholder entries in the punishment data, which could cause the node to …

nil-pointer dereference risk in breach retribution pathlegacy revocation log handling inconsistency with modern formatdefensive hardening added for trimmed/dust HTLCs
500ca51fby ziggieXXX+168−146 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11190 from Roasbeef/zpay32-reject-duplicate-payment-hashes

This change tightens how LND reads Lightning invoices (BOLT 11). Previously, if an invoice contained more than one payment hash field, LND would silently keep the first one and ignore the rest. Now it rejects the invoice entirely. The rele…

Behavior change from 'use first duplicate field' to 'reject duplicate fields'New error type ErrDuplicatePaymentHash returned on duplicate payment hash fieldsMalformed/unsupported-length duplicate payment hash now treated as duplicate and rejected
86306f89by Yong+147−106 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 98 · Strong
LL Lightning LabsLND BitcoinLightning Network

zpay32: reject duplicate payment hash fields

This change tightens how LND reads Lightning invoices. Previously, if an invoice contained more than one payment hash field, LND would silently keep the first valid one and ignore the rest. Now it rejects such invoices outright. This preve…

Behavioral change from silent first-field acceptance to explicit rejection of duplicate payment hash fieldsPrevents invoice parsing from depending on field ordering when multiple payment hashes are presentCovers malformed first field + valid second field, closing a potential bypass
e2f27063by Olaoluwa Osuntokun+147−106 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 53 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11132 from yyforyongyu/task-11129-pong

This change fixes how LND answers network 'ping' messages from other Lightning nodes. Previously, LND would sometimes silently ignore valid pings to limit reply traffic, which violates the Lightning protocol (BOLT 1) and could make a peer …

Protocol compliance fix: BOLT 1 requires a Pong for every valid PingRemoved silent suppression of Pong replies that could cause peer timeout/misbehaviorUnified rate limiting now accounts for amplification bandwidth, not just ping count
d3d1f1d0by Olaoluwa Osuntokun+274−1715 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 90 · Strong
LL Lightning LabsLND BitcoinLightning Network

itest: stop creating legacy channels

This commit updates LND's integration tests to stop using an obsolete 'legacy' channel type and adds a test confirming that LND now rejects that legacy type. The commit message says the real fix is elsewhere in the same pull request: previ…

Deprecated commitment format (legacy) is now rejected by RPCTest added to verify legacy channel type is refusedUnused legacy node configuration flag removed
03d8b09dby ziggie+24−85 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11198 from gijswijs/amp-setlocal-reconstruction-fix

This change fixes a bug in LND's handling of AMP (Atomic Multi-Path) payments. Previously, if one partial payment set failed to reconstruct its secret preimage, the entire invoice was canceled, including unrelated partial payment sets from…

Denial-of-service against reusable static AMP invoices by causing unrelated accepted HTLC sets to be canceledIncorrect invoice state transition from set-local failure to global invoice cancellationAvailability impact on multi-payer AMP invoice scenarios
88959aecby Olaoluwa Osuntokun+155−44 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11200 from ziggie1984/build-go-1.27.1

This commit updates the Go programming language version used to build LND from 1.25.13/1.26.6 to 1.26.8 (language version) and 1.27.1 (toolchain). It also regenerates many automatically generated RPC files and adjusts linter settings. The …

Go version bump may indirectly address unlisted runtime/standard-library security fixesLarge regenerated protobuf files suggest dependency/toolchain refresh rather than logic changeLinter configuration expanded to suppress new checks, consistent with a toolchain upgrade
ef4820e5by Olaoluwa Osuntokun+4932−412670 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: adopt focused golangci-lint v2.13 checks

This commit is a routine build-maintenance change. It updates the project's Go linter configuration to a newer version and fixes the resulting style warnings: a WebSocket header spelling and several documentation comments that didn't start…

bada7ea3by ziggie+27−1911 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnrpc: regenerate protos with Go 1.27

This commit is a housekeeping change that regenerates automatically generated RPC binding files using a newer Go compiler version. The only differences are in code comments (doc-comment formatting), not in actual program logic or API behav…

dd523108by ziggie+4501−369826 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 100 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: fix Go 1.27 compatibility

This commit is a routine build-and-test maintenance patch to make the LND codebase compile and pass tests with the upcoming Go 1.27 release. It upgrades the project's custom linter tool, refreshes many indirect tool dependencies, adjusts o…

No production code changesNo vulnerability fix or CVE reference presentDependency-only refresh in tools module (development tooling)
6b54a387by ziggie+365−3706 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: bump Go language and toolchain versions

This commit is a routine maintenance update that changes which version of the Go programming language is used to build the lnd project. It does not change any application logic, fix a bug, or address a security vulnerability. The project i…

b1f9ca66by ziggie+39−3930 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 83 · Strong
LL Lightning LabsLND BitcoinLightning Network

invoices: cancel only the failing AMP set on reconstruction failure

This commit fixes a bug in LND's invoice handling for reusable AMP (Atomic Multi-Path) invoices. Previously, if one payment set failed to reconstruct its preimage, the entire invoice was canceled, even though other valid payment sets on th…

Denial-of-service-like availability impact: a malicious or buggy payer could cause a whole reusable AMP invoice to be canceled, blocking legitimate concurrent payersSet-local failure incorrectly escalated to invoice-global cancellationRegression test added for concurrent-set survival after reconstruction failure
d74ab6faby Gijs van Dam+141−42 files
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11061 from bitromortac/2604-bolt12-1f

This commit adds the missing cryptographic signature layer for BOLT 12 offers in LND. It builds a Merkle tree from the message fields, signs that tree with a BIP-340 Schnorr signature, and now rejects invoice requests and invoices whose si…

Adds BIP-340 Schnorr signature verification for BOLT 12 invoice_request and invoice messagesMerkle tree commits to canonical re-encoded TLV records; non-minimal feature/amount encodings now rejected to preserve byte-exactnessSignature TLV type 240 and reserved range 240-1000 excluded from the signed Merkle root
1049d301by Yong+2076−7815 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11125 from bhandras/codex/reorg-aware-output-lock-20260825

This commit adds a new optional wallet feature to LND that lets users lock UTXOs until the transaction spending them reaches a chosen confirmation depth, instead of relying on a wall-clock timeout. It is a feature addition with safety chec…

New RPC fields release_after_spend_confs and confirmed_spend_height added to LeaseOutput and FundPsbtCustom lock ID enforced as required for confirmation-controlled FundPsbt leases; all-zero and reserved internal IDs rejectedCapability check (ResolveOutputLeaser) prevents silent downgrade to time-only lease when confirmation control is requested
80dde144by Yong+1293−10021 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #10812 from ziggie1984/chanstate-kv-store-move

This commit is a large internal code reorganization for the LND Lightning node. It moves channel state storage logic from the `channeldb` package into a new `chanstate` package, while keeping the same database keys, serialization formats, …

Large refactoring with no change to cryptographic or consensus-critical logicCodec serialization moved verbatim to new package; wire format unchangedDatabase bucket keys and TLV record types preserved
62b0a073by Olaoluwa Osuntokun+3923−310924 files
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #10804 from GeorgeTsagk/close-immediately-itest-lnd-7c38

This change fixes a data-handling bug in LND's channel-opening code. When opening a Lightning channel using an optional 'auxiliary funding controller' (used for custom channel types such as Taproot Assets), the funding manager was previous…

Data-correctness fix in funding handshake: negotiated channel configs now exposed to auxiliary funding controllerAuxiliary funding controller receives incomplete channel state before patch, complete state after patchNo explicit security claim, CVE, or advisory referenced in commit or supplied materials
1e127653by Olaoluwa Osuntokun+291−254 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 88 · Strong
LL Lightning LabsLND BitcoinLightning Network

bolt12: verify invoice_request and invoice signatures on read

This change makes LND's BOLT 12 invoice and invoice-request reader actually check that the digital signature is valid, instead of only checking that a signature field exists. Before, an attacker could craft or modify a BOLT 12 message and …

Missing cryptographic verification on parsed BOLT 12 messages replaced with BIP-340 Schnorr signature verificationReader accepted any 64-byte placeholder signature before the patchNew negative tests verify rejection of wrong-signer and tampered Merkle-root fields
aa8bd19fby bitromortac+272−723 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

itest: cover confirmation-controlled leases

This commit only adds a new integration test for an existing feature called confirmation-controlled leases. It does not change production code, so it cannot introduce a security vulnerability or fix one directly. The test exercises how lon…

a1ab4e92by Andras Banki-Horvath+152−02 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 68 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11122 from gijswijs/websocket-proxy-hardening

This update fixes two security-related bugs in LND's REST WebSocket proxy. First, a specially crafted WebSocket protocol header could crash the proxy (a panic). Second, the proxy previously had no limit on how large an incoming WebSocket m…

panic fix in request header parsingunbounded incoming WebSocket message read now cappedincorrect header value assignment possible before fix
c662f853by Yong+227−104 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
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 #11065 from ellemouton/agent/walletrpc-create-accountby Yong · b309be58 · Aug 17, 2026 · 20 filesMessage 73 · AdequateInformational 24Details
Commit message · Yong

Merge pull request #11065 from ellemouton/agent/walletrpc-create-account

walletrpc: add XCreateAccount for wallet-derived accounts

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

This commit adds a new, clearly marked experimental RPC and command-line option called XCreateAccount that lets an LND user create a separate, named pocket of on-chain funds within the same wallet. It is not a security patch and does not fix a vulnerability. The main risk is user error: money sent to one of these accounts cannot be found again with only the wallet seed, so the user must separately save extra recovery details. The feature is gated behind an explicit 'I know what I am doing' flag on release builds to reduce accidental misuse.

AI review queuedMerge pull request #8754 from ViktorT-11/2024-05-add-outbound-remote-signerby Yong · 2bbf02ba · Aug 17, 2026 · 37 filesMessage 73 · AdequateLow 37Details
Commit message · Yong

Merge pull request #8754 from ViktorT-11/2024-05-add-outbound-remote-signer

Add `Outbound` Remote Signer implementation

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

This commit adds a new 'outbound' remote-signer mode to LND. In the existing 'inbound' mode, the watch-only node connects to the signer; in the new 'outbound' mode, the signer node connects out to the watch-only node. The change introduces a dedicated gRPC listener, a new macaroon permission ('remotesigner:generate'), and configuration validation. It is a large feature addition rather than a clear-cut vulnerability fix, but it touches authentication, network exposure, and wallet startup logic, so it has security relevance.

Lower-priorityMerge pull request #11081 from ziggie1984/agent/add-11035-to-0.20.4-notesby ziggieXXX · 4045fc9f · Aug 15, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11081 from ziggie1984/agent/add-11035-to-0.20.4-notes

docs: add 11035 entries to the 0.20.4 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
Security candidateMerge pull request #11075 from ziggie1984/agent/fix-transaction-pagination-overflowby ziggieXXX · cfde18d9 · Aug 14, 2026 · 4 filesMessage 78 · AdequateLow 44Details
Commit message · ziggieXXX

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

lnwallet: prevent transaction pagination overflow

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

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

Lower-prioritydocs: add 11035 entries to the 0.20.4 release notesby ziggie · 772374e9 · Aug 14, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · ziggie

docs: add 11035 entries to the 0.20.4 release notes

The p2p wedge fixes from #11035 are being backported to the v0.20.x
branch, so mirror their entries in the 0.20.4 notes on master.

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 #11076 from gijswijs/security-md-supported-versionsby ziggieXXX · 00d006f8 · Aug 14, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11076 from gijswijs/security-md-supported-versions

docs: align SECURITY.md supported versions with support policy

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
AI review queuedMerge pull request #11035 from yyforyongyu/fix-p2p-wedgesby ziggieXXX · 648d635f · Aug 14, 2026 · 8 filesMessage 58 · ThinLow 48Details
Commit message · ziggieXXX

Merge pull request #11035 from yyforyongyu/fix-p2p-wedges

lnwallet+lnwire: handle boundary cases

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 pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 48/100

This commit fixes two separate boundary-case bugs in the Lightning Network Daemon (LND). First, it prevents a peer from getting stuck when a channel-funding message arrives after its wallet reservation has already been cleaned up: the code now sends a completion signal instead of leaving the caller waiting forever. Second, it corrects how zero-block gossip range queries are handled so that empty queries keep their starting block height and so that a densely populated first block no longer triggers an invalid zero-block reply before the real reply.

Lower-prioritydocs: align SECURITY.md supported versions with support policyby Gijs van Dam · 030f5cf5 · Aug 14, 2026 · 1 fileMessage 98 · StrongTriage 0Details
Commit message · Gijs van Dam

docs: align SECURITY.md supported versions with support policy

The Supported Versions section still described the pre-policy
situation: only the last major release as the supported version, with
ad-hoc backports 'given an issue severe enough'.

The published support policy at
https://security.lightning.engineering/lifecycle/ states that the two
most recent release lines are maintained, that both receive security
fixes, and that end of life is triggered by the second major release
after a line. Update SECURITY.md to match, explain the
v0.MAJOR.MINOR-beta versioning scheme, and link to the lifecycle page
as the source of truth for the maintenance table and disclosure
schedule.

98/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✓ Names security-relevant behavior explicitly
Why it was queued
documentation-only discount
Lower-prioritydocs: add transaction pagination fix to release notesby Ziggie · a207fac5 · Aug 14, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · Ziggie

docs: add transaction pagination fix to release notes

62/100 · AdequateMessage clarity
✓ Specific, 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 candidatelnwallet: prevent transaction pagination overflowby Ziggie · 62aeca57 · Aug 14, 2026 · 2 filesMessage 50 · ThinLow 40Details
Commit message · Ziggie

lnwallet: prevent transaction pagination overflow

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

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

Lower-prioritydocs: add 0.20.4 release noteby yyforyongyu · 1f6a385f · Aug 14, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · yyforyongyu

docs: add 0.20.4 release note

Add the foreign commitment spend fix to the 0.20.4 release notes.

Credit the contributor alongside the release entry.

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-priorityMerge pull request #11069 from ziggie1984/agent/add-0.20.4-release-notesby Yong · 1be0e411 · Aug 14, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11069 from ziggie1984/agent/add-0.20.4-release-notes

docs: add empty release notes for v0.20.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
Lower-priorityMerge pull request #11070 from ziggie1984/agent/add-0.21.3-release-notesby ziggieXXX · 552ba580 · Aug 14, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · ziggieXXX

Merge pull request #11070 from ziggie1984/agent/add-0.21.3-release-notes

docs: add release notes for v0.21.3

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-priorityhtlcswitch: reconcile resumed forward replaysby Olaoluwa Osuntokun · 50407808 · Aug 13, 2026 · 5 filesMessage 68 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

htlcswitch: reconcile resumed forward replays

In this commit, we let the switch reconcile replayed adds whose incoming
circuit has already been committed.

Once the interceptor resumes a forward, the switch commits its incoming
circuit and removes the packet from the held set. If the incoming link then
replays that add before the return packet is committed, the packet can be
offered to the interceptor a second time.

The circuit map still distinguishes in-memory duplicates from circuits
restored during recovery. Fresh packets continue through the normal
interception path.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydocs: add release notes for v0.21.3by ziggie · 90993861 · Aug 13, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · ziggie

docs: add release notes for v0.21.3

Scaffold release-notes-0.21.3.md with the standard section structure and repeat the v0.22 removal warnings carried by the earlier v0.21 release notes.

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-prioritydocs: add empty release notes for v0.20.4by ziggie · 8cf8ac75 · Aug 13, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · ziggie

docs: add empty release notes for v0.20.4

Scaffold release-notes-0.20.4.md with the standard section structure so contributors have a place to add entries for the next v0.20 patch release.

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-priorityMerge pull request #11066 from starius/fix-docker-releaseby Olaoluwa Osuntokun · 8ea98fd5 · Aug 13, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11066 from starius/fix-docker-release

docker-release: fix running from Git worktree and if Go cache dir is missing

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: initialize Docker release cachesby Boris Nagaev · f2a70731 · Aug 12, 2026 · 2 filesMessage 92 · StrongTriage 8Details
Commit message · Boris Nagaev

build: initialize Docker release caches

Create and validate host cache directories before Docker bind mounts them.

On a fresh Go installation, Docker otherwise creates missing sources as
root. The release helper runs as the invoking user and cannot write
to those caches.

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
defensive validation
Lower-prioritybuild: support Docker releases from Git worktreesby Boris Nagaev · ff98891f · Aug 12, 2026 · 1 fileMessage 92 · StrongTriage 0Details
Commit message · Boris Nagaev

build: support Docker releases from Git worktrees

Mount a linked worktree's shared Git directory into the release helper
at its original path.

Its .git pointer otherwise resolves to a path absent from the container,
preventing tag checks and source archiving.

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
Security candidatedocs: update release notesby bitromortac · 9cfd5a66 · Aug 11, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · bitromortac

docs: update release notes

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

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

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

Lower-priorityMerge pull request #11057 from starius/add-boris-keyby Yong · 8464116a · Aug 11, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Yong

Merge pull request #11057 from starius/add-boris-key

scripts/keys: add pub key for boris

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/keys: add pub key for borisby Boris Nagaev · 69176c5d · Aug 10, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Boris Nagaev

scripts/keys: add pub key for boris

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritymulti: identify taproot success leavesby yyforyongyu · 5266bc0e · Aug 8, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

multi: identify taproot success leaves

Taproot leaf identity includes both the script and its leaf version. An
auxiliary leaf may reuse the success script under another version.

Normalize BIP341 annexes in the input package so success-spend
classification can share the exact predicate. Cover annex boundaries
and same-script auxiliary leaves.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritycontractcourt: validate revealed preimagesby yyforyongyu · b9a3f844 · Aug 8, 2026 · 3 filesMessage 68 · AdequateTriage 8Details
Commit message · yyforyongyu

contractcourt: validate revealed preimages

Timeout cleanup extracts a preimage from a success-shaped witness
before updating the cache and settling the incoming link.

Verify that the revealed preimage opens the resolver HTLC. Update
fixtures to use matching preimages and cover a mismatched
success-shaped witness.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validation
Lower-prioritymulti: classify annexed HTLC spendsby yyforyongyu · 6267d180 · Aug 8, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

multi: classify annexed HTLC spends

Taproot spenders can append a BIP341 annex without changing the
spend path.

Normalize timeout and revocation witness stacks before matching their
shapes. This keeps annexed key and script path spends classified the
same as their plain forms.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context