Bitcoin Core

This is a routine code cleanup: a function called RemoveStaged had an extra parameter (updateDescendants) that was no longer used, so it was removed from the function definition and every place that called it. There is no security-relevant change here.

This is a small CMake build-system change. It makes the optional test suite for an experimental library (BUILD_KERNEL_TEST) automatically disabled when the library itself (BUILD_KERNEL_LIB) is not being built. Previously, the test option could be left on independently, which could cause a build configuration error. There is no runtime security issue here.

This commit changes Bitcoin Core's Windows build configuration so that the optional ZeroMQ notification feature is enabled by default in the Windows CMake presets. It also updates CI and documentation to match. There is no security-relevant code change here; it is purely a build-system consistency fix to align Windows builds with the existing default in the dependency manifest.

This is a documentation-only change that adds a new Windows cross-compilation target to the build instructions. It does not modify any executable code, build scripts, or configuration logic. There is no security relevance.

This is a minor cleanup to Bitcoin Core's continuous integration (CI) configuration. It removes one redundant line that explicitly set compiler names for a Windows cross-compilation job, because the build system already figures out those names automatically. There is no security relevance.

This commit only renames a GitHub Actions CI job and adds a comment to make clear that the workflow tests a maximum of 6 ancestor commits. There is no code, build, or runtime change, and no security issue is introduced or fixed.

This commit only changes the error message/name returned when a tapscript transaction provides an empty public key. The actual consensus rule—rejecting empty public keys in tapscript—already existed. The change makes debugging and testing clearer by giving this failure its own distinct error code instead of reusing a more general one. It does not alter what transactions are accepted or rejected by the network.

This commit tightens a build-time check used in Bitcoin Core's reproducible Guix build process. It removes several common system symbols (like 'environ' and '_environ') from a list of exports that the build script is allowed to ignore. The change itself does not fix a vulnerability in running Bitcoin Core software; it is a hardening of the release-build verification tooling to catch accidental symbol exports earlier. There is no claim in the commit that this resolves a security bug.

This commit only adds documentation comments to a build script. It lists which versions of two graphics-related system libraries (libfontconfig and libfreetype) are expected on Ubuntu 22.04 for the Bitcoin Qt wallet application. No code behavior was changed, so there is no security issue in this patch itself.

This commit updates the FreeType font-rendering library used in Bitcoin Core's build dependencies from version 2.11.0 to 2.11.1. It changes the download URL, archive format, and verification hash, and adjusts a small build patch. FreeType is a widely used library for drawing text, and newer point releases often include bug fixes. The commit itself does not say whether this fixes a security issue, and no security references were provided.

This commit is a straightforward logging cleanup. It changes many messages from the generic LogPrintf to a new LogWarning helper, which is designed for severe-but-non-fatal problems. The wording of the messages is mostly unchanged, and no program logic, permissions, or security behavior is modified. It is not a security fix.

This commit only changes which logging function is used for error and fatal-condition messages across Bitcoin Core. It replaces generic LogPrintf calls with LogError (and one LogInfo) so that serious problems are more clearly marked in logs. There is no change to program logic, no bug fix, and no security vulnerability being patched.

A small change to a helper Python script used for building network maps. The script now refuses to write raw binary output directly to a terminal window, because doing so can garble the screen and, in rare cases, cause a terminal to misinterpret control characters. This is a hardening improvement rather than a fix for an active attack.

This commit is a minor test-code cleanup. It moves four named constants related to BIP68 sequence locktime rules from one test file into the shared test framework library. No production code, consensus rules, or security behavior is changed.

This commit fixes a single-word typo in a log message. The phrase 'on non-prune mode' was corrected to 'in non-prune mode'. It has no effect on program behavior, security, or user data.

This is a small internal cleanup in how Bitcoin Core wallets report balances for reused addresses. It does not fix a vulnerability or change user-facing totals; it just computes the 'used' balance in one pass instead of calling the balance function twice and subtracting. There is no security issue visible in the change.

This commit fixes a memory-handling bug that occurs when Bitcoin Core shuts down its network connections. A list of pending reconnections held references to a memory resource (semaphore) that was freed during shutdown. When the program later destroyed that list, it could read already-freed memory, which can cause crashes or unpredictable behavior. The fix clears the reconnection list before freeing the underlying resource and adds code annotations to prevent the wrong lock from being held during shutdown.

This commit only changes a test file. It improves an existing test by checking that a warning message ('TestShell is already running!') is actually printed to the screen when a second TestShell is started. There is no change to Bitcoin Core's production code, no security fix, and no vulnerability.

This is a small cleanup change to a helper script used for comparing internet routing maps (asmap files). It only changes how the tool reports summary statistics: it now counts the number of changed entries separately from the number of affected IP addresses, and uses a built-in library function instead of a manual calculation. There is no security relevance.

This Bitcoin Core commit relaxes a mempool policy rule. Previously, only a special transaction type called TRUC could be below the minimum relay fee when submitted as part of a package. Now any transaction version can be below that fee if it is part of a package that overall pays enough fees. The change is described by the developers as safe because of the newer cluster mempool design, but it removes one anti-pinning protection and makes zero-fee parent transactions relayable under certain conditions.

This commit adds a GitHub Actions cleanup step that deletes large pre-installed software folders (like .NET, Android SDK, Node modules) on CentOS CI runners to free disk space. It only affects Bitcoin Core's own continuous integration environment and does not change any Bitcoin node code, wallet logic, or network behavior. There is no security issue in the change itself.

This commit simply renames a helper script from gen-sdk to gen-sdk.py and updates the documentation link. The file contents are identical. It is a routine tooling change with no security relevance.

This commit changes the macOS SDK packaging script for Bitcoin Core so that it produces an uncompressed .tar archive instead of a .tar.gz archive. The reason is that different Linux distributions use different underlying compression libraries, which can produce slightly different compressed files even from identical input. That breaks reproducible builds (determinism), where everyone expects the exact same output. The uncompressed archive is larger (~157 MB) but byte-for-byte identical across machines. There is no security vulnerability being fixed here.

This change trims the macOS software development kit (SDK) archive used to build Bitcoin Core for Mac. Instead of bundling the entire SDK, the script now only includes specific directories needed for compilation. This reduces download size and shrinks the attack surface by leaving out unnecessary files such as Swift modules, module maps, and manpages. It is a hardening and maintainability improvement rather than a fix for a known vulnerability.

This is a one-word change in a test file. A developer fixed a misspelled string ('invald wallet' to 'invalid_wallet_content') used only to create intentionally corrupted wallet data for a test. It has no effect on the actual Bitcoin Core software that users run.