CommitWatch RSS
EP
← All projectsElements Project

Core Lightning

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

BitcoinLightning NetworkNormal
Source repository ↗
Repository coverage

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

158security candidates263second-pass queue137AI analyses
146commits · 30 days
225commits · 60 days
803commits · 180 days
1853commits · 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.

70/100 average clarity
430Strong · 80–100
1163Adequate · 60–79
231Thin · 40–59
29Opaque · 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.
Rusty Russell9587363072
Sangbida Chaudhuri1463129066
Dusty Daemon771310066
ShahanaFarooqui931010063
daywalker908953062
Níckolas Goline4054076
Lagrang37642069
Christian Decker3643072
Vincenzo Palazzo833080
Chandra Pratap5622082
ekzyis222063
Peter Neuroth9711070
Analysis record

Published AI watches

Last scanned 53 minutes ago

Informational 23 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

downgrade: we need to remove "impressions" from askrene datastore when downgrading to v26.06.

This is a database downgrade helper fix, not a live network vulnerability. Core Lightning's downgrade tool previously failed to strip out new 'channel impression' records when rolling a database back to version v26.06. The patch teaches th…

Database downgrade path could leave incompatible records in older schemaOffline tool only; no remote or on-chain triggerFix prevents potential node startup failure after version rollback
4d926285by Rusty Russell+43−111 file
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

downgrade tool: fix invalid memory bug

This commit fixes a typo in a database downgrade helper tool. The bug caused the tool to pass a negative number (turned into a huge positive size) when copying data, which led to an out-of-memory (OOM) error. The fix swaps two variable nam…

Integer underflow / negative-to-size_t wrap leading to excessive allocationOut-of-memory crash in maintenance toolMemory corruption potential if allocation somehow succeeded
42995326by Lagrang3+8−81 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 90 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

add a test for downgrading askrene datastore

This commit adds a regression test for Core Lightning's database downgrade path. It ensures that when a user downgrades from an upcoming v26.09 release to an older version (v26.06), the new 'impressions' data added by the askrene routing s…

Database downgrade path for new askrene schema (impressions table)Regression test only; no production code changeNo input validation, cryptography, network, or authorization changes
1818553eby Lagrang3+156−13 files
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightning-hsmtool: Fix getsecret does not show mnemonic after typing passphrase

This is a bug fix in a command-line helper tool used by Core Lightning node operators. The `getsecret` command was accidentally refusing to show the wallet recovery words (mnemonic) when the wallet was protected by a passphrase. After the …

Functional bug in secret-recovery pathError path blocked legitimate mnemonic recoveryNo input validation, memory-safety, or cryptographic change
8480f6c2by ekzyis+1−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: add regression test for hsmtool commands with passphrase

This commit only adds and updates a regression test in the project's test suite. It checks that the hsmtool utility correctly handles both empty and non-empty passphrases when working with BIP39 mnemonic-based wallet secrets. There is no c…

Regression test added for passphrase handling in hsmtoolNo production code changes observedTest-only change to tests/test_wallet.py
8c42be35by ekzyis+47−201 file
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 76 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wally: update libwally to v1.5.6

This commit updates the bundled libwally library to version 1.5.6. The practical effect is that calling the JSON-RPC `signpsbt` command on a PSBT that is already signed now succeeds as a harmless no-op, instead of returning an error on Bit…

Dependency update to incorporate upstream bug fixBehavior change from error to no-op on re-signing signed PSBTsTaproot keypath handling change in upstream cryptographic library
37526ca4by daywalker90+7−82 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: rename b32script to scriptpubkey in PSBT change paths

This commit is a simple variable rename inside a Bitcoin/Lightning wallet file. The old name 'b32script' suggested all change addresses were bech32 format, but the project now uses a newer address type (p2tr) by default. The developer rena…

b8a60579by Sangbida Chaudhuri+12−141 file
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 78 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: register scriptpubkey watches at startup

This change makes Core Lightning register long-lasting 'watches' for all wallet deposit addresses when the node starts up, so the new bwatch plugin can spot incoming payments from the first block it scans. It also removes a now-redundant p…

Change is part of an experimental chain-watcher (bwatch) featureAdds startup registration of scriptPubKey watches for all derived wallet keysRemoves a redundant unconfirmed-change watch, relying on the new blanket coverage
4a951d65by Sangbida Chaudhuri+89−114 files
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: dual-write chaintopology UTXO changes into our_outputs

This is a database refactoring commit in Core Lightning. It makes the wallet write UTXO (unspent transaction output) state to a new table called our_outputs in addition to the legacy outputs table, while reads still use the old table. The …

Database schema migration with dual-write mirror patternNo security claim in commit title or messageNo CVE, advisory, or researcher attribution in commit metadata
824e8195by Sangbida Chaudhuri+118−162 files
No security note in commit
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: record bwatch-discovered wallet outputs

This commit adds new wallet bookkeeping code for Core Lightning. It records Bitcoin deposits found by a new chain-watcher ('bwatch') into database tables and handles blockchain reorganizations by demoting transactions back to unconfirmed r…

New database write paths for wallet UTXOs and transactionsReorg revert logic demotes rather than deletes rows to preserve metadataOwner-string constructors added to avoid silent unwatch failures from format mismatches
bc021011by Sangbida Chaudhuri+543−07 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: add our_outputs + our_txs schema migrations

This commit only adds two new empty database tables (our_outputs and our_txs) to Core Lightning's wallet. It is a preparatory schema change for a future feature; no code reads from or writes to these tables yet, and no existing behavior is…

Schema-only migration with no runtime codeNew tables are not yet populated or queried by any code pathDesign note: sentinel 0 replaces NULL for blockheight/txindex/reserved_til, which could reduce NULL-handling bugs in future code
ea4d1fcaby Sangbida Chaudhuri+38−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 28 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: add migrate_backfill_bwatch_tables

This commit adds a database migration that copies existing wallet data into new tables used by an upcoming 'bwatch' wallet component. It is a data backfill, not a code fix for an active vulnerability. The main risk is that if the migration…

Database migration touching wallet UTXO and transaction tablesPotential for data inconsistency if mapping logic is wrongON CONFLICT DO NOTHING prevents overwrite but could hide duplicate-key anomalies
2e23893bby Sangbida Chaudhuri+513−04 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: mirror bwatch writes into legacy outputs table

This change is a behind-the-scenes bookkeeping patch for Core Lightning's wallet database. The project is moving to a new table (`our_outputs`) for tracking spendable coins, but older versions of the software still read from the old table …

Race-condition guard for foreign-key-backed confirmation_height and spend_height when bwatch is ahead of chaintopologyTemporary mirroring to keep legacy outputs table consistent with new our_outputs tableON CONFLICT DO NOTHING used for legacy insert to avoid duplicate-key failures
bba68e0aby Sangbida Chaudhuri+101−62 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 51 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: Update the max_index cache when issuing new addresses

This commit fixes a bug where Core Lightning's in-memory record of the highest address index could fall out of step with the database. When a user generated a new on-chain address, the code updated the database directly but left the cached…

Cache/database inconsistency in address index trackingPotential for stale lower index to overwrite newer persisted indexFreshly generated addresses invisible to wallet rescan/listing until restart
d05815f5by Christian Decker+37−292 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: Cache the max_index for bip32 and bip86 address indices

This commit is a straightforward performance optimization. It caches two address-index values in memory instead of reading them from the database twice for every transaction output in every scanned block. The change fixes a slowdown during…

565da833by Christian Decker+15−52 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 90 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

common: add randbytes() wrapper to override cryptographic entropy: $CLN_DEV_ENTROPY_SEED

This commit adds a developer-only feature that lets programmers override the randomness source used by Core Lightning during testing, via an environment variable. It is explicitly gated behind 'developer mode' and is not intended for produ…

New cryptographic-randomness override mechanism, but explicitly developer-mode onlyEnvironment-variable seeding could reduce entropy if accidentally enabled in productionNo production code changes visible in the diff
1c925e0aby Rusty Russell+29−05 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

common: don't consume deterministic randbytes stream for trace ids

This change fixes a subtle bug in Core Lightning's tracing code. When running with a special developer-only deterministic randomness override (CLN_DEV_ENTROPY_SEED), trace IDs were being drawn from the same predictable random stream used f…

