Bitcoin Core

This commit changes the build setup for Bitcoin Core's Guix deterministic build environment so that GCC no longer builds the libgomp library. libgomp is the GNU Offloading and Multi Processing Runtime Library, used for OpenMP parallel programming. Removing it reduces the attack surface and build artifacts, but there is no direct evidence in the commit that a specific vulnerability is being fixed.

This commit changes Bitcoin Core's Guix build recipe to stop GCC from building the libquadmath library. Quadmath provides extra-precision floating-point math, which Bitcoin Core does not need. Removing it shrinks the build environment and reduces the chance that unnecessary code accidentally gets linked into release binaries. There is no direct evidence in the commit that this fixes an active security bug.

This commit simply removes a single line of information—the 'Starting Block' field—from the peer details window in Bitcoin Core's graphical user interface. It is a cleanup following an earlier deprecation and does not change any network, consensus, or wallet behavior. There is no security issue here.

This commit only renames the word 'command' to 'message type' in comments and a debug log string. It is a documentation cleanup with no functional code changes and no security impact.

This commit simply deletes an unused internal function called FixLinearization and its associated test. There is no security relevance: no bug is fixed, no behavior changes, and no live code path is altered.

This commit is an internal optimization to how Bitcoin Core organizes and prioritizes groups of related transactions (clusters) in its memory pool. It introduces new quality states that let the node defer fixing non-topological orderings until later, instead of doing the work immediately. There is no indication in the commit or title that this fixes a security bug; it is described as an optimization.

This is a Bitcoin Core code cleanup that removes a special internal quality state called NEEDS_SPLIT_ACCEPTABLE from the transaction graph (txgraph) module. The change simplifies how clusters of related transactions are tracked after transactions are removed or fees change. It does not appear to be a security fix; it is described by the author as a simplification enabled by an upcoming algorithm improvement. There is no disclosed security relevance and no independent researcher credited.

This is a routine internal optimization in Bitcoin Core's transaction graph code. It removes two calls to a helper named PostLinearize and updates comments, replacing an explicit cleanup step with work done by a newer algorithm (SFL). There is no indication this fixes or introduces a security bug.

This is a routine internal refactor of Bitcoin Core's transaction-cluster linearization code. It lets the linearization algorithm accept an existing ordering that may not follow dependency rules, and automatically fix it. There is no indication this change addresses a security bug or is exploitable.

This commit simply moves existing Python linting code from one file to another without changing what it does. It is a code cleanup change with no security relevance.

This commit is a simple housekeeping change: it moves two existing code-checking helper functions into a new file and runs a code formatter on another file. There is no change to Bitcoin's actual behavior, no bug fix, and no security relevance.

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.