Bitcoin Core

This commit only changes an error message in a test file so that when a test fails, it prints the HTTP reason phrase (like 'Not Found') alongside the status code. It does not change any production code, user-facing behavior, or security logic.

This commit only adds a new automated test to Bitcoin Core's REST interface test suite. It checks that the /blockpart/ endpoint correctly rejects unsupported request types with proper error messages. There is no code change to the actual REST server behavior, and no security vulnerability is being fixed.

This commit is a bulk update of copyright notice years in source-code comments. It changes phrases like '2012-2022 The Bitcoin Core developers' to '2012-present The Bitcoin Core developers' across 988 files. There are no changes to program logic, no bug fixes, and no security-related code changes.

This commit changes Bitcoin Core's GitHub Actions CI workflow so that when a Windows cross-build job runs, a separate job records the exact commit ID being built, and the follow-on native Windows test job checks out that same recorded commit. This prevents a race condition where a new commit pushed during the cross-build could cause the native tests to run against different source code than what was compiled. It is a CI reliability improvement, not a security fix.

This commit only adds a new unit test file for an existing feature called private broadcast storage. It does not change any production code, so it cannot introduce a security vulnerability or fix one on its own.

This commit only adds documentation: a release note describing a previously merged privacy feature (PR #29415). It does not change any code, so it cannot introduce or fix a security vulnerability on its own. The feature it describes lets users optionally broadcast transactions only over Tor or I2P to hide their IP address and avoid linking separate transactions.

This commit only adds a new automated test file for Bitcoin Core's existing 'private broadcast' feature. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The test verifies that transactions submitted through the RPC are broadcast privately over Tor/I2P-style connections and checks related edge cases.

This commit updates the sendrawtransaction RPC command so that, when the optional -privatebroadcast setting is enabled, it broadcasts raw transactions over privacy-preserving networks (Tor/I2P) instead of sending them to all connected peers. It also adds a check that at least one of those networks is reachable, and updates the command's help text. There is no direct evidence in the commit of a security vulnerability being fixed; it appears to be a privacy feature enhancement.

This commit adds a retry mechanism for a new optional 'private transaction broadcast' feature in Bitcoin Core. If a transaction sent privately isn't seen back from the network within about a minute, the node schedules extra private outgoing connections to rebroadcast it. It is a feature-completion patch, not a fix for an active vulnerability, and it does not appear to introduce obvious security bugs on its own.

This Bitcoin Core change improves how the node stops privately re-broadcasting a transaction once it sees that same transaction come back from the network. It is a hardening/efficiency fix for the new private transaction broadcast feature, not a fix for a known remote exploit. The patch makes the node stop its private re-broadcast attempts when the exact transaction it sent is seen again, while still continuing to broadcast the original if a peer returns a malleated (altered-witness) version.

This commit adds a new 'private broadcast' feature in Bitcoin Core that lets users send transactions through short-lived, disguised peer connections to reduce the risk that someone watching the network can figure out which IP address originated a transaction. The patch also fixes a related privacy leak: without the change, a malicious peer could have tricked the node into revealing its real network address during one of these private broadcasts. The commit is defensive and improves privacy, but it is a new and complex network feature, so it deserves careful review.

This commit simply moves an internal consistency check (an `Assume()` assertion) to an earlier point in the code that handles a peer's VERACK message. The check itself and the surrounding logic are unchanged. The author explicitly states this is a non-functional change, meaning it does not alter program behavior in release builds or fix any active bug.

This is a straightforward code cleanup in Bitcoin Core's network handshake routine. It renames local variables, splits declarations from assignments, and merges two nearly identical log lines into one. The commit message explicitly calls it a non-functional change, and the diff shows no altered behavior, no new network data, and no changed security checks.

This commit simply moves a diagnostic log message that records receipt of a peer's VERSION message to an earlier point in the network processing code. It does not change any protocol behavior, validation logic, or security checks. The change only affects debug logging output, making it more likely the log line is printed even if the connection is interrupted shortly after receiving VERSION. There is no security issue here.

This commit adds infrastructure for a new privacy feature in Bitcoin Core. It creates a storage area for transactions that should be broadcast privately, and a method to request short-lived connections to privacy-network peers to broadcast them. The code is purely additive scaffolding; it does not by itself introduce a vulnerability, nor does it complete the private-broadcast feature. It simply wires a new code path into the existing transaction-broadcast logic.

This commit simply rearranges the order of steps inside the code that handles a peer's VERSION message in Bitcoin Core. It moves the sending of two optional follow-up messages (WTXIDRELAY and SENDADDRV2) to a later point in the same function. The commit message explicitly calls this a non-functional change, and the diff shows no logic changes—only moved code blocks.

This commit adds a new placeholder option for broadcasting Bitcoin transactions more privately, but the option is not actually used anywhere yet. It is a non-functional change that prepares the code for a future feature. There is no security issue in this patch itself.

This commit simply renames a function inside Bitcoin Core from RelayTransaction() to InitiateTxBroadcastToAll(). No behavior changes; the new name is more accurate because the function only queues a transaction for possible later broadcast rather than sending it immediately. It is a code clarity and documentation improvement.

This commit adds a new optional Bitcoin Core feature called private broadcast connections. It lets the node open short-lived outbound connections over Tor, I2P, or clearnet through a Tor proxy, separately from normal peer connections. The change is defensive/privacy-oriented: it tries to avoid reusing a permanent I2P address and only routes these connections through anonymity networks. There is no obvious security bug in the diff, but it is a new networking subsystem with concurrency, proxy handling, and resource limits, so it carries some implementation risk.

This commit adds a new type of network connection called 'private-broadcast' to Bitcoin Core. It is a feature for improving user privacy when broadcasting transactions over anonymity networks like Tor or I2P. There is no indication in the commit that this fixes a security vulnerability; it is a privacy enhancement.

This commit adds a new optional Bitcoin Core setting called -privatebroadcast. When enabled, transactions submitted through the sendrawtransaction RPC are broadcast over short-lived Tor or I2P connections instead of being placed in the node's public mempool first. The change is purely additive: it introduces the option, sets its default to off, and adds startup checks that warn or error if the feature is configured incorrectly. There is no bug fix or vulnerability patch here.

This commit simply adds a new logging category named 'privatebroadcast' to Bitcoin Core's logging system. It does not change any network behavior, privacy rules, or security logic. It only gives developers and users a new on/off switch for log messages that will be added separately.

This commit adds a new test case to an existing fuzz test. Fuzz tests are automated tools that feed random or semi-random inputs to a program to find crashes or bugs. The new test simulates re-downloading a block that was previously pruned (deleted to save disk space), similar to what happens when a user runs the getblockfrompeer RPC. It does not change normal node behavior, only test code.

This commit adds a new automated fuzz test for Bitcoin Core's block index tree. It is purely a testing/quality-assurance change: it creates fake block trees and simulates events such as adding headers, receiving blocks, reorganizing chains, and pruning, then checks the tree's integrity. It does not change any production code that runs on real Bitcoin nodes, so it cannot directly introduce a network-exploitable vulnerability.

This commit only changes test infrastructure code. It moves some internal class members from private to protected access and adds test-only wrapper methods so that fuzz tests can reach validation logic without making those functions public in the main codebase. There is no change to how Bitcoin Core behaves in production, and no security bug is being fixed or introduced.