Bitcoin Core

This commit only adds a new automated test to Bitcoin Core. It checks that wallet backups can (or cannot) be loaded on pruned nodes that are using the assumeutxo snapshot feature. There is no change to production wallet, consensus, or networking code, so it does not introduce or fix a live security issue on its own.

This commit is a minor cleanup of a Bitcoin Core test file. It moves existing snapshot-import and background-validation checks into new helper functions without changing what the test actually verifies. There is no change to production code, no security fix, and no vulnerability.

This change adds a warning when users import a Bitcoin wallet descriptor containing an 'older()' time or block lock that looks safe but actually has no consensus effect. Because of how Bitcoin encodes relative locktimes, values above 65535 silently wrap around: older(65536) behaves like older(1). Someone could accidentally create a wallet that unlocks far sooner than they think. The patch does not block the import; it only warns.

This commit changes the format of a Bitcoin Core RPC command called getmempoolcluster so it groups transactions into 'chunks' rather than listing each transaction separately. It also adds a clearer error message when the requested transaction is not in the memory pool. The change is a user-facing output improvement, not a fix for a security vulnerability.

This commit only changes documentation. It adds a new design document explaining Bitcoin Core's cluster mempool concept, renames a link in the policy README, and deletes an older document about mempool limits. No code, configuration, or behavior is modified. There is no security issue in this change.

This is a small internal code cleanup in Bitcoin Core's transaction memory pool. It rewrites a helper function called GetChildren so that it no longer builds a temporary set to remove duplicate child transactions; instead it uses a lightweight 'epoch' marker to skip duplicates. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit refactors how Bitcoin Core removes a transaction and all of its dependent transactions from the memory pool (mempool). It replaces an older, more manual descendant-finding method with a newer graph-based helper. The change is described as a simplification. There is no direct evidence in the commit that this fixes a security bug, but any change to mempool removal logic carries a small risk of introducing or masking consistency issues.

This commit updates the FreeType font-rendering library used in Bitcoin Core's build dependencies from version 2.11.0 to 2.11.1. It changes the download URL, archive format, and verification hash, and adjusts a small build patch. FreeType is a widely used library for drawing text, and newer point releases often include bug fixes. The commit itself does not say whether this fixes a security issue, and no security references were provided.

This commit is a straightforward logging cleanup. It changes many messages from the generic LogPrintf to a new LogWarning helper, which is designed for severe-but-non-fatal problems. The wording of the messages is mostly unchanged, and no program logic, permissions, or security behavior is modified. It is not a security fix.

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.

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 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 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 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 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 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 updates the libxcb dependency used when building Bitcoin Core from source. It bumps the version from 1.14 to 1.15, switches the download archive format from .tar.xz to .tar.gz, updates the SHA-256 checksum, and refreshes a documentation link. There is no direct evidence in the commit that this fixes a specific security vulnerability, but dependency updates can include upstream security fixes.

This commit simply bumps the version of a third-party graphics-related library (libXau) used in Bitcoin Core's build dependencies from 1.0.9 to 1.0.12, updating the corresponding download hash. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.

This commit fixes a test-only race condition in a Bitcoin Core functional test. It changes which node is checked first when verifying that a newly submitted block has propagated, so the test waits for the local node to update its own chain before checking that all nodes agree. There is no change to production code, no user-facing behavior change, and no security vulnerability in the Bitcoin Core software itself.

This commit adds new read-only ways to inspect Bitcoin's mempool through RPC: it exposes 'cluster' information for transactions, adds chunk-based fee/weight fields to existing mempool entries, and introduces a hidden diagnostic command that prints the mempool's feerate diagram. It is a feature/informational change, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that it addresses a security bug or was triggered by a security report.

This commit simply moves a single internal helper function, removeConflicts, from the public section of a C++ class to the private section in the header file. It does not change what the function does, how it behaves, or any executable code. It is a routine encapsulation/cleanup change with no security effect.

This small code change updates an internal Bitcoin mining-simulation tool so it calculates ancestor transaction data on the spot rather than relying on a precomputed cache. The change appears aimed at preventing the mini-miner from using stale or incorrect cached values, which could lead to wrong fee estimates when simulating which transactions to include in a block. There is no direct evidence in the commit that this fixes an active security vulnerability, but it removes a dependency that could produce inconsistent results.

This commit removes Bitcoin Core's old 'ancestor count/size' mempool limits, leaving only newer 'cluster' and 'descendant' limits. The change is intentional and part of a broader mempool policy simplification. It does not by itself create a known exploit, but it changes what transaction shapes are allowed into the mempool. A miner or node operator relying on the old ancestor limits now has different protections, which could matter if the remaining cluster limits are weaker in some edge cases.

This commit adds a new helper method called size() to the AutoFile class, which reports how large a file is. It also updates two existing places in the code to use this new helper instead of manually seeking to the end of the file and asking for the current position. The change is purely a code cleanup (refactor) and does not fix any security bug.