2
← Developer activityStrong match

21M4TW

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

3 commits1 monitored projects0 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 21M4TWA visual map of monitored and externally discovered repositories.2developer3Core Lightning
Monitored evidence

CommitWatch projects

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

lightningd: don't allow enableoffer on single-use offer.

This commit fixes a bug in Core Lightning's offer management. A 'single-use offer' is meant to be used once and then become inactive. Previously, calling the enableoffer command on an already-used single-use offer could cause the node to c…

Denial-of-service vector: unhandled state transition could crash the lightningd daemonInput validation gap: enableoffer did not guard against re-activation of used single-use offersNew error code introduced to explicitly reject invalid state transition
d76e4e71by 21M4TW+5−13 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

Changelog-Fixed: Replacing sed by $(SED) in Makefile

This is a tiny build-system cleanup: the Makefile now uses a variable named $(SED) instead of directly calling the 'sed' command. It does not change what the software does, only how the build system refers to the sed tool. There is no secu…

dbfd352aby 21M4TW+2−21 file
No security note in commit
Low 35 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

offers: require opt_onion_message for incoming invoices too. Changelog-Fixed: offers: require peers for blinded paths to have `option_onion_messages`, due to reports of LND not forwarding our blinded payments correctly.

This change tightens which network peers Core Lightning will choose when creating hidden (blinded) payment paths for incoming invoices. Previously it only required support for route blinding; now it also requires support for onion messages…

Change in peer-selection logic for blinded payment pathsInteroperability failure with a third-party implementation (LND) cited as motivationNo explicit vulnerability disclosure or CVE referenced in commit
29e4c3feby 21M4TW+6−11 file
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →