B
← Developer activityStrong match

brunoerg

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

35 commits1 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 brunoergA visual map of monitored and externally discovered repositories.Bdeveloper35Bitcoin Core
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 12 AI analysisMessage 87 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: add test that EvictTxPeerIfFull only evicts tx-relaying peers

This commit only adds a new automated test to Bitcoin Core. It checks that when the node is full of block-only peers (peers that do not relay transactions), an incoming connection is rejected rather than incorrectly kicking out a block-onl…

69ce0dbaby brunoerg+21−01 file
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: wallet: BnB incomplete result on attempt-limit success

This commit adds a new unit test for Bitcoin Core's coin selection algorithm. It checks that when the Branch-and-Bound (BnB) search finds a usable coin selection early but then keeps searching for a better one until it hits the attempt lim…

6ee05c4bby Bruno Garcia+20−01 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: cover disconnect on private broadcast peer with relay=false

This commit only adds a new automated test to Bitcoin Core. It verifies that when a node connects to a 'private broadcast' peer which signals it does not relay transactions (relay=false), the node disconnects that peer. There is no change …

1fc9277aby Bruno Garcia+27−01 file
No security note in commit
Informational 18 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

addrman: remove unreachable tried-collision branch

This commit removes a fallback code path in Bitcoin Core's address manager that the authors say can never be reached under current rules. It replaces that fallback with internal consistency checks (assertions). The change is a code-cleanup…

Removal of purportedly unreachable branch in collision-resolution logicAddition of Assume() assertions to enforce internal invariantNo change to network-facing behavior or data formats
bc7d9050by Bruno Garcia+5−41 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: connman: cover AddLocalServices/RemoveLocalServices

This commit adds new test code to Bitcoin Core's fuzzing harness for the network connection manager. It exercises the AddLocalServices and RemoveLocalServices functions, which control what network service flags a node advertises. The chang…

1a3cfdf1by Bruno Garcia+16−01 file
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: connman: add outbound-bytes invariants

This commit only adds extra consistency checks (assertions) inside an existing fuzz test for Bitcoin Core's network connection manager. It does not change production code, network behavior, or wallet logic. There is no user-facing bug fix …

c507fb30by Bruno Garcia+14−51 file
No security note in commit
Informational 15 AI analysisMessage 75 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: connman: add AddNode/RemoveAddedNode invariants

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. It adds checks that verify how Bitcoin Core's connection manager handles manually added nodes. There is no change to p…

4a6fce43by Bruno Garcia+20−51 file
No security note in commit
Informational 23 AI analysisMessage 67 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: announce field must be 0 or 1 in sendcmpct

This commit adds a new test to Bitcoin Core's functional test suite. The test verifies that if a peer sends a 'sendcmpct' message with an invalid 'announce' value (anything other than 0 or 1), the node logs an error and disconnects that pe…

Tests protocol-mandated rejection of malformed P2P message fieldVerifies peer disconnection on invalid boolean-like field valueReferences BIP152 specification requirement
abc33ff0by brunoerg+13−01 file
No security note in commit
Low 47 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

net_processing: fix BIP152 first integer interpretation

This change tightens how Bitcoin Core handles a compact-blocks handshake message. The old code read a small number from the network and treated any non-zero value as 'true'; the new code rejects values other than 0 or 1. This prevents a pe…

Protocol field validation gap closedBIP152 specification non-compliance in deserializerPotential state inconsistency between bool interpretation and explicit 0/1 expectation
2d0dce0aby brunoerg+8−11 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: descriptor: bare multisig at TOP level with 3 pubkeys is allowed

This is a tiny test-only change. It adds one new test case verifying that a specific Bitcoin descriptor pattern—bare multisig with exactly 3 public keys at the top level—is accepted by the descriptor parser. No production code was changed,…

55a4c946by brunoerg+1−01 file
No security note in commit
Informational 12 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: connman: add network activity invariants

This commit only changes a fuzz test file. A fuzz test is an automated testing harness that throws random inputs at code to find bugs. The change adds an assertion that after setting network activity on or off, reading the value back match…

4b84c912by Bruno Garcia+3−21 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: connman: set m_local_services/m_use_addrman_outgoing/m_max_automatic_connections

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. The change adds three new random settings to the test and adds two assertions to verify those settings are stored corr…

a5859edeby Bruno Garcia+9−21 file
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: remove redundant CScript method calls from script harness

This commit is a minor cleanup of Bitcoin Core's fuzz testing code. It removes duplicate calls to CScript methods from one fuzz harness and adds one missing method call to another harness. There is no change to production code, consensus l…

c9d85822by Bruno Garcia+1−72 files
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: remove GetDescriptorChecksum from string harness

This commit removes one line from a fuzz test file. Fuzz tests are automated tools that feed random inputs to functions to find crashes or bugs. The change simply stops calling the GetDescriptorChecksum function in this particular test, be…

91cd0e3aby Bruno Garcia+0−11 file
No security note in commit
Informational 18 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: script: boundary at exactly 65535 bytes must use OP_PUSHDATA2

This commit only adds a new test case to Bitcoin Core's test suite. It verifies that a 65535-byte data push in Bitcoin scripts is considered 'minimal' only when encoded with OP_PUSHDATA2, not OP_PUSHDATA4. The commit does not change any pr…

Script minimal-push rule boundary testNo production code changeConsensus-adjacent encoding rule
f8996746by Bruno Garcia+8−01 file
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: set whitelist permissions on connman target

This commit adds fuzz-testing coverage for whitelist permission settings inside a test harness. It does not change production network code, user-facing behavior, or fix a live vulnerability. It is a test-quality improvement that helps auto…

Touches permission/whitelist code, but only in a fuzz targetAdds new fuzz input surface for CConnman initializationNo bounds, validation, or logic changes in production code
32debfa1by Bruno Garcia+12−01 file
No security note in commit
Informational 14 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: wallet: add target for `MigrateToDescriptor`

This commit adds a new automated fuzz test for Bitcoin Core's wallet migration feature. It does not change production wallet code; it only adds test code that feeds random inputs to the existing migration function to help find bugs. There …

No production code modifiedNo bug fix or vulnerability patch presentAdds fuzz coverage for wallet descriptor migration
779e7825by brunoerg+144−11 file
No security note in commit
Informational 12 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: addrman: successive failures in the last week for IsTerrible

This commit only adds a new unit test for Bitcoin Core's address manager. It checks that an address with many recent connection failures is correctly marked as 'terrible' and filtered out when peers are returned, while still remaining in t…

6202acd2by brunoerg+36−01 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: addrman: move consts to .h

This commit simply moves a set of fixed numeric constants (such as how many buckets addresses are spread across, retry limits, and time windows) from the implementation file to the header file. It does not change any values, logic, or beha…

f611d3bdby brunoerg+21−202 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: addrman: test self-announcement time penalty handling

This commit only adds a new test to Bitcoin Core. It verifies that when a Bitcoin node announces its own network address, it does not receive a time penalty, but addresses announced by other nodes do receive a time penalty. There is no cod…

e7703920by Bruno Garcia+40−01 file
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →