Bitcoin Core

This commit is a pure code reorganization: it moves four existing C++ lint checks from the main Rust file into a new dedicated module named lint_cpp.rs. No lint logic, rules, or behavior changed. It is comparable to moving files into a new folder without editing their contents.

This commit is a straightforward code reorganization: it moves three documentation-related lint checks from the main test runner file into a new dedicated Rust module, and renames one function from lint_doc to lint_doc_args. No behavior changes, security fixes, or vulnerability patches are present.

This commit simply reorganizes existing code. It moves four text-format lint checks (for trailing whitespace, missing trailing newlines, tab characters, and commit message formatting) from the main Rust file into a new module named lint_text_format.rs. No lint logic, command behavior, or security-sensitive code was changed.

This commit simply moves existing helper functions from one Rust source file to a new utility file. It is a code cleanup change with no functional or security impact on the Bitcoin Core software itself. The moved code is part of the internal lint test runner, not the Bitcoin node that users run.

This Bitcoin Core patch adds a missing validation check during PSBT (Partially Signed Bitcoin Transaction) parsing. Specifically, it now rejects MuSig2 aggregate and participant public keys that are not cryptographically valid, rather than silently accepting malformed or invalid key bytes. This prevents downstream code from operating on bad public keys, which could lead to incorrect behavior or crashes.

This Bitcoin Core change tweaks how a node tells other nodes about its own internet address when they first connect. Previously, the node's own address could get bundled with other addresses in the same network message. Because new connections only get one temporary 'token' that lets a single address through, the node's own address could accidentally be dropped by the peer's rate limiter. The fix sends the first self-announcement in its own dedicated message so it isn't crowded out by other addresses. It also makes the initial address exchange cleaner for inbound connections.

This is a one-line fix inside a single automated test file. The test was occasionally failing because the test's internal expected timestamp was being read after the simulated clock had already advanced, so the expected value could be slightly newer than the test anticipated. The fix simply records the expected time before advancing the simulated clock. It does not change any production code, network behavior, or wallet logic.

This commit adds a new, safer way for external mining programs to ask Bitcoin Core for the pieces needed to build a coinbase transaction, instead of receiving a complete dummy transaction they must edit. It is a defensive API improvement, not a fix for an active bug or vulnerability. The old method is kept but marked deprecated.

This change hides one piece of information—the 'startingheight' field—from the getpeerinfo RPC output unless the user explicitly enables it with a deprecation flag. It is a planned API cleanup, not a security fix. There is no vulnerability or exploit here.

This is a simple code cleanup change that renames an internal constant from ALWAYS to FORCE_FLUSH. It does not change what the software does, only how a label is spelled. There is no security issue here.

This Bitcoin Core change tweaks how the in-memory UTXO cache is flushed to disk during certain RPC operations and snapshot creation. Previously these operations always wiped the cache, which could cause temporary performance slowdowns. The patch adds a non-wiping flush mode and uses it where the cache contents are still useful. It is a performance/robustness improvement, not a fix for an active security vulnerability.

This is a minor test-only fix. It moves a block-syncing step so that a wallet-related test only runs when the wallet feature is actually compiled in. There is no change to Bitcoin Core's production code, no security bug, and no user impact.

This commit simply adds a new documentation file archiving the release notes for Bitcoin Core version 30.1. It contains only text describing what changed in that release and credits contributors. No program code was modified, so it cannot introduce a security vulnerability or fix one.

This commit is a quality-assurance cleanup for Bitcoin Core's test runner. It changes how tests are excluded from a comma-separated list to one test per `--exclude` flag. There is no security relevance: it does not touch consensus code, networking, wallet handling, or any production behavior. It only affects internal test tooling and CI scripts.

This commit reorganizes how Bitcoin Core runs its benchmark sanity checks. Previously, the bench_bitcoin -sanity-check command was run as a separate CI step and as a CMake test. Now, it is run as part of the functional test suite, with each individual benchmark sanity check executed in parallel alongside other functional tests. There is no change to production code, consensus logic, wallet handling, or network behavior. It is purely a testing infrastructure change.

This commit only adds plumbing so the Bitcoin Core test framework can locate and run the existing bench_bitcoin benchmark executable during tests. It does not change any network, wallet, consensus, or cryptographic code, and it introduces no user-facing behavior.

This commit only fixes five instances of accidental repeated words (like 'the the' or 'for for') inside code comments and documentation strings. No actual program logic was changed, so it cannot affect how the software runs or introduce any security issue.

This is a routine documentation update for building Bitcoin Core on OpenBSD. It changes the recommended OpenBSD version from 7.6 to 7.8 and replaces instructions to build Cap'n Proto from source with a simpler command to install it via the OpenBSD package manager. There is no code change and no security relevance.

This is a small developer-tooling fix for Bitcoin Core's fuzzing test runner. It changes how a Python script calls Git so the script works correctly no matter which folder you run it from. There is no security vulnerability or user-facing risk.

This is a small code cleanup change in Bitcoin Core. It removes an unused option from a function that checks whether a group of transactions (a 'package') is properly ordered. The option was always set to 'true' everywhere it was used, so the code path for 'false' was never reachable. The change simplifies the function and its tests but does not alter actual behavior or fix any security issue.

This commit only updates the copyright year from 2025 to 2026 in three documentation/legal files. It does not change any executable code, build logic, or network behavior, and has no security relevance.

This is a test-only change in Bitcoin Core's functional test suite. It adjusts a test to wait for orphan transactions to be cleared after a peer disconnects, because a previous code change made orphans disappear faster than the test originally expected. There is no change to production code, no vulnerability, and no security risk to users.

This commit only changes a single test file. It simplifies how test transactions are created by using zero-fee parent transactions instead of carefully calculated low-but-nonzero fees. There is no change to Bitcoin Core's actual network, consensus, or wallet code, so it cannot affect real users or funds.

This commit only removes an outdated explanatory paragraph from a documentation file. No code, logic, or behavior of the Bitcoin Core software is changed. It is purely a cleanup of stale text that referenced a note removed in an earlier pull request.

This commit only turns on a Python style lint rule (E713) that prefers 'not in' over 'not ... in'. It updates test scripts and helper tools to match the style, with no changes to the Bitcoin Core software that users run. There is no security issue here.