CommitWatch RSS
GS
← Developer activityStrong match

Greg Sanders

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

24 commits2 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 Greg SandersA visual map of monitored and externally discovered repositories.GSdeveloper23Bitcoin Core1libwally-core
Monitored evidence

CommitWatch projects

Bitcoin CoreBitcoin Core23 commits1 candidates0 high risklibwally-coreElements Project1 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.

Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: don't connman.ReceiveMsgFrom oversized msg

This is a small fix to a Bitcoin Core fuzz test (an automated internal testing harness), not to the live network code. The fuzzer was sometimes creating fake P2P messages larger than the real protocol allows and passing them into a test he…

Test-only fuzz harness hardeningOversized message guard added before ReceiveMsgFrom() in fuzz targetNo change to production P2P message acceptance logic
bb19f1daby Greg Sanders+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 23 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Release cs_main between individual private tx re-attempts

This commit changes how Bitcoin Core holds an internal lock (cs_main) when retrying private transaction broadcasts. Previously, the lock was held for the entire batch of stale transactions; now it is released and re-acquired between each i…

Lock scope reduction (cs_main) in network processing codePerformance/liveness improvement for large rebroadcast queuesNo explicit security claim in commit message or diff
cbf8c107by Greg Sanders+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

private broadcast: add release note for limited cap

This commit only adds a release note describing a previously implemented limit on a transaction queue. It does not change any code behavior, so it has no direct security impact on its own. The note tells users that a privacy-related transa…

4e29de71by Gregory Sanders+8−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 45 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

private broadcast: limit outstanding txs to count of 10,000

This commit adds a hard cap of 10,000 transactions to Bitcoin Core's private-broadcast queue. Before the change, that queue could grow without bound, potentially consuming large amounts of memory and CPU if many transactions were submitted…

Unbounded memory growth in private broadcast queue is boundedNew error path returns TransactionError::PRIVATE_BROADCAST_FULLRPC error mapping added: RPC_OUT_OF_MEMORY
5aea3d03by Gregory Sanders+229−2313 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 67 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: ensure group data cluster pointers are live

This is a small change to an internal self-check (SanityCheck) inside Bitcoin Core's transaction graph code. It adds a new consistency check to make sure that certain cached cluster pointers actually point to currently live data structures…

assertion added to internal sanity checkerpointer liveness validation for cached cluster referencesno network-facing or consensus code changed
df9eb72bby Greg Sanders+13−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 39 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

mempool: remove all subsequent tx in pkg on failure

This change tightens a safety check in Bitcoin Core's transaction memory pool (mempool) handling. When a group (package) of related transactions is submitted and one fails a final consensus check, the code now removes that failing transact…

Defensive hardening against mempool inconsistencyPotential inconsistent mempool state if parent fails consensus but child does notPackage transaction submission failure handling
ac9aa71bby Greg Sanders+3−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

policy: don't CheckEphemeralSpends on reorg

This Bitcoin Core change adjusts how the network's memory pool (mempool) handles tiny-value 'dust' transactions when a blockchain reorganization occurs. Previously, during a reorg, transactions that had been mined in a block were re-checke…

Policy/standardness bypass only under reorg path (m_bypass_limits)Functional test rewritten to assert reorged sweep and descendants are acceptedNo consensus code changed; no signature or script validation altered
33fbaed3by Greg Sanders+24−203 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: add optimal result to getmempoolinfo

This commit simply adds a new read-only field called 'optimal' to the getmempoolinfo RPC output. It exposes whether the mempool is currently in a known-optimal transaction ordering. There is no change to transaction processing, consensus r…

a9e59f7dby Greg Sanders+8−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

mempool: log if we detect a non-optimal mempool

This commit only adds extra logging messages. It does not change how the mempool behaves or fix any bug. It lets developers see, via debug logs, when the mempool's internal transaction ordering is not in the best possible state after routi…

