Bitcoin Core

This commit is a small internal cleanup in how Bitcoin Core notifies other parts of the program when a block is disconnected from the chain. It changes the notification so that ownership of the block data is transferred into the background scheduler thread, making the existing behavior more explicit. There is no indication this fixes a security vulnerability or introduces a new attack.

This commit is a small internal cleanup in how Bitcoin Core hands off newly connected blocks to background notification threads. It moves a block's shared ownership explicitly onto the scheduler thread so the heavy validation thread is not delayed by memory cleanup. There is no user-facing bug fix or security vulnerability being patched; it is a performance and clarity improvement.

This commit is a code cleanup in Bitcoin Core's validation notification system. It reduces unnecessary copying of data when block and transaction events are passed between internal components, and it changes how debug log messages are formatted. There is no direct security vulnerability being fixed here; it is preparation for later commits that clarify object ownership.

This is a routine build-system cleanup. The developers renamed how their CMake scripts refer to the SQLite database library so they use the current, non-deprecated target name. It does not change Bitcoin Core's behavior, fix a bug, or alter how wallets store data. There is no security relevance in the commit itself.

This commit only changes Bitcoin Core's continuous-integration (CI) test setup. It switches the compiler used during Valgrind memory-checking jobs from GCC to Clang, because a known bug in Valgrind makes it report false problems on GCC-optimized executables that use std::optional. No user-facing code, consensus rules, wallet, networking, or node behavior is changed. There is no security vulnerability being fixed or introduced here.

This is a documentation-only change to a continuous integration script. A developer replaced a vague 'TODO enable GUI' comment with a clearer explanation that the GUI is disabled in the valgrind CI task because it only passes with a special debug build. No code behavior changed, and there is no security fix or vulnerability here.

This commit simply adds a new read-only function to the Bitcoin Core kernel library that lets callers retrieve a transaction input's nSequence value. It is a straightforward API addition with no security implications.

This commit simply adds a new read-only function to the Bitcoin Core kernel library that lets callers retrieve a transaction's nLockTime value. nLockTime is a standard, public field in every Bitcoin transaction. The change does not alter how transactions are validated, stored, or relayed, and it introduces no security fix or vulnerability.

This commit only adds new test code for an existing Bitcoin Core wallet component. It expands a fuzzing harness to exercise more methods of the CCoinControl class, which is used to choose which coins are spent in transactions. There is no change to production wallet logic, no bug fix, and no security patch.

This commit only improves a fuzz test for the Bitcoin Core wallet's coin selection helper. It adds extra checks (assertions) inside the test to make sure the coin control object behaves as expected. It does not change any production wallet code, network code, or consensus rules, so it cannot introduce a security vulnerability in the running software.

This commit updates the version of the GNU C library (glibc) used in Bitcoin Core's reproducible build system (Guix) from one specific 2.31 snapshot to a newer 2.31 snapshot. It changes a commit hash and its corresponding cryptographic hash in a build manifest. There is no direct evidence in the commit that this fixes a specific security vulnerability; it appears to be a routine dependency refresh within the same glibc release branch.

This commit only adds a comment to an existing build-system patch file. It documents which future GCC versions will make this patch unnecessary. No code behavior is changed, and there is no security relevance.

This commit removes a temporary build-script workaround that was only needed for older versions of CMake on Apple macOS builds. It is a routine cleanup with no security relevance.

This commit changes how Bitcoin Core's Guix build system obtains a Python cryptography helper library called oscrypto. Previously, Bitcoin Core maintained its own custom package definition and a patch that forced oscrypto to use a specific OpenSSL library path. Now it uses the standard upstream package from the Guix distribution. This is primarily a build-maintenance simplification. It is not a direct fix for a known vulnerability, but it removes a local patch and custom package, which could slightly change what code is compiled into release builds.

This change removes a custom Guix package definition for osslsigncode (a Windows code-signing tool) and instead uses the version already maintained in upstream Guix. It is a build-system maintenance cleanup, not a security fix. The old custom package had a workaround for tests that would fail after the year 2025, but that workaround is being removed because the upstream Guix package presumably handles it. There is no direct evidence in the commit of a vulnerability or attack.

This commit updates a Python library used only in Bitcoin Core's continuous integration lint job from version 0.16.6 to 0.17.5, and removes a now-unneeded build compatibility patch. It does not change any code that runs in the Bitcoin Core software itself or affect how the network operates.

This commit removes a custom-built copy of the python-lief package from Bitcoin Core's Guix build manifest and switches to using the upstream Guix package instead. It is a build-system maintenance change that reduces custom code. There is no indication of a security vulnerability being fixed.

This commit updates the Guix build environment used to create reproducible Bitcoin Core release binaries. It bumps many dependency versions (compiler toolchain, glibc, Python, etc.) and makes the build container's root filesystem writable. There is no direct evidence this fixes a specific security vulnerability in Bitcoin Core itself; it is routine build-system maintenance.

This commit changes the Bitcoin Core Guix build script to add '--no-same-owner' to the TAR_OPTIONS environment variable. This option tells tar not to restore the original file ownership when extracting archives, instead using the current user. The change is intended to make tarball extraction more deterministic and avoid relying on the user running the build being able to assume arbitrary file ownership. It is a hardening/determinism improvement rather than a fix for an active, exploitable vulnerability.

This is a small code cleanup in Bitcoin Core's index synchronization logic. It adds an explicit early return when the code has already reached the latest block in the chain, separating that case from the more complex 'block is no longer in the main chain' reorganization handling. The change is primarily about making the code's intent clearer and avoiding unnecessary work, not about fixing a known security bug.

This is a small continuous-integration (CI) maintenance change. It makes the lint setup script download the correct tool versions for the computer architecture it is running on (e.g., ARM instead of only x86_64), and switches curl from silent mode to fail-on-error mode. It is not a security fix for Bitcoin Core itself and does not change any wallet, networking, or consensus code.

This is a straightforward internal code cleanup: it moves a debug-only logging call out of a low-level threading header file and into a source file. There is no user-facing change, no bug fix, and no security relevance visible in the commit.

This commit is purely cosmetic: it replaces tab characters with spaces in a lint script and removes that script from a list of files exempted from whitespace-format checks. There is no change to Bitcoin's network, wallet, consensus, or cryptographic code, and no security relevance.

This commit is a minor linting fix. It adds a new test directory (src/ipc/test) to an internal script that checks whether Bitcoin's C++ test files use a specific Boost test macro correctly. It does not change any production code, wallet logic, networking, or consensus rules. There is no security issue here.