Bitcoin Core

This commit adds a patch to Bitcoin Core's build system that fixes a missing C++ header include in the ZeroMQ library. The missing include can cause compilation to fail on some systems because the compiler cannot find 'std::nothrow'. It is a build-compatibility fix, not a security vulnerability fix, and it does not change how Bitcoin Core handles transactions, wallets, or network data.

This is a harmless CI (continuous integration) configuration change for Bitcoin Core. It adds a space and a non-ASCII character to a build directory path used only in automated testing, so the test environment exercises how the code handles unusual directory names. There is no security issue here.

This commit fixes a Windows installer build script so that directory paths containing spaces are properly quoted. It is a build-system reliability fix, not a security vulnerability. There is no indication it can be exploited to attack users or the software.

This commit is a purely cosmetic code cleanup. It changes the number 100000 to 100'000 in a fuzz-testing helper, using a C++ digit separator to make the value easier to read. It does not alter program behavior, logic, or security.

This change makes Bitcoin Core assume that hard-coded and DNS seed nodes support the newer BIP324 encrypted transport (v2) when first connecting. If the guess is wrong, the software falls back to the older v1 protocol automatically. It is a network-hardening/performance tweak, not a fix for an exploitable vulnerability.

This commit fixes a fuzz-testing-only issue. When Bitcoin Core runs under AFL (a fuzzing tool), it forks the process after setup. Previously, worker threads created during initialization could become 'dangling' after the fork, causing crashes or unreliable fuzz results. The fix disables those extra threads during fuzzing, making tests more stable and deterministic. This does not affect normal Bitcoin node operation or end-user wallets.

This is a tiny build-script cleanup. It replaces a hardcoded Windows build target string with a variable that already holds the same value. There is no security issue visible in the change itself.

This commit removes workarounds that skipped three Bitcoin Core Qt test suites on macOS when using the 'minimal' Qt platform plugin. The previous commit fixed the underlying crash cause, so these tests can now run. It is a test-infrastructure cleanup, not a security patch for end-user software.

This commit fixes a macOS-specific behavior in Bitcoin Core's Qt interface. Previously, two pieces of code called [NSApplication sharedApplication], which has the side effect of creating the macOS application object if it didn't already exist. When running Bitcoin Core's GUI in headless/minimal test modes on macOS, this unintended creation could cause subtle state problems. The fix uses the NSApp global instead and skips the calls if no application object exists. It is a defensive bug fix rather than a clear-cut security vulnerability.

This is a build-system cleanup for the Bitcoin Core graphical wallet. It silences new compiler warnings that appear with GCC 16.x by changing how Qt's meta-object compiler output is included, and it hides some wallet-only user-interface fields when the wallet is disabled at compile time. There is no security bug being fixed and no behavior change for end users.

This commit reorganizes how Bitcoin Core's official macOS and Windows release binaries are built using the Guix reproducible-build system. It splits one big build script into smaller, platform-specific scripts for non-GUI and GUI parts. There is no indication this fixes a security vulnerability; it is a build-system refactoring.

This commit reorganizes how Bitcoin Core's official release builds are produced using the Guix build system. It splits Linux builds into two separate steps—one for command-line/daemon programs and one for the graphical wallet interface—and moves some build tools into a separate manifest file. There is no indication this fixes a security vulnerability or introduces a security-relevant bug; it is a build-system refactoring.

This commit fixes a crash bug in Bitcoin Core's chainstate manager. When deleting a temporary chainstate used for AssumeUTXO loading, the code assumed every chainstate had a memory pool (mempool) attached. In the 'kernel' library mode, a ChainstateManager can be created without a mempool, so deleting a chainstate dereferenced a null pointer and crashed. The fix simply checks whether the mempool exists before checking its size, and adds a test for this lifecycle.

This commit is a build-system refactor for creating the Windows installer. It moves the NSIS installer generation logic into a separate, reusable CMake script and changes the template to use configurable directories instead of hardcoded build-tree paths. There is no indication this changes what gets installed, how user data is handled, or any runtime behavior of Bitcoin Core itself.

This is a small internal cleanup in Bitcoin Core's coin-cache code. It makes a temporary set of transaction IDs use the same hash function as the main coins cache, instead of a separate one. The change is described by the authors as a performance/consistency improvement, not a security fix. There is no evidence in the commit that it repairs an exploitable vulnerability.

This commit changes the hash function used inside Bitcoin Core's in-memory coin cache (the UTXO cache) from SipHash-2-4 to a faster SipHash-1-3 variant. The change is framed as a performance optimization. The commit message and code comments explicitly argue that the weaker hash is still safe here because the keys are real transaction IDs, attackers cannot inject arbitrary long-lived keys into this cache, and the hash values are never saved to disk or shared between processes. There is no direct evidence in the commit of an exploitable vulnerability, but it is a deliberate relaxation of a cryptographic primitive in a security-sensitive data structure, which warrants scrutiny.

This is a code cleanup (refactor) that moves the internal SipHash mixing steps into shared helper methods. It does not change how Bitcoin hashes data, how many rounds are run, or any user-visible behavior. There is no security bug being fixed here.

This commit adds a new, weaker variant of the SipHash algorithm inside Bitcoin Core's cryptography module. It is explicitly designed for low-security uses such as internal hash tables, not for protecting funds or network messages. The code itself appears to be a clean, intentional addition with extensive comments explaining the trade-offs. There is no indication in the commit that this fixes a vulnerability or introduces an exploitable bug.

This commit only adds new test cases and fuzzing coverage for an existing SipHash variant called SipHash-1-3-UJ. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The change makes the software's test suite more thorough by verifying that the existing hash implementation produces expected outputs.

This commit only adds new performance benchmark tests for a hash function called SipHash. It does not change any production code that handles Bitcoin transactions, networking, or wallet data. There is no security issue here.

This commit adds two new shortcut methods for computing a specific SipHash variant on fixed-size inputs. It is a pure performance/ergonomics addition: the new methods copy the hasher's internal state before operating, so they do not alter the original object. There is no indication of a security bug or fix.

This commit only adds new test data and test code for the SipHash hashing function used in Bitcoin Core. It does not change any production code that handles transactions, networking, or wallets. The goal is to make sure the existing SipHash implementation behaves correctly and stays correct during future cleanups.

This is a compiler-specific workaround, not a fix for a security vulnerability in Bitcoin Core itself. The change swaps a low-level memory comparison for a C++ standard-library comparison in a 256-bit integer class, solely to silence a false-positive warning produced by GCC 14. There is no indication it changes runtime behavior or fixes an exploitable bug.

This commit is a minor code cleanup in a test-only header file. It moves helper functions from an anonymous namespace into a named namespace and removes some compiler-hint annotations. There is no change to how Bitcoin Core validates transactions, handles money, or protects user data.

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 limit, the result is correctly marked as 'incomplete' (the algorithm did not fully finish exploring all possibilities). There is no code change to the actual wallet behavior—only a new test.