Bitcoin Core

This commit only adds a new automated test that checks what information the getblockchaininfo RPC returns about a background validation process. It does not change any production code, network behavior, or wallet logic, so it cannot introduce a security vulnerability or fix one.

This commit simply adds a new optional information block called 'backgroundvalidation' to the getblockchaininfo RPC output. It exposes read-only status about an existing background chain-validation process, plus some minor capitalization fixes in help text. There is no security-relevant change.

This commit is a documentation-only release note. It describes a new RPC feature that exposes background validation progress for the assumeutxo feature. There is no code change, no bug fix, and no security issue.

This commit only changes how Bitcoin Core calculates and prints a progress percentage in log messages during a special background validation mode (used with the assume-utxo feature). It does not change consensus rules, network behavior, wallet handling, or any security-critical logic. The old code could show a misleading progress number; the new code makes the log estimate more accurate. There is no security vulnerability here.

This is a small internal cleanup change for a Bitcoin Core function that calculates statistics about the unspent coin set (used by the gettxoutsetinfo RPC). It moves where a variable is declared and refactors how the statistics object is built so the code is easier to read. There is no direct security fix in this commit itself; it is described as a follow-up to a prior pull request that addressed a race condition.

This is a tiny code cleanup in Bitcoin Core's networking code. It removes an unnecessary conversion of a string-like variable to std::string before passing it to a function that accepts std::string_view. There is no security impact.

This commit adds a new automated build test for Bitcoin Core that compiles the software for FreeBSD from a Linux machine. It does not change any Bitcoin code, wallet logic, networking, or security behavior. It only affects internal continuous integration (CI) scripts.

This commit adds FreeBSD to the list of operating systems for which Bitcoin Core's build system will compile the optional QR code generation library (qrencode). It is a one-line build configuration change with no apparent security relevance.

This commit updates Bitcoin Core's build system to support cross-compiling FreeBSD binaries using Clang and the LLVM toolchain. It changes compiler and linker settings in makefiles used only during the build process. There is no indication this fixes or introduces a security vulnerability.

This commit changes how Bitcoin Core builds the Qt GUI library on FreeBSD. It disables Qt's inotify feature during the build process. Inotify is a Linux-style file-change notification mechanism that Qt tries to use on FreeBSD, but it can cause build or runtime problems because FreeBSD's support differs. The change is a build-system compatibility fix; there is no direct evidence in the commit that it fixes an exploitable security vulnerability.

This commit is a simple cleanup: it removes extra line-break characters from the ends of log messages in the Tor control code. Modern logging functions already add their own line breaks, so the old manual ones were creating blank lines in log files. There is no security issue here.

This commit is a pure code cleanup: it renames variables in Bitcoin Core's Tor control module to follow the project's modern naming style (adding 'm_' prefixes to member variables and using snake_case for local names). No behavior, logic, or security properties of the code are changed.

This commit is a straightforward code cleanup in Bitcoin Core's Tor control module. It changes several constant variable declarations from 'static const' to 'constexpr' for integer and float values. This is a non-functional style/refactoring change with no security relevance.

This is a small internal cleanup in Bitcoin Core's lock-tracking code. It swaps the standard C++ mutex for a project-specific wrapper (StdMutex) and adds compile-time annotations that tell the compiler which data structures are protected by the mutex. There is no change to network behavior, consensus rules, or user-facing functionality, and no security bug is being fixed.

This commit is a purely mechanical rename in Bitcoin Core's logging code. It replaces the old name 'StdLockGuard scoped_lock' with a shorter macro name 'STDLOCK' everywhere it appears. The actual locking behavior is unchanged, so there is no security impact.

This commit adds compiler hints about which locks must not be held when calling two logging helper functions. It does not change any actual code behavior, memory layout, or runtime logic. The change helps automated tools detect potential future threading mistakes during development, but it does not fix an active bug by itself.

This commit tightens a compile-time safety check in Bitcoin Core's custom mutex wrapper. It adds a macro called STDLOCK() that, when used, asks the compiler to verify the same lock is not being acquired twice in a row by the same thread. It does not change runtime behavior or fix an active exploit; it is a defensive hardening change to catch a specific programming mistake during compilation.

This commit fixes a small user-interface bug in Bitcoin Core's Qt wallet GUI. When the user turns on 'privacy mode' (the 'mask values' checkbox that hides balances), then switches to a different wallet, the 'History' button was incorrectly staying enabled. Clicking it would reveal the transaction list for the newly selected wallet, defeating the intended privacy setting. The fix makes the transaction view stay disabled when privacy mode is active during a wallet switch. It is a local, UI-only information-disclosure issue that requires the attacker to already have access to the unlocked GUI and the ability to switch wallets.

This commit is a routine maintenance update for the project's automated code-quality tooling. It upgrades the Include-What-You-Use (IWYU) static-analysis tool from version 0.21 to 0.26 to match Clang 22, refreshes the tool's internal header-mapping patch, removes now-unnecessary workarounds, and adds or removes a few C++ standard-library #include lines in two source files so the code continues to pass the updated analyzer. There is no change to Bitcoin Core's runtime behavior, consensus logic, networking, wallet handling, or any user-facing feature.

A single missing semicolon in Bitcoin Core's wallet coin-selection code caused a comparison to run before an assignment. As a result, the variable that was supposed to hold the total available amount instead held just true or false. The code still mostly worked by accident, but the wrong value could mislead the wallet's decision about whether it has enough funds, especially when unconfirmed transactions with long chains are involved. This could lead to confusing error messages or, in edge cases, incorrect transaction creation.

This commit only updates the help text for the generateblock command in Bitcoin Core. It adds a note explaining that the command does not collect transaction fees in the block reward. There is no code behavior change, no bug fix, and no security issue.

This commit is a routine cleanup of Bitcoin Core's GitHub Actions CI configuration for Windows builds. It switches the build from using a standalone vcpkg installation to the one that comes bundled with Visual Studio, matching the project's own documentation. The change only affects internal continuous-integration tooling and does not alter the Bitcoin Core software that users run.

This commit is a simple code cleanup in Bitcoin Core's test suite. It moves a small helper function that creates a mining test object from two individual test files into a shared utility file, so the same code isn't duplicated. There is no change to the actual Bitcoin node software, no change to how tests behave, and no security relevance.

This commit only adjusts timeout values in a single automated test file. It makes the test wait longer under slow CI conditions to avoid false failures. There is no change to the actual Bitcoin Core software that users run, and no security issue is present.

This commit only adds a new automated test and a small test helper. It checks that the Bitcoin Core IPC mining server returns a clean error when given invalid data, instead of crashing. There is no change to production code, so it does not introduce or fix a live security vulnerability by itself.