Bitcoin Core

This commit is a pure rename of a test-only helper class from NodeClockContext to FakeNodeClock, plus renaming its variables from clock_ctx to clock. It touches only test, benchmark, and fuzz code. There is no change to runtime Bitcoin node behavior and no security relevance.

This is a test-only code cleanup. It swaps old mock-time helpers for a newer test helper (NodeClockContext) in benchmarks and unit tests. The commit message explicitly says it does not change behavior, and the diff shows only mechanical replacements in test/bench files with no changes to production code.

This is a tiny test-only code cleanup. It removes a +1 second adjustment in a test helper constructor that was meant to prevent mock clock timestamps from looking like they moved backward due to rounding. The change only affects Bitcoin Core's internal unit tests and has no impact on the live Bitcoin network or wallet software.

This is a minor internal test-only change in Bitcoin Core. It moves a mock clock setup earlier in a unit test so that simulated connection times are recorded consistently. There is no change to production code, no user-facing effect, and no security vulnerability.

This commit only adds a release note documenting that two RPC commands now return a 'method not found' error when a specific optional feature is not enabled. It is purely documentation and contains no code changes.

This commit only adds two new test assertions to an existing functional test file. It verifies that two Bitcoin Core RPC commands (getprivatebroadcastinfo and abortprivatebroadcast) return a documented error when the -privatebroadcast feature is not enabled. There is no change to production code, no bug fix, and no security vulnerability being patched.

This commit makes two Bitcoin Core RPC commands—getprivatebroadcastinfo and abortprivatebroadcast—return a clear 'method not available' error when the optional -privatebroadcast feature is turned off. Previously these methods may have been callable even though the underlying feature was inactive, which could have led to confusing or misleading results rather than any direct loss of funds.

This commit fixes a one-line bug in a Bitcoin Core fuzz test (an automated testing tool). The test was supposed to check that serializing and then deserializing HD keypaths produced the same data, but it accidentally wrote the deserialized result back into the original map. This made the test's final check always pass, so the round-trip was not actually being tested. It is a test-only bug, not a vulnerability in live Bitcoin Core code.

This is a small fix inside Bitcoin Core's internal fuzz-testing harness. Fuzz testing feeds the program many random inputs in sequence; the harness is supposed to reset global state between inputs so each test starts clean. The reset code already cleared the regular mock clock but forgot to clear a separate 'steady' mock clock. That meant one fuzz input could leave a fake time value behind, polluting later inputs and making fuzz results less reliable. The patch adds one line to clear that steady mock clock too. It is a test-infrastructure bug, not a vulnerability in live Bitcoin node code.

This is a minor code-quality change. It fixes a test linting script so it also checks test files that use a simpler Boost test setup (BOOST_AUTO_TEST_SUITE), and renames one test suite to match its filename. There is no security issue here.

This commit only changes a continuous integration (CI) configuration file for running tests on ARM processors. It adds a Python package needed for inter-process communication (IPC) tests. There is no change to the Bitcoin Core software that users run, and no security issue is present in the diff.

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.