Bitcoin Core

This commit adds a single configuration line telling CDash (a test-results dashboard) what time to consider the start of a 'nightly' test run. It has no effect on Bitcoin Core's code, network behavior, or user security.

This commit simply deletes a helper shell script that was used by Bitcoin Core maintainers as a Git pre-push hook. The script checked whether commits being pushed to the project's GitHub repository were cryptographically signed. It is being moved to a separate maintainer tools repository. There is no code change to Bitcoin Core itself, no vulnerability, and no security fix.

This commit fixes a minor double-space typo in a macOS build instruction document. It has no effect on software behavior or security.

This commit only updates two documentation files. It replaces a stale reference to the old Autotools 'configure script' with 'CMake configuration' in the NetBSD build guide, and fixes a typo ('SQlite' to 'SQLite') while simplifying a heading in the macOS build guide. There are no code changes and no security implications.

This commit simply moves some test command-line flags from one continuous integration (CI) test job to another. It does not change any production code, wallet logic, networking, or anything users interact with. There is no security issue here.

This commit fixes an off-by-one bug in Bitcoin Core's read-only wallet migration tool. The tool checks whether a Berkeley DB (BDB) wallet file is self-contained before migrating it. Due to a half-open loop, the tool was skipping the very last page of the database when verifying that all pages had their log sequence numbers (LSNs) reset. As a result, it could have accepted a wallet whose final page still depended on separate BDB log files, potentially leading to incomplete or inconsistent migration data. The fix changes the loop to include the last page.

This commit only updates user-facing help text and a tooltip to explain that wallets and indexes should be loaded and kept active while block pruning is enabled. It is a documentation-only change with no code behavior changes, no bug fix, and no security patch.

This commit only updates documentation links and adds Doxygen anchor comments in source code so that the developer documentation points to the right places. It does not change any program behavior, logic, or security settings.

This is a tiny code cleanup in a Bitcoin Core RPC command. It removes an unnecessary cast to uint64_t when reporting how many bytes were written to a file. The actual value being reported does not change, and there is no security issue.

This commit tweaks the Bitcoin Core dependency build system so that an environment variable used for reproducible builds (SOURCE_DATE_EPOCH) is cleared before generating package IDs. The goal is to avoid unnecessary rebuilds of dependencies when only that timestamp changes, improving build-cache reuse. There is no direct security vulnerability in the diff itself; it is a build-system hygiene change.

This commit adds a one-line configuration file telling CMake/CTest where to upload test results (a CDash dashboard URL). It does not change how Bitcoin Core is built or tested by default, and it does not introduce any security-relevant code change.

This commit simply adds a new person's PGP key to the project's security contact list in a documentation file. It is an administrative update with no code changes and no security vulnerability.

This commit fixes a bug in a Bitcoin Core fuzz test (a randomized testing harness), not in the main Bitcoin software. The test was building a sample P2SH (pay-to-script-hash) output incorrectly by placing an 'OP_EQUAL' instruction at byte 12 instead of byte 22. This only affects the test's internal data setup and has no effect on real transactions, wallets, or network behavior. The second change is a trivial typo fix in a comment.

This commit only changes a benchmark test file used to measure wallet coin-selection performance. It replaces an old, unrealistic benchmark with a more diverse and deterministic one. There is no change to production wallet code, consensus rules, networking, or any code that runs on real user wallets or nodes.

This is a minor code cleanup in a benchmark test file. It removes an unused wallet parameter from a helper function used only for performance testing of coin selection. The change does not affect live wallet behavior, network consensus, or user funds.

This is a minor code cleanup in a benchmark file. It changes a function parameter type from signed to unsigned to match how it is actually used, and removes a duplicated comment. It does not affect the live Bitcoin wallet or network code and has no security relevance.

This commit fixes a memory safety bug in Bitcoin Core's block validation. When checking a new block, the program creates a queue of script checks that may run on multiple threads in the background. It also precomputes some transaction data used by those checks. Previously, the precomputed data was destroyed before the background check queue finished, so the workers could read memory that had already been freed. An attacker could craft a malicious block to trigger this, potentially causing crashes, memory corruption, or worse. The fix simply moves the precomputed data variable so it is created before the queue and destroyed after it, guaranteeing the data stays alive as long as the checks need it.

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. The change makes the fuzzer exercise more code paths in the connection manager, but it does not alter the actual Bitcoin Core networking code that runs on real nodes. There is no security vulnerability here.

This commit only updates a help text string in bitcoin-cli. It clarifies that the -rpcclienttimeout option does not work for local inter-process (IPC) connections. There is no code behavior change and no security fix.

This commit only changes a code comment explaining why the blockfilterindex gets 5% of the total cache budget. It adds a note that a typical two-week offline gap produces a working set of about 200 kB, which fits comfortably within that 5% allocation. No code behavior, cache sizes, or logic are modified.

This change loosens a security sandbox only for one 32-bit Linux continuous-integration test job. Docker's newer default profile was blocking an old 32-bit system call used for sockets, causing the CI job to fail. The patch tells Docker not to apply its default seccomp filter to that container so the tests can run. It does not change Bitcoin Core code that end users run, and it does not appear to be a fix for a vulnerability in Bitcoin itself.

This is a pure variable-name cleanup in Bitcoin Core's ARM SHA-256 code. The old names (ABEF_SAVE/CDGH_SAVE) were misleading labels; the new names (ABCD_SAVE/EFGH_SAVE) match how ARM's SHA-256 instructions actually order the hash state. No instructions, values, or behavior change.

This commit adds a new public function to Bitcoin Core's libbitcoinkernel library that lets outside programs ask the kernel to perform basic, context-free checks on a transaction (for example, whether it has valid outputs and no duplicate inputs). It is purely an API addition: it exposes an existing internal validation routine through a C interface and adds tests. There is no bug fix, no change to consensus rules, and no indication of a security vulnerability.

This is a minor code hygiene change that adds a missing C++ standard library header (<concepts>) to a utility header file. It does not change program behavior, fix a vulnerability, or introduce any security-relevant functionality. It is an 'include what you use' (IWYU) cleanup.

This commit changes a single internal lock in Bitcoin Core's networking code from a recursive mutex (one that lets the same thread lock it multiple times safely) to a plain non-recursive mutex. It also adds many compile-time and runtime checks to make sure no code path tries to lock it twice. The change is defensive hardening: it makes the locking rules stricter so that accidental deadlocks or re-entrancy bugs are caught earlier, but it does not by itself fix a known, exploitable vulnerability.