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

Lower-prioritypeer: price outgoing queue messagesby yyforyongyu · 4fbc13f3 · Aug 25, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: price outgoing queue messages

Estimate memory retained by each outgoing wire message without
serialization. Include peer-controlled onion, gossip feature-map,
address, and opaque payload allocations in the byte budget.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritypeer: define outgoing queue limitsby yyforyongyu · e67713c6 · Aug 25, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: define outgoing queue limits

Define the per-peer outgoing backlog count and retained-memory bounds.
Keep the policy grouped so queue ownership and producers share one
immutable configuration.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatepeer: test outgoing queue costsby yyforyongyu · 64645cc5 · Aug 25, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · yyforyongyu

peer: test outgoing queue costs

Cover each non-serializing queue cost rule with declarative message
shapes. Pin the retained opaque data charged for all active v1 bulk
gossip messages.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
access control
AI analysis · Informational 15/100

This commit only adds a new automated test file. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The test verifies how the outgoing message queue calculates the memory cost of different network messages, helping ensure future code changes do not accidentally under-count or over-count queue memory usage.

Security candidateMerge pull request #11008 from LNBIG-COM/fix/psbt-funding-lock-orderby Yong · a912dd69 · Aug 24, 2026 · 3 filesMessage 73 · AdequateModerate 66Details
Commit message · Yong

Merge pull request #11008 from LNBIG-COM/fix/psbt-funding-lock-order

lnwallet: fix limboMtx/intentMtx lock order inversion in PsbtFundingVerify

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

This commit fixes a classic multi-threading bug in LND's wallet code. Two functions were acquiring the same two locks in opposite orders, which could cause a deadlock. When triggered, the wallet's single request-handler goroutine would freeze, permanently stopping all channel opening on the node and preventing newly confirmed channels from being announced. Only a restart would recover. The fix reorders the lock acquisition so both functions now take the locks in the same order.

Lower-prioritypeer: test routed ping floodsby yyforyongyu · 120f307d · Aug 21, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: test routed ping floods

Use a mock message router that would consume an oversized Ping. Prove
flood accounting disconnects first and preserves the sentinel error for
operator diagnostics.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritypeer: test ping policy boundariesby yyforyongyu · a97db0e4 · Aug 21, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: test ping policy boundaries

Exercise exact production burst, refill, and Pong-size boundaries.
Retain deterministic cadence and reply-suppression coverage without
relying on wall-clock scheduling.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Security candidatepeer: rate limit inbound pingsby yyforyongyu · b9388cca · Aug 21, 2026 · 2 filesMessage 68 · AdequateModerate 65Details
Commit message · yyforyongyu

peer: rate limit inbound pings

Bound Pong replies with separate reply and flood token buckets.
Count every decoded Ping before generic routing. Disconnect peers that
exhaust the flood budget through a stable sentinel error.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Moderate 65/100

This commit adds rate limits on incoming ping messages in LND's peer connection handler. Without these limits, a malicious or misconfigured peer could send a flood of ping messages, forcing the node to waste CPU, memory, and bandwidth processing them and sending pong replies. The fix counts every incoming ping and disconnects peers that exceed a flood threshold, while also limiting how often pong replies are sent. This is a defensive hardening change against a potential denial-of-service attack.

Lower-priorityMerge pull request #11106 from ziggie1984/invoice-sql-migby ziggieXXX · 90ea05d5 · Aug 20, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11106 from ziggie1984/invoice-sql-mig

invoices: migrate legacy AMP invoice HTLCs

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #11105 from ziggie1984/bump-grpc-1.82.1by Yong · 19563915 · Aug 20, 2026 · 6 filesMessage 58 · ThinTriage 0Details
Commit message · Yong

Merge pull request #11105 from ziggie1984/bump-grpc-1.82.1

build: bump grpc to v1.83.1

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-prioritykvdb: bump grpc module floorby ziggie · 81c3fb26 · Aug 20, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · ziggie

kvdb: bump grpc module floor

The kvdb module is versioned and published independently, so it must
also be tested or consumed as a nested module on its own.

Run go mod tidy in kvdb so the transitive requirements and checksums
match the grpc version selected by the module graph.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritybrontide: clarify InitializeKey error-discard invariantby ziggie · 8a23e33c · Aug 20, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · ziggie

brontide: clarify InitializeKey error-discard invariant

x/crypto v0.51.0 adds a second failure mode to chacha20poly1305.New:
it now returns an error under Go's strict FIPS 140-only mode, in
addition to the existing bad-key-length case. The key here is a fixed
[32]byte, and lnd cannot run under strict FIPS mode because brontide
mandates ChaCha20-Poly1305, so the discarded error remains unreachable.
Expand the comment to record that widened invariant.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-prioritybuild: bump grpc to v1.83.1by ziggie · ad7ccc00 · Aug 20, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · ziggie

build: bump grpc to v1.83.1

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritypeer: attach outgoing queue costsby yyforyongyu · 99f537a4 · Aug 19, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: attach outgoing queue costs

