Bitcoin Core

This commit only touches documentation and test code. It removes an outdated comment about how pruned nodes track partially downloaded blocks and fixes a timing bug in a test where wallet status was being checked from a stale snapshot instead of live data. There are no changes to production code, no security fix, and no vulnerability.

This commit only changes a test file. It adjusts which block height is invalidated in an existing functional test so that the test exercises a specific edge case involving duplicate block processing in pruned nodes. There is no change to production code, so it does not introduce or fix a live vulnerability by itself. It is a test-coverage improvement.

This Bitcoin Core update fixes a bug where, during a deep chain reorganization on a pruned node, the same block entries could accidentally be added twice to an internal waiting list. If processed twice later, this could corrupt an ordered set used to choose the best chain, potentially causing crashes or undefined behavior. The fix prevents duplicates and adds a safety check.

This commit is a small fuzz-test improvement. It fixes an obvious test bug where the same function was being called twice with the same argument, and instead calls it with both possible arguments, then adds assertions about the results. It does not change any production wallet, consensus, or networking code, and there is no security fix or vulnerability indicated.

This is a tiny test-only cleanup that swaps a plain Python assert for a custom helper that prints better error messages when a test fails. It does not change any production code, network behavior, or security logic.

This commit only changes a fuzz test file (a special kind of automated test that feeds random data to the code to find bugs). It rewrites how a concurrent-read fuzz target works, replacing a result-comparison approach with an oracle-based assertion approach and reusing a global thread pool. There is no change to production Bitcoin Core code, no fix to a real vulnerability, and no security-relevant change to how the software behaves on real networks or wallets.

This commit adds a new automated test to Bitcoin Core. The test checks what happens when a user cancels a wallet rescan while importing descriptors. It does not change any production wallet code; it only adds test coverage. There is no security vulnerability here.

This commit only adds a new test case to Bitcoin Core's test suite. It checks that the wallet's importdescriptors RPC returns a specific error message when used during an in-progress assumeutxo background sync. There is no change to production code, no bug fix, and no security vulnerability being introduced or patched.

This commit only adds a new automated test to Bitcoin Core. It checks that if you try to import wallet descriptors while the wallet is already busy rescanning the blockchain, the second import attempt is rejected with a clear error message. There is no change to production wallet code, so this patch does not fix or introduce any live security issue by itself.

This is a minor cleanup of a Bitcoin Core test file. It renames a helper function parameter from 'different_key' to 'different_field' and combines two separate length checks into one three-argument equality assertion. There is no change to production code, no security fix, and no behavior change in what the test verifies.

This commit is a code cleanup that adjusts which C++ header files are included in the project's benchmark code and a few related source files. It enables a stricter 'include what you use' (IWYU) check for the benchmark directory so missing or unnecessary #include lines are treated as errors in continuous integration. There is no change to program logic, no bug fix, and no security-relevant behavior.

This commit simply removes two unused C++ standard library header includes (<compare>) from source files because a code-quality tool (IWYU) now flags them after the CI's standard library version was bumped. There is no functional code change, no bug fix, and no security relevance.

This commit updates several Bitcoin Core automated testing scripts to use a newer version of the underlying Linux container image (Ubuntu 26.04 instead of Ubuntu 24.04 or Debian testing). The compiler version is kept the same, and the change only affects internal continuous integration (CI) environments, not the Bitcoin software users run. There is no indication this fixes or introduces a security vulnerability.

This commit simply swaps the Linux distribution used in Bitcoin Core's automated testing environment from Debian Trixie to Ubuntu 26.04. It updates container image names and a comment in a Valgrind suppression file. There is no change to the Bitcoin software itself, no bug fix, and no security-relevant behavior change.

This commit fixes a rare crash in Bitcoin Core's networking code. When a user called a specific RPC command to fetch a block, the program could crash with an assertion failure if a peer disconnected at exactly the wrong moment. The fix moves a lock earlier so the peer's state cannot be cleaned up while the RPC thread is still using it. It is a stability bug, not a code-execution vulnerability, and requires precise timing to trigger.

This is a small internal cleanup of a test file. It swaps a hand-rolled mock clock helper for a standard test utility called SteadyClockContext. There is no change to the actual Bitcoin network code, no bug fix, and no security-relevant behavior change.

This commit only changes Bitcoin Core's internal test code. It replaces the old global SetMockTime() helper with a new local FakeNodeClock object in three test files so that test time adjustments are scoped to each test and easier to read. There is no change to the actual Bitcoin node software that users run, so it cannot affect live wallets, transactions, or network security.

This commit is a test-only cleanup. It replaces scattered mock-time calls with a single shared fake clock in the test harness, making test behavior clearer and removing a misleading comment. It does not change production Bitcoin Core code or fix any security bug.

This is a minor code cleanup in Bitcoin Core's internal benchmarking (performance testing) code. It changes a function parameter from std::string to std::string_view to avoid unnecessary header includes. There is no security relevance.

This commit simply updates the version of the LLVM compiler toolchain used in automated testing from 22.1.3 to 22.1.7. It is a routine CI maintenance change with no apparent security relevance.

This is a Bitcoin Core continuous integration (CI) build script change. It removes the libunwind runtime from an LLVM/Clang library build used for sanitizer testing and adds a comment explaining why. There is no user-facing code change, no wallet or consensus change, and no security fix or vulnerability introduced.

This commit is a simple rename of an internal helper macro from UNIQUE_NAME to BITCOIN_UNIQUE_NAME. The change prevents a potential future build failure on Windows because a Windows system header also defines UNIQUE_NAME. It does not change program behavior, fix a vulnerability, or affect live network code.

This commit only adds a new test case to Bitcoin Core's test suite. It checks that trying to import a wallet descriptor into an encrypted wallet fails with a helpful error message when the wallet is still locked. There is no change to production wallet code, no bug fix, and no security vulnerability being addressed.

This commit removes a redundant internal lock called cs_LastBlockFile from Bitcoin Core's block storage code. The developer argues that the lock was unnecessary because another lock, cs_main, already protects the same data. The change replaces the old lock with explicit annotations and checks that cs_main is held. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a code cleanup and simplification.

This is a test-only change that adds a safety guard to prevent two test helper objects from being used at the same time. It does not affect the live Bitcoin network or production code, and there is no security vulnerability being fixed.