Bitcoin Core

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.

This commit simply adds a new documentation file containing the release notes for Bitcoin Core version 30.2. It does not change any program code, configuration, or build scripts. There is no security-relevant change in the diff itself.

This commit only changes Bitcoin Core's internal test framework. It switches test-only SOCKS5 proxy and P2P mock servers to use dynamic port allocation (port=0) so automated tests are less likely to fail with 'address already in use' errors. There is no change to production Bitcoin node code, no user-facing behavior change, and no security vulnerability being fixed.

This commit adds an exception list to Bitcoin Core's commit-verification tool. Normally the tool rejects commits whose verification uses the older SHA-1 algorithm. The change lets one specific commit (aeaa67a9eac0decb89c60a67f9755ca10cbcc1d9) skip that SHA-1 check. It is a maintenance/operational tweak rather than a fix for a runtime vulnerability in Bitcoin itself, but it weakens a security control for that one commit.

This is a minor fix to a Bitcoin Core functional test, not to the main Bitcoin software. It moves an 'import random' statement to the top of the test file and changes one test helper to use a wallet-provided output script instead of a hardcoded one. There is no security issue in the production code and no vulnerability being patched.

This is a small internal code cleanup in Bitcoin Core's transaction acceptance logic. It moves a check so that a package-replacement-specific validation routine is only called when actually processing a package RBF (replace-by-fee), rather than having that routine itself decide to return early when there is no conflict. The change does not alter the overall validation outcome and is described by the author as a refactor.

This commit removes a single internal safety check (an 'Assume' assertion) in Bitcoin Core's wallet code. The assertion could incorrectly fail during a blockchain reorganization, causing the wallet process to abort unexpectedly. Removing it prevents a potential crash, but does not by itself fix any underlying logic bug in how transactions are handled.

This commit only changes a test file. It renames a test method and adds explicit checks that a wallet finishes rescanning after restarting pruned Bitcoin nodes. There is no change to production code, no fix for a live bug, and no security-relevant behavior change in the software users run.

This commit only changes a test file. It refactors an existing test for failed wallet migration and adds more test cases for wallets with relative and absolute paths. There is no change to production wallet code, so it does not introduce or fix a security issue in the software users run.

This commit fixes a minor behavior bug: if a user interrupted Bitcoin Core while it was starting up, the program would wrongly report that it had failed (non-zero exit code). The change makes an interrupted startup return a normal success exit code, matching how an interrupt is treated after startup is complete. It also updates the graphical (GUI) startup path to recognize when the user asked for shutdown during initialization.

This commit simply adds a new trusted PGP key to the list used by Bitcoin Core's commit verification script. It is an administrative change, not a code fix or vulnerability patch. There is no indication of a security issue being addressed.

This commit fixes an internal consistency check in Bitcoin Core's mini-miner, a testing and block-template simulation tool. Previously, the code assumed that a transaction's total fees including ancestors were always at least as large as the transaction's own fee. That assumption can be false when a user uses the prioritisetransaction feature to assign a negative fee to a transaction. The old assumption could cause debug builds to abort (via Assume) or mask incorrect accounting, though this appears limited to the mini-miner and not consensus-critical mining code.

This change adds a safety check to a Bitcoin Core fuzz test (an automated testing harness, not production wallet code). It rejects fuzz inputs that would create descriptor strings with unusually long 'leaf' segments before feeding them to the wallet's descriptor parser. The goal is to prevent the fuzzer from wasting time or hitting limits on pathologically large inputs, not to fix a user-facing security bug.

This is a small change to a Bitcoin Core fuzz test (a developer testing tool that feeds random data to code to find bugs). It makes the test skip more kinds of unusually complex descriptor strings so the fuzzer spends time on realistic inputs instead of wasting compute on pathological ones. It does not change any production wallet or network code, so it has no direct effect on real users' funds or node security.

This commit fixes a build-time test failure in the software packaging process. The osslsigncode tool's own test suite started failing because it contains a hardcoded check that expires after 2025. The fix makes the tests run as if the date were January 1, 2025, so they pass again. This is a build/test maintenance change, not a security fix for Bitcoin Core itself.