LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Repository coverage

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

142security candidates195second-pass queue1287AI analyses
88commits · 30 days
194commits · 60 days
617commits · 180 days
1245commits · 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
324Strong · 80–100
661Adequate · 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
ziggie45016413165
Yong28513171
LNBiG111173
Jared Tobin909171
bitromortac661153071
yyforyongyu83861068
Erick Cestari26726070
Andras Banki-Horvath11311072
Gijs van Dam33230073
ziggieXXX2226070
Analysis record

Published AI watches

Last scanned 54 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
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
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
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
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
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
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
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
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
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
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
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
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
Informational 15 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

bolt12: describe the lnwire dependency

This is a documentation-only change. A package comment was updated to accurately describe that the bolt12 codec library does depend on LND's lnwire package for low-level message types, while clarifying it still does not interact with the r…

5f53171dby bitromortac+3−21 file
No security note in commit
Moderate 60 AI analysisMessage 91 · Strong
LL Lightning LabsLND BitcoinLightning Network

bolt12: cover the amount overflow guard

This commit adds a test to ensure that when a BOLT 12 invoice is validated against a request, the multiplication of the offer amount by the requested quantity cannot overflow and wrap around to zero. Without this guard, a malicious or malf…

Integer overflow / wraparound in amount calculationMissing test coverage for security-critical branchBOLT 12 invoice amount validation
3c8e2bcbby bitromortac+47−01 file
Vendor flagged security relevance
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
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
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
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
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
Repository ledger

Explore captured commits

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

Lower-prioritydocs: add release noteby George Tsagkarelis · e7f7fe41 · Sep 25, 2025 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · George Tsagkarelis

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
AI analysis · Informational 15/100

This commit only adds a release note describing a new experimental RPC endpoint and a known limitation (manually created aliases are lost on restart). It changes documentation only and contains no code modifications.

Lower-prioritylnrpc: add XFindBaseLocalChanAlias rpcby George Tsagkarelis · f14190c0 · Sep 25, 2025 · 8 filesMessage 58 · ThinLow 26Details
Commit message · George Tsagkarelis

lnrpc: add XFindBaseLocalChanAlias rpc

Add the new RPC method that looks up the base scid for a given alias.
Given the previous stepping stones this commit is fairly simple, we just
call into the alias manager and return the lookup result.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
AI analysis · Low 26/100

This commit adds a new read-only experimental RPC called XFindBaseLocalChanAlias to LND's router service. It lets an authorized caller ask the node: 'Given a short channel alias, what is the underlying real (base) channel ID?' The change only exposes a lookup and does not, by itself, modify any channel state or balances. It is a feature addition rather than a fix for a known vulnerability.

Lower-prioritymulti: add base lookup option to AddLocalAliasby George Tsagkarelis · 472a2f96 · Sep 25, 2025 · 6 filesMessage 68 · AdequateInformational 21Details
Commit message · George Tsagkarelis

multi: add base lookup option to AddLocalAlias

We add an extra option to the AddLocalAlias method which only controls
whether we store a reverse lookup from the alias back to the base scid
it corresponds to. The previous flag "gossip" is still maintained, and
in a way supercedes the new flag (it will also store the base scid
lookup even if the base lookup flag isn't set). The only call that sets
this option is the XAddLocalChanAlias RPC endpoint, where we want to
make sure that a reverse lookup is stored in the alias manager in order
to later expose it via the new RPC method.

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

This commit adds a new optional flag to LND's internal alias manager that lets callers request a reverse lookup from a channel alias back to the underlying real channel ID. It is a small feature enhancement for a new RPC endpoint and does not appear to fix or introduce a security vulnerability. The change is defensive in nature and improves consistency for manually-added aliases.

Lower-prioritylnd: update docs on nodeann addresses retainingby Abdullahi Yunus · ed2880ef · Sep 24, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Abdullahi Yunus

lnd: update docs on nodeann addresses retaining

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates user-facing documentation and code comments in LND. It explains that removing the externalip config option does not stop a node from advertising previously configured addresses, and tells users how to explicitly remove them. It also clarifies that alias and color settings persist from previous runs if not set. There are no code behavior changes and no security fix or vulnerability introduced.

Lower-prioritybrontide: add new maxMessageSize variableby Olaoluwa Osuntokun · 06826f85 · Sep 24, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Olaoluwa Osuntokun

brontide: add new maxMessageSize variable

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only adds a new constant named maxMessageSize in the brontide/noise.go file. It defines the largest allowed encrypted message size as 65,535 bytes of payload plus 16 bytes of authentication data. The constant is declared but not used anywhere in the visible diff, so it does not change any runtime behavior by itself.

Lower-prioritybrontide+peer: use internal sync/pool to reduce allocationsby Olaoluwa Osuntokun · 4c737d3f · Sep 24, 2025 · 3 filesMessage 73 · AdequateInformational 12Details
Commit message · Olaoluwa Osuntokun

brontide+peer: use internal sync/pool to reduce allocations

This ensures that under medium to high load, we eliminate all
allocations once we arrive a steady state, re working memory.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 12/100

This commit is a performance optimization, not a security fix. It replaces freshly allocated memory buffers with reusable buffer pools in LND's encrypted peer connection code (brontide). The goal is to reduce memory allocations under load. There is no indication in the commit or supplied references that this addresses a security vulnerability.

Lower-prioritydocs: add docs explaining usage of pprof+benchmarks to optimizeby Olaoluwa Osuntokun · f9682068 · Sep 24, 2025 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

docs: add docs explaining usage of pprof+benchmarks to optimize

In this commit, we add some docs that explain how to use tools like
heap escape analysis and memory profiling to fully eliminate allocations
in a sample program.

This guide is meant to help devs/contributors use Go's excellent perf
tools to zoom in on an optimization problem.

85/100 · StrongMessage clarity
✓ Specific, 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
AI analysis · Informational 15/100

This commit only adds a new documentation file explaining how to use Go's built-in performance profiling and benchmarking tools. It contains no code changes, no configuration changes, and nothing that alters how the software runs. It is purely an educational guide for developers.

Lower-prioritybrontide: use a static buffer for the packet lengthby Olaoluwa Osuntokun · 83e28119 · Sep 24, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Olaoluwa Osuntokun

brontide: use a static buffer for the packet length

In this commit, we eliminate the final allocation that takes place when
we write out messages. Once again this was escaping to the heap, so we
make it an attribute on the Machine struct, which allows pure static
allocation.

```
goos: darwin
goarch: arm64
pkg: github.com/lightningnetwork/lnd/brontide
cpu: Apple M4 Max
BenchmarkWriteMessage-16 25840 46376 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25646 46672 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25874 46391 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25512 46427 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25760 46309 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25789 46520 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25602 46619 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25766 46464 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25820 46487 ns/op 2 B/op 0 allocs/op
BenchmarkWriteMessage-16 25634 46553 ns/op 2 B/op 0 allocs/op
PASS
ok github.com/lightningnetwork/lnd/brontide 16.907s
```

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This is a routine performance optimization, not a security fix. The developer replaced a small temporary memory allocation with a reusable buffer inside a connection object to reduce memory allocations when sending encrypted messages. There is no security-relevant change here.

AI review queuedbrontide: use a fixed size buffer for the nonce within the brontide machineby Olaoluwa Osuntokun · 1fe156f2 · Sep 24, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Olaoluwa Osuntokun

brontide: use a fixed size buffer for the nonce within the brontide machine

In this commit, we use a fixed sized buffer for the nonce when we
read/write messages. This was actually escaping to the heap. We can
avoid this by statically allocating it alongside the struct itself.

The benchmark state at this point:

```
goos: darwin
goarch: arm64
pkg: github.com/lightningnetwork/lnd/brontide
cpu: Apple M4 Max
BenchmarkWriteMessage-16 25264 47012 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 23542 46809 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 25989 47256 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 25542 46388 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 26083 46612 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 25860 46367 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 24967 46748 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 26088 46485 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 25561 46425 ns/op 4 B/op 1 allocs/op
BenchmarkWriteMessage-16 25474 47249 ns/op 4 B/op 1 allocs/op
PASS
ok github.com/lightningnetwork/lnd/brontide 16.911s
```

```
goos: darwin
goarch: arm64
pkg: github.com/lightningnetwork/lnd/brontide
cpu: Apple M4 Max
│ old.txt │ new2.txt │
│ sec/op │ sec/op vs base │
WriteMessage-16 50.34µ ± 1% 46.68µ ± 1% -7.28% (p=0.000 n=10)

│ old.txt │ new2.txt │
│ B/op │ B/op vs base │
WriteMessage-16 73788.000 ± 0% 4.000 ± 0% -99.99% (p=0.000 n=10)

│ old.txt │ new2.txt │
│ allocs/op │ allocs/op vs base │
WriteMessage-16 5.000 ± 0% 1.000 ± 0% -80.00% (p=0.000 n=10)
```

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This change is a routine performance optimization, not a security fix. The developer replaced a temporary 12-byte nonce buffer that was repeatedly created on the fly with a fixed buffer stored inside the encryption state struct. This removes almost all memory allocations during message encryption/decryption and makes the code faster, but it does not change what data is encrypted or how keys are managed.

Lower-prioritybrontide: add benchark for WriteMessageby Olaoluwa Osuntokun · 6e0083a3 · Sep 24, 2025 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Olaoluwa Osuntokun

brontide: add benchark for WriteMessage

In this commit, we add a benchmark for the WriteMessage method. This is
the first step in an upcoming optimizooor series of commits.

The baseline is:
```
goos: darwin
goarch: arm64
pkg: github.com/lightningnetwork/lnd/brontide
cpu: Apple M4 Max
BenchmarkWriteMessage-16 22736 50667 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 23217 50463 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 24241 49941 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 23574 51021 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 23784 49926 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 24230 50538 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 24058 49971 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 23762 50224 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 24266 53034 ns/op 73788 B/op 5 allocs/op
BenchmarkWriteMessage-16 23317 50045 ns/op 73788 B/op 5 allocs/op
PASS
ok github.com/lightningnetwork/lnd/brontide 17.433s
```

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

This commit only adds a new performance benchmark test for the brontide encrypted connection code. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

Lower-prioritylnd: use persisted addrs if not set in configby Abdullahi Yunus · cf287e96 · Sep 24, 2025 · 1 fileMessage 45 · ThinLow 32Details
Commit message · Abdullahi Yunus

lnd: use persisted addrs if not set in config

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 32/100

This small change makes LND reuse previously saved network addresses when the user has not configured any external IP addresses. It is a behavior fix that likely prevents a node from accidentally advertising no addresses after restart, which could make it unreachable on the Lightning Network. There is no direct evidence in the commit that this is a security fix, and no exploit is described.

Lower-prioritylnd: stop using prev persisted addressesby Abdullahi Yunus · 783c8878 · Sep 24, 2025 · 1 fileMessage 68 · AdequateInformational 24Details
Commit message · Abdullahi Yunus

lnd: stop using prev persisted addresses

In this commit we stop using persisted address in LND's prev run.
This means addresses set using `externalip` will be used without
merging them with the ones from prev run. We will introduce the
condition to use persisted addresses in the next commit.

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

This commit changes how LND (a Bitcoin Lightning Network node) builds its own network address list when starting up. Previously, it merged newly configured addresses with addresses stored from a previous run. Now it stops doing that merge, using only the freshly configured addresses. The commit message says a condition to re-enable persisted addresses will be added in a follow-up commit. On its own, this is a behavior change, not a clear security fix or vulnerability.

Lower-priorityitest: check for config addrs precedenceby Abdullahi Yunus · 141cc571 · Sep 24, 2025 · 1 fileMessage 90 · StrongInformational 12Details
Commit message · Abdullahi Yunus

itest: check for config addrs precedence

In this commit, we update the itest to check for precedence of the
config addresses over the persisted addresses.

We did not check for address persistence after restart (without the
extraArgs `--externalip`) because in `lntest/node/config.goL300`,
`GenArg` by default sets the `--externalip` flag, which makes
the config addrs to always take precedence over the persisted
addrs, for the tests.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 12/100

This commit only changes an integration test file. It adjusts the test expectations so that the test now verifies that command-line configuration addresses take precedence over addresses that were previously updated and persisted via RPC. There is no change to production code, no fix for a security bug, and no disclosed security relevance.

Lower-prioritydocs: add release noteby George Tsagkarelis · 2302debd · Sep 23, 2025 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · George Tsagkarelis

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
AI analysis · Informational 15/100

This commit only adds a line to the release notes describing a new developer-facing component called AuxChannelNegotiator. There are no code changes, no bug fixes, and no security-related content in the diff.

Lower-priorityfunding: notify aux negotiator on ChannelReadyby George Tsagkarelis · a58a52ee · Sep 23, 2025 · 2 filesMessage 60 · AdequateInformational 18Details
Commit message · George Tsagkarelis

funding: notify aux negotiator on ChannelReady

We notify the aux channel negotiator that an established channel is now
ready to use.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 18/100

This commit adds a small notification hook so that an optional auxiliary channel negotiator is told when a new Lightning channel is ready to use. It is a feature addition, not a fix for a known security problem, and the commit message does not describe any security relevance.

AI review queuedlnwallet: include peer pub key in aux chan stateby George Tsagkarelis · be413455 · Sep 23, 2025 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · George Tsagkarelis

lnwallet: include peer pub key in aux chan state

In order to help external components to query the custom records of a
channel we need to expose the remote peer pub key. We could look-up
custom records based on the funding outpoint, but that relation is
established when receiving the ChannelReady message. The external
components may query the AuxChanState before that message is received,
so let's make sure the peer pub key is also available.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds the remote peer's public key to an internal data structure (AuxChanState) used by external components to look up custom channel records. Public keys are not secrets, and the change only exposes information that was already available elsewhere in the channel state. There is no indication this fixes a vulnerability or changes security behavior.

Lower-prioritylnwire: update tests for init messageby George Tsagkarelis · 68bd35f7 · Sep 23, 2025 · 2 filesMessage 55 · ThinInformational 15Details
Commit message · George Tsagkarelis

lnwire: update tests for init message

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only adds and updates test code for the Lightning Network wire protocol's Init message. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly.

Lower-priorityhtlcswitch+peer: set and read aux custom recordsby George Tsagkarelis · 6dff1bd5 · Sep 23, 2025 · 3 filesMessage 68 · AdequateLow 25Details
Commit message · George Tsagkarelis

htlcswitch+peer: set and read aux custom records

This is the final step, we actually call the interface and either
provide or retrieve the custom features over the message. We also notify
the aux components when channel reestablish is received.

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

This commit adds a new optional plugin hook called AuxChannelNegotiator to LND. It lets external 'auxiliary' components attach custom data to Lightning protocol handshake messages (init and channel re-establishment) and read the peer's custom data. The change itself is infrastructure: it wires up the hook but does not contain the actual plugin logic. Any security risk depends entirely on what future external components do with this hook, so on its own it is best viewed as a new attack surface rather than a vulnerability.

Lower-prioritylnwire: add custom records to initby George Tsagkarelis · 7724d0fa · Sep 23, 2025 · 1 fileMessage 60 · AdequateInformational 21Details
Commit message · George Tsagkarelis

lnwire: add custom records to init

Before calling the new interface we first add the ability for the peer
message itself to encode the new data records.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 21/100

This commit updates the Lightning Network 'init' handshake message in LND so it can carry custom data records using a standard format (TLV). It is a protocol-level feature addition that enables future functionality, not a fix for a known bug or vulnerability. There is no direct evidence in the commit that this change addresses a security issue.

Lower-prioritylnd: add AuxChannelNegotiator to AuxComponentsby George Tsagkarelis · 56c56060 · Sep 23, 2025 · 1 fileMessage 68 · AdequateInformational 17Details
Commit message · George Tsagkarelis

lnd: add AuxChannelNegotiator to AuxComponents

We now plug-in the aux channel negotiator to the server impl config. We
also provide it to the peer config as that's where it's needed in order
to inject custom records in the appropriate peer messages.

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

This commit adds a new optional component called AuxChannelNegotiator to LND's auxiliary components configuration. It is a small wiring change that lets optional custom channel implementations inject and process custom records in peer messages. There is no direct security bug visible in the diff itself; it is a feature/extension hook being added.

AI review queuedlnwallet: introduce AuxChannelNegotiator interfaceby George Tsagkarelis · 44406db8 · Sep 23, 2025 · 1 fileMessage 63 · AdequateInformational 15Details
Commit message · George Tsagkarelis

lnwallet: introduce AuxChannelNegotiator interface

We introduce this new interface with the purpose of injecting and
handling custom records on the init message, and also notifying
external components when receiving the ChannelReady or
ChannelReestablish message.

63/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds a new Go interface definition with no actual implementation or logic. It defines hooks that future code could use to inject custom data during Lightning channel setup and to react when a channel becomes ready. There is no executable code, no change to existing behavior, and no security issue visible in this patch.

Lower-prioritygithub: change to form-based issue templateby bitromortac · f23b4d1f · Sep 19, 2025 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · bitromortac

github: change to form-based issue template

This commit introduces a more structured approach to issue generation,
where we can make certain info required.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply replaces GitHub's free-text bug report template with a structured form. It does not change any LND code, configuration defaults, network behavior, or security controls. There is no security issue here.

Lower-priorityrpcserver+itest: skip err from `FlapCount`by yyforyongyu · 2d59976e · Sep 18, 2025 · 2 filesMessage 80 · StrongLow 25Details
Commit message · yyforyongyu

rpcserver+itest: skip err from `FlapCount`

We need to make sure the `ListPeers` to be robust against errors from
the `FlapCount` so this RPC won't fail due to no flap count info. Also
updated the itest to check this field.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI analysis · Low 25/100

This change makes the ListPeers RPC more reliable. Previously, if the system couldn't retrieve a peer's 'flap count' (a count of connection up/down events), the entire ListPeers request would fail. Now it logs the error and continues, returning the rest of the peer information. This is a robustness improvement rather than a typical security vulnerability, but the original behavior could have been used to deny access to peer information.

Lower-prioritydocs: update release notesby yyforyongyu · 7b658936 · Sep 18, 2025 · 1 fileMessage 47 · ThinInformational 15Details
Commit message · yyforyongyu

docs: update release notes

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates the release notes documentation. It adds a single bullet describing a prior code change that limits two peer-tracking metrics to peers that share channels. There is no code change, no bug fix, and no security-relevant content in the commit itself.

Lower-prioritylntest+rpcserver: ignore `chanfitness.ErrPeerNotFound` in rpcby yyforyongyu · 22fddd62 · Sep 18, 2025 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · yyforyongyu

lntest+rpcserver: ignore `chanfitness.ErrPeerNotFound` in rpc

Similar to how we handle `chanfitness.ErrChannelNotFound`, we now also
ignore the `ErrPeerNotFound`. This is needed as previously we will
always see the peer in the channel event store given it'd added when
connected. This is no longer the case as we only add the peer to the map
when the channel is added.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 19/100

This change is a small hardening fix in LND's RPC server. It makes the code gracefully handle a newly introduced error case—when a peer is not yet known to the channel event store—instead of potentially failing or returning unexpected behavior. It is not a fix for an active exploit, but it prevents a class of operational/logic errors from surfacing to users.