Bitcoin Core

This Bitcoin Core commit removes a custom `Clear()` method from a wallet coin-selection helper struct and replaces its uses with a full default reset (`available_coins = {}`). The stated reason is to avoid accidentally leaving fields partially reset in the future. The change is defensive code cleanup; there is no direct evidence in the commit or supplied references that it fixes an active security vulnerability or exploitable bug.

This commit fixes a subtle programming bug in Bitcoin Core's peer-to-peer networking code. A local network address score counter could, in theory, overflow when repeatedly incremented, which is 'undefined behavior' in C++ and could potentially cause the program to misbehave or crash. The fix makes the counter stop increasing once it reaches the maximum integer value, and adds tests to confirm that behavior.

This commit is a routine CI infrastructure change. It tells Bitcoin Core's GitHub Actions build system to use a faster local cache service (called 'Warp') for Docker image layers, instead of GitHub's slower default cache. There is no change to Bitcoin's actual code, consensus rules, wallet handling, or network behavior. It is not a security fix and does not introduce an obvious security issue based on the supplied materials.

This commit only changes a continuous integration (CI) test script. It adds the Python package 'pyzmq' to the list of packages installed for a memory-sanitizer (MSAN) test job, so that a ZeroMQ-related functional test can run. It does not change any production code, wallet logic, networking code, or anything users run.

This is a one-line change to a Bitcoin Core CI (continuous integration) script for macOS. It swaps the Python package name 'zmq' for 'pyzmq' when installing test dependencies. The project page for 'zmq' on PyPI says it is effectively an alias for 'pyzmq' and recommends using 'pyzmq'. This is a routine build/test maintenance fix with no apparent security relevance.

This commit fixes a wallet migration bug in Bitcoin Core. When converting old-style wallets to modern descriptor wallets, the migration code could process the same BIP 32 seed more than once because it identified seeds by a 'seed ID' that changes depending on a technical detail (public-key compression) that does not actually affect the seed's value. The fix now detects duplicate seeds by comparing the derived master extended public key, preventing redundant or conflicting descriptors from being created during migration. There is no direct evidence this is exploitable as an attack; it appears to be a correctness and robustness fix.

This commit adds build-system support so that Bitcoin Core's graphical user interface (GUI) and QR-code library can be compiled on OpenBSD. It does not change how Bitcoin validates transactions or handles wallets; it only fixes compilation and packaging issues for a new operating-system target. There is no indication this introduces a security vulnerability.

This is a test-only fix. It changes one functional test so that a bitcoin-cli subprocess is launched with the project's standard valgrind wrapper and uses the test node's temporary data directory instead of the developer's real default Bitcoin directory. There is no change to production code, no vulnerability, and no security risk to users.

This commit adds a new fuzz test that exercises Bitcoin Core's database wrapper (CDBWrapper) with many simultaneous read threads while a background database compaction runs. It also makes the test's mock LevelDB environment thread-safe by adding a mutex around its task queue. The change is purely in test code and does not alter production behavior.

This commit is a simple code cleanup inside a fuzz test file. It pulls out a repeated block of code into a helper function named ConsumeDBParams() so it can be reused later. The commit message explicitly calls it a 'pure refactor with no behavior change,' and the diff only moves existing logic around without changing any values, checks, or program behavior.

This commit is a routine GitHub Actions CI optimization. It removes a separate 'runner selection' metadata job and instead directly decides whether to use fast internal (Warp) runners or standard GitHub-hosted runners based on the repository name. There is no security-relevant change to Bitcoin Core's code, build outputs, or secrets handling.

This is a minor build-system tweak. It adds one internal test target ('mptest') to a list of targets that should not be included in the compile_commands.json database used by developer tools like clang-tidy. There is no user-facing or security-relevant change.

This commit changes a single line in a Bitcoin Core test script. It makes the test recognize any IP address beginning with '127.' as a loopback address, instead of only '127.0.0.1'. This is a test-only fix to prevent false failures when VPNs or other software add extra loopback addresses. It does not change the Bitcoin Core software that users run, and it has no security impact.

This commit only updates a code comment in a header file to describe the current behavior of a cache used for tracking Bitcoin softfork deployment status. No executable code was changed, and there is no security impact.

This commit only updates documentation. It adds a release note and a BIP implementation list entry describing a prior code change (PR #34779) that makes Bitcoin Core ignore certain BIP 9 soft-fork signal bits per BIP 323. There is no code change here and no direct security risk in the commit itself.

This commit only adds a new test case to Bitcoin Core's existing test suite. It checks that the software does not produce spurious warnings for version bits that belong to deployments that have been explicitly disabled/ignored. There is no change to production code, no bug fix, and no security vulnerability in the commit itself.

This Bitcoin Core change narrows which version bits trigger live 'unknown soft fork' warnings from 29 bits down to 5, following the new BIP323 specification. It does not change how many bits exist in block headers or how test networks behave; it only reduces false or misleading upgrade alerts for bits that the network no longer treats as active deployment candidates.

This commit is a routine change to Bitcoin Core's continuous integration (CI) setup. It swaps the GitHub Actions cache for a faster third-party cache service (WarpBuild) on Warp runners, while keeping GitHub's cache as a fallback for forks. There is no change to the Bitcoin software itself, to wallets, transactions, consensus rules, or network code.

This change removes a default value for a network-connection setting called proxy_override. Previously, callers could leave it unset without thinking. Now every caller must explicitly pass a value, which helps prevent accidental mistakes about which proxy a connection uses. It is a defensive code-quality fix, not a patch for a known active bug or attack.

This commit only adds a new regression test file and registers it in the test runner. It does not change any production code in Bitcoin Core. The test verifies that if a private broadcast connection using the newer v2 transport fails, the node falls back to the older v1 transport through the Tor proxy. There is no security patch or vulnerability fix here.

This commit only changes a test file. It makes a wallet functional test more explicit by passing replaceable=False so the test reliably checks anti-fee-sniping locktime behavior, instead of relying on a coincidental wallet default. There is no change to production wallet or node code, so it does not fix a live security vulnerability.

This commit changes several Bitcoin Core kernel library functions so they crash the program (via assertions) instead of returning a null pointer when callers pass a null buffer with a non-zero length. It also tightens one function to require exactly 80-byte block headers. The change treats these as programmer errors rather than runtime failures, which can help catch misuse early but may cause denial-of-service crashes if an attacker can trigger those calls with bad inputs.

This is a test-only code change that restores the string format of an error message shown when a Bitcoin Core functional test encounters a JSON-RPC failure. It only affects test framework output formatting and has no bearing on the live Bitcoin Core software or its users' funds or network security.

This commit is a pure test-code refactoring. It moves a list of fake network addresses and a helper loop from one test file into the shared test framework so other tests can reuse it. No production Bitcoin Core code is changed, and nothing about how real nodes connect or broadcast is modified.

This commit is a simple code cleanup in Bitcoin Core's test suite. It moves a small helper that starts a temporary peer-to-peer listener from one test file into a shared test framework file so other tests can reuse it. There is no change to the actual Bitcoin network code, no change to how nodes communicate, and no security fix or vulnerability.