Deterministic RNG stream contamination by observability codeTransaction output divergence between instrumented and non-instrumented buildsDeveloper-only entropy override affecting reproducibility of transaction generation
23b4b38aby ShahanaFarooqui+18−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: don't trigger siphash_seed() init from span hashing either.

This is a small bug-fix commit in Core Lightning's tracing code. It fixes a situation where enabling tracing accidentally changed the sequence of random numbers used elsewhere in the program, causing test outputs to differ between builds w…

No direct memory safety issueNo input validation bypassNo authentication or authorization change
e54fe678by ShahanaFarooqui+6−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

autogenerate-rpc-examples.py: disable entropy for generation.

This commit changes Core Lightning's internal test tooling so that automatically generated RPC documentation examples use predictable randomness and a fixed clock time. It only affects test/example generation code, not the production Light…

81443075by Rusty Russell+14−12 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

autogenerate-rpc-examples.py: pin the full sorted UTXO set for multiwithdraw examples

This commit only changes an internal test script that automatically generates example RPC commands for documentation. It makes the examples more deterministic by explicitly selecting which coins the test wallet uses, so the generated docum…

6f464e46by ShahanaFarooqui+35−81 file
No security note in commit
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-priorityCODEOWNERS: remove @devrandomby daywalker90 · 12790264 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · daywalker90

CODEOWNERS: remove @devrandom

without write access CODEOWNER does not work

Changelog-None

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI review queuedecdh_hsmd: ensure HSM fd is blocking on setupby Níckolas Goline · f40be192 · Jul 14, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Níckolas Goline

ecdh_hsmd: ensure HSM fd is blocking on setup

On macOS under load, socketpair fds sent via SCM_RIGHTS can have
O_NONBLOCK set (from the sender's io_new_conn call in hsmd's
pass_client_hsmfd). This causes wire_sync_read to return NULL
with EAGAIN, killing connectd or channeld with "No hsmd ECDH response".

The fix mirrors the "Don't trust subd to set it blocking" pattern
already used in lightningd/subd.c:read_fds(): explicitly call
io_fd_block(hsm_fd, true) in ecdh_hsmd_setup.

Changelog-Fixed: connectd: fix intermittent "No hsmd ECDH response" crash on macOS under load.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
Lower-prioritycrates: update dependencies and upgrade quick-xml, tower-http, and tokio-tungsteniteby daywalker90 · 678ff47d · Jul 14, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · daywalker90

crates: update dependencies and upgrade quick-xml, tower-http, and tokio-tungstenite