Calculate retained-memory charges when messages enter the peer queue.
Carry them as immutable metadata. Keep generic priority queue accounting
independent of wire types.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatepeer: test outgoing queue boundsby yyforyongyu · d65c97cf · Aug 19, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · yyforyongyu

peer: test outgoing queue bounds

Exercise prospective admission through the direct queue and public
sending API. Pin inclusive count and byte limits and preserve the
overflow cause across synchronous batches.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
access controlmemory safety
AI analysis · Informational 15/100

This commit only adds new unit tests for the outgoing message queue in LND's peer connection code. It does not change any production logic, fix a bug, or alter behavior that an attacker could exploit. The tests verify that queue size limits are enforced correctly.

Lower-prioritypeer: enforce outgoing queue limitsby yyforyongyu · 259d96d8 · Aug 19, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · yyforyongyu

peer: enforce outgoing queue limits

Route queueHandler through the bounded queue abstraction and disconnect
when either the count or retained-memory budget is exceeded. Use one
nil-gated send case for empty and non-empty states, and keep servicing
producers during teardown so disconnect cannot deadlock.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydocs: add v0.20.4 invoice migration noteby ziggie · b7a2f153 · Aug 19, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add v0.20.4 invoice migration note

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 v0.21.3 invoice migration noteby ziggie · cb9c8619 · Aug 19, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · ziggie

docs: add v0.21.3 invoice migration note

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-priorityinvoices: migrate legacy AMP invoice HTLCsby ziggie · 96a0a261 · Aug 19, 2026 · 2 filesMessage 78 · AdequateTriage 8Details
Commit message · ziggie

invoices: migrate legacy AMP invoice HTLCs

AMP invoices created before reusable invoices store their HTLCs inline
and have no AMPState metadata. Reconstruct the sub-invoice state from
each HTLC set ID before inserting it into SQL. This preserves the AMP
associations during read-back verification.

Add regression coverage for settled and canceled legacy sets, AMP
metadata, and custom records.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validation
AI review queuedMerge pull request #11098 from ziggie1984/agent/bump-go-1.25.13-toolchain-1.26.6by Yong · eac5a5b8 · Aug 19, 2026 · 30 filesMessage 73 · AdequateInformational 15Details
Commit message · Yong

Merge pull request #11098 from ziggie1984/agent/bump-go-1.25.13-toolchain-1.26.6

build: bump Go language to 1.25.13 and toolchain to 1.26.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
merge-commit duplicate discountsecond-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a routine maintenance update that changes the version numbers of the Go programming language used to build LND from 1.25.11 to 1.25.13 (and the build toolchain from 1.26.4 to 1.26.6). It only edits configuration files, Dockerfiles, documentation, and module files. There is no code change, no bug fix, and no security patch visible in the diff.

Lower-priorityMerge pull request #11058 from starius/doc-expiryby ziggieXXX · 155683c4 · Aug 18, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11058 from starius/doc-expiry

lnrpc: clarify payment request expiry semantics

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #11001 from bitromortac/2604-bolt12-1eby ziggieXXX · ae9e86a5 · Aug 18, 2026 · 12 filesMessage 83 · StrongTriage 0Details
Commit message · ziggieXXX

Merge pull request #11001 from bitromortac/2604-bolt12-1e

bolt12: add Bech32 string codec and spec test vectors

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
fuzzing or regression evidencemerge-commit duplicate discount
Lower-priorityMerge pull request #11091 from ziggie1984/docs-move-11065-notes-to-0.21.3by ziggieXXX · d157ed3e · Aug 18, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · ziggieXXX

Merge pull request #11091 from ziggie1984/docs-move-11065-notes-to-0.21.3

docs: move XCreateAccount release notes to 0.21.3

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-prioritydocs: move XCreateAccount release notes to 0.21.3by ziggie · 0889fdf0 · Aug 17, 2026 · 2 filesMessage 88 · StrongTriage 0Details
Commit message · ziggie

docs: move XCreateAccount release notes to 0.21.3

XCreateAccount is being backported to the v0.21.x branch in #11086, so
its entries belong with the release that first ships it rather than with
0.22.0. This matches how the other changes backported to 0.21.3 (#11035,
#11075, #10869) are documented: their entries live only in the 0.21.3
notes, even though their code is on master and will also ship in 0.22.0.

The entry text is moved verbatim. Elle Mouton is added to the 0.21.3
contributor list.

88/100 · StrongMessage clarity
✓ 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: note peer ingress limitsby yyforyongyu · 839027e0 · Aug 17, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · yyforyongyu

docs: note peer ingress limits

Document the ping reply rate and outgoing queue bounds in both supported
patch release notes so operators know that peer-controlled resource
exhaustion is mitigated.

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 #10869 from yyforyongyu/fix-10840-success-resolverby Yong · 47c70ae6 · Aug 17, 2026 · 10 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #10869 from yyforyongyu/fix-10840-success-resolver

contractcourt: fix HTLC success resolver phantom-input bug (#10840)

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