CommitWatch RSS
F
← Developer activityStrong match

frankomosh

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

11 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 frankomoshA visual map of monitored and externally discovered repositories.Fdeveloper11Bitcoin Core
Monitored evidence

CommitWatch projects

Bitcoin CoreBitcoin Core11 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 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: populate wallet TXO index in wallet_create_transaction

This is a fix to a Bitcoin Core fuzz test (an automated testing harness), not to the main wallet code that real users run. The test was inserting fake wallet transactions in a way that skipped updating an internal index called m_txos. Beca…

Test-only change in fuzz harnessFixes internal test-state consistency, not production wallet behaviorNo validation, consensus, or P2P networking changes
1eac6a72by frankomosh+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: add p2p_private_broadcast harness

This commit adds a new automated fuzz test for Bitcoin Core's private transaction broadcast feature. It is purely a testing/quality-assurance change and does not modify any production networking or consensus code. There is no security vuln…

d24d3cbaby frankomosh+254−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: exercise ForNode/ForEachNode callbacks in connman fuzz harness

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. The change makes the fuzzer exercise more code paths in the connection manager, but it does not alter the actual Bitco…

371eac80by frankomosh+17−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: apply node context reset pattern to p2p_handshake

This change fixes a bug in a Bitcoin Core fuzz test (an automated testing harness, not production code). The test was creating new address-manager and peer-manager objects on every fuzzing iteration while leaving the connection manager poi…

dangling pointer / use-after-free class bug in test harnessfix follows a previously established reset pattern (fabf8d1)change is confined to fuzz test code (src/test/fuzz/p2p_handshake.cpp)
dfe5d6a8by frankomosh+18−191 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: set fSuccessfullyConnected in connman harness

This commit fixes a Bitcoin Core fuzz test harness so that simulated peer nodes are marked as successfully connected. Without this flag, the test's code coverage was poor because the harness filtered out all fake nodes before running impor…

685a44c6by frankomosh+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: add validation check for initial self-announcement

This Bitcoin Core patch fixes a small inconsistency in how a node tells other nodes about its own network address. Normally, before sharing any address, the code checks whether the receiving peer can actually understand that address type. …

Missing input/peer-capability validation in network message constructionInconsistent enforcement of address-format compatibilityPotential protocol violation or peer confusion from unsupported address format
6a8dbf9bby frankomosh+7−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: exercise TransactionMerklePath with empty block; targets the MerkleComputation empty-leaves path that was only reached by fuzz tests

This commit only adds a new test case to Bitcoin Core's test suite. It checks that when a block has no transactions, a helper function called TransactionMerklePath returns an empty path. There is no change to production code, no bug fix, a…

ffcae82aby frankomosh+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: mention coverage build in quickstart section

This commit only adds a documentation sentence pointing readers to existing developer notes about coverage builds for fuzz testing. It changes no code, build scripts, or configuration.

dee7eec6by frankomosh+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: Add cmake help option in Windows build instructions

This commit only updates two Windows build instruction documents to mention a standard CMake help command. It does not change any program code, build scripts, or configuration logic, and has no security relevance.

9577daa3by frankomosh+5−02 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: add assertion for BlockTransactionsRequest indexes

This commit adds a safety check in Bitcoin Core's network message handling for a specific message type (GETBLOCKTXN). After reading the message, it verifies that a list of transaction indexes is strictly increasing. This is a defensive cod…

Defensive invariant check added after deserializationCompact block transaction index ordering validationUse of Assume() rather than fatal error handling
65a10fc3by frankomosh+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: add a target for DifferenceFormatter Class

This commit adds a new automated fuzz test for a Bitcoin Core data-formatting helper called DifferenceFormatter. It does not change any production code, network behavior, or wallet logic. It only adds a test file and registers it in the bu…

58be359fby frankomosh+33−02 files
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 →