No security fix: only adds debug loggingNo change to transaction validation, eviction, fee estimation, or P2P behaviorNo new assertions, locks, or resource limits introduced
a3fb3dd5by Greg Sanders+9−31 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 66 AI analysisMessage 68 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: Fix BIP118 ANYPREVOUTANYSCRIPT sighash

This commit fixes a bug in how a special Bitcoin/Elements signature hash flag (BIP118 ANYPREVOUTANYSCRIPT) is processed. Because of the order of checks, the code was accidentally treating ANYPREVOUTANYSCRIPT as if it also needed to include…

Incorrect cryptographic hash construction for BIP118 ANYPREVOUTANYSCRIPT sighashFlag implication bug: APOAS implies ANYONECANPAY, causing fall-through to wrong branchPotential signature malleability or replay risk due to extra prevout data being hashed
fb75bae7by Greg Sanders+4−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

release note: cpfp carveout removed in 31.0

This commit only adds a release note documenting that a mempool feature called the 'CPFP Carveout' was removed in Bitcoin Core version 31.0. It does not change any code, fix a bug, or address a security vulnerability. It is purely informat…

61726483by Greg Sanders+8−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 67 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: add coverage for issue 34206

This commit only adds a new regression test to Bitcoin Core. It does not change any production wallet, consensus, or mempool code. The test exercises a scenario involving v2 and v3 (TRUC) transactions across a blockchain reorganization, li…

Regression test added for issue 34206Test covers reorg handling for v2 parent + TRUC child clustersNo production code changes
d09a19fdby Greg Sanders+106−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: remove erroneous-on-reorg Assume()

This commit removes a single internal safety check (an 'Assume' assertion) in Bitcoin Core's wallet code. The assertion could incorrectly fail during a blockchain reorganization, causing the wallet process to abort unexpectedly. Removing i…

Removal of an Assume() invariant that could be violated by blockchain reorganizationWallet crash / denial-of-service vector via reorg-triggered assertion failureNo logic change to coin selection or transaction spending itself
4c7cfd37by Greg Sanders+0−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: change low fee parents to 0-fee

This commit only changes a single test file. It simplifies how test transactions are created by using zero-fee parent transactions instead of carefully calculated low-but-nonzero fees. There is no change to Bitcoin Core's actual network, c…

25e84d37by Greg Sanders+4−301 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 98 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: ensure clean orphanage before continuing

This is a test-only change in Bitcoin Core's functional test suite. It adjusts a test to wait for orphan transactions to be cleared after a peer disconnects, because a previous code change made orphans disappear faster than the test origin…

95ef0fc5by Greg Sanders+15−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: fix test_limit_enforcement_package

This commit fixes a bug in a Bitcoin Core functional test, not in the actual Bitcoin network code. The test was accidentally creating the same transaction twice and putting fees on the wrong transaction, so it wasn't really testing what it…

No production code modifiedTest-only change in functional test suiteFixes test logic bug rather than implementation vulnerability
0a8d303dby Greg Sanders+13−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: gate mempool entry based on weight

This is a small fix to a Bitcoin Core fuzz test (an automated testing harness, not production code). The test was using an outdated size check after the real mempool code switched from measuring transaction size in 'vsize' to measuring it …

Integer-limit guard in fuzz harnessTest-only code changeGuard against FeeFrac limit overflow in fuzzing input generation
80432940by Greg Sanders+3−21 file
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

policy: Allow any transaction version with < minrelay

This Bitcoin Core commit relaxes a mempool policy rule. Previously, only a special transaction type called TRUC could be below the minimum relay fee when submitted as part of a package. Now any transaction version can be below that fee if …

Relaxation of mempool fee policyRemoval of per-transaction minimum relay fee enforcement for non-TRUC transactions in packagesZero-fee parent transactions become relayable through package submission
1488315dby Greg Sanders+26−536 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

TxGraph: change m_excluded_clusters

This is a small internal code cleanup in Bitcoin Core's transaction graph code. It swaps one data structure (an ordered set of cluster pointers) for another (an unordered set of cluster sequence numbers). The behavior is unchanged; the cha…

9b43428cby Greg Sanders+6−41 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 →