Menu

What auditing a Bitcoin 0.1.0 fork in 2026 turned up
📰

What auditing a Bitcoin 0.1.0 fork in 2026 turned up

DEV Community: cpp·Bitflash·3 days ago
#1QNP9qBx
#devtocpp#devto#dev#every#audit
Reading 0:00
15s threshold

Bitflash started from the source of Bitcoin 0.1.0, the 2009 release, ported to a modern toolchain. Two parts were replaced: proof of work is RandomX, and IP addresses are gone, so every node is a Tor onion service. Before release 1.2.33 we audited the whole node and published every finding. Here is what that looked like and what it found.

The tooling

Everything free and open:

Static analysis: CodeQL, cppcheck, clang-tidy, the Clang Static Analyzer, flawfinder and Semgrep.

Fuzzing: 19 harnesses, each run under libFuzzer, AFL++ and honggfuzz with AddressSanitizer and UndefinedBehaviorSanitizer, sharing one corpus per target.

Instrumented self-tests: every self-test under ASan, under ThreadSanitizer and under Valgrind.

Reproducibility: reprotest builds the node twice, varying time, locale, umask and paths, and compares the binaries.

The whole pass is one script, scripts/audit/run-audit.sh , so anyone can rerun it.

Things worth sharing

A checksum hid the P2P layer from the fuzzer.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.