Bitcoin Core

This commit only changes Bitcoin Core's internal test scripts. It removes five lines that previously told the test framework these particular tests cannot be run with the command-line bitcoin-cli tool. There is no change to the actual Bitcoin node software, no security fix, and no vulnerability.

This is a minor fix to a Bitcoin Core functional test script. It allows the dbcrash test to be run with the --usecli option by catching an additional error type that occurs when commands are sent through the bitcoin-cli tool instead of the direct RPC interface. It does not change the production Bitcoin node code and has no security impact on real users.

This is a minor change to a single test file in Bitcoin Core. It swaps the test RPC from 'echo' to 'echojson' so the test can also run against the command-line bitcoin-cli tool. There is no change to production code, no wallet or network behavior change, and no security fix or vulnerability introduced.

This is a minor fix to a Bitcoin Core functional test script. It changes the test setup so that the test nodes are stopped before their configuration files are edited, then started again afterward. Previously, the test restarted the nodes after editing the config, which could cause the command-line tool bitcoin-cli to read settings that had not yet taken effect. There is no change to production Bitcoin Core code and no security vulnerability in the software itself.

This commit is a small internal code cleanup for Bitcoin Core. It adds shortcut versions of two functions used only for test networks (RegTest and SigNet) so callers don't have to pass an empty options object. There is no user-facing change and no security relevance.

This commit lets Bitcoin Core accept two testing-only command-line options on test networks (testnet, testnet4, signet) instead of only on regtest. It also adds an explicit guard so those options cannot be used on the real mainnet. The change is aimed at making unit tests more flexible, not at fixing a live security bug.

This change tightens two low-level math helper functions so they only accept whole-number (integer) types. Previously, a non-integer type could slip through and silently produce wrong min/max values because the generic fallback for numeric limits returns 0. The patch prevents that misuse at compile time rather than relying on an internal check.

This commit adds release notes describing a privacy bug that was fixed in Bitcoin Core pull request #35319. The bug could accidentally reveal a user's real IP address when sending a transaction privately using the sendrawtransaction RPC with privatebroadcast enabled. Normally, such transactions are forced through the Tor network to hide the sender's IP. But if a peer falsely advertised support for the newer P2P v2 protocol, Bitcoin Core would try v2, fail, then fall back to v2 over a direct IPv4/IPv6 connection—bypassing Tor and potentially exposing the originator's IP address. This commit only documents the fix; it does not contain the actual code change.

This change adds a safety check in Bitcoin Core's networking code to make sure a specific kind of private message-sending connection (called a 'private broadcast' connection) never connects directly over the internet. Instead, it must go through a proxy like Tor or I2P. Without this guard, a future code mistake could cause the sender's real IP address to be exposed. The patch is described by the authors as a preventive guard, not a fix for an active bug.

This commit fixes a bug in Bitcoin Core's networking code. When a user or operator had configured a specific proxy (a privacy-routing middleman) to be used for a particular outgoing connection, that proxy was correctly used on the first connection attempt. But if the modern v2 transport protocol handshake failed and Bitcoin Core automatically fell back to the older v1 protocol, the fallback connection ignored the specified proxy and used the global/default proxy instead. The fix stores the requested proxy override inside the peer object so the fallback reconnection remembers to use it.

This commit changes a single variable type in Bitcoin Core's mining RPC code. The variable that holds signature-operation counts for transactions is now declared as a plain integer type (int64_t) instead of the money-amount type (CAmount). The commit message frames this as a type-safety cleanup, not a security fix. There is no direct evidence in the commit or supplied references that this change fixes an exploitable vulnerability.

This is a minor code cleanup in Bitcoin Core's test framework. It removes a lazy (deferred) import and replaces it with a normal import at the top of the file. There is no security issue here—it's purely a refactoring change to simplify the code after an earlier dependency cleanup.

This is a harmless internal code cleanup in Bitcoin Core's test suite. It moves a Python exception class named JSONRPCException from one test helper file (authproxy.py) to another (util.py) and updates the files that import it. There is no change to how Bitcoin nodes behave, no fix for a security bug, and no change that affects real users or live networks.

This commit only adds documentation to the developer notes. It describes the project's rules for phasing out old features (RPC methods, startup options, REST endpoints, and ZMQ topics) over time. No code behavior changed, so there is no security issue or vulnerability here.

This is a minor test-framework bug fix. It moves one line of code earlier so that a test-only URL field is set before creating a command-line RPC connection. This allows a specific functional test to run with the --usecli option. It does not affect the Bitcoin Core software that users run, nor does it touch network code, wallets, consensus, or any production security mechanism.

This commit is a one-word documentation update. It removes the phrase 'RPC only' from the help text of the -walletrbf command-line option because the feature is now also available through the graphical user interface. There is no code behavior change and no security impact.

This commit only adds documentation. It announces that two Bitcoin Core settings related to transaction replacement (RBF/BIP125) are now deprecated and will be removed later. There is no code change, no bug fix, and no security issue in the commit itself.

This commit is a routine infrastructure change for Bitcoin Core's continuous integration (CI) system. It switches the CI cache provider from Cirrus to GitHub's own cache service because Cirrus is being phased out and GitHub now offers more cache storage. The changes only affect how build artifacts and dependencies are stored between automated test runs; they do not modify the Bitcoin Core software that users run, nor do they introduce any known security vulnerability.

This is a tiny code-cleanup change in Bitcoin Core's RPC helper code. It removes unnecessary 'std::move' calls on plain enum values, which do not benefit from moving. There is no security impact.

This is a tiny code-cleanup change in Bitcoin Core's internal transaction graph logic. It swaps three std::move calls for plain assignments because the variables are simple numbers or booleans, where moving and copying do the exact same thing. There is no security impact.

This is a small code cleanup change. It changes one internal function so it accepts a constant reference to an outpoint instead of taking ownership by moving it. Since COutPoint is a tiny, cheap-to-copy object, moving it was unnecessary and forced callers to write extra std::move() calls. The behavior of the program is unchanged; there is no security fix here.

This commit only adds a release note describing a prior code change. It does not modify any executable code, configuration, or behavior. The release note explains that two mining-related settings will now be rejected when invalid rather than silently adjusted. There is no security issue in this documentation-only commit itself.

This commit only changes which source files are checked by an automated CI linting tool called 'Include What You Use' (IWYU). It expands the list of files where missing or unnecessary #include statements are treated as errors. It does not change any Bitcoin Core runtime code, network behavior, wallet logic, or cryptographic operations, so it has no direct security impact on users.

This commit is a pure code cleanup: it adjusts which header files are included in mining-related source files so each file explicitly includes only what it actually uses. There are no functional code changes, no bug fixes, and no security-relevant behavior changes.

This commit is a straightforward internal code cleanup: it reads mining-related command-line options once when the program starts and stores them in a shared node structure, instead of re-reading and re-parsing them every time a block template is created or an RPC mining-info call is answered. There is no user-visible behavior change, no bug fix, and no security relevance in the diff itself.