Bitcoin Core

This is a routine change to Bitcoin Core's automated testing setup. It switches the macOS CI jobs from running directly on a Git checkout to running on a snapshot of the source code created by 'git archive'. The commit message says the goal is simply to verify that compilation works this way. There is no security-relevant change here.

This commit removes two compiler-hint annotations (LIFETIMEBOUND) that were technically incorrect. The function only inspects the input objects during the call and does not keep pointers or references to them afterward. Removing the annotations prevents the compiler from enforcing lifetime rules that do not actually apply, but it does not change runtime behavior or fix any active security bug.

This commit is a routine improvement to Bitcoin Core's GitHub Actions CI workflow. It makes sure every CI job prints a machine-readable annotation containing the pull request number, because GitHub discards those annotations when individual checks are re-run. There is no security-relevant change here.

This change simply makes the automated CI (continuous integration) system retry building a lint Docker image one time if the first attempt fails, waiting 3 seconds between attempts. It is a reliability improvement for internal testing infrastructure and does not touch any Bitcoin Core code that handles transactions, wallets, networking, or consensus rules.

This commit removes an unused Qt tool called qdbusviewer from Bitcoin Core's dependency build. It is a build-system cleanup with no apparent security relevance.

This commit changes how Bitcoin Core's graphical wallet (bitcoin-qt) links to a low-level Linux graphics library called libxcb. Previously, libxcb and several related extension libraries were allowed to be loaded dynamically from the operating system. Now they are built as static libraries and linked directly into the application. The main practical effect is to reduce the application's dependency on whatever versions of these libraries happen to be installed on the user's Linux distribution, which can make builds more reproducible and avoid crashes or compatibility problems caused by mismatched library versions. It is a build-system hardening change, not a fix for an active remote-attack vulnerability.

This commit adds a patch to Bitcoin Core's build system so that when Qt is built statically for Linux, it correctly links several helper libraries from the XCB (X11 client communication) family. The patch itself comes from upstream Qt bug reports and fixes missing dependency declarations that could cause build failures or incomplete linking. It is a build-system correctness fix rather than a runtime code change, and there is no direct evidence it fixes an exploitable vulnerability.

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 Bitcoin Core's build system handles a low-level graphics helper library called libxcb-util-image. Previously it was built as a shared library that had to be present on the user's system; now it is built as a static library that is copied directly into the Bitcoin Core executable. This is a build/packaging change, not a fix for a known vulnerability in the library itself. It mainly reduces the chance that a missing or incompatible system library prevents Bitcoin Core from running, and slightly changes the attack surface around dynamic library loading.

This commit changes how a low-level graphics helper library (libxcb-render-util) is bundled when building Bitcoin Core. It switches the build from producing a shared library to a static library, and removes that shared library from the list of files allowed in release binaries. This is a build-hardening change that reduces external runtime dependencies; it does not by itself fix a known exploitable bug in Bitcoin Core.

This commit changes how a low-level Linux graphics helper library (libxcb-util-wm) is bundled with Bitcoin Core. It switches the build from producing a shared library to a static library, and removes one shared library name from the list of allowed runtime dependencies. The change is a build-hardening improvement, not a fix for an active security bug. It reduces the chance that a malicious or incompatible version of that library on the user's system could affect Bitcoin Core, but it does not patch any vulnerability 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 is a minor code cleanup in Bitcoin Core. It changes a copyright year range to 'present', adds a blank line between include statements, and reformats a comment about how git fills in commit IDs in archived source code. There is no security-relevant change.

This commit is a build-system cleanup, not a fix for an active security flaw. It removes old CMake settings that forced build-time library paths to be stripped from binaries, because the release build script now runs its security checks after installing the software rather than before. It also removes two unused developer maintenance targets and makes the security checks cover one extra directory (libexec). The change is hygiene work that slightly hardens the build pipeline, but it does not by itself create or close a user-exploitable vulnerability.

This commit only adds new automated test cases for the Bitcoin Core Qt console's command-history filtering feature. It checks that sensitive wallet commands (like createwallet and migratewallet) are displayed in shortened form in the console history. There is no change to production code and no security fix or vulnerability.

This change moves the location where a Qt plugin path is set for Windows testing from the CI workflow file into the CMake test configuration. It is a build/test infrastructure cleanup to make tests run more reliably in the Windows CI environment. There is no indication it fixes a security vulnerability.

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 commit removes a build-system patch that Bitcoin Core used to apply to Qt during compilation. The patch told Qt's meta-object compiler (moc) to ignore a GCC internal macro. The commit message says the underlying Qt bug was fixed in Qt 6.5 or 6.6, so the patch is no longer needed. There is no direct evidence in the commit of a security vulnerability in Bitcoin Core itself.

This commit rewrites a small GitHub Actions CI step from Bash to Python. It does not change what the CI step does; it only changes how the command is built and executed. The rewrite fixes a shell-script lint warning about unsafe word splitting and makes the code easier to maintain. There is no security vulnerability here.

This is a minor cleanup of a GitHub Actions workflow file. It rewrites a simple input-validation check from Bash to Python, with no functional change to what values are accepted or how the action behaves. There is no security issue visible in the change.

This commit simply deletes an old, unused patch file from the build system. The patch was no longer being applied to Qt, so removing it has no effect on the compiled Bitcoin Core software and does not change any security behavior.

This is a routine cleanup of Bitcoin Core's continuous integration (CI) configuration for macOS. It replaces a long list of build options with a pre-defined 'dev-mode' preset and shortens the job name shown in GitHub's web interface. There is no change to the actual Bitcoin software that users run, and no security relevance.

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 changes Bitcoin Core's continuous integration (CI) settings for Windows builds. It turns on two extra test executables in the automated build/test pipeline and renames a CI job. There is no change to the actual Bitcoin node, wallet, or network code that users run, so it does not create a security vulnerability or fix one.

This commit adds a new public helper function that lets outside code compare two block tree entries to see if they point to the same block. It is a pure API convenience addition with no bug fix, behavior change, or security-sensitive logic.