Bitcoin Core

This commit only removes a test case from Bitcoin Core's automated test suite. It deletes the part of a test that exercised the deprecated '-walletrbf' startup option and related opt-in RBF transaction behavior. There is no change to the actual Bitcoin Core wallet, node, or network code, and no security vulnerability is present in the diff.

This commit only changes a single test file. It removes the use of the deprecated '-walletrbf' startup option and its associated deprecation warning from the wallet_bumpfee.py functional test. There is no change to production wallet code, no bug fix, and no security issue.

This commit only changes Bitcoin Core's own test code. It removes the obsolete -walletrbf startup option from two functional tests and adds a missing PSBT v2 field (fallback locktime) to a test helper that creates blank PSBTs. There is no change to production wallet or node code, so it does not affect real users' funds, transactions, or network security.

This commit only changes a test script to make it run faster. It swaps one internal test helper for another equivalent one when sending transactions during a crash-recovery test. There is no change to the actual Bitcoin Core software that users run, and no security relevance.

This is a minor cleanup commit in Bitcoin Core's test code only. It replaces a manual time-comparison helper with a direct comparison and removes some code-comment markers related to include-file management. There is no change to production code, no security fix, and no vulnerability.

This commit is a simple code cleanup in a test file. It merges three nearly identical helper functions into one shared method used by Bitcoin Core's automated compact block tests. There is no change to the actual Bitcoin network software or its security behavior.

This commit is a build-system housekeeping change for Bitcoin Core's Guix reproducible-build tooling. It takes one large package list file (manifest.scm) and splits it into two smaller files: one used when compiling the software (manifest_build.scm) and one used when applying release signatures (manifest_codesign.scm). The scripts that invoke Guix are updated to point at the correct new file. There is no change to the Bitcoin Core node software, wallet logic, or network behavior, and nothing in the commit suggests a security vulnerability or fix.

This commit updates a build dependency called python-signapple, which is used to create and verify digital signatures on macOS Bitcoin binaries. It also adds environment variables so the tool can find OpenSSL libraries during the Guix reproducible build process. There is no direct evidence in the commit that this fixes an exploitable security flaw in Bitcoin Core itself; it appears to be a build tooling/maintenance change.

This commit adds a new internal 'submitBlock' method to Bitcoin Core's Mining interface, used by external mining software (like Stratum v2 servers) to submit fully assembled blocks for validation. It is a feature addition that mirrors the existing submitblock RPC. There is no direct evidence in the commit of a security vulnerability, but it exposes block submission over the IPC interface, which carries the same general risks as any block-submission path: a compromised or buggy caller could submit invalid or duplicate blocks. The implementation explicitly rejects duplicates and requires a complete block, including coinbase witness data when needed.

This commit only adds new automated tests for the Bitcoin Core IPC mining interface. It does not change any production node code, consensus rules, or network behavior. The tests verify that a new submitBlock IPC method correctly accepts valid blocks and rejects invalid, duplicate, or malformed ones. There is no security vulnerability here.

This commit is a straightforward internal code reorganization (refactor) in Bitcoin Core. It moves the logic for submitting a newly mined block into a shared helper function called SubmitBlock(). The actual behavior of block submission does not change; the code just becomes cleaner and easier to reuse for future features like IPC (inter-process communication). There is no security bug being fixed and no new attack surface introduced.

This is a tiny code cleanup in Bitcoin Core's wallet setup. It changes how the deprecated '-walletrbf' setting is read so the value is fetched once and reused, rather than checked for existence and then fetched separately. There is no security issue here.

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.