Bitcoin Core

This is a harmless code cleanup in Bitcoin Core's test suite. A large test function was split into two smaller, easier-to-read functions. No production code or security behavior changed.

This commit only changes Bitcoin Core's continuous integration (CI) configuration. It adds a Windows CI step to run a specific functional test that was previously excluded because of UTF-8 limitations in an old release. There is no change to Bitcoin Core's actual code, network behavior, or wallet logic, and no security issue is introduced or fixed.

This is a small code cleanup in Bitcoin Core's wallet creation RPC. It replaces a local error-handling block with an existing shared helper function, and adds one missing error code (encryption failure) to that helper. There is no direct evidence this fixes a security vulnerability; it is best characterized as a maintainability/refactoring change that incidentally makes error reporting more consistent.

This is a documentation-only change. A developer renamed a function called PackageMempoolChecks to PackageRBFChecks and removed an outdated comment. No actual transaction-validation logic was changed, so this cannot affect security or behavior.

This is a straightforward code cleanup in Bitcoin Core's graphical user interface. It replaces older-style std::bind calls with modern C++ lambda functions when connecting internal message-box and question handlers. There is no security-relevant change: the same functions are called with the same arguments, and no behavior changes.

This is a minor code cleanup that removes an extra semicolon inside a macro definition. The macro is used to declare signal-handling functions in Bitcoin Core's user-interface layer. All places that use the macro already add their own semicolon, so the one inside the macro was redundant. There is no security or functional change.

This commit updates the libmultiprocess library inside Bitcoin Core. The most important change fixes a classic multi-threaded 'fork safety' bug in the process-spawning code. Before the fix, the code could run a callback inside the child process after fork(), which can cause the child to deadlock forever if the parent happened to be holding a lock at the exact moment of fork. The patch moves that callback work into the parent before fork(), and also makes the child process use simple, non-throwing error handling after fork. Other changes are mostly documentation, CI build setup, and version tracking.

A one-character bug fix in Bitcoin Core's PSBT (Partially Signed Bitcoin Transaction) handling. The code used the wrong comparison in a safety check, so it was possible to request an input index exactly equal to the number of inputs. That would read one element past the end of the list, which can cause a crash or undefined behavior. The fix changes the check so it correctly rejects that out-of-bounds index.

This is a minor code cleanup in Bitcoin Core's internal benchmarking test code. It changes how a macro is written so callers must add a semicolon, and it updates a type alias style. It does not affect the live Bitcoin network, wallets, or consensus rules.

This commit is a code-quality fix for Bitcoin Core's internal benchmark test harness. It removes a confusing use of line numbers in benchmark names and adds checks to prevent duplicate benchmark names. It does not affect the live Bitcoin network, wallet funds, consensus rules, or node security.

This commit is a cleanup change to Bitcoin Core's internal benchmark test code. It removes an unused 'priority level' argument from the BENCHMARK macro and from all benchmark definitions. The change does not affect the live Bitcoin network, wallet funds, node operations, or any security-sensitive code.

This commit removes a command-line option called -priority-level from Bitcoin Core's internal benchmark testing tool. It is a code cleanup change affecting only the benchmark test harness, not the live Bitcoin network node software. There is no security relevance.

This is a minor user-interface improvement, not a security fix. The Bitcoin Core wallet restore dialog used to silently do nothing when a user left the wallet name blank. Now it shows a clear error message explaining that the wallet name cannot be empty. There is no vulnerability here.

This commit only adds a release note documenting that a mempool feature called the 'CPFP Carveout' was removed in Bitcoin Core version 31.0. It does not change any code, fix a bug, or address a security vulnerability. It is purely informational documentation for users and developers.

This commit is a routine feature addition to Bitcoin Core's transaction-cluster linearization code. It adds a second optimization pass that splits large 'chunks' of transactions into smaller pieces that have the same fee rate, while preserving the overall quality of the resulting block template. The change is algorithmic and does not introduce any obvious security vulnerability; it is not a bug fix or a security patch.

This commit only adds a new regression test to Bitcoin Core. It does not change any production wallet, consensus, or mempool code. The test exercises a scenario involving v2 and v3 (TRUC) transactions across a blockchain reorganization, likely to ensure a previously reported issue stays fixed. There is no patch to runtime behavior here, so it does not introduce or fix an exploitable vulnerability by itself.

This commit simply moves a small helper function that reads a socket's local address from one source file to another, making it usable by more parts of the program. The actual code behavior is unchanged; it is a routine refactoring, not a security fix or vulnerability.

This commit is a performance optimization, not a security fix. It changes how Bitcoin Core decides whether it is still downloading the historical blockchain (Initial Block Download, or IBD). Previously, every check for IBD status had to grab a global lock, which could slow down busy code paths. Now the status is cached in an atomic variable and only updated at specific safe points. There is no evidence in the commit or supplied references that this fixes a vulnerability or is being exploited.

This commit is a routine code cleanup in Bitcoin Core. It pulls out a small, existing check ('is the chain tip recent enough?') from one function into a reusable helper, and slightly tidies a nearby block-import wrapper. There is no security-relevant behavior change.

This commit is a simple rename and logic inversion inside Bitcoin Core. It changes an internal cached flag from 'finished IBD' to 'is IBD' so the code avoids double negatives. The actual behavior of the program is unchanged.

This commit only adds a new unit test and fixes a couple of comment typos. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The test documents when Bitcoin Core considers itself to have finished Initial Block Download (IBD).

This commit fixes a bug in Bitcoin Core's handling of partially signed Bitcoin transactions (PSBTs) that use the MuSig2 multi-signature scheme. Previously, when reading certain MuSig2 fields, the code accepted invalid public keys (points that are not valid on the Bitcoin elliptic curve). The fix adds checks that reject these invalid keys during deserialization, turning potential crashes or undefined behavior into clean error messages. The commit also adds test cases with deliberately bad keys to confirm they are rejected.

This commit simply deletes unused helper code from two Python scripts in the contrib/ directory. No security vulnerability is introduced or fixed; it is a routine cleanup change.

This commit tightens an internal assumption in Bitcoin Core's coin cache. It removes a special code path that handled the theoretical case where a parent view returns a spent coin, replacing it with a hard assertion that this never happens. It also simplifies related bookkeeping and sanity checks. The change is defensive cleanup rather than a fix for a known exploitable bug.

This commit only updates a documentation file (doc/bips.md) to list that Bitcoin Core supports BIP 433 (Pay to Anchor) as of version 28.0. It does not change any executable code, network rules, or wallet behavior. There is no security issue here.