Bitcoin Core

This commit only changes Bitcoin Core's internal fuzz tests—specialized randomized test programs used during development to catch bugs. It adds test coverage for a new caching helper called CoinsViewOverlay::StartFetching. There is no change to the actual Bitcoin node software that users run, so this cannot directly affect live Bitcoin networks or user funds.

This is a preparatory code change for future multi-threaded coin fetching in Bitcoin Core. It adds a synchronization flag (std::atomic_flag) around a shared data field so that worker threads can safely signal when they have finished writing a 'coin' object and the main thread can safely read it. The commit itself does not introduce a known exploitable vulnerability; it is a defensive concurrency fix to prevent potential race conditions or memory-visibility bugs in upcoming parallel code.

This commit is a performance optimization for Bitcoin Core's block validation. It pre-fetches the previous transaction outputs (the 'coins' being spent) for all inputs in a block before the main validation work begins, and it does so in parallel using a thread pool. It is not a security fix and does not change consensus rules or network behavior visible to users.

This commit adds a new user-configurable setting called -prevoutfetchthreads that controls how many background worker threads Bitcoin Core uses to fetch previous transaction outputs (prevouts) from the UTXO database while connecting a new block. It is a performance and resource-tuning feature, not a security fix or vulnerability. There is no indication in the commit that it addresses any security issue.

This Bitcoin Core change adds a shared worker thread pool to a new internal caching layer called CoinsViewOverlay. It is not a security fix for users; it is mostly a performance and test-stability improvement. The commit message notes that without reusing a thread pool, fuzz testing could leak memory because threads are created and destroyed faster than the operating system can clean them up. The change also wires a configurable number of 'prevout fetch' threads into normal block validation.

This commit adds a new command-line utility feature to Bitcoin Core. The `bitcoin-util netmagic` command simply prints the network magic bytes (a public identifier for which Bitcoin network is being used, such as mainnet or testnet). It does not change network behavior, wallet handling, or consensus rules, and it introduces no security-relevant code.

This change fixes a subtle bug in how Bitcoin Core reports disk flush errors during block acceptance. Previously, if writing block data to disk failed (for example, because the disk was full during pruning), the error could be misreported to callers as 'this block is invalid.' That could trick other parts of the program or external logic into permanently rejecting a perfectly valid block. Now the disk-flush error is handled separately, and the node still shuts down safely on serious disk problems. The fix is defensive and prevents a non-validation failure from being misclassified as a consensus failure.

This is a tiny test-only fix for parsing network interface output on NetBSD. It changes one regular expression so that Bitcoin Core's functional tests can correctly read IP addresses when NetBSD prints them in CIDR notation (like 127.0.0.1/8). It does not touch any production code, network protocol, wallet, or consensus logic, and it has no security relevance.

This commit only updates the NetBSD build documentation to add the `lsof` utility as a test suite dependency and explains how to force-install it if needed. It is a documentation-only change with no code modifications and no security relevance.

This is a minor test-framework fix for Bitcoin Core's automated QA on NetBSD. It tells the `lsof` network tool to ignore harmless warning messages about device cache files and operating-system version mismatches so those warnings don't break tests. There is no security vulnerability or user-facing change.

This is a small test-only change that lets Bitcoin Core's internal test tools recognize the illumos operating system (reported as 'sunos5') when listing network addresses and interfaces. It does not change the Bitcoin node software itself, does not touch wallet or consensus code, and has no direct security relevance.

This is a small test-only change. A helper function used by Bitcoin Core's automated tests is being updated to no longer claim OpenBSD as a supported platform, because OpenBSD does not include the 'lsof' tool that the function relies on. It does not change the Bitcoin Core software that users run, nor does it fix or introduce a security vulnerability.

This commit simply updates the FreeBSD build documentation to add the `lsof` utility to the list of packages needed to run the test suite. It is a documentation-only change with no code modifications and no security implications.

This is a harmless test-suite maintenance change. It adds a helper that skips certain Bitcoin Core functional tests on non-Linux systems when the 'lsof' tool is missing. It does not change the actual Bitcoin node software, network rules, wallet handling, or any code that processes untrusted data.

This commit only changes a test file. It strengthens an existing test for the Bitcoin Core HTTP server so it can better catch a race condition where the server might stop reading new requests from a connection. The commit itself does not change the actual server code, so it is not a fix—it is a test that checks whether a previously suspected race condition is truly fixed.

This is a test-only change. It updates a single unit test file to run the HTTP request handler on a separate worker thread instead of handling it synchronously. There is no change to production code, no security fix, and no vulnerability.

This commit only adds new unit tests for the Bitcoin Core HTTP server. It creates a fake network socket that sometimes returns a 'try again' error, then verifies the server retries and still sends all replies. No production code is changed, so it cannot introduce a security vulnerability or fix one in running software.

This commit fixes a subtle timing bug in Bitcoin Core's built-in HTTP server. Under a specific race between a worker thread preparing a response and the I/O thread sending data, a connection could get permanently stuck waiting to write even though there was nothing left to send. Once stuck, the server would stop reading new requests from that client, effectively hanging the connection. The fix moves the 'ready to send' flag update under the same lock as the send buffer and protects reads of that flag with a separate lock to avoid deadlocks.

This commit adds an empty placeholder for OpenBSD linker flags in the dependency build system. It is a build configuration change with no functional or security effect visible in the diff.

This commit adds a new automated build test for Bitcoin Core that cross-compiles for OpenBSD. It downloads official OpenBSD system files from the OpenBSD project's own download server and sets up the build environment. There is no change to the Bitcoin Core software itself, no user-facing feature, and no security fix or vulnerability.

This commit is a straightforward internal cleanup in Bitcoin Core's wallet code. It replaces a single mixed-purpose data field called vOrderForm with two clearer fields: one for BIP 21 payment messages and one for BIP 70 payment requests. The change preserves existing wallet data and behavior, and does not appear to fix or introduce a security vulnerability.

This is a routine code cleanup in Bitcoin Core's wallet. It changes how optional 'message' fields from payment URIs are passed through the wallet when committing a transaction, replacing a generic 'order form' container with explicit named parameters. There is no security fix or vulnerability here.

This commit fixes a small cleanup issue in Bitcoin Core's internal fuzz testing code. Fuzz tests are automated tools that feed random data into functions to find bugs; they are not part of the live Bitcoin network software. The change saves the original socket-creating function before replacing it with a fake one, then restores it afterward. This prevents one fuzz test from accidentally leaving its fake socket in place for later tests. There is no indication this affects real users, wallets, nodes, or the live Bitcoin network.

This is a straightforward code cleanup change that renames three internal status labels (INFO, WARN, ERR) to different capitalisation (Info, Warn, Error) because one of those names clashed with a system macro on illumos operating systems when running tests. It does not change program logic, user-facing behaviour, or security properties. It only prevents a possible build failure on an uncommon platform.