Bitcoin Core

This commit only changes which logging function is used for error and fatal-condition messages across Bitcoin Core. It replaces generic LogPrintf calls with LogError (and one LogInfo) so that serious problems are more clearly marked in logs. There is no change to program logic, no bug fix, and no security vulnerability being patched.

A small change to a helper Python script used for building network maps. The script now refuses to write raw binary output directly to a terminal window, because doing so can garble the screen and, in rare cases, cause a terminal to misinterpret control characters. This is a hardening improvement rather than a fix for an active attack.

This commit is a minor test-code cleanup. It moves four named constants related to BIP68 sequence locktime rules from one test file into the shared test framework library. No production code, consensus rules, or security behavior is changed.

This commit fixes a single-word typo in a log message. The phrase 'on non-prune mode' was corrected to 'in non-prune mode'. It has no effect on program behavior, security, or user data.

This is a small internal cleanup in how Bitcoin Core wallets report balances for reused addresses. It does not fix a vulnerability or change user-facing totals; it just computes the 'used' balance in one pass instead of calling the balance function twice and subtracting. There is no security issue visible in the change.

This commit fixes a memory-handling bug that occurs when Bitcoin Core shuts down its network connections. A list of pending reconnections held references to a memory resource (semaphore) that was freed during shutdown. When the program later destroyed that list, it could read already-freed memory, which can cause crashes or unpredictable behavior. The fix clears the reconnection list before freeing the underlying resource and adds code annotations to prevent the wrong lock from being held during shutdown.

This commit only changes a test file. It improves an existing test by checking that a warning message ('TestShell is already running!') is actually printed to the screen when a second TestShell is started. There is no change to Bitcoin Core's production code, no security fix, and no vulnerability.

This is a small cleanup change to a helper script used for comparing internet routing maps (asmap files). It only changes how the tool reports summary statistics: it now counts the number of changed entries separately from the number of affected IP addresses, and uses a built-in library function instead of a manual calculation. There is no security relevance.

This Bitcoin Core commit relaxes a mempool policy rule. Previously, only a special transaction type called TRUC could be below the minimum relay fee when submitted as part of a package. Now any transaction version can be below that fee if it is part of a package that overall pays enough fees. The change is described by the developers as safe because of the newer cluster mempool design, but it removes one anti-pinning protection and makes zero-fee parent transactions relayable under certain conditions.

This commit adds a GitHub Actions cleanup step that deletes large pre-installed software folders (like .NET, Android SDK, Node modules) on CentOS CI runners to free disk space. It only affects Bitcoin Core's own continuous integration environment and does not change any Bitcoin node code, wallet logic, or network behavior. There is no security issue in the change itself.

This commit simply renames a helper script from gen-sdk to gen-sdk.py and updates the documentation link. The file contents are identical. It is a routine tooling change with no security relevance.

This commit changes the macOS SDK packaging script for Bitcoin Core so that it produces an uncompressed .tar archive instead of a .tar.gz archive. The reason is that different Linux distributions use different underlying compression libraries, which can produce slightly different compressed files even from identical input. That breaks reproducible builds (determinism), where everyone expects the exact same output. The uncompressed archive is larger (~157 MB) but byte-for-byte identical across machines. There is no security vulnerability being fixed here.

This change trims the macOS software development kit (SDK) archive used to build Bitcoin Core for Mac. Instead of bundling the entire SDK, the script now only includes specific directories needed for compilation. This reduces download size and shrinks the attack surface by leaving out unnecessary files such as Swift modules, module maps, and manpages. It is a hardening and maintainability improvement rather than a fix for a known vulnerability.

This is a one-word change in a test file. A developer fixed a misspelled string ('invald wallet' to 'invalid_wallet_content') used only to create intentionally corrupted wallet data for a test. It has no effect on the actual Bitcoin Core software that users run.

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.