CommitWatch RSS
KS
← Developer activityVerified account

Ken Sedgwick

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

@ksedgwic on GitHub ↗
12 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 Ken SedgwickA visual map of monitored and externally discovered repositories.KSdeveloper12Core Lightning
Monitored evidence

CommitWatch projects

Core LightningElements Project12 commits0 candidates0 high risk
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 17 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: update graceful notifications when HTLC states change

This commit fixes a notification bug in Core Lightning's `graceful` JSON-RPC command. The `graceful` command tells users about the next pending payment (HTLC) that is closest to expiring, including its current state. Previously, if a user …

No memory safety, authentication, authorization, or cryptographic issues present in diffChange is purely a notification/state-update correctness fixNo input parsing or external data handling changes
2e5bc4fcby Ken Sedgwick+21−192 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 100 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pyln-testing: don't let wait_for_log match its own forwarded announcement

This commit fixes a bug in Core Lightning's Python testing toolkit. When tests used an 'inline plugin' and ran with detailed (DEBUG) logging, the test helper wait_for_log() would accidentally see its own 'Waiting for...' message in the nod…

Test-framework self-match bug caused real test race and assertion failureLog forwarding filter prevents internal machinery messages from polluting node logsNo privilege escalation, remote attack surface, or cryptographic weakness introduced
ae8dee8aby Ken Sedgwick+79−13 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 76 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix flaky test_bwatch_listwatch

This commit fixes a flaky automated test. It does not change production code or fix a security bug. The test was sometimes failing because it counted all 'watches' in a list, but the wallet also registers its own watches in the background,…

46702dadby Ken Sedgwick+13−71 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 66 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: fail sendpay cleanly when the route does not fit the onion

This commit fixes a crash bug in Core Lightning's payment command. When a user or plugin submitted a payment route with too many hops to fit inside the cryptographic 'onion' envelope, the software failed to check whether the onion was actu…

NULL-pointer dereference leading to daemon crash (SIGSEGV)Missing return-value check on create_onionpacket()Denial-of-service vector: malformed/long route crashes lightningd
90c60d01by Ken Sedgwick+30−02 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pyln-testing: wait for listen port release before starting a node

This is a testing-framework fix, not a fix in the Core Lightning node software itself. It stops automated tests from failing when a background process (connectd) is slow to release a network port after a node restart. There is no direct se…

No security-relevant code change in production daemonFixes a test-framework race condition, not an exploit primitiveNo input validation, cryptography, or authorization changes
1136b217by Ken Sedgwick+38−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix broken race handler in test_funding_external_wallet_corners

This is a one-line fix to a flaky automated test. The test was supposed to tolerate a harmless race condition where a peer disconnects during connection, but the assertion was checking the wrong part of the error object, so the test failed…

a87aa28aby Ken Sedgwick+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix flaky test_simple_close_dust_output_omitted mempool race

This commit fixes a flaky automated test, not a security bug in the actual Core Lightning software. The test sometimes failed because it took a snapshot of Bitcoin's memory pool and then tried to fetch each transaction, but one transaction…

406fc7a4by Ken Sedgwick+16−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: compare medians in test_no_delay instead of means

This commit only changes a single test file. It swaps a flaky statistical comparison (mean with standard-error margin) for a more stable one (median with a fixed 20 ms margin) in a timing test about TCP Nagle delays. There is no change to …

365428bbby Ken Sedgwick+20−301 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix flaky test_sql blockheight race

This commit fixes a flaky test, not a security vulnerability. The test sometimes failed because one node was slower to process newly mined blocks than the others, causing payment route expiry values to be rejected. The fix simply waits for…

4323207cby Ken Sedgwick+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix flaky listchannels doc example by waiting for l3 to disable its l4 channel

This commit fixes a flaky automated test that generates documentation examples. It adds a wait so that a channel disabled by one node is consistently reflected before taking a snapshot. There is no security vulnerability or user-facing bug…

fc82dc25by Ken Sedgwick+6−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix flaky reckless tests by waiting for the canned github server

This commit fixes a flaky automated test, not a security bug. The test harness previously started a fake GitHub server and sometimes tried to use it before it was ready, causing random test failures. The patch simply waits for the server t…

d4a960baby Ken Sedgwick+16−11 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 →