Bitcoin Core

This commit is a code cleanup (refactor) that changes how a lookup table of script verification flag names is created and accessed. It moves the table from a global variable constructed at program startup to a function that creates the table the first time it is called. There is no change to transaction validation rules, no bug fix, and no security-relevant behavior change.

This commit simply raises the minimum supported Clang compiler version from 16 to 17 and removes a now-unnecessary C++ deduction guide. It is a routine build-system/maintenance change with no security relevance.

This commit simply bumps a GitHub Actions helper from version 4 to version 5 in the project's continuous-integration workflow. It is a routine dependency update with no visible security relevance in the diff itself.

This is a routine subtree update for the libmultiprocess library used by Bitcoin Core. The bulk of the changes are developer-facing improvements: adding log levels, fixing typos, updating CI sanitizer settings, and adding tests. The most notable functional change is a fix for a crash that could occur when multiple IPC calls were made on the same thread at the same time. The fix makes the code throw a controlled 'thread busy' error instead of crashing. It is a stability/reliability improvement rather than a traditional security vulnerability fix.

This commit removes a Windows-specific helper class that converted command-line arguments from Windows' native wide-character format to the standard character format used by the rest of the program. The change is a cleanup to avoid using a C++ standard library feature (`std::wstring_convert`) that is being phased out. It is not a security fix and does not appear to introduce a vulnerability; it simply changes how Windows command-line arguments are handled, likely relying on a newer mechanism elsewhere.

This is a routine code cleanup in Bitcoin Core. It removes helper functions that let custom filesystem path objects be passed directly to C++ file streams, because the project no longer uses them that way and the C++ standard now discourages it. The commit updates a handful of file-opening calls to use the underlying standard path object instead. There is no security bug being fixed here.

This is a portability fix for compiling Bitcoin Core on Windows with newer versions of the libc++ standard library. It does not change runtime behavior on currently working platforms; it only ensures the code still builds on a less-common Windows toolchain. There is no security vulnerability being fixed here.

This commit only adds a new functional test to Bitcoin Core. It checks that the wallet correctly refuses to spend an unconfirmed TRUC (version 3) transaction output when that output already has an unconfirmed parent—in other words, it prevents creating a third unconfirmed generation in a chain. There is no change to production wallet, consensus, or networking code, so it does not introduce or fix a live security vulnerability on its own.

This Bitcoin Core wallet patch prevents users from accidentally creating invalid or poorly structured transactions. Specifically, it stops the wallet from spending coins that come from an unconfirmed 'TRUC' (version 3) transaction which already has parent transactions in the mempool. Without this check, the wallet could build a transaction chain that violates Bitcoin's new TRUC rules, causing the new transaction to be rejected by the network instead of confirmed.

This commit is a routine code cleanup in Bitcoin Core's RPC (remote procedure call) handling. It replaces some uses of std::string with std::string_view to avoid unnecessary string copying and modernize the API. There is no security-relevant change here—no bug fix, no vulnerability patch, and no behavior change visible to users.

This commit only changes a single test file. It makes an existing functional test more reliable by using mock time instead of looping up to 100 times and hoping for the right timing. There is no change to the actual Bitcoin Core node software, so it cannot affect real users, wallets, or network behavior.

This commit changes how Bitcoin Core wallets store temporary secret signing data (MuSig2 'secnonces') for multi-signature transactions. Previously, these secrets may have been kept in a more general signing provider; now they are kept inside the wallet's descriptor key manager. The change is defensive: it ensures these one-time secrets stay only in memory and are never written to disk, which prevents a dangerous nonce-reuse bug that could leak private keys. The commit itself is a small code move/addition, not a complete fix, and the commit message does not call it a security vulnerability.

This commit only adds a new automated test file for the MuSig2 multi-signature wallet feature. It does not change any production wallet, cryptography, or consensus code. There is no security-relevant change to the software users run.

This commit adds a new helper function that combines multiple MuSig2 partial signatures into one final Schnorr signature for Bitcoin transactions. It is a feature addition, not a fix. The code includes verification of each partial signature before aggregation, which is good defensive practice. There is no evidence in the commit or supplied references that this change addresses a security vulnerability.

This commit adds a new helper function for creating MuSig2 cryptographic nonces in Bitcoin Core. MuSig2 is a multi-signature scheme that lets multiple parties jointly sign a transaction. The change is a feature addition: it introduces a nonce generator, a session ID helper, and wiring for signing code. There is no direct evidence in the commit or supplied references that this fixes a known security vulnerability. It is best treated as a normal code addition that may carry implementation risks rather than a disclosed security patch.

This Bitcoin Core change makes the wallet's signing code record key-origin metadata for both the internal key and the final output key of a Taproot address, not just the internal key. That metadata helps external signers (like hardware wallets) understand which key path was used to derive the address. On its own this is a small correctness/data-availability fix; it does not directly change how coins are spent or introduce an obvious exploit, but missing key-origin data could previously have caused signing failures or user confusion for Taproot key-path spends.

This commit adds a new function that lets a Bitcoin Core wallet create a partial MuSig2 signature as part of a multi-party signing process. It is a feature addition, not a fix. There is no direct evidence in the commit or supplied references that this change introduces a security vulnerability.

This change tweaks how Bitcoin nodes schedule transaction announcements to inbound peers. Previously, all inbound peers were told about new transactions on the same shared timer, which could let a spy with multiple connections figure out when a node first learned of a transaction and possibly trace it back to its source. The patch splits that timer by network group so that different peer networks get staggered announcement times, making that timing-based fingerprinting harder. It is a privacy-hardening fix, not a fix for a code crash or theft bug.

This change updates a Bitcoin Core GitHub Actions workflow so that it no longer downloads and runs a third-party JavaScript action (ilammy/msvc-dev-cmd) to set up the Microsoft Visual Studio build environment on Windows. Instead, it uses a small PowerShell script that runs a tool already installed with Visual Studio (vswhere.exe) and then calls the official Microsoft batch file (vsdevcmd.bat). The main benefit is reducing supply-chain risk: the project no longer depends on an external, pinned-but-third-party action that could be compromised or behave unexpectedly. There is no direct vulnerability being fixed in Bitcoin Core's own code.

This commit is a routine cleanup of Bitcoin Core's functional test code. It removes a helper method called convert_to_json_for_cli that was used to wrap arguments when tests were run against the command-line bitcoin-cli tool. The change only affects internal test scripts and has no impact on the live Bitcoin network, wallets, or node security.

This commit is a documentation-only correction. It removes an incorrect mention of the bitcoin-wallet tool from a design document that describes which programs use the inter-process communication (IPC) library. There is no code change and no security impact.

This commit is a harmless build-system fix. It tells the CMake installer to also include the manual page (help documentation) for the main `bitcoin` command-line program when installing Bitcoin Core. There is no security issue.

This commit adds a placeholder manual page file for the bitcoin binary. It contains only documentation text and instructions for generating real manpages later. There is no executable code, no configuration change, and no security relevance.

This change fixes a bug in how Bitcoin Core handles repeated compact-block transaction messages from peers. In debug builds, receiving multiple blocktxn messages for the same block could trigger an internal consistency check (Assume) crash because the code tried to look up information from a header that had already been cleared. The patch detects the empty-header situation, marks the peer as misbehaving, and returns early instead of crashing. It is a robustness fix that prevents a debug-only crash and tightens handling of misbehaving peers.

This commit is a routine update of the non-English user-interface translations for the Bitcoin Core Qt (graphical) wallet. It adds, removes, and reorders translated text strings and drops a number of very low-translation-coverage locale files. There is no executable code change, no change to wallet logic, networking, consensus, or cryptography, and no security-relevant behavior is introduced or fixed.