Bitcoin Core

This change fixes a wallet shutdown timing issue in Bitcoin Core. Previously, when a wallet was unloaded, some background blockchain notifications could still run after the wallet had already finished shutting down. The patch makes the wallet explicitly wait for those pending notifications to finish before completing shutdown, preventing potential crashes or use-after-free problems.

This commit adds a new public interface method that lets callers wait for background notification processing to finish. It is a straightforward API addition with no security relevance visible in the diff or commit message.

This commit only changes documentation links from absolute GitHub URLs to relative markdown links. It does not modify any executable code, network behavior, cryptography, wallet logic, or configuration handling. There is no security relevance.

This commit is a straightforward modernization of the Bitcoin Core codebase: it replaces older C++ standard-library iterator-based calls like std::sort and std::unique with their newer C++20 'ranges' equivalents (std::ranges::sort, std::ranges::unique). The behavior of the code is intended to stay exactly the same; only the syntax is updated. There is no security fix or vulnerability being addressed here.

This is a code-cleanup change in Bitcoin Core that replaces confusing custom comparison operators on a fee/size data structure with clearly named wrapper classes. It does not fix a known vulnerability or change network behavior; it is a refactor to make the code easier to understand and maintain.

This is a one-line fix in a test script for Bitcoin Core's ZeroMQ (ZMQ) notification interface. It makes a test socket timeout scale with the test framework's configurable slowdown factor, preventing flaky test failures on slow machines. It does not change production code and has no security impact on real Bitcoin nodes or wallets.

This commit only adds a new test to Bitcoin Core. It checks that the wallet software will re-broadcast a transaction it learned about from another peer, not just transactions it created itself. There is no change to production code, so it does not fix or introduce a security issue on its own.

This commit simply moves a Valgrind suppressions file from one directory to another. It does not change any code that runs in production, nor does it alter the suppressions themselves. All references to the file's path are updated so tests and documentation still point to the right location. There is no security issue here.

This is a one-line fix in Bitcoin Core's test framework. It ensures that when running tests under the Valgrind memory-checking tool, the correct suppressions file is found even if the test script is accessed through a symbolic link. It does not change the Bitcoin node software itself and has no security impact on users' funds or the network.

This commit fixes a single grammar typo in a comment within a test file. It changes 'drain' to 'drains' in a sentence explaining test behavior. There is no code change, no functional change, and no security relevance.

This is a routine continuous-integration (CI) configuration tweak. It changes the starting port number used by Bitcoin Core's test runner in one GitHub Actions workflow, so it no longer overlaps with a port used by the Cirrus CI cache service. There is no security vulnerability here—just a port-collision avoidance fix for automated testing infrastructure.

This is a build-fix change only. A developer fixed a compiler warning that caused compilation to fail on FreeBSD 15 because a system header changed the type of a constant used in a network-routing helper. There is no change to program logic, no security bug, and no way to exploit it.

This commit only updates two comments in a test file. It replaces the word 'Appveyor' (an old Windows continuous-integration service) with 'Windows' to reflect that the project no longer uses Appveyor. No actual code behavior changes, and there is no security relevance.

This change updates Bitcoin Core's Windows continuous integration (CI) scripts to download a test data file used by unit tests. It is a build/test infrastructure fix, not a change to the Bitcoin node software itself, and it does not introduce a security vulnerability.

This is a harmless test-only code cleanup. It moves a status print statement from one test helper script into another shared test utility, with no change to what the program actually does. There is no security relevance.

This commit simply moves an existing download helper function from one test script into its own small utility file. There are no functional code changes, no bug fixes, and no security-related modifications.

This is a routine fix to Bitcoin Core's GitHub Actions CI workflow. Two Windows test jobs were accidentally trying to save their build-tool cache under the same name, which could cause a harmless cache-save conflict. The patch makes only one of the two jobs save the cache. It does not change Bitcoin Core software, wallet code, networking, or cryptography, and has no security relevance for users.

This is a harmless code cleanup in Bitcoin Core's test suite. It moves a small helper class called HasReason from a large test-framework header into a smaller, more focused header so that simple unit tests don't need to pull in the entire testing framework. There is no change to how the software behaves in production, no bug fix, and no security issue.

This commit only adds new test code to Bitcoin Core. It expands an existing unit test to check that a background worker pool (ThreadPool) returns the correct error messages when tasks are submitted while the pool is not started, interrupted, or stopped. There is no change to production code and no security fix or vulnerability is introduced.

This is a minor cleanup of a test file. It changes how one unit test checks that error messages from background tasks are correctly passed back to the caller. There is no change to the actual Bitcoin Core program that users run, only to the test code, and no security relevance.

This commit is a pure test-code refactoring. It moves helper functions that let Boost test macros print custom Bitcoin types (like transaction IDs and 256-bit numbers) into a shared test header, and replaces several specific helpers with one generic template. It does not change any production code, network behavior, or wallet logic, and it introduces no security fix or vulnerability.

This is a tiny test-only change that adds the server's response text to an error message shown when a Bitcoin Core functional test receives an unexpected non-JSON HTTP response. It only affects the test framework's debugging output and does not change production Bitcoin Core code, network behavior, or security boundaries.

This commit adds a new automated test for Bitcoin Core's internal thread pool. It checks that when the thread pool is stopped while tasks are still waiting, the thread that calls Stop() helps finish those remaining tasks. There is no change to production code and no security fix or vulnerability is described.

This commit changes how Bitcoin Core's internal thread pool shuts down. Instead of the shutdown thread passively waiting for worker threads to finish leftover tasks, it now pitches in and processes tasks itself while workers finish up. The goal is a faster node shutdown when many RPC/REST requests are still queued. The change itself is a performance/cleanup improvement, not a security fix.

This commit only adds a new automated test to Bitcoin Core. It checks that a worker thread pool still finishes tasks that were already waiting in line after the pool is told to stop accepting new work (Interrupt). There is no change to production code and no security fix or vulnerability patch.