Bitcoin Core

This commit changes the -version output of Bitcoin's command-line and GUI programs so the name of the executable (for example 'bitcoind' or 'bitcoin-node') is printed alongside the version string. It is a testing/debugging convenience change and does not alter how wallets, network messages, or consensus rules are handled.

This commit simply moves a small block of code that builds a synthetic extended public key into its own reusable function. There is no change in behavior, no bug fix, and no security-relevant change.

This is a routine build-system maintenance update for the Microsoft Visual Studio (MSVC) dependency manifest. It bumps the vcpkg baseline and several bundled library versions (Boost, Qt, SQLite) to newer releases. There is no code change to Bitcoin Core itself, and the commit message does not describe any security fix.

This commit is a code-quality and performance cleanup, not a security fix. It changes many Bitcoin Core calls to the libsecp256k1 cryptography library so they use a shared, read-only 'static context' instead of a special signing context. The signing context is only needed for operations that actually multiply a secret key with a generator point, such as creating public keys or signing. Using the static context elsewhere is harmless and matches the library's documented recommendations. There is no indication this fixes an active vulnerability.

This change fixes a logic issue in Bitcoin Core's network handling. When a node operator configures special permissions (like bypassing connection limits or relay rules) for specific IP addresses, those permissions were mistakenly being granted to inbound connections arriving through a Tor hidden service. Because Tor hides the true IP address of the connecting peer, the node cannot verify that the peer actually belongs to the whitelisted address range. The patch ensures that whitelist permissions are not applied to Tor inbound connections, so only connections whose real network address is known can receive those privileges.

This commit is a harmless build-system fix. It tells the CMake installer to also include the manual page (help documentation) for the main `bitcoin` command-line program when installing Bitcoin Core. There is no security issue.

This commit is a routine code cleanup in Bitcoin Core's networking layer. It removes a platform-specific type alias (sockopt_arg_type) and replaces it with direct void*/char* casts where needed. The behavior of the program is unchanged; there is no security fix or vulnerability here.

This is a minor test-only change. A Bitcoin Core unit test was accidentally configured to use the main network (mainnet) parameters, which caused a harmless but noisy warning about needing hundreds of gigabytes of disk space. The fix makes the test use the small regtest network parameters instead. It does not change production code or affect real users, wallets, or funds.

This commit adds a new automated test for the Bitcoin Core mining IPC (inter-process communication) interface. It exercises the submitSolution and checkBlock methods with both an invalid block version and a valid block. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit changes a single Bitcoin Core continuous-integration (CI) script so that one automated testing job uses the Mold linker instead of the default system linker. It adds the 'mold' package to the CI container and tells the build to use it. There is no change to the Bitcoin Core software that users run, no bug fix, and no security relevance.

This commit only changes comments and adds one explanatory assertion inside a Bitcoin Core test file. There is no change to production code, no behavior change, and no security fix or vulnerability introduced.

This is a small code cleanup inside Bitcoin Core's test suite. It changes how one test object is created and stored so it lives on the stack instead of the heap. There is no change to the actual Bitcoin network code, no bug fix, and no security-relevant behavior change.

This commit only reorganizes existing test code in Bitcoin Core. It splits one large test case into three smaller, logically separate test cases and adds a missing comment. No production code, network behavior, or security-sensitive logic is changed.

This is a small internal cleanup in Bitcoin Core's header synchronization code. It replaces std::vector with std::span for passing batches of block headers, avoiding unnecessary copying in tests. There is no security-relevant change to network behavior, validation logic, or consensus rules.

This commit is a code cleanup and refactoring change for Bitcoin Core's initial block header synchronization. It moves hardcoded tuning constants out of the headers-sync source file and into each network's chain parameters, so test networks can use values appropriate to their own history. It is not a security fix and does not patch a known vulnerability. The change does add a small runtime safety check that the commitment period is non-zero, which prevents an accidental misconfiguration from causing undefined behavior.

This commit only improves existing test code for Bitcoin Core's header synchronization logic. It adds helper macros and stricter assertions to make tests clearer and more thorough, but it does not change any production code, fix a bug, or alter network behavior. There is no security issue here.

This is a test-only change for Bitcoin Core. It expands an existing unit test to verify how the headers synchronization logic returns proof-of-work-validated headers. The change increases the number of generated test blocks and adds assertions that check internal behavior of the sync state machine. There is no change to production code, no fix for a vulnerability, and no security-relevant behavior change in the software users run.

This is a code cleanup (refactor) change in Bitcoin Core. It makes a 256-bit integer type usable in compile-time constants and reorganizes a test file so that repeated test data is generated in helper functions. There is no change to network behavior, consensus rules, or wallet handling, and no security fix.

This is a small CMake build-system fix. A command that tells the build system to use the C programming language was moved from inside a function to the top of the file. The old placement could cause CMake configuration to fail or behave incorrectly when building the secp256k1 cryptographic library, but it does not change how the Bitcoin software itself runs or processes transactions.

This commit updates the systemtap dependency used in Bitcoin Core's build system from version 4.8 to 5.3. Systemtap is a developer/tracing tool, not part of the live Bitcoin network code. The change is a routine dependency bump with a small upstream patch that fixes a C header macro check to avoid compiler warnings/errors. There is no indication this fixes a security vulnerability in Bitcoin Core itself.

This is a minor internal cleanup in Bitcoin Core's Python test runner. It replaces a regular Python list used as a FIFO queue with a purpose-built deque, which avoids a theoretical slowdown when popping items from the front. The change only affects test infrastructure, not the live Bitcoin node software, and the commit message explicitly states behavior is unchanged.

This commit simplifies the internal copy behavior of a core Bitcoin data type (arith_uint256) by letting the compiler generate default copy routines instead of hand-written loops. The change is framed as a performance/cleanup improvement and includes a compile-time check that the type remains trivially copyable. There is no indication this fixes a security bug or introduces a vulnerability.

This is a Bitcoin Core continuous integration (CI) script change. It switches the LLVM source checkout from trying to match the locally installed clang version to always using a fixed tag (llvmorg-21.1.1). The commit message says this avoids intermittent CI issues. There is no change to the Bitcoin Core software that users run, no wallet or consensus code is touched, and no security vulnerability is described.

This commit only adds extra test cases and assertions for how Bitcoin Core handles script verification flags. It does not change any production code that processes real transactions, so it cannot introduce a security vulnerability or fix one in live software.

This commit changes Bitcoin Core's continuous integration (CI) configuration for GitHub Actions. It adds a per-job option to override which cache provider is used for Docker setup, specifically setting a 32-bit ARM job to use GitHub Actions' native cache instead of Cirrus Labs' cache. This is a build-infrastructure tweak with no apparent effect on the Bitcoin software users run, on their funds, or on network security.