CommitWatch RSS
RR
← Developer activityStrong match

Rusty Russell

Public commit activity attributed with strong match confidence. This page describes observable work, not personal trustworthiness.

959 commits2 monitored projects73 candidates0 high-risk analyses
Project constellation

Where the commits appear

Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.

Monitored External sample
Projects connected to Rusty RussellA visual map of monitored and externally discovered repositories.RRdeveloper958Core Lightning1Eclair
Monitored evidence

CommitWatch projects

Core LightningElements Project958 commits73 candidates0 high riskEclairACINQ1 commits0 candidates0 high risk
External discovery

Other public projects

No external sample loaded yet.

A verified GitHub handle is needed before external discovery.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

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 ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

global: replace randombytes_buf() with randbytes() wrapper.

This commit only adds a new header include (<common/randbytes.h>) to 24 test files. It does not change any production code, cryptographic operations, or runtime behavior. The change is a test-infrastructure refactor to support deterministi…

72fd8b5cby Rusty Russell+24−024 files
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 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 ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: expose is_signature_field as is_tlv_signature_field.

This commit simply renames an internal helper function and makes it publicly available in a header file so other parts of the codebase can use it. There is no bug fix, behavior change, or security-sensitive logic alteration. It is a routin…

bc2411b5by Rusty Russell+8−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightning-downgrade: prepare for downgrading to v26.04.

This commit is routine release bookkeeping. It adds a new version marker (v26.04) to the downgrade tool and a comment in the database migration list so that users who later downgrade from v26.04 to an earlier release have the correct metad…

cc8c043fby Rusty Russell+2−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

BOLT quotes: split cross-section quotes; prepare for new `...` semantics.

This commit is a documentation and code-comment cleanup. It splits BOLT (Bitcoin Lightning specification) quote comments so a new internal tool can check them more accurately, and removes a few stray leading ellipses from comments. There i…

07d1db00by Rusty Russell+35−1911 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 86 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

Update outdated BOLT quotes in channel open/close handling.

This commit updates code comments that quote the Lightning Network specification (BOLT) in four files. Most changes are cosmetic: fixing outdated wording, malformed quote markers, and removing one incorrect quote. One change in connectd/qu…

Comment-only/spec-alignment changes with no functional code changes visible in the diffOne stale/incorrect BOLT quote removed in connectd/queries.c, but behavior already matched the correct interpretationUpdated BOLT quotes in dual_open_control.c around feerate and RBF failure conditions, but surrounding failure logic remains
39ac3f14by Rusty Russell+50−494 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 67 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: follow BOLT 4 requirements to make decryption constant time.

This change fixes a privacy weakness in how Core Lightning processes returned error messages from the Lightning network routing protocol. Previously, the software stopped decrypting as soon as it found the error's origin, which could let a…

Timing side-channel mitigation in cryptographic error handlingConstant-time / fixed-iteration decryption loopDummy secret substitution for out-of-range hops
d5508e1eby Rusty Russell+30−131 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

connectd: rescue constant message size feature by exploiting option 154 (Eclair).

This commit adjusts when Core Lightning pads ping messages to keep packet sizes uniform. It now skips padding when talking to Eclair nodes that advertise feature bit 154, because Eclair had a similar bug where it did not reply to certain p…

Workaround for a known interoperability bug in another implementation (Eclair)Avoids sending 'no reply' pings to peers known to mishandle themReferences a prior bug where uniform writes caused issues with non-replying peers
a65c6975by Rusty Russell+8−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

connectd: rescue constant message size feature by exploiting OPT_ONION_MESSAGES (LND)

This change adjusts when Core Lightning pads its network messages to a constant size. Previously padding was controlled by a developer/testing flag. Now it is enabled only when the connected peer advertises support for 'onion messages' (a …

Privacy feature preservation: uniform packet sizes can reduce traffic-analysis leakage.Interoperability workaround: avoids disconnects with LND peers that do not tolerate padded pings.No direct security bug patched in the diff (no bounds check, auth, crypto, or memory fix).
52b70043by Rusty Russell+5−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: fix flake in test_easy_splice_out_into_channel

This commit fixes a flaky test in Core Lightning's test suite. The test sometimes failed because it checked immediately whether an 'inflight' splice entry had disappeared from a channel, but the nodes l1 and l3 may not have processed the l…

3e878280by Rusty Russell+2−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: add tal_free_if_taken() helper for common case.

This commit is a straightforward code cleanup: it introduces a small helper function called tal_free_if_taken() and replaces many repeated two-line patterns across the codebase with calls to that helper. The behavior of the program is unch…

9b85a247by Rusty Russell+55−9229 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

bitcoin: hoist script_with_len out of wallet/ into here.

This commit is a routine code cleanup: it moves a small helper structure and its hash/equality functions from the wallet module to the more general Bitcoin module so other code can reuse them. It also updates many test files to provide a s…

8f8cab0eby Rusty Russell+187−7056 files
No security note in commit
Open full analysis →Source commit ↗
Informational 24 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

chaintopology: don't use txfilter, rely on wallet_extract_owned_outputs.

This commit removes an old shortcut (a Bloom-like 'txfilter') that Core Lightning used to guess whether a new Bitcoin block contained transactions relevant to the wallet. Instead, it now asks the wallet directly to identify which transacti…

Removal of redundant address-matching filter in favor of authoritative wallet lookupChange to on-chain output discovery path that affects UTXO detection and invoice payment recognitionPotential for missed or delayed UTXO detection if wallet_extract_owned_outputs population behavior differs from txfilter
5cdb7bdeby Rusty Russell+13−151 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: make global exclusion for "That's weird: Request X took Y msec" under valgrind.

This is a test-only change that stops CI test failures caused by slow valgrind runs. It does not change the actual Core Lightning node software that users run, so it has no direct security impact on real systems.

a9a72adcby Rusty Russell+7−53 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tools: delete gossip_store of needed for downgrade even if db hasn't changed.

This is a small bug-fix in a downgrade helper tool. Previously, the tool only deleted an incompatible gossip data file when the database actually needed changes. Now it deletes that file even if the database is already compatible, preventi…

No security-relevant signals in commit message or diffChange is a functional correctness fix in a maintenance toolNo input validation, memory safety, or cryptographic changes
d4c62f8cby Rusty Russell+7−62 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 75 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: conduct unit tests with both bip86 and bip32.

This commit only changes test code. It makes the wallet unit tests run twice: once using the older BIP32 key derivation setup and once using the newer BIP86 setup. No production code is modified, so it cannot directly affect real users or …

fe5c3c95by Rusty Russell+32−251 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: make sure to use old_hsmsecret on downgrade tests.

This change only updates a test file so that downgrade tests create nodes using an older-format secret key file. It does not change any production code, network protocol, or wallet behavior, and there is no security issue in the commit its…

c7973b8aby Rusty Russell+3−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

Makefile: update next and prev versions now we've released.

This is a routine post-release maintenance commit for Core Lightning. It updates version numbers in the build files and test infrastructure after a new release, adjusts downgrade tests to reflect that downgrading past the new release no lo…

No direct security patchRoutine release/version housekeepingTest-only changes for downgrade compatibility
ee0175b8by Rusty Russell+17−177 files
No security note in commit
Open full analysis →Source commit ↗
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →