Bitcoin Core

This is a straightforward code cleanup: a function that asks the user questions used to accept an unused 'caption' parameter. The only caller always passed an empty caption, so the developer removed the parameter entirely. No behavior changes, no security implications.

This commit is a routine code cleanup in Bitcoin Core's test-only fuzzing utilities. It adjusts which C++ header files are included in two test files and fixes two minor comment typos. There is no change to the actual Bitcoin network code, consensus logic, wallet handling, or any code that runs in production.

This change updates Bitcoin Core's Windows CI workflow to install the Python `pyzmq` package before running functional tests. It is a build/test infrastructure fix with no direct effect on the Bitcoin Core software users run, and no security relevance is apparent from the commit itself.

This commit adds new automated tests to Bitcoin Core that exercise two known bugs in the experimental multiprocess (IPC) interface: one where disconnecting during a long-running call can crash the node, and another where sending too many calls to the same server thread triggers a 'thread busy' error. The tests document current behavior so future library upgrades can be checked against it. The commit does not fix the bugs; it only adds test coverage.

This commit changes Bitcoin Core's build configuration. It removes one compiler flag (-fdebug-prefix-map) from the main CMake build and adds it instead to the Guix reproducible-build script. The change is described by the project as fixing a 'confusing and brittle' build setup, not as a security fix. It primarily affects how source-code paths are embedded in debug information, which can influence build reproducibility and debuggability, but does not by itself create or fix a vulnerability in the running software.

This is a tiny formatting fix in Bitcoin Core's test runner. On Windows, the test output includes a hidden carriage-return character ('\r') that was making the closing parenthesis in log messages appear on a new line. The patch simply trims whitespace from the captured text so the log looks tidy. It does not change any network, wallet, consensus, or node behavior.

This commit only changes a user-facing help string. It corrects the description of the -logips option from saying it controls IP addresses in 'debug output' to saying it controls IP addresses in 'log output' generally. No code behavior changes, no security fix, no vulnerability.

This commit adds a simple informational log message warning users that enabling debug logging may write privacy-sensitive details (like transaction IDs) into log files, so they should be careful when sharing logs. It is a user-awareness/privacy-hardening change, not a fix for an exploitable security flaw.

This commit changes Bitcoin Core's internal test tooling so that self-check warnings always cause test runs to fail, instead of only doing so when a special '--ci' flag was passed. It also removes the now-unused '--ci' flag from CI scripts. This is a testing-hygiene improvement, not a fix for a security vulnerability in the Bitcoin software itself.

This change is a privacy hardening patch for Bitcoin Core's 'private broadcast' feature, which lets users send transactions over anonymity networks like Tor or I2P. Previously, routine log messages about private broadcasts—including transaction identifiers and peer details—were written to the default debug.log file. Because users often share their logs for troubleshooting, this could accidentally reveal which transactions they created. The patch moves those detailed messages behind a special debug logging category, so they only appear when a user explicitly enables it. Warnings stay visible but no longer include sensitive identifiers.

This is a small change to a Bitcoin Core functional test. It adds a check that when the test interrupts (stops) a running node, the node exits with status code 0 (success). Previously the test only waited for the node to stop without checking the exit code. This is a test-hardening improvement, not a fix to the Bitcoin Core software itself.

This is a harmless code cleanup in Bitcoin Core's test suite. A large test function was split into two smaller, easier-to-read functions. No production code or security behavior changed.

This commit only changes Bitcoin Core's continuous integration (CI) configuration. It adds a Windows CI step to run a specific functional test that was previously excluded because of UTF-8 limitations in an old release. There is no change to Bitcoin Core's actual code, network behavior, or wallet logic, and no security issue is introduced or fixed.

This is a small code cleanup in Bitcoin Core's wallet creation RPC. It replaces a local error-handling block with an existing shared helper function, and adds one missing error code (encryption failure) to that helper. There is no direct evidence this fixes a security vulnerability; it is best characterized as a maintainability/refactoring change that incidentally makes error reporting more consistent.

This is a documentation-only change. A developer renamed a function called PackageMempoolChecks to PackageRBFChecks and removed an outdated comment. No actual transaction-validation logic was changed, so this cannot affect security or behavior.

This is a straightforward code cleanup in Bitcoin Core's graphical user interface. It replaces older-style std::bind calls with modern C++ lambda functions when connecting internal message-box and question handlers. There is no security-relevant change: the same functions are called with the same arguments, and no behavior changes.

This is a minor code cleanup that removes an extra semicolon inside a macro definition. The macro is used to declare signal-handling functions in Bitcoin Core's user-interface layer. All places that use the macro already add their own semicolon, so the one inside the macro was redundant. There is no security or functional change.

This commit updates the libmultiprocess library inside Bitcoin Core. The most important change fixes a classic multi-threaded 'fork safety' bug in the process-spawning code. Before the fix, the code could run a callback inside the child process after fork(), which can cause the child to deadlock forever if the parent happened to be holding a lock at the exact moment of fork. The patch moves that callback work into the parent before fork(), and also makes the child process use simple, non-throwing error handling after fork. Other changes are mostly documentation, CI build setup, and version tracking.

A one-character bug fix in Bitcoin Core's PSBT (Partially Signed Bitcoin Transaction) handling. The code used the wrong comparison in a safety check, so it was possible to request an input index exactly equal to the number of inputs. That would read one element past the end of the list, which can cause a crash or undefined behavior. The fix changes the check so it correctly rejects that out-of-bounds index.

This is a minor code cleanup in Bitcoin Core's internal benchmarking test code. It changes how a macro is written so callers must add a semicolon, and it updates a type alias style. It does not affect the live Bitcoin network, wallets, or consensus rules.

This commit is a code-quality fix for Bitcoin Core's internal benchmark test harness. It removes a confusing use of line numbers in benchmark names and adds checks to prevent duplicate benchmark names. It does not affect the live Bitcoin network, wallet funds, consensus rules, or node security.

This commit is a cleanup change to Bitcoin Core's internal benchmark test code. It removes an unused 'priority level' argument from the BENCHMARK macro and from all benchmark definitions. The change does not affect the live Bitcoin network, wallet funds, node operations, or any security-sensitive code.

This commit removes a command-line option called -priority-level from Bitcoin Core's internal benchmark testing tool. It is a code cleanup change affecting only the benchmark test harness, not the live Bitcoin network node software. There is no security relevance.

This is a minor user-interface improvement, not a security fix. The Bitcoin Core wallet restore dialog used to silently do nothing when a user left the wallet name blank. Now it shows a clear error message explaining that the wallet name cannot be empty. There is no vulnerability here.

This commit only adds a release note documenting that a mempool feature called the 'CPFP Carveout' was removed in Bitcoin Core version 31.0. It does not change any code, fix a bug, or address a security vulnerability. It is purely informational documentation for users and developers.