Bitcoin Core

This commit simply bumps the GitHub Actions 'checkout' step from version 5 to version 6 in the project's continuous integration (CI) workflow file. It does not change any Bitcoin Core source code, consensus rules, wallet logic, or network behavior. There is no indication of a security fix or vulnerability.

This commit is a portability fix for compiler warnings about missing braces when initializing IPv6 address constants. It introduces platform-specific macros so the code compiles cleanly on illumos and Microsoft Visual C++ without changing behavior. 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 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 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 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 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 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 is a code cleanup (refactor) in Bitcoin Core's assumeutxo snapshot feature. It renames functions and changes how the snapshot validation code receives its inputs, so it no longer relies on hardcoded internal chainstate names. The change does not alter the actual snapshot validation logic or security checks; it is preparation for future work to reduce how long a global lock is held during snapshot validation. There is no direct security vulnerability in this patch.

This is a code cleanup (refactor) in Bitcoin Core that changes how the program tracks whether a chainstate is based on an unvalidated snapshot (assumeutxo). It replaces a simple disabled flag with explicit state tracking. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a maintainability and correctness improvement.

This is a code cleanup (refactor) change in Bitcoin Core. It replaces a three-value enum called ChainstateRole with a small struct carrying two yes/no flags: whether a chainstate is fully validated and whether it is historical (used for assumeutxo background validation). The logic that decides how wallets, indexes, and network processing react to block notifications is preserved; only the internal data type and comparisons are changed. There is no security fix or behavior change intended here.

This commit adds a new GUI feature that lets a user restore a wallet backup file and then automatically convert it from the older 'legacy' wallet format to the newer 'descriptor' wallet format. It shows confirmation and progress dialogs, copies the backup into the normal wallets folder without changing the original file, and then runs the existing migration logic. There is no obvious security bug in the change itself; it is a user-facing convenience feature built on top of existing wallet restore and migration code.

This commit is a simple code cleanup in the Bitcoin Core graphical wallet. It takes the actual wallet-migration steps out of the user-facing 'migrate' function and puts them into a new internal helper function called 'do_migrate'. The user confirmation dialog and the migration logic itself are unchanged; the code is just reorganized so the same migration steps can be reused later. There is no security issue visible here.

This commit is a small, non-security code cleanup. It exposes an existing internal option called load_after_restore through the wallet interface so that callers can choose whether a restored wallet should be loaded automatically. The GUI code is updated to pass true, preserving the previous behavior. There is no indication this fixes a vulnerability or introduces a security risk.

This commit is a code-style and static-analysis configuration change. It tells the clang-tidy linter to allow discarding function return values when the call is explicitly cast to void, and updates a few places in benchmark, test, and HTTP server code to use that style instead of a temporary variable marked 'maybe unused'. There is no security-relevant behavior change.

This commit updates the Boost dependency used by Bitcoin Core's build system from version 1.88.0 to 1.90.0. It also removes a custom patch that was previously needed to skip compiling certain Boost.Test libraries, because the newer Boost version now includes that functionality directly. There is no indication in the commit that this fixes a security vulnerability.

This is a small internal cleanup in Bitcoin Core's transaction-broadcasting code. It replaces a hand-rolled 'promise/future' wait mechanism with an existing helper function that does the same job. There is no security bug being fixed here; the change just makes the code simpler and easier to maintain.

This commit is a small internal cleanup: it reads the '-capturemessages' debug/logging setting once at startup and stores it in a class member, instead of looking it up from global command-line arguments every time a message is sent. It also adds a test helper to set the flag directly. There is no security fix here and no behavior change visible to users.

This is a code cleanup change that turns on a static-analysis check (clang-tidy 'bugprone-unused-return-value') and makes small, behavior-preserving edits so the codebase passes the new check. It does not fix a security bug or change how the software behaves at runtime.

This commit is a simple automated rename that changes every use of the logging macro LogPrintf to LogInfo across 15 source files. The commit message and the included verification script confirm it is a pure refactor with no intended behavior change. There is no security issue here.

This commit is a code cleanup that replaces old-style 'count the number of matching entries' checks with newer, clearer 'does this container contain the key' checks. It does not change program behavior, fix a bug, or address a security issue. It is purely a readability and maintainability improvement.

This commit is a pure code cleanup: it replaces older-style container lookups like `m.count(k)` with the newer, clearer `m.contains(k)` across many files. The behavior is identical, so there is no security impact.

This commit is a pure code cleanup: it replaces verbose 'find ... == end()' checks with the simpler 'contains()' method on C++ containers. There is no change in behavior, no bug fix, and no security impact.