Bitcoin Core

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

This commit only edits documentation. It removes detailed macOS fuzzing setup instructions and replaces them with a note that macOS fuzzing is not officially supported, recommending Linux instead. No code, build scripts, or security behavior changed.

This commit changes the bitcoin-cli -addrinfo command so it reports the full set of addresses known to the node, not just the subset previously filtered for quality and recency. The change is purely informational: it makes the displayed statistics more accurate and useful, but does not alter peer selection, network behavior, or any security-sensitive logic.

This commit updates the Bitcoin Core continuous integration (CI) configuration to use a newer version of Apple's Xcode development tools (16.2 instead of 16.0) when building and testing on macOS. It is a routine infrastructure/maintenance change with no apparent security relevance.

This commit adds an internal consistency check inside Bitcoin Core's memory pool validation routine. It verifies that two different ways of ranking transactions by mining priority produce the same order. It is a defensive assertion, not a fix for a known bug or vulnerability, and it does not change network behavior.

This commit adjusts a startup configuration check for Bitcoin Core's memory pool (mempool) size. It changes the internal sanity check so that the minimum allowed -maxmempool value is based on the newer 'cluster size limit' rather than the older 'descendant size limit', and it explicitly allows users to set -maxmempool=0 to disable the mempool. This is a routine consistency fix for configuration validation logic, not a security patch for an exploitable vulnerability.

This commit only updates documentation in a Markdown file describing how Bitcoin Core accepts groups (packages) of transactions. It removes outdated descriptions of ancestor/descendant limit checks and CPFP Carve Out behavior, and updates the package replacement rule wording. No code, logic, or behavior changes are present in the diff.

This commit only changes a test file. It makes an existing functional test for package Replace-By-Fee (RBF) use slightly larger transaction clusters (3 transactions per cluster instead of 2). There is no change to production code, so it cannot directly affect live Bitcoin nodes or introduce a security vulnerability.

This commit adds an internal sanity check inside Bitcoin Core's transaction memory pool (mempool) self-check routine. It verifies that a newly introduced feerate diagram data structure stays within expected size bounds. The change is defensive and only affects debug/self-check code, not normal network operation. There is no indication it fixes an active security vulnerability or that it is exploitable by an attacker.

This commit only updates the explanatory comments at the top of the mempool header file. No code, logic, or data structures were changed. It is a documentation-only edit and has no security relevance.

This commit adds calls to a background graph-maintenance routine (TxGraph::DoWork) after three kinds of mempool changes: applying a batch of new transactions, handling a blockchain reorganization, and processing a newly found block. It also defines a constant telling the graph how much cleanup work to do each time. The change looks like a performance or consistency fix: without these calls, the in-memory transaction graph might not be updated promptly, possibly leading to stale data, incorrect fee estimates, or degraded mempool behavior. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

This commit only renames CI (Continuous Integration) job names and a configuration script filename to clarify that they are for Windows builds using the older MSVCRT runtime. It does not change any actual build commands, compiler flags, source code, or runtime behavior. There is no security issue here.