Bitcoin Core

This commit changes how Bitcoin Core's graphical wallet (bitcoin-qt) links a keyboard-handling library called libxkbcommon. Previously it was linked dynamically (the program loads the library from the user's system at runtime). Now it is linked statically (the library code is built into the program binary). This is a build-system hardening change that reduces the chance of runtime failures or supply-chain issues caused by incompatible system versions of that library, but it is not a fix for a known exploitable bug in Bitcoin Core itself.

This commit changes how a low-level graphical keyboard library (libxcb-keysyms) is bundled with Bitcoin Core's build system. Previously it was allowed as a shared library that had to be present on the user's system; now it is compiled directly into the Bitcoin Core binary. This is a build-hardening change that reduces external runtime dependencies and makes the release binary more self-contained, but it is not a fix for an active security vulnerability in Bitcoin Core itself.

This commit is a simple cleanup: it updates comments and documentation strings that still pointed to an old file path (`policy/fees.h`) after that file was apparently moved or split. The actual code behavior does not change at all. There is no security issue here.

This is a routine internal cleanup of Bitcoin Core's continuous integration (CI) testing setup. It renames a test job from 'No wallet, libbitcoinkernel' to 'No wallet' and switches its build configuration to use a standard developer preset while still explicitly turning off the wallet. There is no change to the actual Bitcoin node software that users run, and nothing in the commit suggests a security issue.

This commit only adds a new test case to Bitcoin Core's automated test suite. It demonstrates an existing behavior of the CoinGrinder coin-selection algorithm: if too many combinations must be tried, the algorithm stops before finding a valid solution. The commit does not change any production wallet code, so it cannot by itself introduce a security vulnerability or fix one in live software.

This commit simply removes two unused helper functions from Bitcoin Core's test code. The helpers relied on an old wallet command that no longer works and were only used for another removed test feature. There is no security issue here.

This commit only adds a new automated testing job to Bitcoin Core's continuous integration (CI) pipeline. It runs the existing fuzz tests under MemorySanitizer (MSan), a tool that detects use of uninitialized memory. The change does not modify Bitcoin Core's actual source code, network behavior, or wallet logic, so it cannot directly introduce or fix a security vulnerability in the software users run.

This commit adds a new public library API to Bitcoin Core's 'kernel' module that lets outside programs create block objects from raw bytes and ask the chainstate manager to process/validate them. It is a feature addition, not a fix. The code mostly forwards work to existing internal validation routines and adds tests using 206 regtest blocks. There is no direct evidence in the commit that this introduces a security vulnerability, but any new block-processing surface can affect consensus-critical code paths.

This commit introduces a brand-new C and C++ programming interface for Bitcoin Core's experimental "kernel" library. It exposes functions for parsing transactions, reading transaction outputs, and verifying Bitcoin scripts. The change is primarily a feature addition: it replaces the older libbitcoinconsensus-style API with a cleaner, modern one and adds tests. The commit message notes that one new error code was added specifically to prevent crashes when callers combine script-verification flags in invalid ways. There is no direct evidence in the commit of an exploitable vulnerability in existing code, but the new API does handle untrusted transaction data and must be used carefully.

This is a routine code modernization change in Bitcoin Core's Qt wallet interface. It replaces an older Qt filtering API call (invalidateFilter) with newer equivalents (beginFilterChange/endFilterChange) for future Qt 6 compatibility. There is no security-relevant behavior change.

This commit changes the Bitcoin Core dependency build system (the 'depends' Makefile) to tell GNU Make not to use its built-in default variable values. Built-in variables like 'CC' or 'CFLAGS' can silently override or mix with project-specific settings, which in rare cases could cause the wrong compiler or flags to be used when building third-party dependencies. The patch is a hardening measure rather than a fix for a known active vulnerability.

This commit is a routine code cleanup: it removes hand-written 'not equal' comparison operators across many files because modern C++ compilers can automatically generate them from the existing 'equal' operators. There is no functional change and no security risk.

This is a code cleanup change in Bitcoin Core's internal transaction graph logic. It removes branches of code that the author proved can never actually run, replacing them with explicit 'this should never happen' assumptions. There is no security bug being fixed; it is purely a refactoring to simplify the code and document invariants.

This commit only changes a code comment in a header file to clarify when a particular block-building helper function is safe to use. No executable code was modified, so it cannot introduce or fix a security vulnerability on its own.

This commit only changes a user-interface tooltip in the Bitcoin Core wallet creation dialog. It removes an outdated sentence that incorrectly said an HD seed could be added later to a blank wallet, which is not true for descriptor wallets. There is no code behavior change and no security impact.

This commit adds the Tcl programming language package to the Guix build environment used to create reproducible Bitcoin Core releases. It is a build-system dependency fix, not a change to Bitcoin's wallet, networking, consensus, or node logic. There is no indication this introduces a security vulnerability or fixes one.

This commit is a documentation-only cleanup for Bitcoin Core's RPC help text. It makes the help description for the wallet's gettransaction RPC match the actual fields returned, and lets the shared DecodeTxDoc helper show an extra 'ischange' field only when used in wallet contexts. There is no code behavior change, no bug fix, and no security impact.

This commit simply moves a helper function that builds documentation for decoded transactions from one file to another so it can be reused elsewhere. It does not change any behavior, logic, or security-sensitive code.

This commit is a routine maintenance update for Bitcoin Core's automated code-quality ('tidy') CI job. It upgrades the Clang compiler version used for style checks from 20 to 21 and adjusts several source files to satisfy new style warnings. There is no functional behavior change, no bug fix affecting consensus, networking, or wallets, and no security-relevant change.

This commit is a pure code reorganization: it renames the fee estimation source files from `policy/fees.cpp` and `policy/fees.h` to `policy/fees/block_policy_estimator.cpp` and `policy/fees/block_policy_estimator.h`, and updates all include paths accordingly. No logic, behavior, or security properties of the code were changed.

This commit is a pure code cleanup: it reorders the arguments of an internal helper function called GetTransaction so that an input parameter (blockman) comes before an output parameter (hashBlock), and updates the documentation comment to mention blockman. All callers are updated to match the new order. There is no change to what the function does or to any security-sensitive behavior.

This commit is a straightforward code cleanup: it replaces a true/false 'relay' flag with a named enum so the code is easier to read and future-proof. It does not change what the program actually does—transactions are still added to the mempool and/or broadcast exactly as before. There is no security fix or vulnerability here.

This commit is a routine subtree update that pulls in the latest minisketch library changes. The visible changes are almost entirely build-system and documentation additions: a new CMake build system, CI configuration files, README updates, and generated field-parameter documentation. There is no indication in the commit message or diff of any bug fix, behavior change, or security patch to the actual sketching code.

This commit is a performance improvement, not a security fix. It changes how Bitcoin Core's multiprocess mode handles log messages coming from the libmultiprocess library. Previously, all libmultiprocess log messages were processed through expensive serialization even when they would be discarded. Now, Bitcoin Core tells libmultiprocess which log levels it actually cares about, so unneeded messages are skipped earlier, reducing CPU usage. There is no indication this change fixes a vulnerability or security bug.

This is a routine code update that changes how an internal logging object is created to match a newer version of an upstream library. There is no security issue visible in the change itself.