G
← Developer activityStrong match

glozow

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

25 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 glozowA visual map of monitored and externally discovered repositories.Gdeveloper25Bitcoin 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 15 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[doc] coin selection filters by max cluster count, not descendant

This commit only renames variables and updates comments in Bitcoin Core's coin selection code. It changes names like 'descendants' to 'cluster_count' to make the code match what it actually does, with no change in behavior. There is no sec…

a067ca34by glozow+48−417 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[refactor] rename variable to clarify it is unused and cluster count

This commit is a simple code cleanup: it renames a local variable from 'descendant_count' to 'unused_cluster_count' in two wallet files to make clear that the value is not actually used. There is no functional change, no bug fix, and no se…

f7be5fb8by glozow+4−42 files
No security note in commit
Informational 18 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

remove glozow from trusted keys

This commit updates Bitcoin Core's commit-verification trust list. It removes one developer's PGP key from the trusted-keys file and changes the trusted-git-root hash. On its own, this is an administrative access-control change, not a code…

Trusted key removed from verify-commits trust listTrusted git root hash changedCommit message references a specific individual's removal from trusted keys
f2b8acc0by glozow+1−22 files
No security note in commit
Low 42 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[miniminer] stop assuming ancestor fees >= self fees

This commit fixes an internal consistency check in Bitcoin Core's mini-miner, a testing and block-template simulation tool. Previously, the code assumed that a transaction's total fees including ancestors were always at least as large as t…

Assertion assumption invalidated by negative-fee transaction featurePotential debug-build crash or incorrect accounting in mini-miner simulationNo direct consensus or network protocol change
2cade5d5by glozow+3−51 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[test] rework/delete feature_rbf tests requiring large clusters

This commit only changes Bitcoin Core's functional test suite. It reworks and deletes some Replace-By-Fee (RBF) tests that previously needed very large transaction clusters. The production mempool rules are not modified, and no security vu…

edb3e7cdby glozow+7−241 file
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[doc] correct topology requirements in submitpackage helptext

This commit only updates the help text for the submitpackage RPC command. It corrects the documentation to match the actual rules for what transactions can be submitted together. No code behavior changed, and there is no security issue.

3d222825by glozow+3−21 file
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[test] wallet send 3 generation TRUC

This commit only adds a new functional test to Bitcoin Core. It checks that the wallet correctly refuses to spend an unconfirmed TRUC (version 3) transaction output when that output already has an unconfirmed parent—in other words, it prev…

dcd42d6dby glozow+45−01 file
No security note in commit
Low 43 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[wallet] never try to spend from unconfirmed TRUC that already has ancestors

This Bitcoin Core wallet patch prevents users from accidentally creating invalid or poorly structured transactions. Specifically, it stops the wallet from spending coins that come from an unconfirmed 'TRUC' (version 3) transaction which al…

Denial-of-service / fund-locking risk: creating a transaction that violates TRUC topology rules would be rejected by the mempool, potentially leaving user funds stuck or dependent on a parent that may never confirm.Protocol-rule violation: TRUC transactions have stricter ancestor/descendant limits than standard transactions; the wallet was not enforcing them for coin selection.Defensive correctness fix in coin-selection logic.
e753fadfby glozow+5−01 file
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[doc] archive v29.1 release notes

This commit simply adds a documentation file: the archived release notes for Bitcoin Core version 29.1. It contains no code changes, no configuration changes, and no executable modifications. It is purely informational text describing what…

61ec8866by glozow+229−01 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc fixups for 33106

This commit only updates documentation and code comments to match a previously merged change (PR 33106). It does not modify any executable network, consensus, wallet, or mempool code, so it has no security impact on its own.

daa40a3fby glozow+4−43 files
No security note in commit
Informational 14 AI analysisMessage 90 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test fixup for incremental feerate

This is a test-only change in Bitcoin Core. It clarifies comments and strengthens a functional test for Replace-By-Fee (RBF) behavior when the incremental relay feerate is set to zero. No production code, consensus rules, or network behavi…

c568511eby glozow+14−111 file
No security note in commit
Informational 15 AI analysisMessage 0 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test fixups

This commit only changes Bitcoin Core's internal functional test scripts. It fixes log-message formatting, adjusts test thresholds and comments to match current fee-relay behavior, and adds one extra test case for a v3 transaction package.…

636fa219by glozow+14−95 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[rpc] expose blockmintxfee via getmininginfo

This commit simply adds a new read-only field called 'blockmintxfee' to the output of the getmininginfo RPC command. It exposes an existing configuration setting through the API so users can query it remotely. There is no security issue he…

9169a50dby glozow+5−02 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[doc] release note for min feerate changes

This commit only adds a release note document explaining upcoming changes to default Bitcoin transaction fee rates. It contains no code changes and no security fix or vulnerability.

18720bc5by glozow+17−01 file
No security note in commit
Low 41 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[policy] lower default minrelaytxfee and incrementalrelayfee to 100sat/kvB

This commit lowers Bitcoin Core's default minimum relay fee and replacement fee from 1000 satoshis per kilovbyte to 100 satoshis per kilovbyte. The stated goal is to make it cheaper for legitimate transactions to propagate while still keep…

Default fee policy constants changed by 10xCommit message describes attacker bandwidth-exhaustion threat modelAffects mempool admission and RBF anti-DoS fee requirements
6da5de58by glozow+49−4712 files
Vendor flagged security relevance
Informational 16 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[prep/util] help MockMempoolMinFee handle more precise feerates

This is a small test-only change in Bitcoin Core. It adjusts a mock mempool helper used in automated tests so that fee calculations line up more precisely when non-integer fee rates are used. The change only affects test code and does not …

No security signal: change is confined to test utilitiesNo consensus, networking, wallet, or mempool policy code modifiedChange addresses unit-test precision/rounding, not a vulnerability
457cfb61by glozow+4−01 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[prep/test] replace magic number 1000 with respective feerate vars

This commit only changes test code. It replaces hard-coded fee rate numbers like 1000 with named constants and removes duplicated hard-coded values in test assertions. There is no change to the actual Bitcoin Core node behavior, so it cann…

3eab8b72by glozow+17−233 files
No security note in commit
Informational 21 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

[miner] lower default -blockmintxfee to 1sat/kvB

This change lowers the default minimum fee a Bitcoin miner requires to include a transaction in a block from 1000 satoshis per kilovbyte to 1 satoshi per kilovbyte. The intent is to let miners include any transaction already accepted by th…

Default mining policy parameter changedNo consensus or validation logic modifiedMempool admission policy (minrelaytxfee) remains the gatekeeper
5f2df0efby glozow+7−33 files
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →