Bitcoin Core

This commit is a routine code cleanup in Bitcoin Core's helper and test scripts. It replaces manual UTF-8 decoding of subprocess output with Python's built-in text=True option. There is no security-relevant change: the behavior is functionally equivalent, only the code is simpler and more consistent.

This commit only updates copyright years in file headers from a fixed range (for example '2018-2022') to 'year-present'. It makes no changes to program logic, network behavior, or security-sensitive code. There is no security relevance.

This commit removes explicit 'UTF-8' encoding declarations from dozens of helper and test scripts in the Bitcoin Core repository. In Python 3, removing the encoding argument makes file operations fall back to the system's default locale encoding. On most modern systems that default is UTF-8, so the change is intended to be a no-op cleanup. However, on systems where the locale is not UTF-8, some scripts could fail or behave differently when reading files that contain non-ASCII characters. The commit deliberately keeps explicit UTF-8 handling in the two places where it actually matters.

This commit removes a lint (code-quality) script that checked whether Python code in the repository explicitly specified UTF-8 encoding when opening text files or reading subprocess output. It is a tooling/development cleanup, not a change to Bitcoin Core's runtime code, consensus logic, wallet handling, or network behavior. There is no direct security vulnerability in the diff itself.

This commit only updates a test documentation file (test/README.md) to clarify that Python's UTF-8 mode is already the default on most systems. It is a documentation-only change with no code modifications, no security fixes, and no behavior changes.

This is a minor change to a linting script that checks shell scripts for locale settings. It removes an optional opt-out for locale-dependent scripts and clarifies documentation. There is no security-relevant change to Bitcoin Core's runtime behavior, consensus code, or network handling.

This commit only changes Bitcoin Core's internal functional test scripts. It replaces the old way of simulating blockchain reorganizations in tests (using invalidateblock/reconsiderblock) with a more realistic method that builds an actual competing fork and submits it. No production node code is modified, so this cannot directly affect live Bitcoin nodes or users.

This commit simply moves a helper function used only in Bitcoin Core's internal test suite from one test file into a shared test-framework library. It does not change any production code, network behavior, or wallet logic. There is no security issue here.

This commit only adds new test cases to Bitcoin Core's existing MuSig wallet test file. It checks that the software correctly refuses to finalize transactions when required nonces or partial signatures are missing. There is no change to production wallet, consensus, or networking code, so it does not introduce or fix a live security vulnerability on its own.

This commit removes a protective lock around a simple mempool check. The change is presented as a cleanup of a redundant lock, but removing synchronization around concurrent data structures can in theory introduce race conditions. There is no direct evidence in the commit or supplied materials that this causes a real exploitable bug.

This commit is a routine internal cleanup of Bitcoin Core's continuous integration (CI) scripts. It moves logic from a Bash script into an equivalent Python script to avoid a shell lint warning about word splitting. There is no user-facing change, no network code change, and no security-relevant behavior change.

This is a small change to Bitcoin Core's internal continuous integration (CI) shell script. It removes a fallback message that previously printed if the rsync command failed, so rsync is now treated as a hard requirement. The change does not affect the Bitcoin network, wallets, consensus rules, or production nodes. It only matters if someone runs the CI system directly on their host machine without rsync installed, which the commit message itself calls an edge case.

This is a routine cleanup of Bitcoin Core's internal continuous integration (CI) shell scripts. It rewrites a helper function so arguments are passed more safely and moves a directory change and a test-only PATH tweak into the script that actually runs tests. There is no change to the Bitcoin node software, wallet handling, network protocol, or any user-facing behavior.

This is a code cleanup change in Bitcoin Core's internal CI (continuous integration) tooling. It moves a macOS-specific setup step so it sits inside the branch that already handles running tests directly on the host machine. There is no change to Bitcoin's network code, wallet, consensus rules, or anything users interact with. It only affects how the project's own automated tests are organized.

This commit is a documentation and code cleanup change for Bitcoin Core's continuous integration (CI) system. It makes sure the 'retry' helper script is available in the system PATH both when running tests inside a container and when running directly on the host. There is no security vulnerability here.

This commit is a routine cleanup of Bitcoin Core's continuous integration (CI) scripts. It moves some folder-creation and Docker cleanup logic from a shell script into an equivalent Python script. There is no user-facing change, no change to Bitcoin's consensus or networking code, and no security relevance.

This commit updates a single helper script used during Bitcoin Core's build process to the latest upstream version from the GNU project. The changes are routine maintenance: a copyright year bump, a timestamp update, and minor adjustments to how the script identifies one obscure operating system (Ironclad). There is no indication of a security fix, vulnerability, or malicious change.

This commit updates a single helper script used during Bitcoin Core's build process. The script, called config.sub, comes from the GNU project and is responsible for recognizing different operating systems and CPU types when compiling software. The update adds support for newer or less common platforms (for example, Ironclad, Tock, Banan OS, Apple simulator targets, and the arm64_32 CPU) and fixes a duplicate entry. There is no indication this change fixes a security vulnerability or introduces malicious behavior; it is a routine dependency refresh.

This commit simply removes an unused type alias named cacheMap from the transaction mempool header file. It is a routine code cleanup with no functional change and no security relevance.

This commit removes the ability to reassign a TxGraph::Ref after it is created (move assignment), while keeping the ability to construct a new Ref by moving an existing one (move construction). The change is framed as a cleanup to prevent misuse of a reference-counting-like handle in Bitcoin Core's transaction graph code. There is no direct evidence in the commit that this fixes an active security bug, but removing a complex operator can reduce the risk of lifetime or double-management bugs.

This commit simply moves a constant value (MUSIG_CHAINCODE) from a header file to the source file where it is actually used. It is a routine code cleanup with no functional change and no security relevance.

This commit hardens Bitcoin Core's MuSig2 multi-signature code by refusing to save a second secret nonce under the same session ID. Before the change, an attacker or buggy caller could potentially overwrite a nonce, which in multi-signature schemes can lead to nonce reuse and theft of funds. The fix uses try_emplace plus an assertion so duplicate session IDs are caught instead of silently replacing the existing nonce.

This commit removes an internal safety assertion in Bitcoin Core's transaction signing code and tweaks a comment. The removed assertion checked that Schnorr signatures were only created for the intended Taproot/Tapscript contexts. The change appears to be a minor cleanup because the same check is performed elsewhere, but removing a defensive assertion slightly reduces code safety margin. There is no direct evidence this introduces a real vulnerability.

This commit only adds new automated testing jobs for compiling Bitcoin Core for Windows using a different C runtime library (UCRT). It does not change any Bitcoin Core source code that users run, so it has no direct security impact on the software itself.

This commit only adds a new automated test to Bitcoin Core. It checks that the -alertnotify feature correctly warns users when the node sees a competing chain with more total work that it considers invalid. There is no change to production code, no bug fix, and no security vulnerability introduced or patched.