CommitWatch RSS
F
← Developer activityVerified account

fanquake

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

@fanquake on GitHub ↗
244 commits2 monitored projects22 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 fanquakeA visual map of monitored and externally discovered repositories.Fdeveloper243Bitcoin Core1libsecp256k1
Monitored evidence

CommitWatch projects

Bitcoin CoreBitcoin Core243 commits22 candidates0 high risklibsecp256k1Bitcoin Core1 commits0 candidates0 high risk
External discovery

Other public projects

No external sample loaded yet.

Authenticated GitHub discovery can enrich this profile.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35928: doc: mention -DWITH_ZMQ=ON in macOS build guide

This is a one-line documentation update to the macOS build guide. It adds a note telling users to pass a specific CMake option if they want ZeroMQ notification support. There is no code change and no security impact.

8397e09eby merge-script+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35482: fuzz: exercise the transaction-handling path in process_message(s)

This commit only changes Bitcoin Core's internal fuzz testing code. It makes the fuzz tests exercise more of the transaction-handling code path by toggling Initial Block Download mode and resetting the mempool between test runs. There is n…

No production code modifiedNo consensus, validation, net_processing, or wallet logic changedOnly fuzz test harnesses and test utilities affected
f11dc617by merge-script+105−798 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35914: test, fuzz: Remove unused variables

This commit removes unused variables from Bitcoin Core's test and fuzzing code. It is a cleanup/refactoring change with no effect on the live network software or user funds. It does not fix or introduce any security vulnerability.

d36bf709by merge-script+1−138 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35896: refactor: Default uint256::operator==, add operator<=>

This commit is a routine code cleanup in Bitcoin Core. It switches the uint256 equality and comparison operators to use standard C++20 defaults, removes an old custom Compare() helper, and marks an internal assertion-failure function as ne…

ed2c59abby merge-script+99−245 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35842: rpc: Properly make RPCResult::Type::ANY non-test-only

This is a small cleanup and documentation fix for Bitcoin Core's RPC help system. It removes a comment that incorrectly said a certain output type was 'for testing only' and makes the help text properly display those outputs. There is no d…

No memory safety, cryptography, consensus, or authorization changes observedChange is confined to RPC help/schema metadata generationComment-only/type-label change from 'for testing only' to general use
c36ffd87by merge-script+42−364 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35895: refactor: Enable clang-tidy rule to reject anon namespace in header

This is a code cleanup change that turns on a static-analysis rule to prevent a specific C++ coding pattern (anonymous namespaces in header files) and updates two headers to comply. It does not change how Bitcoin Core behaves at runtime an…

No security-relevant code changeNo memory safety, cryptography, consensus, or network changesTooling-only refactor (clang-tidy configuration)
c4fbd3c7by merge-script+9−123 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: move python-minimal to GUI build

This commit is a build-system housekeeping change. It moves the Python package dependency from the non-GUI build manifest to the GUI build manifest in Bitcoin Core's Guix reproducible-build setup. There is no indication this fixes or intro…

b75eb938by fanquake+3−32 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 71 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: remove -Werror=dev

This commit removes a strict compiler/build flag (-Werror=dev) from Bitcoin Core's Guix build scripts. The flag previously turned CMake developer warnings into fatal errors. It was removed because an upcoming change (removing Python from n…

101400b2by fanquake+3−63 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

lint: document CI lief version requirement

This commit only adds a one-line comment to a requirements file used by the continuous integration (CI) linting system, noting that the pinned lief version should match the version used in Guix. It does not change any code, dependency vers…

8221d714by fanquake+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

lint: re-add guix scripts to mypy linting

This commit is a routine linting fix. It re-adds some Guix build helper scripts to the Python type-checker (mypy) configuration and adds two comment-only annotations to suppress false-positive type warnings. There is no change to Bitcoin C…

594a02c3by fanquake+5−53 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: consolidate config flags

This commit is a housekeeping change to Bitcoin Core's Guix build scripts. It only reorders and consolidates CMake configuration flags, and adds a couple of disabled test/build options. There is no change to the actual Bitcoin software cod…

683ae4c5by fanquake+16−146 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 98 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: turn linux/win linker warnings into errors

This commit changes Bitcoin Core's build scripts so that linker warnings are treated as fatal errors during Linux and Windows release builds. It is a hardening of the build process, not a fix for a user-facing security bug. The change make…

Build hardening: linker warnings promoted to errorsExclusion for riscv64-linux-gnu references upstream Boost issueNo runtime, consensus, or cryptographic code changed
b12a70f3by fanquake+8−23 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: consolidate mingw-w64 toolchain setup

This commit is a straightforward cleanup of Bitcoin Core's Windows build scripts. It moves duplicated toolchain setup code into a shared helper function, with no functional changes visible in the diff. There is no indication this affects r…

288f76edby fanquake+35−523 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: consolidate gcc toolchain setup

This commit is a routine cleanup of the Bitcoin Core build scripts used for Guix (a reproducible build system). It moves duplicated GCC toolchain setup code from two separate files into a single shared function in setup.sh, with no functio…

665f11d0by fanquake+35−523 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: consolidate LLVM toolchain setup

This commit is a straightforward cleanup of Bitcoin Core's macOS build scripts. It moves repeated LLVM/clang toolchain setup code from two separate scripts into a single shared function, with no change to the actual commands or build behav…

cc9b0f22by fanquake+20−303 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

build: set CMAKE_VISIBILITY_INLINES_HIDDEN in REDUCE_EXPORTS

This is a build-system hardening change for Bitcoin Core. It tells the compiler to hide inline C++ functions from the list of symbols exported by shared libraries and executables. This reduces the attack surface by making fewer internal fu…

Defense-in-depth symbol visibility reductionBuild hardening, not a runtime vulnerability fixNo functional code change
3f313a77by fanquake+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: disable-nls in *-base-gcc

This commit changes the Bitcoin Core build setup for Guix (a reproducible build system) by adding '--disable-nls' when compiling the base GCC compiler used in the build process. NLS stands for Native Language Support, which provides transl…

Build toolchain hardeningReduction of locale-dependent build variabilityNo explicit vulnerability or exploit described
e0b8fbdeby fanquake+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: mirror some arguments from linux-gcc to mingw-w64-gcc

This commit adjusts the build settings used to compile the Windows version of Bitcoin Core's toolchain. It copies some hardening and cleanup options from the Linux build configuration to the Windows (MinGW) build configuration, and reorder…

Adds stack-smashing protection default (--enable-default-ssp=yes) to Windows toolchainAdds host bind-now hardening (--enable-host-bind-now=yes) to Windows toolchainDisables unused/extra runtime components (gcov, libgomp, lto, nls, libsanitizer, gprofng) in Windows toolchain
9c258963by fanquake+7−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: pass --disable-tm-clone-registry to base GCC

This commit changes how Bitcoin Core's reproducible build system compiles its own copy of the GCC compiler. It adds a flag that removes unused support for 'transactional memory' from a low-level compiler helper library. This is a build-har…

Build toolchain hardeningReduction of unused libgcc surface areaNo runtime code change in Bitcoin Core
baa5a2ceby fanquake+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: disable-lto in *-base-gcc

This commit changes the build setup for Bitcoin Core's Guix reproducible-build toolchain so that the base GCC compilers used to build release binaries are compiled without Link-Time Optimization (LTO). LTO can sometimes make builds behave …

Build toolchain hardeningReproducibility improvementLTO disabled in base GCC packages
7dc87f8eby fanquake+2−01 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 →