CommitWatch RSS
L
← Developer activityStrong match

Lagrang3

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

76 commits1 monitored projects4 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 Lagrang3A visual map of monitored and externally discovered repositories.Ldeveloper76Core Lightning
Monitored evidence

CommitWatch projects

Core LightningElements Project76 commits4 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.

Low 32 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: safer iterating over changing htable

This change fixes a subtle bug in Core Lightning's askrene plugin where adding items back into a hash table while looping through it could cause some items to be skipped. The fix collects items that need to be re-added and inserts them onl…

Hash table mutation during iterationPotential skipped entries leading to stale routing constraintsRouting-layer correctness issue
2a3feb7eby Lagrang3+17−41 file
No security note in commit
Open full analysis →Source commit ↗
Low 38 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

libplugin: json_id: guard against weird prefixes

This commit tightens a safety check in Core Lightning's plugin library. When a plugin sends a JSON-RPC request, it builds an internal ID from a method name and a prefix. The code already replaced the method name with a safe placeholder if …

Hardening of request/response correlation ID generationPotential mismatch between outgoing JSON-RPC id and incoming reply id if escaping occursDefensive validation of plugin-supplied strings before use in protocol identifiers
dd652105by Lagrang3+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 80 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: explain failure: add known enabled case

This commit improves an internal diagnostic message inside Core Lightning's payment routing plugin (askrene). It adds a new explanation category called 'known_usable' so that when a payment fails, the software can more precisely report tha…

No security-relevant signals detected in the diff or commit message.Change is a diagnostic/UX improvement to failure explanation strings.No memory safety fixes, input validation changes, or cryptographic changes.
76396dd4by Lagrang3+29−81 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Add unit tests for str_to_u64

This commit only adds a new automated test file that checks how a helper function (str_to_u64) converts text strings to unsigned 64-bit integers. It does not change any production code, so it cannot by itself introduce a security vulnerabi…

dddb455dby Lagrang3+203−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: trim constraints: small optimization

This commit is a small internal code cleanup in Core Lightning's payment routing plugin. It replaces a loop that removes old routing hints one-by-one with a single bulk removal. There is no indication this fixes a security bug or changes e…

ab9fd89aby Lagrang3+17−171 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 ↗
Low 35 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: don't leak channel intel entries

This commit fixes a memory leak in the askrene plugin of Core Lightning. When individual channel intelligence entries were deleted, the code removed the entry from its array but forgot to free two internal pointers (impression and constrai…

Memory leak in plugin data structure cleanupMissing deallocation of nested pointers before array removalFix located in routing/intelligence plugin (askrene)
8891f414by Lagrang3+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 98 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: test explain: fix flake

This commit only changes a test file. It makes the test channels and payment amounts ten times larger so that small on-chain fee variations no longer cause the test to fail on liquid-regtest. There is no change to production code, no user-…

52fd6ae4by Lagrang3+13−131 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: add helper to remove a range of elements

This commit adds a new internal helper function for removing a contiguous block of items from a memory array. It is a straightforward utility addition with no bug fix, no change to existing behavior, and no security relevance visible in th…

3700f4b8by Lagrang3+22−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: tests should expect the new error messages

This commit only updates test files so that automated checks expect slightly different error wording from the xpay payment command. It does not change any production code, so it cannot introduce a security vulnerability or fix one on its o…

0b67601fby Lagrang3+24−32 files
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 ↗
Informational 15 AI analysisMessage 78 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: fakenet test: skip temporarily

This commit simply skips a single automated test in the project's test suite. It does not change any production code, network protocol handling, or wallet logic. The commit message explains the test is being disabled temporarily because a …

0f144dc7by Lagrang3+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 78 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: test for very long log entries

This commit adds a test that reveals Core Lightning can crash when a plugin produces an extremely long log message. The crash happens because the logging code sometimes allocates memory using one method but tries to free it with another, l…

Heap allocator mismatch (libc free on tal-allocated pointer)Denial-of-service crash (SIGABRT) from plugin-generated log inputUse of xfail test to document a reproducible crash
a9b43851by Lagrang3+17−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: add traces for payments

This commit adds diagnostic tracing to the xpay plugin so developers can measure how long payments take. It does not change payment behavior, network handling, or access controls. There is no security issue visible in the change.

1e871ffdby Lagrang3+7−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 13 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: added subtrace to measure getroutes

This change adds a small tracing wrapper around an internal function call so developers can measure how long route-finding takes. It does not change payment logic, amounts, routing decisions, or network behavior. There is no indication it …

5870ffb8by Lagrang3+29−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: add sub-trace to measure injectpaymentonion

This commit only adds tracing instrumentation to measure how long the injectpaymentonion operation takes in the xpay plugin. It does not change payment logic, cryptographic handling, network behavior, or access controls. There is no securi…

c48afd97by Lagrang3+14−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 75 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

renepay: add test to check for wrong CLTV computation

This commit only adds a new test case to the Core Lightning test suite. The test is marked as expected to fail (xfail) and checks whether the renepay plugin computes the CLTV (a timeout value used in Lightning payments) correctly. It does …

40a74a7fby Lagrang3+28−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

renepay: fix CLTV value for the first hop

This commit fixes a bug in Core Lightning's renepay plugin where the time-lock expiry (CLTV) for the first hop of a payment was incorrectly calculated by adding the current block height twice. This caused HTLCs to be created with expiry va…

CLTV/expiry miscalculation in payment routingDouble-counting of blockheight leading to far-future HTLC expiriesTest previously marked xfail now passing after fix
9181505eby Lagrang3+3−54 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

CODEOWNERS: add self as owner of xpay/askrene/renepay

This commit only updates the GitHub CODEOWNERS file to assign one developer as the automatic reviewer for several plugin directories and their test files. It makes no code changes and has no security relevance.

2d367befby Lagrang3+6−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Makefile: fix depedency of autogenerated files

This is a one-line build-system fix in the Makefile. It adds generated Python gRPC files to a list used for dependency tracking during build checks. There is no indication of any security issue, vulnerability, or runtime behavior change. I…

2e6ae4cdby Lagrang3+1−01 file
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 →