PN
← Developer activityStrong match

Peter Neuroth

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

97 commits1 monitored projects1 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 Peter NeurothA visual map of monitored and externally discovered repositories.PNdeveloper97Core 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.

Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

doc: add notification schemas for native topics

This commit only adds new JSON schema documentation files describing notification messages that Core Lightning already sends. It does not change any executable code, network behavior, or security logic. There is no security fix or vulnerab…

95b13b9cby Peter Neuroth+1707−018 files
No security note in commit
Informational 19 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

msggen: generate native notification bindings from schemas

This commit is a large, routine code-generation update for Core Lightning's Rust and gRPC client libraries. It adds native bindings for many existing node notifications (such as payment events, log messages, and coin movements) so that ext…

Large generated diff (+6199/-579) across RPC/gRPC bindingsNew gRPC streaming RPCs expose additional node events to subscribersAdds new notification types including coin_movement, forward_event, sendpay_failure/success, log, warning, plugin lifecycle, and xpay payment part events
8b6374e1by Peter Neuroth+6199−57922 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

cln-grpc: add round-trip tests for notification bindings

This commit only adds new automated tests for notification message bindings in the cln-grpc Rust component. It does not change any production code, network behavior, or security logic. There is no security issue here.

9336e360by Peter Neuroth+335−11 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

doc: update pay_part_start and pay_part_end

This commit only updates developer documentation. It changes example JSON snippets for two plugin event notifications so that the fields appear directly under 'params' instead of being nested inside a 'payload' object. There is no code cha…

48271d53by Peter Neuroth+26−301 file
No security note in commit
Low 28 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: unreserve UTXOs from withheld funding PSBT when dropping channel

This fix ensures that when a user opens a 'zero-confirmation' channel whose funding transaction is deliberately withheld and then the channel is closed/aborted, any bitcoin inputs that had been set aside (reserved) for that funding transac…

Fixes a resource-availability / denial-of-service condition where wallet UTXOs remain unnecessarily reservedAdds explicit unreserve logic for a previously unhandled edge case (withheld funding PSBT)Includes a regression test asserting UTXO status after withheld close
05736f96by Peter Neuroth+24−02 files
No security note in commit
Moderate 60 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: fail in-flight HTLCs upstream when dropping withheld channel

This commit fixes a bug in Core Lightning where money-transfer promises (HTLCs) stuck in a special 'withheld' channel were silently dropped when that channel was force-closed. Previously, the upstream sender was never told the payment fail…

Denial-of-service via forced channel closure: missing HTLC failure caused upstream peers to force-close channels unnecessarilyFunds lockup risk: unresolved HTLCs could leave funds locked until cooperative close or further on-chain resolutionState inconsistency: HTLCs freed locally without upstream failure notification
1c1e83e4by Peter Neuroth+85−02 files
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: add preimage to forward_event notification

This change adds the payment preimage to a plugin notification that fires when a forwarded Lightning payment succeeds. The preimage is already known to the node at that moment, so nothing secret is being exposed that wasn't already availab…

No memory-safety defects visible in diffNo change to authentication, authorization, or cryptographic checksPreimage is already possessed by the node before notification is sent
13608c5aby Peter Neuroth+18−75 files
No security note in commit
Informational 18 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: add channel_id filter to listpeerchannels

This commit adds a new optional 'channel_id' filter to the listpeerchannels RPC command in Core Lightning. It lets users look up a channel by its funding-transaction identifier when the short channel ID isn't yet known. The change is purel…

2971f5d9by Peter Neuroth+917−85912 files
No security note in commit
Informational 14 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: refactor lsps2 and lsps0 error enums

This is a routine code cleanup in Core Lightning's LSPS (Lightning Service Provider Specification) plugin. It reorganizes how error codes are defined and generated, moving from hand-written helper functions to a macro-generated trait patte…

b7be5ef3by Peter Neuroth+92−1068 files
No security note in commit
Informational 12 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: add slim multiplexing transport

This commit adds a new internal helper for the LSPS (Lightning Service Provider Specification) plugin that multiplexes JSON-RPC request/response messages over a generic sender. It is purely a refactor/addition of new code with no obvious s…

3cf99c35by Peter Neuroth+238−21 file
No security note in commit
Informational 14 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: slim down lsps service

This commit is a large internal refactoring of the experimental LSPS (Lightning Service Provider Specification) plugin in Core Lightning. It removes a lot of old code and replaces it with a slimmer service adapter. There is no direct evide…

Large negative diff (-2028 lines) removing prior LSPS2 request handlers and HTLC-accepted hook logicNew custom-message adapter decodes untrusted hex payloads and routes them; decode errors are logged and ignoredNo input validation changes beyond moving existing decode_frame/encode_frame calls into a new module
9adc8cdfby Peter Neuroth+238−20289 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: remove peer_id from transport

This is a small internal code cleanup in the experimental LSPS (Lightning Service Provider Specification) plugin. It removes a stored peer/node ID from a transport helper struct and instead passes the peer ID as a function argument when se…

e591323aby Peter Neuroth+14−193 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: move lsps2 model to proto module

This commit is a pure code refactor: it moves the LSPS2 data model (request/response types, fee calculation, validation, and tests) from one internal module path to another within the same plugin crate. No functionality, logic, or security…

b88dc597by Peter Neuroth+674−6746 files
No security note in commit
Informational 11 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: switch to typed transport

This commit is a routine internal code cleanup in Core Lightning's experimental LSPS (Lightning Service Provider Specification) plugin. It replaces a generic JSON-RPC helper with a more specific, typed client. There is no indication this f…

b9172239by Peter Neuroth+118−3385 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: move primitives into lsps0

This is a straightforward code reorganization: the developer moved shared data types (like monetary amounts and channel identifiers) from a file called 'primitives.rs' into a file called 'lsps0.rs' because the LSPS0 specification actually …

ba93a7caby Peter Neuroth+203−2066 files
No security note in commit
Informational 10 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: add router compatible lsps2 service handler

This commit adds a new experimental plugin feature for the LSPS2 protocol, which lets a Core Lightning node act as a service provider that opens just-in-time channels for payments. The change is purely additive (about 1,500 lines of new Ru…

New feature code, not a patch of existing vulnerabilityMultiple FIXME/TODO comments indicate known incomplete hardeningNo vendor security disclosure or advisory referenced
461065afby Peter Neuroth+1587−04 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: use transport specific error

This is a tiny code cleanup in a Lightning plugin. The developer replaced a generic Rust error type with a project-specific error type in two function signatures. There is no functional change visible in the diff, no bug fix, and no securi…

e08756cdby Peter Neuroth+2−21 file
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: add own trait for lsps offer provider

This commit is a routine internal code cleanup in Core Lightning's experimental LSPS (Lightning Service Provider Specification) plugin. It splits two policy-related RPC methods out of a large generic 'ClnApi' trait into a new, smaller 'Lsp…

Refactoring only: no new network listeners, no new permissions, no cryptographic changes.New client_rejected flag is a policy/control-flow addition, not a vulnerability fix by itself.Error message for get_offer failures becomes less specific (internal_error instead of 'failed to fetch policy'), which is an information-hiding change but not a security fix.
38b3d14eby Peter Neuroth+140−1072 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugins: lsps: move primitives into proto module

This commit is a straightforward code reorganization. It moves shared data types (like monetary amounts and channel identifiers) from one internal module location to another, without changing how they work. There is no security-relevant ch…

06fe54c4by Peter Neuroth+205−2037 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

plugin: lsps: move json-rpc server to core module

This commit is a simple internal code reorganization: it moves the JSON-RPC server implementation from a 'jsonrpc' module into the 'core' module and updates import paths in other files. No security-relevant behavior changes are visible in …

1159adb0by Peter Neuroth+310−3107 files
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →