EP
← All projectsElements Project

Core Lightning

Modular C implementation of the Lightning Network protocol and node stack.

BitcoinLightning NetworkActive incident
Repository coverage

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

228security candidates319second-pass queue1977AI analyses
99commits · 30 days
229commits · 60 days
709commits · 180 days
1578commits · 365 days
Backfill bands
Aug 5 → Feb 61049 seen37 candidatesComplete
Feb 6 → Jun 6579 seen10 candidatesComplete
Jun 6 → Jul 678 seen1 candidatesComplete
Jul 6 → Aug 5147 seen16 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.

71/100 average clarity
628Strong · 80–100
1399Adequate · 60–79
272Thin · 40–59
31Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
cdecker331217581
daywalker9019315113471
Níckolas Goline961252376
Amperstrand322278
Rusty Russell96977961173
Sangbida Chaudhuri18537157167
Vincenzo Palazzo19714185
Lagrang3115679170
dovgopoly18016165
Dusty Daemon821378066
ShahanaFarooqui931093063
Peter Neuroth1469110074
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 15 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

doc: bring lightning-downgrade's version list up to v26.12.

This commit only updates documentation. It adds new version entries to the manual page for the lightning-downgrade tool and mentions the tool in the upgrade guide. No code, database logic, or security behavior is changed.

2e7a9f5aby Ken Sedgwick+9−12 files
No security note in commit
Informational 23 AI analysisMessage 66 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Makefile: install lightning-downgrade.

This is a packaging/build fix, not a security vulnerability. The `lightning-downgrade` utility was being compiled but accidentally left out of the list of programs installed by `make install`. As a result, official release archives contain…

06ea9ba0by Ken Sedgwick+1−01 file
No security note in commit
Low 27 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: create bwatch tables before backfilling them

This commit fixes a database upgrade bug in Core Lightning. Wallets created with version v26.06.10 were missing two new tables (our_outputs and our_txs) because they skipped the migrations that create them. When users later upgraded, a fol…

Database migration failure could prevent node startup after upgradeFixes missing table creation before data backfillAdds regression test for upgrade path from v26.06.10
ce2a6836by daywalker90+105−02 files
No security note in commit
Informational 15 AI analysisMessage 5 · Opaque
EP Elements ProjectCore Lightning BitcoinLightning Network

v26.12rc1

This commit is a routine version bump from v26.06.10 to v26.12rc1 for Core Lightning. It only updates version strings in packaging files, a changelog, and a lockfile. There are no code changes that introduce, fix, or modify any security-se…

4002c4e9by Níckolas Goline+164−1110 files
No security note in commit
Low 30 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: store payment failure details per groupid

This commit fixes a database bug in Core Lightning where failure details for a payment attempt were being overwritten by later retry attempts that shared the same payment identifier fragment. The fix makes the failure record match on an ad…

Data integrity bug causing incorrect error reporting across payment retry groupsNo memory safety, authentication, authorization, or cryptographic issues presentNo external input is trusted or validated differently
24082c6dby daywalker90+6−34 files
No security note in commit
Low 43 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

cln-plugin: do not panic when the log writer task is gone

This commit fixes a bug in Core Lightning's Rust plugin library where a plugin could crash with a panic if it tried to log a message after the internal log-writing task had already stopped, such as during shutdown. The fix makes the plugin…

panic on send failure replaced with stderr fallbacklog message no longer silently dropped on writer task exitunit test added for dropped-receiver scenario
8661ffabby cdecker+29−11 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

docs: explain hsmtool HTLC recovery

This commit only adds documentation to the manual page for an existing command-line tool (hsmtool). It explains how to recover funds from old Lightning payment commitments (HTLCs) after losing channel state. There are no code changes, no n…

f90c140dby Sangbida Chaudhuri+85−01 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: make test_delpay_works deterministic

This commit only changes a test file to make a flaky test more reliable. It does not modify any production code, so it has no security impact on real users.

a224ca81by daywalker90+16−161 file
No security note in commit
Informational 20 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

doc: say that listtransactions gives blockheight 0 for a tx not in a block

This commit only updates documentation to explain that the `listtransactions` command reports a block height and transaction index of 0 when a transaction is not currently in a block (for example, because it hasn't been mined yet or was re…

bc281be3by Peter Neuroth+4−42 files
No security note in commit
Informational 20 AI analysisMessage 50 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

fixup! pyln-client: don't crash Millisatoshi.to_approx_str() on zero

This is a small bug fix in a Python helper library used by Core Lightning. The Millisatoshi.to_approx_str() method previously crashed with a math error when converting a zero amount to a human-readable string. The patch makes zero return "…

No security-relevant signals presentFix is a routine correctness/robustness improvement
02612ed5by Amartya Singh+4−31 file
No security note in commit
Moderate 62 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: reject unmodifiable PSBTs in addpsbtoutput/addpsbtinput

This update fixes a crash in two wallet commands, addpsbtoutput and addpsbtinput. These commands let users add extra transaction outputs or inputs to a PSBT (a Bitcoin transaction planning file). If a user supplied a PSBT whose version 2 '…

Daemon crash (assertion failure) on crafted/strict PSBT inputMissing validation of PSBT v2 modifiable flags before mutationUser-controlled input directly passed to libwally without precondition check
42472816by daywalker90+14−12 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: show addpsbtoutput/addpsbtinput crash on an unmodifiable v2 PSBT

This commit only adds a new test case that demonstrates two Core Lightning commands, addpsbtoutput and addpsbtinput, crash with an internal assertion when given a v2 PSBT that does not allow adding inputs or outputs. The test is marked as …

Daemon abort due to failed assertion in PSBT helper functionsRPC commands addpsbtoutput and addpsbtinput lack validation of PSBT modifiability flags before calling libwallyPotential denial-of-service vector: any caller able to submit a crafted v2 PSBT can crash lightningd
42e268abby daywalker90+60−01 file
No security note in commit
Informational 20 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

pyln-client: don't crash Millisatoshi.to_approx_str() on zero

This commit fixes a minor bug in Core Lightning's Python client library where calling a pretty-printing method on a zero-amount payment would crash with a ValueError. It is a routine correctness fix, not a security vulnerability. There is …

5ebe365dby Amartya Singh+3−12 files
No security note in commit
Moderate 59 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

dualopen and splicing: add minimal verification of tx_signatures

This commit adds missing safety checks in Core Lightning when a peer sends signatures for opening or splicing a dual-funded Lightning channel. Before the patch, the software accepted peer-provided transaction witnesses without verifying th…

Missing input validation on peer-provided witness dataBOLT-2 compliance fix for tx_signaturesRejection of empty witness stacks
c6be4f71by Lagrang3+633−97 files
Vendor flagged security relevance
Moderate 54 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

channeld: abort_channels no longer fails a channel with a signed splice

This fix prevents a user-issued 'abort channels' command from incorrectly failing a Lightning channel when a splice transaction has already been signed. Previously, the code would pass the latest in-flight splice to a routine that aborts i…

Denial-of-service/availability impact: user-initiated abort could inadvertently fail a funded channelProtocol compliance fix: avoids sending tx_abort after tx_signatures, which BOLT 2 forbidsState-handling bug in splice negotiation lifecycle
c87f5573by Andezion+22−11 file
No security note in commit
Moderate 51 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: fix crash on mutual close of an unconfirmed dual-funded channel

This update fixes a bug where a specific type of Lightning channel close could crash the node. It only happens when both parties cooperatively close a dual-funded channel that has not yet been confirmed and has gone through a funding bump …

NULL pointer dereference leading to daemon crash (denial of service)Crash occurs in cooperative-close path for unconfirmed dual-funded/RBF channelsFix uses canonical channel funding key instead of splice-only field
555143beby Sangbida Chaudhuri+9−31 file
Vendor flagged security relevance
High 74 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

cln-grpc: reject malformed request values instead of panicking

This commit fixes a security bug in Core Lightning's gRPC plugin (cln-grpc). Previously, a malformed request from a gRPC client could crash the plugin: bad public keys, hashes, secrets, channel IDs, or enum values triggered Rust 'unwrap()'…

Denial-of-service via malformed gRPC request causing tonic worker task panicDenial-of-service via std::process::exit(1) in ProofField conversion on missing oneofSilent integer truncation of u16/u8 fields via 'as' casts
b2703436by daywalker90+1558−12135 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 51 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

nix: drop protobuf again

This commit removes the protobuf package from the Nix build environment because it is no longer needed. A previous change made the cln-grpc component use its own bundled protoc compiler instead of relying on the system one. The Python bind…

a0459eeeby Peter Neuroth+0−11 file
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

make: check gRPC protos for breaking changes against the last release

This commit adds a new automated check to the project's build process that compares gRPC protocol definitions against the last release to catch accidental breaking changes early. It does not change any runtime code, fix a bug, or introduce…

db5fea70by daywalker90+43−84 files
No security note in 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-prioritynix: don't use the host's pg_config in the default dev shellby Peter Neuroth · 8a0a56a2 · Nov 10, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Peter Neuroth

nix: don't use the host's pg_config in the default dev shell

The default dev shell has no postgres, so configure found the host's
pg_config on PATH and added its include and lib dirs. On Linux that is
-I/usr/include, which put the host's sqlite3.h (3.54) ahead of nix's
(3.50). On a Mac with Homebrew it linked Homebrew's libpq.

Set PG_CONFIG to the empty string, which configure takes as "postgres
disabled". The postgres dev shell is unchanged and uses nix's pg_config.

Reported-by: daywalker90
Changelog-None

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: sign HTLC recovery transactionsby Sangbida Chaudhuri · 90a8e7b8 · Nov 10, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: sign HTLC recovery transactions

Build a single transaction spending every matched HTLC output and sign each input with the appropriate timeout or preimage witness.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: find recoverable HTLC outputsby Sangbida Chaudhuri · 432f67e9 · Nov 10, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: find recoverable HTLC outputs

Build both anchor variants of the requested HTLC script and use the commitment transaction to determine which one contains the outputs.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: match HTLC commitment outputsby Sangbida Chaudhuri · ce1990b5 · Nov 10, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: match HTLC commitment outputs

Match reconstructed P2WSH scripts against commitment outputs and retain every matching index so identical MPP parts can be recovered together.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: reconstruct HTLC witness scriptsby Sangbida Chaudhuri · b5658d6d · Nov 10, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: reconstruct HTLC witness scripts

Build offered and received HTLC scripts for the peer’s commitment, including anchor channels and CLTV expiry.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: derive keys for HTLC recoveryby Sangbida Chaudhuri · 6aa7fb3c · Nov 10, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: derive keys for HTLC recovery

Derive the channel basepoints and commitment-specific keys needed to recover HTLC outputs without contacting lightningd or hsmd.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: make hsm secret loading reusableby Sangbida Chaudhuri · 9ff4fe2c · Nov 10, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: make hsm secret loading reusable

The recovery tool is long, so it is best kept in its own file. Expose load_hsm_secret in a header so it can be shared with the recovery tool.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsm: share channel seed derivationby Sangbida Chaudhuri · 67674864 · Nov 10, 2026 · 5 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsm: share channel seed derivation

Move the historical channel-seed calculation into common/hsm_secret and reuse it from hsmd, checkchannels and lightning-hsmtool.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityhsmtool: add point-only dumpcommitments modeby Sangbida Chaudhuri · afd5ce95 · Nov 10, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Sangbida Chaudhuri

hsmtool: add point-only dumpcommitments mode

Allow callers to derive one public commitment point without printing the shaseed or any per-commitment secrets.

Co-authored-by: Cursor <cursoragent@cursor.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityaskrene: stress probability(amount+fees) in routesby Lagrang3 · e136b59c · Nov 9, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Lagrang3

askrene: stress probability(amount+fees) in routes

Even if refine does the job of adjusting the fee+amount to fit the
known_max in a channel, the flow probability computation does not
consider the eventual fees that a flow might carry.

Changelog-None

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityCI: update MacOS version in smoke testby daywalker90 · ac964edd · Nov 9, 2026 · 1 fileMessage 82 · StrongTriage 0Details
Commit message · daywalker90

CI: update MacOS version in smoke test

macos-14 is no longer supported by github

Changelog-None

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
documentation-only discount
AI review queueddoc: say that listtransactions gives blockheight 0 for a tx not in a blockby Peter Neuroth · bc281be3 · Nov 7, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · Peter Neuroth

doc: say that listtransactions gives blockheight 0 for a tx not in a block

listtransactions also lists transactions that are not in a block: ones
we sent that aren't mined yet, and ones a reorg took out of the chain.
For those, blockheight and txindex are 0, which the schema didn't say.

Changelog-None

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit only updates documentation to explain that the `listtransactions` command reports a block height and transaction index of 0 when a transaction is not currently in a block (for example, because it hasn't been mined yet or was removed by a blockchain reorganization). No code behavior was changed.

Lower-prioritypyln-proto: reject out-of-range ShortChannelId elements in from_strby Anmol Adwani · ef9c4ac6 · Nov 6, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Anmol Adwani

pyln-proto: reject out-of-range ShortChannelId elements in from_str

ShortChannelId.from_str() accepted any integers, so an element too big
for its field produced an object whose to_int() spilled into the
neighbouring field ('1x0x65536' gives the same to_int() as '1x1x0') and
whose to_bytes() could raise struct.error. A wrong element count only
failed with a TypeError from the constructor.

Raise ValueError for a wrong element count, a negative element, or an
element out of range (block and txnum are 3 bytes, outnum is 2), and
use `cls` for the classmethod. This matches the cln-rpc parser.

Changelog-Fixed: pyln-proto: `ShortChannelId.from_str` now raises ValueError for malformed or out-of-range ids.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritycln-rpc: reject out-of-range short_channel_id elementsby Anmol Adwani · 3dc58d90 · Nov 6, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Anmol Adwani

cln-rpc: reject out-of-range short_channel_id elements

ShortChannelId::from_str() parsed each element as a u64 and shifted
them into place without checking their size. An element that doesn't
fit spilled into the neighbouring field, so a malformed id silently
became a different, valid-looking channel:

"1x0x65536" -> 1x1x0
"16777216x0x0" -> 0x0x0

cln-grpc converts every short_channel_id in a request with this parser,
so a bad scid from a gRPC client could select the wrong channel instead
of failing.

Reject a block or txindex above 0xFFFFFF and an outnum above 0xFFFF,
and add a unit test for the bounds and the malformed cases.

Changelog-Fixed: cln-rpc: `ShortChannelId` parsing now rejects out-of-range elements instead of silently corrupting the id.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedfixup! pyln-client: don't crash Millisatoshi.to_approx_str() on zeroby Amartya Singh · 02612ed5 · Nov 5, 2026 · 1 fileMessage 50 · ThinInformational 20Details
Commit message · Amartya Singh

fixup! pyln-client: don't crash Millisatoshi.to_approx_str() on zero

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 20/100

This is a small bug fix in a Python helper library used by Core Lightning. The Millisatoshi.to_approx_str() method previously crashed with a math error when converting a zero amount to a human-readable string. The patch makes zero return "0btc" instead of raising an exception. It is a correctness fix, not a security vulnerability.

AI review queuedfixup! pyln-client: don't crash Millisatoshi.to_approx_str() on zeroby Amartya Singh · 081ca6c1 · Nov 5, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Amartya Singh

fixup! pyln-client: don't crash Millisatoshi.to_approx_str() on zero

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a trivial formatting cleanup (removing an extra blank line and adding one) in a test file. It does not change any code behavior, fix any bug, or alter any security-relevant logic.

Lower-prioritydocs: askrene-age: add missing mention of impressions and node biasby Lagrang3 · 35512470 · Nov 5, 2026 · 2 filesMessage 77 · AdequateTriage 0Details
Commit message · Lagrang3

docs: askrene-age: add missing mention of impressions and node bias

Changelog-None

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritytests: add coverage for askrene-age on biasesby Lagrang3 · b608ff8c · Nov 5, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Lagrang3

tests: add coverage for askrene-age on biases

Changelog-None

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Security candidatewallet: reject unmodifiable PSBTs in addpsbtoutput/addpsbtinputby daywalker90 · 42472816 · Nov 5, 2026 · 2 filesMessage 73 · AdequateModerate 62Details
Commit message · daywalker90

wallet: reject unmodifiable PSBTs in addpsbtoutput/addpsbtinput

Both commands took a user PSBT and appended to it without checking its
v2 modifiable flags, so libwally refused the change and lightningd
crashed:

```
lightningd: bitcoin/psbt.c:269: psbt_add_output: Assertion `wally_err == WALLY_OK' failed.
wallet/reservation.c:728 (json_addpsbtoutput)

lightningd: bitcoin/psbt.c:233: psbt_append_input: Assertion `wally_err == WALLY_OK' failed.
wallet/reservation.c:302 (psbt_using_utxos)
wallet/reservation.c:892 (json_addpsbtinput)
```

Check the flags up front and return an error instead.

Changelog-Fixed: JSON-RPC: `addpsbtoutput` and `addpsbtinput` no longer crash when given a v2 PSBT that does not allow modification.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 62/100

This update fixes a crash in two wallet commands, addpsbtoutput and addpsbtinput. These commands let users add extra transaction outputs or inputs to a PSBT (a Bitcoin transaction planning file). If a user supplied a PSBT whose version 2 'modifiable' flags forbade such changes, the underlying library refused the operation and the lightning daemon crashed with an assertion failure. The patch now checks those flags beforehand and returns a clean error instead of crashing.

Security candidatetests: show addpsbtoutput/addpsbtinput crash on an unmodifiable v2 PSBTby daywalker90 · 42e268ab · Nov 5, 2026 · 1 fileMessage 83 · StrongModerate 59Details
Commit message · daywalker90

tests: show addpsbtoutput/addpsbtinput crash on an unmodifiable v2 PSBT

A v2 PSBT without PSBT_GLOBAL_TX_MODIFIABLE (e.g. one signed by a
BIP-370 signer) makes libwally refuse new inputs and outputs, and both
commands then hit an assertion:

```
lightningd: bitcoin/psbt.c:269: psbt_add_output: Assertion `wally_err == WALLY_OK' failed.
wallet/reservation.c:728 (json_addpsbtoutput)

lightningd: bitcoin/psbt.c:233: psbt_append_input: Assertion `wally_err == WALLY_OK' failed.
wallet/reservation.c:302 (psbt_using_utxos)
wallet/reservation.c:892 (json_addpsbtinput)
```

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 59/100

This commit only adds a new test case that demonstrates two Core Lightning commands, addpsbtoutput and addpsbtinput, crash with an internal assertion when given a v2 PSBT that does not allow adding inputs or outputs. The test is marked as expected to fail for now, so the underlying crash is not fixed in this commit. A remote or local user who can call these RPC commands with a crafted PSBT could cause the lightning daemon to abort.

Lower-priorityrelease: bump to v26.06.10by daywalker90 · 2f410be3 · Nov 5, 2026 · 9 filesMessage 68 · AdequateTriage 0Details
Commit message · daywalker90

release: bump to v26.06.10

Point release version bump for v26.06.10. The version was
set with make update-versions NEW_VERSION=v26.06.10.

Changelog-None

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritywally: update libwally to v1.6.0by daywalker90 · 0b50b2b1 · Nov 5, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · daywalker90

wally: update libwally to v1.6.0

Changelog-Changed: Update libwally to v1.6.0

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI review queuedpyln-client: don't crash Millisatoshi.to_approx_str() on zeroby Amartya Singh · 5ebe365d · Nov 5, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · Amartya Singh

pyln-client: don't crash Millisatoshi.to_approx_str() on zero

round_to_n() took log10() of the amount to find its magnitude, which
fails for 0. Zero needs no rounding, so return it as is; the shortest
unit then comes out as "0btc", the same way 1 BTC prints as "1btc".

Changelog-Fixed: pyln-client: `Millisatoshi(0).to_approx_str()` no longer raises a ValueError.

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 20/100

This commit fixes a minor bug in Core Lightning's Python client library where calling a pretty-printing method on a zero-amount payment would crash with a ValueError. It is a routine correctness fix, not a security vulnerability. There is no way to exploit it to steal funds, bypass security, or attack a node.

Lower-prioritypytest: test Millisatoshi.to_approx_str() on a zero amountby Amartya Singh · 3ae83ceb · Nov 5, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Amartya Singh

pytest: test Millisatoshi.to_approx_str() on a zero amount

It currently raises "ValueError: math domain error", since rounding to
significant digits takes log10() of the amount.

Changelog-None

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityCHANGELOG: add the 26.06.10 release entryby Níckolas Goline · 4fc822f9 · Nov 4, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Níckolas Goline

CHANGELOG: add the 26.06.10 release entry

Changelog-None
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019hbJ3AeummizNQSXoHKhYo

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount