Bitcoin Core

This commit is a pure code move: it takes the CreateMuSig2PartialSig function out of the CKey class in key.cpp/key.h and places it in the musig.cpp/musig.h module. The function's logic is unchanged, and the only caller is updated to use the new free-function name. There is no security fix or behavior change.

This commit is a code cleanup: it moves a function that creates MuSig2 cryptographic nonces from the CKey class into a dedicated musig module. The actual logic and security behavior are unchanged; only where the code lives and how callers reference it are modified.

This commit simply adds a public accessor function that returns an internal cryptographic context object. It does not change how keys are created, signed, or verified, and it introduces no new behavior that could be exploited. It is a routine code-organization change to support future work.

This is a documentation-only change that adds a clarifying note to the fuzzing quickstart guide. It explains that using the libfuzzer-nosan preset creates binaries in a different directory (build_fuzz_nosan) than the regular libfuzzer preset (build_fuzz). There is no code change and no security issue.

This is a minor test-only cleanup. It removes a TODO comment and two command-line flags that forced a specific address type in one of Bitcoin Core's automated functional tests. The change has no effect on production code, user wallets, or network behavior.

This commit is a pure cleanup of the project's Python linter configuration file (ruff.toml). It replaces a long explicit list of individual style/error checks with shorter category codes and a small 'ignore' list. There is no change to Bitcoin Core's actual code, behavior, or security.

This Bitcoin Core wallet patch fixes a bug where the software underestimated the size (and therefore the required transaction fee) of certain externally provided transaction inputs. The fix passes the actual outpoint being spent into the size-estimation function, so the fee calculation can account for extra data that some inputs require. The included test demonstrates that without the fix, the estimated size is one byte too small.

This commit only turns on three new lint checks in the project's Python code style tool (ruff). These checks warn when text contains Unicode characters that look like ordinary ASCII letters but are actually different characters, which can be confusing or misleading. There is no code behavior change, no bug fix, and no security patch.

This commit is a defensive hardening change for Bitcoin Core's handling of BIP32 'chain codes'—secret-derived values used when creating child keys from a master key. Previously these values were stored as ordinary 256-bit numbers that could remain in memory after use. The change makes ChainCode a dedicated type that securely wipes its own memory when it goes out of scope, similar to how private keys are already handled. It is a preventive security improvement rather than a fix for an active exploit.

This change tweaks how Bitcoin Core's MuSig2 multi-signature code keeps track of active signing sessions. Previously, the session identifier was based only on the public keys and the transaction hash. Now it also includes each participant's public nonce. This matters because the same keys and transaction can legitimately be signed more than once, and without the nonce in the identifier the code could confuse two different signing sessions and risk reusing or misplacing secret nonce data. The commit itself is framed as a safety improvement, not a fix for a known active bug or exploit.

This commit only adds a new automated test to Bitcoin Core. It does not change any production code. The test checks that when a node restarts after pruning a stale side-chain block, the internal block-tracking data structure does not incorrectly mark the block as 'unlinked.' There is no fix or vulnerability patch here—just extra test coverage for an existing invariant.

This commit fixes a bug in Bitcoin Core's descriptorprocesspsbt RPC command. Previously, the command could mark a partially-signed Bitcoin transaction (PSBT) as 'complete' and return a finalized transaction hex even when one of the signatures was actually invalid. The fix makes the command verify signatures cryptographically, not just check that signature data is present. The new test deliberately corrupts a signature and confirms the command now correctly reports the PSBT as incomplete.

This is a small documentation-only change to Bitcoin Core release notes. It clarifies how developers should check for Taproot support after the 'taproot' field was removed from the getdeploymentinfo RPC. No code behavior changed, and there is no security vulnerability in the commit itself.

This commit is a defensive hardening patch for Bitcoin Core's HMAC code. It wipes two temporary memory buffers that previously held sensitive key-derived data after the HMAC operation finishes. The change reduces the risk that leftover key material could leak through memory dumps, core dumps, or side-channel attacks, but it does not fix an active bug or known exploit.

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.