Bitcoin Core

This commit only adds a new automated test to Bitcoin Core. It checks that when a user tries to migrate an old wallet on a pruned node, and the wallet's last known block has already been pruned (deleted) from the local copy of the blockchain, the migration fails with a clear error message instead of doing something unsafe. There is no change to production wallet or node code.

This commit only improves user-facing log messages during Bitcoin Core's wallet migration process. It adds a message saying the new wallets are being loaded after migration, and another message if a wallet fails to load and the migration must be rolled back. There is no security fix or behavior change beyond clearer logging.

This commit only adds a new automated test to Bitcoin Core. It does not change any production wallet code. The test checks that if migrating the default (unnamed) wallet fails, the main wallets directory is not deleted, a backup file is created, and the original wallet is restored. It is a regression test for a previously fixed bug, not a security fix itself.

This commit fixes a bug in Bitcoin Core's wallet migration feature. When a user tried to migrate an old-style unnamed wallet and the migration failed, the cleanup code accidentally deleted the entire /wallets/ directory, wiping out all wallets and the backup file. The fix changes the cleanup to only remove specific database files created during migration, and only remove newly created empty directories. It also adjusts wallet restore to allow restoring into an existing directory as long as no database file would be overwritten.

This commit only adds new automated tests for the wallet restore feature in Bitcoin Core. It does not change any production wallet code. The tests verify that restoring a wallet backup behaves correctly in edge cases: restoring into an empty directory, a directory with unrelated files, a directory that already contains a wallet database file, the default unnamed wallet file, and a pruned node where the backup is too old. Because no actual wallet logic is modified, this commit does not introduce or fix a live security issue on its own.

This change fixes a cleanup bug in Bitcoin Core's wallet restore feature. Previously, if restoring a wallet failed part-way through, the code would delete the entire wallet directory using a broad 'remove everything' command. The patch makes the function remember exactly which files and folders it created, and only delete those specific items on failure. Right now this doesn't cause data loss, but it is needed to safely support a follow-up change where restore may reuse an existing directory that could contain other important files.

This is a test-only cleanup. It fixes a fake test helper so it no longer returns already-spent coins, matching how the real Bitcoin Core coin database works. It does not change production code, so it cannot directly affect live Bitcoin nodes or user funds.

This is a change to a Bitcoin Core fuzz test, not to the live Bitcoin network code. It fixes a test-only simulator so that it no longer pretends that spent coins still exist in the underlying database. This makes the fuzz test behave more like the real code, but it does not fix a vulnerability in production Bitcoin Core.

This change adds a safety check inside Bitcoin Core's database lookup for coins (unspent transaction outputs). It ensures that if the database somehow returns a spent coin, the program will stop immediately rather than continue with bad data. It is a defensive hardening patch, not a fix for a known active attack.

This commit only changes which Linux distribution version Bitcoin Core's automated testing system uses for a handful of test jobs. It switches from Ubuntu 24.04 to Debian Trixie so the tests can run with a newer compiler (GCC 14). There is no change to the Bitcoin software itself, no user-facing change, and no security fix or vulnerability.

This commit applies a patch to the GCC compiler used by Bitcoin Core's Guix build system. The patch fixes a compiler bug where the order of internal numbering could differ depending on the build machine's processor architecture (x86_64 vs aarch64). This caused the same source code to produce slightly different binary outputs when cross-compiled on different host machines. The fix ensures the numbering happens in a fixed, predictable order, restoring 'deterministic builds'—the property that the same source always produces the exact same binary. This is not a vulnerability in Bitcoin Core itself and does not create a way to attack users directly.

This commit hardens the Bitcoin Core Guix build by compiling GCC itself with a security flag called --enable-host-bind-now. That flag tells the linker to mark the resulting GCC programs so they resolve all dynamic-library addresses immediately at load time, rather than lazily when first used. This is a defensive hardening measure that makes certain memory-corruption attacks harder, but it is not a fix for a known exploitable bug in Bitcoin Core.

This commit changes the build recipe used by Guix (a reproducible-build system) to compile GCC with gprofng disabled. gprofng is a newer profiling tool bundled with some GCC versions. The change is a hardening/packaging tweak: it removes an unneeded component from the compiler used to build Bitcoin Core releases, reducing the attack surface and build-time dependencies. There is no direct evidence in the commit or supplied references that this fixes a known exploitable vulnerability.

This commit updates the Bitcoin Core build system to use a newer version of the GCC compiler (14.3.0 instead of 13.3.0) for its reproducible Guix builds. There is no security-relevant code change here; it is a routine toolchain version bump.

This commit changes the build setup for Bitcoin Core's Guix deterministic build environment so that GCC no longer builds the libgomp library. libgomp is the GNU Offloading and Multi Processing Runtime Library, used for OpenMP parallel programming. Removing it reduces the attack surface and build artifacts, but there is no direct evidence in the commit that a specific vulnerability is being fixed.

This commit changes Bitcoin Core's Guix build recipe to stop GCC from building the libquadmath library. Quadmath provides extra-precision floating-point math, which Bitcoin Core does not need. Removing it shrinks the build environment and reduces the chance that unnecessary code accidentally gets linked into release binaries. There is no direct evidence in the commit that this fixes an active security bug.

This commit simply removes a single line of information—the 'Starting Block' field—from the peer details window in Bitcoin Core's graphical user interface. It is a cleanup following an earlier deprecation and does not change any network, consensus, or wallet behavior. There is no security issue here.

This commit only renames the word 'command' to 'message type' in comments and a debug log string. It is a documentation cleanup with no functional code changes and no security impact.

This commit simply deletes an unused internal function called FixLinearization and its associated test. There is no security relevance: no bug is fixed, no behavior changes, and no live code path is altered.

This commit is an internal optimization to how Bitcoin Core organizes and prioritizes groups of related transactions (clusters) in its memory pool. It introduces new quality states that let the node defer fixing non-topological orderings until later, instead of doing the work immediately. There is no indication in the commit or title that this fixes a security bug; it is described as an optimization.

This is a routine internal optimization in Bitcoin Core's transaction graph code. It removes two calls to a helper named PostLinearize and updates comments, replacing an explicit cleanup step with work done by a newer algorithm (SFL). There is no indication this fixes or introduces a security bug.

This is a routine internal refactor of Bitcoin Core's transaction-cluster linearization code. It lets the linearization algorithm accept an existing ordering that may not follow dependency rules, and automatically fix it. There is no indication this change addresses a security bug or is exploitable.

This is a Bitcoin Core code cleanup that removes a special internal quality state called NEEDS_SPLIT_ACCEPTABLE from the transaction graph (txgraph) module. The change simplifies how clusters of related transactions are tracked after transactions are removed or fees change. It does not appear to be a security fix; it is described by the author as a simplification enabled by an upcoming algorithm improvement. There is no disclosed security relevance and no independent researcher credited.

This commit simply moves existing Python linting code from one file to another without changing what it does. It is a code cleanup change with no security relevance.

This commit is a simple housekeeping change: it moves two existing code-checking helper functions into a new file and runs a code formatter on another file. There is no change to Bitcoin's actual behavior, no bug fix, and no security relevance.