Bitcoin Core

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 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 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.

This commit is a minor cleanup of internal linting scripts. It moves one directory path into a shared list so that multiple code-style checkers can reuse it. There is no change to the Bitcoin software that users run, no change to security logic, and no security relevance.

This commit is a code cleanup that fixes inconsistent whitespace (tabs vs. spaces, trailing spaces) in several helper scripts and removes those files from a linting exclusion list. It does not change any program logic, behavior, or security settings.

This is a build-system tweak for Qt translation files. It explicitly tells the translation tool to use English as the target language instead of potentially defaulting to 'en_US'. There is no security issue here—it only affects how translation metadata is generated during compilation.

This commit changes how Bitcoin Core's user-interface text is sorted in translation files. It adds a build option to sort messages alphabetically within each context, which only affects the order of strings in the generated translation source file. There is no change to program behavior, logic, or security.

This commit changes how Bitcoin Core's translation files are generated. It removes source-code file references (line numbers and filenames) from the translation catalog to reduce unnecessary version-control noise. There is no security-relevant change to the running software, wallets, network, or consensus code.

This commit is a routine build-system cleanup. It removes an intermediate file-format conversion step used for translating the Bitcoin Core user interface into other languages. The project will now use Qt's native .ts translation files directly instead of first converting them to the XLIFF (.xlf) format. There is no security-relevant change here.

This commit is a pure code reorganization: it takes the existing logic that handles incoming network address messages and moves it into a new helper function called ProcessAddrs(). No behavior changes, security fixes, or new features are introduced.

This commit is a routine translation workflow update. It changes the file format used for Bitcoin Core's Qt translations from .xlf to .ts and updates the corresponding version slug from 031x to 032x. There is no security relevance.

This is a test-only change in Bitcoin Core. It improves a wallet rescan test so that it actually verifies the FastWalletRescanFilter is updated correctly during scanning. The previous test setup accidentally allowed the filter to be stale and still pass because a fixed non-range descriptor address matched every block. There is no change to production wallet code, so this does not directly fix a live security bug.

This commit removes three source-code files from a linting exclusion list. The lint check in question only enforces whitespace formatting rules. There is no change to Bitcoin Core's runtime behavior, consensus logic, networking, wallet, or any user-facing functionality. It is a pure code-quality tooling cleanup.

This commit fixes a Bitcoin Core fuzz test harness so that simulated peer nodes are marked as successfully connected. Without this flag, the test's code coverage was poor because the harness filtered out all fake nodes before running important connection-management logic. It is a test-only improvement with no effect on live Bitcoin node behavior or user funds.

This is a code-quality fix for Bitcoin Core's RPC help output. It changes how the documentation generator marks parts of the response as '...' (elided) so that the internal type checker can still verify the real data types. It does not change how transactions are decoded or how the network behaves, and it is not a security patch in the usual sense. The only user-visible change is a slightly clearer help message for the decodepsbt command.

This commit simply updates a build dependency, the Cap'n Proto library, from version 1.3.0 to 1.4.0 inside Bitcoin Core's build system. It changes the version number and the cryptographic checksum used to verify the downloaded source. There is no indication in the commit itself that this fixes a security problem, and no security advisory was provided. Dependency updates can sometimes include hidden security fixes, but this change alone does not show one.

This commit adds a build-time check that the compiler supports a modern C++ feature called CTAD (Class Template Argument Deduction). It does not change how Bitcoin Core runs, only how it is compiled. It is a defensive build-system improvement, not a security fix or vulnerability.