Bitcoin Core

This commit is a clean-up change to how Bitcoin Core formats its RPC help text. It replaces a slightly awkward way of hiding or summarising groups of help fields with a clearer helper function. There is no change to transaction handling, networking, wallet logic, or any code that processes untrusted data. It only affects the text users see when they call help commands.

This commit removes a single unnecessary trailing slash from a CMake build setting in Bitcoin Core's dependency build system. It is a cosmetic cleanup that silences a harmless developer warning in newer CMake versions. There is no security relevance.

This commit adds support for a new Bitcoin peer-to-peer message type called FEATURE, defined in BIP 434. It is infrastructure for negotiating optional protocol features during the initial handshake, not a finished feature itself. The code bumps the protocol version to 70017, registers the new message, and adds basic rules: FEATURE messages must appear between VERSION and VERACK, the peer must have negotiated the new version, and the payload must contain a feature ID of at least 4 characters plus up to 512 bytes of feature data. Unknown feature IDs are ignored. There is no immediate security issue visible in the diff, but the change touches network message handling and version negotiation, which are sensitive parts of the node.

This commit only adds a new automated test file for a Bitcoin protocol feature called BIP434. It does not change any production code that runs on real Bitcoin nodes. The test checks how a node handles a new P2P network message called FEATURE, including when it should accept or disconnect peers. Because no actual node behavior is modified, this commit cannot by itself introduce a security vulnerability or fix one in live software.

This commit only updates Bitcoin Core's internal Python test framework to recognize a new P2P protocol version (70017) and a new 'FEATURE' message type as part of BIP 434 support. It does not change the actual Bitcoin node software, network rules, or consensus behavior. There is no security issue here.

This commit is a privacy-focused code cleanup. Bitcoin nodes normally announce a current protocol version number when connecting to peers. For a special 'private broadcast' connection type used to hide transaction origins, the commit makes the node advertise an older fixed protocol version (70016) instead of the latest one. This prevents a small metadata leak that could help an observer identify these privacy connections by their version number. It is not a fix for an exploitable bug.

This commit is a simple test cleanup. It changes one functional test so that it creates multiple wallets on a single Bitcoin Core node instead of spinning up three separate nodes. There is no change to the actual Bitcoin Core software that users run, and no security issue is introduced or fixed.

This commit adds a convenience feature to Bitcoin Core's serialization code: it lets a lightweight read-only string type (std::string_view) be written directly to a data stream, instead of first copying it into a std::string. It also explicitly deletes the matching 'Unserialize' function, because you cannot deserialize into a read-only string_view. The change is a small, safe API improvement with no obvious security relevance.

This commit adds a new helper called LimitedVectorFormatter that lets Bitcoin Core reject serialized data containing vectors (lists of values) that are larger than an allowed maximum. It is a defensive building block, not a fix for an active bug. The commit itself does not change any existing network or file parsing code, so it cannot by itself prevent or cause any vulnerability.

This commit simply moves existing build setup code from one shell script into a new shared file so other scripts can reuse it. There is no change to what the code does, no new features, and no security fix or vulnerability introduced.

This is a one-line change in Bitcoin Core's internal test framework. It only affects how error messages are displayed when a test RPC call times out, suppressing an extra Python traceback. It does not change any production code, network behavior, or security logic.

This commit changes how several Bitcoin Core test scripts clean up after themselves. Previously, cleanup code ran even when a test failed, which could hide the real failure behind extra error messages. Now cleanup is skipped if the test raises an exception, so the original failure is reported clearly. This only affects the project's internal test suite, not the live Bitcoin network or end users.

This is a tiny type-cleanup change. The developer replaced the custom CAmount type with the standard int64_t type in two places where a string is being converted to a numeric amount. In Bitcoin Core, CAmount is defined as int64_t, so the compiled code is identical and behavior does not change. It is essentially a code-quality fix with no security effect.

This is a tiny internal test-only code cleanup. It changes one function parameter in test helper code from the generic 'int' type to the project's specific 'CAmount' type, which is used for money values. It does not change any production code, network behavior, or wallet logic, and there is no security issue here.

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.