E
← Developer activityStrong match

enaples

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

@enaples on GitHub ↗
15 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 enaplesA visual map of monitored and externally discovered repositories.Edeveloper15Core Lightning
Monitored evidence

CommitWatch projects

External discovery

Other public projects

No external sample loaded yet.

Authenticated GitHub discovery can enrich this profile.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

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

nix: fix `nix build` and simplify NixOS install docs

This commit fixes the Nix package build for Core Lightning so that `nix build` works again. It is a build-system/documentation fix, not a security patch. There is no vulnerability being fixed here.

531673a4by enaples+40−72 files
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

docs: fixing Fedora installation

This commit only updates the Fedora installation instructions in the documentation. It changes command syntax, adds required build dependencies (openssl, openssl-devel, uv), bumps the example release tag, and switches the build instruction…

563b21e4by enaples+15−61 file
No security note in commit
Moderate 61 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: test RBF stops after closed tx is confirmed

This commit adds a test that checks whether Core Lightning stops trying to replace (RBF) a penalty transaction once a replacement version has already been confirmed on the blockchain. The test documents a bug where the node would keep firi…

RBF loop does not terminate after replacement tx is confirmedUse of stale original_txid instead of current in-flight txid for confirmation checkIndefinite rebroadcast of on-chain penalty transaction
3e0f48e1by enaples+71−01 file
No security note in commit
Moderate 59 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

chaintopology: fix RBF loop that never stops after replacement tx confirms

This fix resolves a bug where Core Lightning would keep trying to replace a transaction with a higher-fee version forever, even after the replacement had already been confirmed on the Bitcoin blockchain. The loop happened because the code …

CWE-835: Infinite LoopResource exhaustion via repeated on-chain transaction creationPotential fee loss / wallet bloat from perpetual RBF replacements
15a66cbcby enaples+7−21 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: test bookkeeper correctly accounts for splice in/out

This commit only adds new automated tests for the bookkeeper feature, checking that it correctly records accounting events when Lightning channels are spliced in (adding funds) or spliced out (removing funds). It does not change any produc…

f5965b3aby enaples+239−01 file
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fixing flake8 + fixed fees in spliceout

This commit only updates a single test file (tests/test_bookkeeper.py). It removes an experimental feature flag that is no longer needed, fixes Python style issues flagged by flake8, and replaces a hardcoded 5000-satoshi splice-out fee est…

906663a0by enaples+16−281 file
No security note in commit
Informational 17 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: test to reproduce failed to retransmit funding transaction

This commit only adds a new pytest test case that reproduces a minor startup logging bug. Core Lightning was unnecessarily trying to re-broadcast already-confirmed channel funding transactions every time it restarted. Bitcoin rejected the …

Spurious rebroadcast of funding transactions on restartIncorrect channel depth check at startup due to DB load orderingRegression test added; no daemon code patched in this commit
6aae3d48by enaples+16−01 file
No security note in commit
Low 25 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: don't try to re-xmit funding tx for already-confirmed channels.

This commit fixes a harmless but noisy bug in Core Lightning. On every restart, the node was trying to re-broadcast the funding transaction for channels that were already confirmed long ago. Bitcoin rejected these with a routine 'already k…

Spurious re-broadcast of funding transactions on node restartReliance on a field (channel->depth) that is uninitialized at the point of useRoutine bitcoind error -27 ('Transaction outputs already in utxo set') surfaced as UNUSUAL log
d7b0f1faby enaples+8−42 files
No security note in commit
Informational 20 AI analysisMessage 50 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

currencyrate: round to the third digit and adding source argument to `currencyrate` command

This commit updates the currency-rate plugin in Core Lightning. It adds a new optional 'source' argument to the `currencyrate` command so users can pick a specific price source, rounds displayed rates to three decimal places, and adds argu…

Input validation: argument-count limits added to three RPC methodsNew oracle helper validates source name, currency support, and cache TTL before returning a rateRounding change is a presentation-layer change, not a security fix
6175642eby enaples+110−122 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: test new features and improvements of currencyrate plugin

This commit only changes test code for the currencyrate plugin. It adds new tests for rounding behavior, selecting a specific rate source, and rejecting unknown sources or too many RPC arguments. There is no change to production code and n…

727b6eaaby enaples+130−811 file
No security note in commit
Informational 19 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

schemas: added `source` field to `currencyrate`

This commit adds a new optional 'source' argument to the currencyrate RPC command in Core Lightning. It lets users pick a specific exchange-rate source instead of getting the median across all sources. The change is purely a feature additi…

4f8b0416by enaples+283−1537 files
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
EP Elements ProjectCore Lightning BitcoinLightning Network

currencyrate: added README

This commit only adds a README file for the currencyrate plugin. It contains documentation describing how to configure price sources and warning users that stopping the plugin can interrupt invoice creation. There are no code changes and n…

fdce4870by enaples+74−01 file
No security note in commit
Low 44 AI analysisMessage 72 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: test funds don't get stuck as reserved after `withdraw` fails due to broadcast rejection (e.g. feerate below mempoolminfee).

This commit only adds a new test case that demonstrates a known bug in Core Lightning's wallet handling. When a `withdraw` command fails because the Bitcoin node rejects the transaction broadcast (for example, the fee is too low), some fun…

Funds can be marked reserved after a failed broadcast, making them temporarily unavailable for spendingKnown bug is explicitly documented in test commentsNo production code fix is included in the commit
36f02d32by enaples+64−01 file
No security note in commit
Informational 12 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: test reproduce #8863 [ Neated and added xfail -- RR ]

This commit only adds a new test case to the project's test suite. It does not change any production code. The test is marked as expected to fail (xfail) and is intended to reproduce a previously reported issue (#8863) about opening dual-f…

7f949c61by enaples+29−01 file
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: removed old test

This commit simply deletes an old test from the test suite. It removes a pytest function that checked how the software handles opening a dual-funded channel when Bitcoin fee estimates are unavailable. There is no change to the actual softw…

2cc1abcfby enaples+0−291 file
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →