Bitcoin Core

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 differently or become less reproducible, and disabling it is a conservative build-hardening/reliability choice. There is no direct evidence in the commit that this fixes an active security vulnerability.

This commit is a cosmetic/style update to the Guix build manifest used to compile Bitcoin Core. It replaces older Scheme quoting syntax with newer 'gexp' syntax but does not change which compiler flags are actually used. There is no security-relevant change here.

This is a fix to a Bitcoin Core fuzz test (an automated testing harness), not to the main wallet code that real users run. The test was inserting fake wallet transactions in a way that skipped updating an internal index called m_txos. Because newer coin-selection code reads from that index, the fuzz test could no longer actually exercise coin selection, making the test less useful. The patch calls a refresh function after each insertion so the test's fake wallet state is consistent. There is no indication this affects live wallets, consensus, or network security.

This commit is a purely cosmetic change in Bitcoin Core's Guix build scripts. It replaces the short shell command 'set -e' with its long-form equivalent 'set -o errexit'. Both forms do exactly the same thing: they make the script exit immediately if any command fails. There is no security issue and no functional change.

This commit only adds or updates copyright and license header comments at the top of several helper scripts used for Bitcoin Core's Guix build process. It does not change any executable code, logic, or behavior. There is no security risk.

This commit removes one DNS seed server (seed.testnet.bitcoin.sprovoost.nl) from the list used by Bitcoin Core's testnet3 network. DNS seeds help new nodes find peers when they first join the network. The change is a routine operational update by the seed operator and does not fix or introduce any security vulnerability.

This commit only updates outdated web links in documentation and code comments. It does not change any program logic, network behavior, or security checks. There is no security issue here.

This commit updates the secp256k1 cryptographic library inside Bitcoin Core to a newer version. The main change is adding support for a new optional feature called 'Silent Payments' (BIP352), which is a privacy-enhancing way to receive Bitcoin payments. The update also includes several smaller fixes and documentation updates, such as correcting a technical limit in a field-element comparison function, adding a safety check that x-only public keys must have even Y coordinates, and terminating a nonce-generation loop at a fixed maximum iteration count. There is no direct evidence in the commit message or diff that this is an emergency security patch for an active vulnerability; it reads as a routine feature and maintenance subtree update.

This commit is a pure code cleanup: it moves two internal helper functions (FetchCoin and ReallocateCache) into the existing private section of a C++ class. There are no functional changes, no bug fixes, and no security implications.

This commit changes how Bitcoin Core's official macOS builds are produced, switching the build tools from the GNU compiler collection (GCC) to the LLVM/Clang toolchain. It does not change the Bitcoin software itself, only the compiler and linker scripts used to create macOS release binaries. There is no direct security bug visible in the diff, but any toolchain change can affect build reproducibility and the final binary layout.

This is a small internal code cleanup in Bitcoin Core's inter-process communication (IPC) code. It replaces direct references to a global thread-local variable with a helper function so the code works around a compiler bug in Windows MinGW builds. There is no indication this fixes a security vulnerability or changes behavior on supported platforms.

This commit only changes a comment in a build script, correcting the noted version of a software library from 2.39 to 2.41. No actual code behavior is changed, so it has no security effect.

This commit is a routine cleanup that changes the locale setting in Bitcoin Core's Guix build scripts from the old ASCII-only 'C' locale to the modern 'C.UTF-8' locale. It is not a security fix and does not change any behavior that could be exploited. The stated purpose is to reduce harmless warning messages from Qt tools during builds.

This commit adds a single line to a test-only sanitizer suppression file. It tells the UndefinedBehaviorSanitizer (UBSan) to ignore a specific unsigned integer truncation warning inside a hash function used by Bitcoin Core's coin cache. This is not a code fix and does not change runtime behavior in production builds. It merely reduces noise during automated testing with sanitizers.

This is a small code cleanup in Bitcoin Core's address manager. It changes how one internal data structure compares equality so it works correctly when used with const references, and removes an unused header include. There is no security bug being fixed and no exploit possible.

This change only affects Bitcoin Core's own Qt graphical-interface test suite on macOS. It forces the tests to use Qt's 'Fusion' style instead of the native Mac style, because the native Mac style can crash when running in the minimal test environment. It is a test-only hardening fix, not a change to the live Bitcoin wallet or network code that ordinary users run.

This commit only reformats a single Qt test file using clang-format. It moves preprocessor directives (#if, #else, #endif) to the start of lines and adjusts indentation. No code logic, behavior, or functionality was changed.

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.