CommitWatch RSS
JM
← Developer activityStrong match

John Moffett

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

7 commits2 monitored projects2 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 John MoffettA visual map of monitored and externally discovered repositories.JMdeveloper4libsecp256k13Bitcoin Core
Monitored evidence

CommitWatch projects

libsecp256k1Bitcoin Core4 commits2 candidates0 high riskBitcoin CoreBitcoin Core3 commits0 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 36 AI analysisMessage 78 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Add VERIFY_CHECKs that flags are 0 or 1

This commit adds safety checks and documentation to ensure that 'flag' values used in secret-handling code are exactly 0 or 1, not just any 'true' value. These flags control constant-time selection and memory wiping. If a caller passed a d…

constant-time masking invariant enforcementVERIFY_CHECK hardening for secret-dependent flag valuesdocumentation update clarifying 0/1 flag contract
ae00c552by John Moffett+30−811 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qt: Remove HD seed reference from blank wallet tooltip

This commit only changes a user-interface tooltip in the Bitcoin Core wallet creation dialog. It removes an outdated sentence that incorrectly said an HD seed could be added later to a blank wallet, which is not true for descriptor wallets…

929f69d0by John Moffett+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: Always return per-wtxid entries in submitpackage tx-results

This commit fixes a minor bug in Bitcoin Core's submitpackage RPC. Previously, when a package of transactions failed early, the RPC would label the failure as 'unevaluated' but wouldn't actually include each transaction's result in the res…

No memory safety, cryptographic, consensus, or authorization issues evidentChange is an API response completeness/correctness fixAdds a non-fatal assertion (CHECK_NONFATAL) to enforce an internal invariant
cad9a7fdby John Moffett+22−72 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: addpeeraddress: throw on invalid IP

This change tightens error handling in a Bitcoin Core RPC command called addpeeraddress. Previously, if you gave it a bad IP address it would silently return {"success": false}. Now it immediately throws a clear 'Invalid IP address' error,…

Improved input validation and explicit error reporting for RPC addpeeraddressPrevents silent failure (opaque success:false) on invalid IP/hostname inputAligns addpeeraddress behavior with setban/addconnection error handling
316a0c51by John Moffett+22−172 files
No security note in commit
Open full analysis →Source commit ↗
Informational 24 AI analysisMessage 68 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Split memclear into two versions

This commit is a code-quality and testing-hardening change inside a widely used cryptographic library. It splits one internal memory-wiping helper into two: one that guarantees zeros (used where the code later reads the buffer) and one tha…

Refactoring of secret-memory clearing primitivesUse of compiler-barrier / volatile memset to prevent dead-store eliminationAddition of VERIFY-build memory-undefined marking for use-after-clear detection
399b582aby John Moffett+41−2811 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 68 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Rename and clear var containing k or -k

This commit fixes a small but real security hygiene issue in the Schnorr signature code. A 32-byte buffer that holds the secret signing nonce (the random-like value 'k') was not being wiped from memory after use. The patch renames the buff…

Sensitive cryptographic material (Schnorr nonce k/-k) left uncleared in stack memoryAddition of explicit memory clearing via secp256k1_memclearVariable renamed to nonce32 to signal sensitive contents
325d65a8by John Moffett+4−31 file
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 60 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Use size_t instead of int for RFC6979 outlen copy

This commit fixes a variable type mismatch in the RFC6979 nonce-generation code. The code copies a `size_t` length value into an `int` variable. On platforms where `int` is 32 bits and `size_t` is 64 bits, requesting more than about 2 bill…

Integer width truncation from size_t to intPotential signed/unsigned conversion defect leading to out-of-bounds or denial-of-serviceFix located in cryptographic nonce generation path (RFC6979 HMAC-SHA256)
960ba5f9by John Moffett+1−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →