Bitcoin Core

This commit only changes two comment lines in a header file. It renames 'descendants' to 'cluster_count' in documentation to match what the code actually calculates. No executable code, logic, or behavior was changed, so there is no security impact.

This commit only adds a code comment explaining that a function returns results in a deterministic order. No code behavior was changed, so it cannot introduce or fix a security issue on its own.

This commit changes a single word in a code comment, replacing 'chain' with 'cluster count' to accurately describe what the following code checks. It does not alter any program logic, behavior, or security properties.

This commit adds extra internal consistency checks to Bitcoin Core's memory pool validation routine and turns some soft 'Assume' warnings into hard 'assert' failures. It does not change network rules or how transactions are accepted; it only makes the program crash more reliably if its own bookkeeping about transaction fees and weights becomes internally inconsistent. That helps developers catch bugs during testing but is not a fix for an externally exploitable vulnerability.

This is a one-word documentation fix in a Bitcoin Core RPC help message. The error message shown when a user provides an invalid transaction ID now says 'txid' instead of 'parameter 1'. There is no security impact.

This commit renames a single field in a Bitcoin Core RPC output from 'weight' to 'clusterweight' and adds documentation explaining mempool fee/size terminology. It is a user-facing clarity/documentation change with no security-relevant code behavior change.

This commit changes two Bitcoin Core functions that enforce special rules for a new type of transaction called TRUC. Previously, one function locked the memory pool (mempool) itself. Now both functions require their callers to already hold the mempool lock. This is a defensive coding change that makes it explicit who is responsible for thread safety, but it does not by itself fix a known exploitable bug.

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 is a small internal cleanup in Bitcoin Core's memory pool (mempool) code. It changes how transaction fee adjustments are updated, removing an unnecessary wrapper and making a fee field directly mutable. There is no indication this fixes a security bug; it appears to be a refactoring or simplification after an earlier data structure change removed fee-based indexes.

This commit only adds a release notes document describing a previously implemented mempool redesign called 'cluster mempool.' It contains no code changes, no bug fixes, and no security-related disclosures. It is purely documentation.

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 fix to a Bitcoin Core fuzz test (an automated testing harness, not production code). The test was using an outdated size check after the real mempool code switched from measuring transaction size in 'vsize' to measuring it in 'weight'. The change tightens a guard so the fuzzer stops adding transactions before hitting an internal integer limit. It does not change how real nodes handle transactions and is not a vulnerability in live Bitcoin Core.

This commit is a simple renaming of internal function names and variables in Bitcoin Core's block-building code. It changes words like 'package' to 'chunk' to match terminology used elsewhere in the project. No behavior changes, no security fixes, and no bug fixes are visible in the code.

This is a small code cleanup change. It adds a new accessor method to retrieve a fee rate and uses it in one place when building blocks. There is no security-relevant change visible in the diff.

This is a one-line change inside a Bitcoin Core unit test file. It updates a test assertion to use the newer 'cluster size limit' constant instead of the older 'ancestor size limit' constant when checking that a deliberately oversized placeholder transaction is recognized as too large. The change only affects test code and does not alter any production behavior, network rules, or security logic.

This is a tiny code-comment and compile-time sanity-check update in Bitcoin Core's TRUC transaction policy. It changes which default mempool limit is referenced in a static_assert, switching from ancestor/descendant size limits to the newer cluster size limit. There is no runtime behavior change, no bug fix for active code, and no disclosed security relevance.

This commit removes two size-based controls from Bitcoin Core's memory pool (mempool) settings: the maximum virtual-byte size of an ancestor package and of a descendant package. It is a code cleanup that follows earlier work to replace those limits with a single 'cluster size' limit. There is no indication in the commit that this fixes a security bug; it appears to be a refactoring change.

This commit simply deletes two unused constant definitions from a header file. These constants were leftover default values for mempool ancestor and descendant size limits. They had no effect on running code because nothing referenced them. There is no security issue.

This commit updates internal compile-time sanity checks for Bitcoin Core's package transaction limits. It replaces checks based on older 'ancestor/descendant' mempool limits with checks based on newer 'cluster' limits. The change is defensive: it ensures that when users submit groups (packages) of related transactions, the configured limits won't accidentally reject transactions that should be acceptable. There is no direct evidence in the commit that this fixes an active security bug or vulnerability.

This commit only changes help text and adds warning messages for two command-line options that no longer affect how Bitcoin Core handles transactions. It does not fix a security bug, change network behavior, or introduce a vulnerability. It is a user-facing cleanup to prevent confusion after an earlier redesign replaced ancestor/descendant size limits with new cluster limits.

This commit simplifies how Bitcoin Core removes transactions from the memory pool when they are included in a newly mined block. It replaces a small two-step staging process with a direct call to the underlying removal function. The change appears to be a straightforward code cleanup with no obvious security impact, though it removes a thin abstraction layer that previously ensured removal events were recorded consistently.

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 Bitcoin Core commit rewrites the mempool cleanup logic that runs during blockchain reorganizations. It replaces an older set-based approach with a newer graph-based method for finding all transactions that must be removed because an ancestor became invalid. The change also adds a test for a tricky edge case where a transaction's child is only invalidated because its parent no longer spends a mature coinbase output. The commit itself does not describe a security bug, but the rewrite touches consensus-adjacent mempool code and improves test coverage for a previously untested scenario.

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 is a simple automated rename of a test helper function from AddToMempool to TryAddToMempool across test and benchmark files. It does not change any behavior, logic, or security properties of the Bitcoin Core software. The function body remains identical and the change only affects internal test/bench code, not production network code.