Bitcoin Core

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

This commit fixes a flaky test, not a security bug. The test checked for specific peer ID numbers in log messages, but because of unpredictable scheduling in the test framework, those IDs could differ between runs. The fix removes the specific ID numbers from the expected log messages so the test passes reliably. No production code or network behavior was changed.

This commit only changes comments and documentation in the Bitcoin Core source code. It renames terminology from 'background chainstate' to 'validated chainstate' in comments and updates the class description for ChainstateManager. No executable code was modified, so it cannot introduce a security vulnerability or fix one.

This commit is a straightforward internal code cleanup in Bitcoin Core. It merges two nearly identical blocks of code that set up a snapshot-based chainstate into a single helper method called AddChainstate. There is no change to network rules, consensus logic, wallet behavior, or user-facing functionality. It is purely a refactoring to reduce duplication.

This is a code cleanup (refactor) in Bitcoin Core that makes each chainstate object remember which block it is trying to reach, instead of asking the global chain manager. It changes how background validation of UTXO snapshots is tracked, replacing some runtime checks with internal assertions. There is no obvious security bug introduced, but because it touches consensus-adjacent validation logic, any mistake could theoretically affect chain synchronization behavior.

This is a fix to a broken test in Bitcoin Core's own test suite. The test was supposed to check the heights of two chainstates after a simulated node restart, but an `if` condition was always false, so the check never actually ran. The commit also corrects the expected height value. It does not change any production code that runs on real Bitcoin nodes, so it cannot directly affect live network security.

This is a simple internal code cleanup in Bitcoin Core. It renames and slightly rewrites a helper function used to pick which copy of the blockchain data indexes should look at. There is no change in behavior and no security issue visible in the commit.

This commit is a straightforward internal code cleanup. It moves the logic that decides where the UTXO database files live from several scattered places into a single new Chainstate::StoragePath() method. There are no user-facing behavior changes, no bug fixes, and no security-related changes.

This is a routine internal code cleanup in Bitcoin Core. It introduces a new helper method called CurrentChainstate() and replaces a few older helper calls with it. There is no change to network rules, consensus logic, or user-facing behavior, and nothing in the commit suggests a security fix.

This commit is a straightforward internal code cleanup in Bitcoin Core. It removes a helper method called GetAll() and replaces its uses with direct access to an internal list of chainstates. The change also adds a small safety check to ignore chainstates based on invalid snapshots when considering new block candidates. There is no indication this fixes an active security bug or introduces a vulnerability.

This is a routine code cleanup (refactor) in Bitcoin Core. It pulls three nearly identical loops that call ActivateBestChain() into a single new helper method called ActivateBestChains(). There is no change to what the program actually does, no new user-facing behavior, and no indication of a security fix.

This is a straightforward internal code cleanup in Bitcoin Core. It removes a small helper function called SnapshotBlockhash() and replaces its uses with direct access to an existing internal field. There is no change to user-facing behavior, no bug fix, and no security-relevant change.