Bitcoin Core

This is a minor build-system tweak. It adds one internal test target ('mptest') to a list of targets that should not be included in the compile_commands.json database used by developer tools like clang-tidy. There is no user-facing or security-relevant change.

This commit changes a single line in a Bitcoin Core test script. It makes the test recognize any IP address beginning with '127.' as a loopback address, instead of only '127.0.0.1'. This is a test-only fix to prevent false failures when VPNs or other software add extra loopback addresses. It does not change the Bitcoin Core software that users run, and it has no security impact.

This commit only updates a code comment in a header file to describe the current behavior of a cache used for tracking Bitcoin softfork deployment status. No executable code was changed, and there is no security impact.

This commit only updates documentation. It adds a release note and a BIP implementation list entry describing a prior code change (PR #34779) that makes Bitcoin Core ignore certain BIP 9 soft-fork signal bits per BIP 323. There is no code change here and no direct security risk in the commit itself.

This commit only adds a new test case to Bitcoin Core's existing test suite. It checks that the software does not produce spurious warnings for version bits that belong to deployments that have been explicitly disabled/ignored. There is no change to production code, no bug fix, and no security vulnerability in the commit itself.

This Bitcoin Core change narrows which version bits trigger live 'unknown soft fork' warnings from 29 bits down to 5, following the new BIP323 specification. It does not change how many bits exist in block headers or how test networks behave; it only reduces false or misleading upgrade alerts for bits that the network no longer treats as active deployment candidates.

This commit is a routine change to Bitcoin Core's continuous integration (CI) setup. It swaps the GitHub Actions cache for a faster third-party cache service (WarpBuild) on Warp runners, while keeping GitHub's cache as a fallback for forks. There is no change to the Bitcoin software itself, to wallets, transactions, consensus rules, or network code.

This change removes a default value for a network-connection setting called proxy_override. Previously, callers could leave it unset without thinking. Now every caller must explicitly pass a value, which helps prevent accidental mistakes about which proxy a connection uses. It is a defensive code-quality fix, not a patch for a known active bug or attack.

This commit only adds a new regression test file and registers it in the test runner. It does not change any production code in Bitcoin Core. The test verifies that if a private broadcast connection using the newer v2 transport fails, the node falls back to the older v1 transport through the Tor proxy. There is no security patch or vulnerability fix here.

This commit only changes a test file. It makes a wallet functional test more explicit by passing replaceable=False so the test reliably checks anti-fee-sniping locktime behavior, instead of relying on a coincidental wallet default. There is no change to production wallet or node code, so it does not fix a live security vulnerability.

This commit changes several Bitcoin Core kernel library functions so they crash the program (via assertions) instead of returning a null pointer when callers pass a null buffer with a non-zero length. It also tightens one function to require exactly 80-byte block headers. The change treats these as programmer errors rather than runtime failures, which can help catch misuse early but may cause denial-of-service crashes if an attacker can trigger those calls with bad inputs.

This is a test-only code change that restores the string format of an error message shown when a Bitcoin Core functional test encounters a JSON-RPC failure. It only affects test framework output formatting and has no bearing on the live Bitcoin Core software or its users' funds or network security.

This commit is a pure test-code refactoring. It moves a list of fake network addresses and a helper loop from one test file into the shared test framework so other tests can reuse it. No production Bitcoin Core code is changed, and nothing about how real nodes connect or broadcast is modified.

This commit is a simple code cleanup in Bitcoin Core's test suite. It moves a small helper that starts a temporary peer-to-peer listener from one test file into a shared test framework file so other tests can reuse it. There is no change to the actual Bitcoin network code, no change to how nodes communicate, and no security fix or vulnerability.

This commit is a test-only code cleanup. It moves the setup of a fake SOCKS5 proxy server used in automated tests into a shared helper function and lets the operating system pick an available network port instead of guessing one. It does not change any production Bitcoin Core code or fix a security vulnerability.

This commit removes a single 'friend' relationship between two wallet classes in Bitcoin Core. It is a code-cleanup change that reduces unnecessary access to private members; it does not fix a bug or vulnerability and has no direct security impact.

This is a small fix in Bitcoin Core's 'sendall' wallet RPC command. The bug meant that when a user explicitly set a transaction as non-replaceable, the wallet skipped its normal anti-fee-sniping protection. Anti-fee-sniping is a privacy/defense mechanism that uses the current block height as a transaction 'locktime' to make transactions look more similar and slightly harder to target. The fix changes the input sequence number used in that case so the protection still runs even when RBF is disabled.

This commit is a code-quality cleanup: it adjusts which C++ header files are included in many source files under src/script and related areas, and tells the continuous-integration (CI) tool to treat 'include-what-you-use' (IWYU) warnings as errors for those files. There is no functional change to how Bitcoin validates transactions, scripts, or signatures, and no security fix or vulnerability is described.

This commit simply changes the Bitcoin Core GitHub Actions CI configuration to use 'ubuntu-latest' instead of the specific 'ubuntu-24.04' label for fallback runners. It is a routine infrastructure consistency change with no direct security relevance to the Bitcoin software itself.

This commit is a trivial documentation update inside a configuration file for code editors. It changes a comment from referencing 'Cirrus' (a former CI service) to 'ci.yml' (the current CI filename). There is no code change, no security fix, and no user-facing behavior change.

This commit only rewords a code comment in a header file. It changes 'Should only be used for tests / benchmarks' to 'Should only be disabled for tests / benchmarks' to make the documentation clearer. No code behavior changed, and there is no security issue.

This is a one-line fix inside a Bitcoin Core functional test. After restarting a test node, the test wallet's view of available coins is refreshed so the rest of the test can spend them correctly. It does not change production wallet, node, or consensus code, and has no security relevance for real users.

This is a small hardening change in Bitcoin Core's block-building code. It adds internal safety checks (assertions) to make sure a configuration value called block_max_weight has been converted from an optional value to a plain number before it is used in limit comparisons. The change does not by itself fix a known exploitable bug, but it guards against a class of programming mistakes where an unset value could silently behave as zero and cause incorrect block-size decisions.

This is a small test-only code change in Bitcoin Core. It updates a single unit test to use a helper function that merges mining options instead of using a raw mining arguments object directly. There is no change to production code, no network behavior change, and no security fix.

This is a small cleanup in Bitcoin Core's test suite. It replaces a locally-defined timeout value with a shared class attribute that has the exact same value. The commit message explicitly says it does not change behavior, and the diff confirms that: the same timeout formula is used, just in one place instead of two.