Bitcoin Core

This Bitcoin Core commit changes how the mempool (the waiting area for unconfirmed transactions) decides which transactions to kick out when it gets too full. Previously it used 'descendant feerate'; now it uses 'chunk feerate' so that the transactions a miner would pick last are the same ones the mempool evicts first. This is a consistency improvement in transaction selection policy, not a fix for a clear exploit. The change could affect transaction propagation, fee estimation, and mempool behavior under load, but the commit itself does not describe any security vulnerability.

This commit refactors how Bitcoin Core selects transactions for new blocks. It replaces an older, more complex ancestor-feerate algorithm with a new 'chunk feerate' approach driven by a new mempool graph builder. The change is a significant rewrite of mining transaction selection logic, but the commit itself does not describe any security bug or fix. Because it is a large behavioral change in consensus-adjacent code, it carries ordinary implementation risks, but there is no direct evidence in the commit of a vulnerability.

This commit only changes Bitcoin Core's functional test suite. It reworks and deletes some Replace-By-Fee (RBF) tests that previously needed very large transaction clusters. The production mempool rules are not modified, and no security vulnerability is present in the commit.

This is a minor test-only change in Bitcoin Core's functional test suite. It adds a constant and changes one test variable from 100 to 64 in preparation for future mempool work. It does not modify any production code, consensus rules, or network behavior, and presents no security issue.

This commit adds two new command-line options, -limitclustercount and -limitclustersize, and corresponding data fields for mempool limits. However, the commit title and code make clear these new limits are currently unused: no enforcement logic consumes them. It is purely preparatory infrastructure for future mempool policy changes. There is no immediate security impact.

This commit removes a fuzz test that compared two internal Bitcoin components (MiniMiner and BlockAssembler) to ensure they built the same block. The test is being deleted because an upcoming code change ('cluster mempool') will make their outputs intentionally differ. This is a test-only cleanup, not a fix for a security bug.

This Bitcoin Core commit enforces a new mempool policy: groups of related unconfirmed transactions ('clusters') are now capped by configured size and count limits. Previously these limits existed as settings but were not fully enforced by the new in-memory transaction graph. The patch wires the limits into the graph, rejects submissions that would exceed them, and removes transactions from the mempool when a newly accepted block creates oversized clusters. It also reorders some validation checks so cluster-size rejection happens before certain standardness checks, which is why one functional test was temporarily adjusted.

This commit only adds documentation to the CI README explaining how to set up QEMU user-mode emulation for running tests on foreign CPU architectures. It is a pure documentation change with no code modifications, no security fixes, and no functional changes to Bitcoin Core.

This commit only updates a documentation file (ci/README.md) to explain more clearly why the CI system should be run inside a clean environment using the `env -i` command. It does not change any code, build scripts, or configuration that could affect Bitcoin Core's runtime security. There is no vulnerability or security fix here.

This commit changes a single formatting setting in Bitcoin Core's code style configuration file. It tells the clang-format tool to automatically add a blank newline at the end of source files when it runs. This has no effect on how the software runs, what data it processes, or its security. It only affects whitespace in source code files.

This commit is a documentation-only change for Bitcoin Core. It adds comments explaining how PSBT (Partially Signed Bitcoin Transaction) data is read from serialized bytes, with no changes to actual code behavior. The surrounding merge commit also includes a very large number of unrelated file additions (build files, templates, docs, etc.), but the titled change itself is purely explanatory comments.

This commit simply removes an unused local variable from a single function in Bitcoin Core's networking code. There is no functional change, no bug fix, and no security relevance.

This commit simply moves a chunk of Python code from inside a GitHub Actions workflow file into its own separate Python file. The code that runs is unchanged; only its location changed. There is no security issue here.

This is a test-only change. It removes unit tests that created a std::span from a null pointer with a non-zero length, which is undefined behavior and now trapped by hardened std::span implementations. The production code is not changed, and no vulnerability in live Bitcoin Core is introduced or fixed here.

This commit only updates a documentation file for building Bitcoin Core on NetBSD. It changes the recommended Python package from version 3.10 to version 3.13 because the older package is no longer available by default in NetBSD 10.1. There is no code change and no security issue.

This commit only changes Bitcoin Core's own test code. It makes the test framework correctly add a witness commitment to test blocks when they contain a segwit transaction, and adds a new test case for transactions that have unnecessary witness data. There is no change to the actual Bitcoin network code that users run, so this does not create a security vulnerability in Bitcoin Core itself.

This is a small fix to Bitcoin Core's internal Python test framework. When a test talks to a running node and the connection is reset unexpectedly, Python's error object sometimes doesn't include a standard error number. The patch makes the test code treat that as a connection reset, so it can log and retry correctly instead of crashing the test run. It does not change the Bitcoin node itself, user wallets, consensus rules, or network behavior.

This commit only adds a new test to Bitcoin Core. It checks that calling size() on an AutoFile object reports the file size without moving the file's internal read/write position. There is no change to production code and no security fix or vulnerability is present in the diff.

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.

This commit is a minor code cleanup: it changes two logging calls in the asmap file handling from a general log function to a warning-level log function. There is no security-relevant behavior change, no bug fix, and no new vulnerability introduced.

This commit only adds new test cases to Bitcoin Core. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The tests verify that a piece of networking code (the ASMap interpreter, used to map IP addresses to autonomous system numbers) produces expected results for a set of known inputs.

This commit tightens input handling in Bitcoin Core's kernel library. Previously, the library's C interface promised that callers must not pass a null or empty directory path, but it did not actually check. Now it explicitly rejects null or empty data and blocks directories and returns an error instead of potentially misbehaving. It also updates the internal C++ wrapper to accept string views, which can legitimately have null data pointers when empty. This is a defensive hardening change, not a fix for an active exploit.

This commit removes an already-unused command-line option called `-maxorphantx`. The option had no effect since version 30.0 and only produced a warning if someone still had it in their configuration. Now it is fully removed, and a release note explains the change. There is no security issue here.

This is a code-quality annotation change only. It tells the compiler that a function parameter's lifetime is tied to the returned value, which helps catch misuse during development. It does not change program behavior or fix a runtime security bug.

This is a small internal code cleanup in Bitcoin Core. A helper function that finds the earliest block matching certain criteria used to return a raw pointer; now it returns a reference. The change is purely stylistic/safety-related because the function was already guaranteed to return a non-null result (it contains an assertion). No behavior changes, no bug fixes, and no security issue is present.