```
cargo update
Updating crates.io index
Locking 62 packages to latest Rust 1.85.0 compatible versions
Updating anyhow v1.0.102 -> v1.0.103
Updating arc-swap v1.9.1 -> v1.9.2
Updating arrayvec v0.7.6 -> v0.7.8
Updating base58ck v0.1.100 -> v0.1.101
Updating bitcoin v0.32.100 -> v0.32.101
Adding bitcoin-consensus-encoding v1.0.0
Adding bitcoin-internals v0.5.0
Updating bitcoin-io v0.1.100 -> v0.1.101
Updating bitcoin-units v0.1.100 -> v0.1.101
Updating bitcoin_hashes v0.14.100 -> v0.14.101
Adding block-buffer v0.12.1
Updating bytes v1.11.1 -> v1.12.1
Updating cc v1.2.64 -> v1.2.67
Updating chacha20 v0.10.0 -> v0.10.1
Adding const-oid v0.10.2
Adding crypto-common v0.2.2
Adding defmt v1.1.1
Adding defmt-macros v1.1.1
Adding defmt-parser v1.0.0
Adding digest v0.11.3
Updating env_filter v1.0.1 -> v2.0.0
Updating env_logger v0.11.10 -> v0.11.11
Updating fs-err v3.3.0 -> v3.3.1
Updating getrandom v0.4.2 -> v0.4.3
Adding hex-conservative v0.3.2
Adding hybrid-array v0.4.13
Removing id-arena v2.3.0
Updating jiff v0.2.28 -> v0.2.32
Updating jiff-static v0.2.28 -> v0.2.32
Updating js-sys v0.3.102 -> v0.3.103
Removing leb128fmt v0.1.0
Updating lightning v0.1.8 -> v0.1.11
Updating lightning-invoice v0.33.2 -> v0.33.3
Updating lightning-types v0.2.0 -> v0.2.1
Updating log v0.4.32 -> v0.4.33
Updating memchr v2.8.2 -> v2.8.3
Updating num-bigint v0.4.6 -> v0.4.8
Updating possiblyrandom v0.2.0 -> v0.2.1
Updating quote v1.0.45 -> v1.0.46
Removing rand v0.9.4
Removing rand v0.10.1
Adding rand v0.9.5
Adding rand v0.10.2
Updating regex v1.12.4 -> v1.13.0
Updating regex-automata v0.4.14 -> v0.4.15
Updating rust-embed v8.11.0 -> v8.12.0
Updating rust-embed-impl v8.11.0 -> v8.12.0
Updating rust-embed-utils v8.11.0 -> v8.12.0
Updating rustls v0.23.40 -> v0.23.41
Updating rustls-pki-types v1.14.1 -> v1.15.0
Updating rustversion v1.0.22 -> v1.0.23
Updating sha1 v0.10.6 -> v0.10.7
Updating sha2 v0.10.9 -> v0.11.0
Updating syn v2.0.117 -> v2.0.118
Updating thread_local v1.1.9 -> v1.1.10
Removing unicode-xid v0.2.6
Removing wasip3 v0.4.0+wasi-0.3.0-rc-2026-01-06
Updating wasm-bindgen v0.2.125 -> v0.2.126
Updating wasm-bindgen-futures v0.4.75 -> v0.4.76
Updating wasm-bindgen-macro v0.2.125 -> v0.2.126
Updating wasm-bindgen-macro-support v0.2.125 -> v0.2.126
Updating wasm-bindgen-shared v0.2.125 -> v0.2.126
Removing wasm-encoder v0.244.0
Removing wasm-metadata v0.244.0
Removing wasmparser v0.244.0
Updating web-sys v0.3.102 -> v0.3.103
Updating webpki-root-certs v1.0.7 -> v1.0.8
Removing wit-bindgen v0.51.0
Removing wit-bindgen-core v0.51.0
Removing wit-bindgen-rust v0.51.0
Removing wit-bindgen-rust-macro v0.51.0
Removing wit-component v0.244.0
Removing wit-parser v0.244.0
Updating zerocopy v0.8.52 -> v0.8.54
Updating zerocopy-derive v0.8.52 -> v0.8.54
Updating zlib-rs v0.6.3 -> v0.6.6
Updating zmij v1.0.21 -> v1.0.22
```

quick-xml upgraded to 0.41
tower-http upgraded to 0.7
tokio-tungstenite upgraded to 0.30

No code changes needed.

Changelog-None

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatecommon: add randbytes() wrapper to override cryptographic entropy: $CLN_DEV_ENTROPY_SEEDby Rusty Russell · 1c925e0a · Jul 14, 2026 · 5 filesMessage 90 · StrongInformational 18Details
Commit message · Rusty Russell

common: add randbytes() wrapper to override cryptographic entropy: $CLN_DEV_ENTROPY_SEED

Only in developer mode, ofc.

Notes:
1. We have to move the initialization before the lightningd main trace_start,
since that uses pseudorand().
2. To make the results stable, we need to use per-caller values to randbytes().
Otherwise external timing changes the call order.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Informational 18/100

This commit adds a developer-only feature that lets programmers override the randomness source used by Core Lightning during testing, via an environment variable. It is explicitly gated behind 'developer mode' and is not intended for production use. The patch itself only updates test build files and adds missing stub functions so unit tests compile with the new wrapper. There is no indication it weakens real network security.

AI review queuedlightningd: cancel watching original funding when we switch to the new one via splice.by Rusty Russell · 3226d686 · Jul 14, 2026 · 2 filesMessage 73 · AdequateTriage 12Details
Commit message · Rusty Russell

lightningd: cancel watching original funding when we switch to the new one via splice.

