Bitcoin Core

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 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 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 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.

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 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 removes one duplicate line from a test file. It is a code cleanup change with no effect on the actual Bitcoin Core software that users run, and no security relevance.

This commit only updates the wording of a release note for a new Bitcoin Core REST API endpoint. It changes the documentation's placeholder formatting (e.g., BLOCKHASH to BLOCK-HASH) and adds a note that the output can be requested in binary or hex format. There is no code change and no security relevance.

This is a code cleanup change in Bitcoin Core. It changes several internal coin-cache flushing functions from returning true/false to returning nothing, because in normal use they always succeeded anyway. It removes some now-unnecessary error checks and updates tests to match. There is no direct security bug being fixed here; it is a refactoring that simplifies the code and removes a theoretically reachable but practically dead error path.

This is a tiny code cleanup in Bitcoin Core's block storage module. It replaces a manual check that prevents reading beyond the end of a raw block file with a simpler check using a helper called SaturatingAdd. The change appears to be a defensive simplification rather than a fix for a known vulnerability. There is no evidence in the commit or supplied references that this addresses a security issue or was reported by an outside researcher.

This commit is purely cosmetic: it removes two extra spaces of indentation from a list of web API route definitions in Bitcoin Core's REST interface. No code behavior, route order, or functionality changes.

This is a code cleanup change that lets Bitcoin Core tests create transaction IDs from hex strings at compile time instead of runtime. It does not change how the live network or wallet behaves, and it does not fix a security bug. It only makes test code stricter so that bad hardcoded hashes fail during compilation rather than when tests run.

This commit is a routine code cleanup in Bitcoin Core's logging system. It removes an old, confusing logging macro called LogPrintLevel and replaces its remaining uses with newer, clearer macros. It also updates some I2P log messages to say 'I2P SAM session' instead of just 'SAM session' for clarity, and adjusts tests to match. There is no security fix here.

This commit only changes a test file to make the unit test easier to read. It explicitly sets the log level to Debug inside the test, adds one extra debug log line, and replaces a longer logging macro with shorter ones. There is no change to the actual Bitcoin Core software that users run, and no security issue is present.

This is a routine logging cleanup in Bitcoin Core's inter-process communication (IPC) code. It changes how messages from the internal IPC library are written to the log file, mainly to prevent a harmless side effect where enabling detailed debug logging could accidentally suppress some log lines. There is no security vulnerability here.

This commit changes how Bitcoin Core prints log messages coming from the libevent networking library. Previously, all libevent messages went through a single logging path that could be rate-limited. Now, debug messages use the debug-only path, while info/warning/error messages use unconditional logging and are prefixed with 'libevent:'. The main effect is a minor behavior change in log formatting and rate-limiting, not a security fix or vulnerability.

This commit only adds a release note describing a prior change to the bitcoin-cli -addrinfo command. It does not change any code, behavior, or security properties of the software. The release note explains that -addrinfo now returns all known network addresses instead of a filtered subset, and that it requires a newer node version. There is no security issue in this documentation commit itself.

This commit is a simple code cleanup: it takes a block of code that built a simplified tree-shaped dependency graph inside one fuzz test and moves it into a reusable helper function named BuildTreeGraph. The behavior is unchanged; no security issue is introduced or fixed.

This is a one-line bug fix in a fuzz test (automated randomized test) for Bitcoin Core's transaction clustering logic. The test meant to check that running an optimization twice on a copy of a tree-shaped dependency graph produces the same result, but it accidentally ran the optimization on the original variable instead of the copy. That made the comparison trivial and useless. The fix corrects the variable name so the test actually exercises the intended behavior. It does not affect live Bitcoin node code, wallets, consensus, or network behavior.

This commit fixes a bug in an internal Bitcoin Core fuzz test (a randomized self-test used during development). The test was looping over transaction indices using the total transaction count, but some indices can be unused 'holes' in the generated test data. As a result, the test sometimes skipped valid transactions or accessed unused slots. The fix makes the loop iterate over only the actually-used positions. This appears to be a test-only correctness issue, not a vulnerability in live Bitcoin Core code.