Bitcoin Core

This commit adds a build-time patch for the Qt GUI toolkit used by Bitcoin Core's Windows builds. The patch fixes a visual/layout bug in the Windows 11 visual style where spinbox controls (number/date input fields with up/down buttons) could be sized incorrectly or have their user-set widths overridden. It is a cosmetic/user-experience fix, not a security patch.

This commit fixes a formatting inconsistency in how Bitcoin Core's wallet describes certain advanced 'miniscript' descriptors. When a user called the listdescriptors RPC, the same descriptor could contain a mix of 'h' and ''' markers for hardened derivation paths, depending on whether the key was inside a Taproot taptree or not. The patch makes the output uniform. It is a correctness/usability bug rather than a direct loss-of-funds vulnerability, but inconsistent descriptors can confuse downstream tools or users who compare or re-import descriptor strings.

This is a one-line documentation fix in a README file. It adds a missing '--platform=linux' flag to a Docker build command example used by developers running linting tools locally. There is no code change, no security vulnerability, and no risk to users.

This commit fixes a broken CI safety check. When Bitcoin Core moved from Cirrus CI to GitHub Actions, an automated check that verifies commit signatures on the official repository stopped running because it looked for an old environment variable that no longer existed. The patch introduces a new environment variable so the signature check runs again on non-pull-request pushes to the official bitcoin/bitcoin repository. It is a CI hardening fix, not a vulnerability in the Bitcoin software itself.

This is a routine internal cleanup of the Bitcoin Core continuous integration (CI) lint scripts. It renames an environment variable from a Cirrus-specific name to a provider-agnostic one and enables a stricter shell option for catching pipeline failures. There is no user-facing change and no security-relevant behavior change.

This change adjusts Bitcoin Core's GitHub Actions CI workflow so that build caches are only saved when running on the repository's default branch (e.g., 'master'). Previously, caches could be saved from non-default branches too. The patch is a hardening measure: it reduces the risk that a malicious or compromised branch could poison shared CI caches used by later builds. It is not a fix for an active exploit in Bitcoin Core's shipped software, but rather a defensive tightening of the project's own build infrastructure.

This commit only adds new automated tests for Bitcoin Core's mempool cluster features. It does not change any production code that runs on real Bitcoin nodes, so it cannot introduce a security vulnerability or directly fix one in the live software.

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 only updates a documentation file describing Bitcoin Core's mempool replacement policy. It removes outdated rules and adds notes about newer 'feerate diagram' checks and cluster mempool behavior. There are no code changes, no executable changes, and no security fix or vulnerability introduced.

This commit rewrites an internal Bitcoin Core function called GatherClusters so it uses a newer transaction graph (txgraph) implementation instead of manually walking parent/child relationships. The change is a refactor that preserves the same 500-entry DoS limit but moves where and how that limit is enforced. There is no direct evidence in the commit that this fixes a security bug, but refactors of mempool cluster logic can affect denial-of-service protections.

This commit removes a function called CheckPackageLimits that, according to the commit title and message, no longer did anything useful. The function body simply returned success without performing any checks, and callers were already using other mechanisms (like CheckPolicyLimits) for the relevant limits. This is a straightforward code cleanup with no apparent security impact.

This commit only adds new performance benchmark tests for Bitcoin Core's transaction memory pool. It does not change any production code that runs on real networks, so it cannot directly affect security or be exploited by attackers.

This commit is a code cleanup in Bitcoin Core's memory pool (mempool). It removes duplicate bookkeeping: parent/child relationships between transactions used to be tracked both inside each mempool entry object and inside a newer 'txgraph' module. The change makes txgraph the single source of truth for those relationships. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability; it appears to be a refactoring to simplify data structures and reduce maintenance risk.

This commit is a test-only change. It expands Bitcoin Core's fuzz testing for the transaction memory pool (mempool) to cover more behaviors like eviction, expiry, reorg handling, and block template creation. It also adds a sanity check inside the mempool's own consistency verification code. There is no indication this fixes a security vulnerability or changes production network behavior.

This commit only changes a test file (miniminer_tests.cpp) so that existing unit tests still pass after a new mempool 'cluster limit' rule was introduced. It does not change any production code that runs on real Bitcoin nodes, so it cannot directly affect live network security or be exploited by attackers.

This commit fixes Bitcoin Core's own internal test and fuzzing helpers so they stop trying to add fake transactions to the test mempool in ways that break the real mempool policy rules. It does not change production network code, wallet behavior, or consensus rules. The change only affects test utilities and one fuzz target, making the tests more realistic and preventing false fuzz failures.

This Bitcoin Core commit reorders and reworks how two new transaction-handling features—RBF (Replace-By-Fee) and TRUC (a restricted version-3 transaction policy)—are validated. The main goal is to avoid doing expensive 'ancestor' calculations on the whole mempool until cheaper cluster-size checks have already run, so a maliciously crafted transaction can't waste a node's CPU as easily. It also makes sure the same RBF checks apply whether one transaction or a whole package is being accepted, and moves a 'spends a transaction it is replacing' check to a later, safer point.

This commit is a straightforward internal code cleanup in Bitcoin Core. It moves two helper functions—one that finds child transactions and one that finds parent transactions—from being methods on individual mempool entries to being methods on the mempool itself. The behavior is essentially the same; only the code organization and the caller syntax change. There is no indication this fixes a security bug or changes network behavior.

This commit fixes how Bitcoin Core counts the descendants of a special transaction type (TRUC) in the memory pool. Previously it looked only at direct children, which could miss deeper descendants introduced by blockchain reorganizations. The change makes the limit enforcement more accurate and adds a lock to prevent race conditions while checking the pool. It is a correctness and robustness improvement rather than a clear, exploitable vulnerability.

This commit is a routine internal refactoring in Bitcoin Core's memory pool (mempool) code. It replaces one way of calculating transaction ancestors with a newer shared component called txgraph. The visible behavior for users and network peers should stay the same. There is no indication this fixes a security bug or introduces a vulnerability.

This commit simplifies how Bitcoin Core's memory pool (mempool) calculates the descendants of a transaction. It replaces a manual tree-walking routine with a call to a dedicated transaction graph component (m_txgraph). There is no direct evidence in the commit that this fixes a security bug; it appears to be a code cleanup or refactoring change.

This commit is a routine code cleanup in Bitcoin Core's memory pool (mempool) logic. It removes error-handling paths from functions that calculate transaction ancestors, because a previous design change made those errors impossible. The commit does not introduce new behavior or fix a security bug; it simplifies the code after ancestor/descendant limits were removed elsewhere.

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 is a routine code cleanup in Bitcoin Core. It removes an unused 'limits' parameter from several mempool ancestor-calculation functions and their callers. The actual mempool policy limits are still enforced elsewhere, so this change does not alter network rules or introduce a security issue.

This commit removes several unused internal accounting fields from Bitcoin Core's memory pool transaction entry class. It is a straightforward code cleanup: fields that tracked descendant and ancestor transaction sizes, fees, and counts are deleted, and the methods that updated them are left empty. There is no security-relevant change visible in the diff.