This happens if the channel is *not* announcable yet. Then we hit the assertion
in funding_depth_cb that the txid is the same as the current funding.txid.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-EXPERIMENTAL: fixed crash when we splice a channel which hasn't been announced yet.

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: broader security terminologysecond-pass: security-sensitive path
Security candidatecommon: don't consume deterministic randbytes stream for trace idsby ShahanaFarooqui · 23b4b38a · Jul 14, 2026 · 1 fileMessage 83 · StrongLow 37Details
Commit message · ShahanaFarooqui

common: don't consume deterministic randbytes stream for trace ids

Trace/span ids now come from a plain counter when CLN_DEV_ENTROPY_SEED is active, so tracing (which CI's HAVE_USDT=1 build enables by default) no longer shifts the deterministic RNG stream that PSBT serial ids and locktime fuzz are drawn from.

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
entropy or randomnesssigning boundaryfuzzing or regression evidence
AI analysis · Low 37/100

This change fixes a subtle bug in Core Lightning's tracing code. When running with a special developer-only deterministic randomness override (CLN_DEV_ENTROPY_SEED), trace IDs were being drawn from the same predictable random stream used for actual transaction details like PSBT serial IDs and locktime fuzzing. Because tracing may be enabled or disabled depending on build settings, this meant the same test or operation could produce different transaction outputs depending on whether tracing was compiled in. The fix makes trace IDs use a separate simple counter when deterministic mode is active, so tracing no longer shifts the random stream and transaction results stay consistent.

Security candidatecommon: don't trigger siphash_seed() init from span hashing either.by ShahanaFarooqui · e54fe678 · Jul 14, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · ShahanaFarooqui

common: don't trigger siphash_seed() init from span hashing either.

Previous commit stopped trace ids consuming the deterministic
randbytes stream, but tracing still touched it once: span_key_hash()
calls siphash_seed(), whose lazy init draws 16 bytes from the stream.
Since randbytes call sites are assigned their offset blocks in
first-use order, that single draw shifts every later draw in the
process by 1000 when tracing is active (HAVE_USDT builds, as in CI):
keysend preimages and invoicerequest payer keys then differ from a
build with tracing disabled, showing up as an 11-file doc-examples
diff.

Use a cheap multiplicative hash for span keys when the deterministic
override is active, so tracing touches the RNG stream zero times.

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

This is a small bug-fix commit in Core Lightning's tracing code. It fixes a situation where enabling tracing accidentally changed the sequence of random numbers used elsewhere in the program, causing test outputs to differ between builds with and without tracing. The change makes tracing use a simple math hash instead of a randomness-seeded hash when deterministic mode is active. There is no direct security vulnerability here; it is a determinism/reproducibility fix.

Security candidateautogenerate-rpc-examples.py: disable entropy for generation.by Rusty Russell · 81443075 · Jul 14, 2026 · 2 filesMessage 70 · AdequateInformational 15Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: disable entropy for generation.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Informational 15/100

This commit changes Core Lightning's internal test tooling so that automatically generated RPC documentation examples use predictable randomness and a fixed clock time. It only affects test/example generation code, not the production Lightning node software that users run. There is no security issue here; it is a developer convenience change to make generated documentation reproducible.

Lower-priorityautogenerate-rpc-examples.py: remove example mangling.by Rusty Russell · 145edea5 · Jul 14, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: remove example mangling.

We temporarily add a flake8 exception so it doesn't complain about all
the now-unused variables.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityautogenerate-rpc-examples.py: remove unused varsby Rusty Russell · 68507fe2 · Jul 14, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: remove unused vars

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritytests/autogenerate-rpc-examples.py: always use largest UTXO for fundchannel example.by Rusty Russell · 86aa1c04 · Jul 14, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Rusty Russell

tests/autogenerate-rpc-examples.py: always use largest UTXO for fundchannel example.

Now order has changed, the first one is insufficient; this is more robust.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityautogenerate-rpc-examples.py: canned blocks.by Rusty Russell · 0dd214af · Jul 14, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: canned blocks.

Unless REGENERATE_BLOCKCHAIN is true, in which case we make them.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityautogenerate-rpc-examples.py: more refinement.by Rusty Russell · 6f52691e · Jul 14, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: more refinement.

1. Don't mangle bookkeeper events.
2. Use l3, not l1, for listtransactions: it's more stable.
3. Use l2, not l1, for listpeerchannels and listchannels.
3. Use l2, not l2, for listfunds.

(l1 has a lot of variation).

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityautogenerate-rpc-examples.py: more block generation and synchronization.by Rusty Russell · 03b239a4 · Jul 14, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: more block generation and synchronization.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityautogenerate-rpc-examples.py: rewrite problematic examples.by Rusty Russell · 4b762330 · Jul 14, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Rusty Russell

autogenerate-rpc-examples.py: rewrite problematic examples.

And hand in CLN_NEXT_VERSION to replace the version string.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityautogenerate-rpc-examples.py: parameterized base port and cln next versionby ShahanaFarooqui · c928c573 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: parameterized base port and cln next version

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityautogenerate-rpc-examples.py: added 17 new RPC to ignore listby ShahanaFarooqui · c3a3a0ec · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: added 17 new RPC to ignore list

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityautogenerate-rpc-examples.py: added wait functions like wait_for_htlcs_settled, wait_for_wallet_txsby ShahanaFarooqui · c56990f7 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: added wait functions like wait_for_htlcs_settled, wait_for_wallet_txs

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityautogenerate-rpc-examples.py: added feature to be able to rewrite the request in Rewriterby ShahanaFarooqui · cf3467a3 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: added feature to be able to rewrite the request in Rewriter

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityautogenerate-rpc-examples.py: fixed recover examples via `lightning-hsmtool getsecret`by ShahanaFarooqui · 16657264 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: fixed recover examples via `lightning-hsmtool getsecret`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateautogenerate-rpc-examples.py: pin the full sorted UTXO set for multiwithdraw examplesby ShahanaFarooqui · 6f464e46 · Jul 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: pin the full sorted UTXO set for multiwithdraw examples

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100

This commit only changes an internal test script that automatically generates example RPC commands for documentation. It makes the examples more deterministic by explicitly selecting which coins the test wallet uses, so the generated documentation does not vary randomly between test runs. There is no change to the actual Core Lightning node software that users run, and no security vulnerability is being fixed.

Lower-priorityautogenerate-rpc-examples.py: added more rewrite for other RPCsby ShahanaFarooqui · 2e608edc · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: added more rewrite for other RPCs

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityautogenerate-rpc-examples.py: added sorting for some list example to stabilise the responseby ShahanaFarooqui · 9a50cc12 · Jul 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ShahanaFarooqui

autogenerate-rpc-examples.py: added sorting for some list example to stabilise the response

And flake fixes

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritytests: use bitcoind.conf_file instead of hardcoded bitcoin.conf in RawProxy mocksby ShahanaFarooqui · 5de2c855 · Jul 14, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · ShahanaFarooqui

tests: use bitcoind.conf_file instead of hardcoded bitcoin.conf in RawProxy mocks

These tests built their RawProxy against a hardcoded bitcoin.conf in the node's datadir. That only worked on liquid-regtest by accident: BitcoinD.__init__ used to write bitcoin.conf even when the node was actually an ElementsD. Now that config writing is deferred to set_port() and ElementsD only writes elements.conf, the mocks found no config and no .cookie, so their RPC calls failed and bcli's getblock timed out, leaving lightningd stuck during restart.

Use bitcoind.conf_file, which points at the config the running daemon actually uses (elements.conf on liquid-regtest, bitcoin.conf on egtest).

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Security candidatedoc: generate all examples with newchainby ShahanaFarooqui · e392c7d7 · Jul 14, 2026 · 129 filesMessage 45 · ThinInformational 15Details
Commit message · ShahanaFarooqui

doc: generate all examples with newchain

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This commit is a large documentation-only refresh. It regenerates example outputs in the project's JSON API schema files and test data so that all examples use a newer, more realistic test chain setup called 'newchain'. The values shown in the examples (node IDs, transaction IDs, payment hashes, runes, invoices, etc.) are swapped from placeholder/fake-looking strings to ones that look like real Bitcoin Lightning testnet data. There is no code change to the actual lightning node software, no bug fix, and no security patch.