Bitcoin Core

This commit only adds a new automated test and a small test helper. It checks that the Bitcoin Core IPC mining server returns a clean error when given invalid data, instead of crashing. There is no change to production code, so it does not introduce or fix a live security vulnerability by itself.

This commit adds a new automated test to Bitcoin Core. It checks that a mining-related function called createNewBlock() wakes up quickly when a new block is submitted, instead of waiting for an internal cooldown timer. There is no code change to the actual Bitcoin node software—only a new test in the test suite.

This is a code cleanup change only. It tells the Include What You Use (IWYU) tool that the project's main synchronization header (`sync.h`) re-exports another header (`threadsafety.h`), so other files don't need to include both. No program behavior changes, no security fix.

This is a minor code cleanup and documentation change. It replaces direct includes of the standard C++ time library (`<chrono>`) in two files with a project-specific header (`util/time.h`) and adds a comment explaining that `util/time.h` is intended as a drop-in replacement for `<chrono>`. There is no functional code change and no security impact.

This commit only adds a comment explaining how two source-code files relate to each other. It does not change any program behavior, fix a bug, or alter executable code.

This commit only adds documentation to the developer notes. It explains when and why developers may use a specific code-comment directive (`IWYU pragma: export`) for header files. There is no code change, no bug fix, and no security relevance.

This commit is a simple code reorganization: it moves two helper classes (StdMutex and StdLockGuard) from one header file to a new header file and updates which files include them. There is no change to how the code behaves, no bug fix, and no security-related change.

This commit changes how Bitcoin Core's Windows continuous-integration builds select a release-only configuration for vcpkg dependencies. It replaces a workaround that patched vcpkg's source code with a built-in triplet name. There is no security-relevant change to the software users run.

This commit removes a temporary build-system workaround for the Windows CI pipeline. The workaround forced an older CMake compatibility setting when compiling a dependency (libevent) through the vcpkg package manager. Microsoft has now fixed the underlying issue upstream, so Bitcoin Core no longer needs the local override. There is no change to Bitcoin Core's runtime code, consensus rules, wallet handling, or network behavior.

This is a build-system fix for people who compile Bitcoin's dependency Qt on a Mac but intend to run it on Windows. It swaps a wrong variable (host_os) for the correct one (build_os) and turns off two Apple-specific version checks that do not apply when the final target is Windows. There is no indication this changes runtime behavior or fixes a security vulnerability.

This commit only changes Bitcoin Core's internal test and benchmark code. It replaces an older way of faking the system clock during tests (SetMockTime) with a newer helper object (NodeClockContext). No production code is touched, so this cannot affect real users, wallets, or the live network.

This is a tiny internal test-only code cleanup in Bitcoin Core's fuzzing harness. It replaces a direct call that sets a fake global clock with a helper object that automatically resets the fake clock when it goes out of scope. The commit message explicitly says it does not change behavior. There is no indication this affects real Bitcoin node software, wallets, or the live network.

This is a tiny test-only code change that lets Boost unit tests print std::chrono::time_point values when a check fails. It only touches a test helper header, adds a standard library include, and defines a stream output operator. There is no production code change and no security relevance.

This is a minor code cleanup in Bitcoin Core's network address handling. It replaces two separate calls that both retrieved the current time with a single shared call. There is no security-relevant change; the behavior is functionally identical.

This is a minor code cleanup that swaps one internal clock type for another equivalent one. It does not change what the program actually does, so it has no security relevance for users.

This commit changes only the internal test runner for Bitcoin Core. It forces Python's Global Interpreter Lock (GIL) to be enabled when running functional tests, because some optional Python libraries used during testing can misbehave or print warnings on newer 'free-threaded' Python builds where the GIL is disabled by default. There is no change to Bitcoin Core's production code, network behavior, wallet handling, or consensus logic.

This is a routine code cleanup: a missing standard library header is added to one central file, allowing nine other files to stop including it directly. It does not change program behavior or fix any security issue.

This commit fixes a bug in Bitcoin Core's transaction fee-bumping feature. When a user tried to increase the fee on a transaction that was tied to a very large cluster of unconfirmed transactions, the software could not calculate the required fee and returned an empty value. The old code then tried to use that empty value anyway, causing the program to crash (in the GUI) or throw an unhandled exception (in command-line tools). The fix simply checks for the empty value and returns a proper error message instead of crashing.

This commit renames a test-only constant from WAIT_TIMEOUT to TEST_WAIT_TIMEOUT because the old name conflicts with a Windows system macro. It is a build hygiene fix inside the test suite and does not change any production code or affect live Bitcoin network behavior.

This commit is a documentation-only change. It updates the help text for the importdescriptors command to show that error responses include a numeric 'code' and a text 'message', instead of a vague placeholder. No code behavior changed, and there is no security issue here.

This is a routine reliability improvement for Bitcoin Core's automated Windows build scripts. It adds a single retry with a short pause when a build-generation step fails, likely due to temporary network hiccups during CI runs. There is no security relevance.

This commit only changes a single test file. It removes a debug-log assertion and slightly simplifies how a test node is restarted during a reindex test. There is no change to production Bitcoin Core code, no security fix, and no vulnerability.

This is a tiny test-only code cleanup. It changes one argument name from verbose=0 to verbosity=0 inside a test helper function. It does not touch live Bitcoin network code, wallets, consensus rules, or any user-facing behavior. There is no security relevance.

This commit fixes a flaky test in Bitcoin Core's own test suite. It replaces a method that restarted a test node and relied on timing-sensitive behavior with a simpler helper that directly syncs blocks to a specific height. There is no change to production code, no security vulnerability, and no risk to real users.

This commit removes the `dsymutil` tool from Bitcoin Core's dependency build system. `dsymutil` is a macOS developer tool used to bundle debug symbols into a separate file. The change is a cleanup: the build system no longer looks for or configures this tool because it is reportedly no longer needed. There is no indication this fixes or introduces a security vulnerability.