Bitcoin Core

This commit only adds three documentation path strings to the build configuration file. It does not change any compiler behavior, security checks, or executable code. There is no security relevance visible in the diff.

This is a small test-only change in Bitcoin Core's Python testing framework. It moves where an internal networking event loop is created so it is created on the same thread that later runs it, rather than on the main test thread. The goal is to stop an intermittent crash/abort that happens on Windows when running functional tests. It does not change the Bitcoin node itself, consensus rules, wallet handling, or network protocol, and there is no indication it fixes a security vulnerability.

This is a minor test-only change that adds an extra command-line flag to silence false-positive memory-leak messages from the Windows debug runtime during internal Bitcoin Core tests. It does not change any production code, network behavior, or wallet logic, and it does not fix a security vulnerability.

This is a tiny test-only code cleanup. It swaps one way of choosing an older-style event loop on Windows for another equivalent way, because the old approach is being removed in newer Python versions. It does not change Bitcoin Core's production network code, consensus rules, wallet handling, or any user-facing behavior. There is no security issue here.

This commit only changes compiler warning settings. It adds a new warning flag that alerts developers when a switch statement already handles every possible case but also has an unnecessary default label. It does not change any program behavior or fix any security bug.

This commit is a code cleanup (refactor) that changes how switch statements are written so the compiler can warn developers if they forget to handle a new option in the future. It does not fix a security bug, change program behavior, or introduce a vulnerability. It only makes the code style more consistent and improves future maintainability.

This commit fixes a single-word typo in a documentation file. The text incorrectly said a server class was in the 'bitcoin-wallet' process when the surrounding explanation describes the 'bitcoin-node' process. There is no code change and no security relevance.

This commit only updates comments and an error message in test-related code. It does not change any program logic, so it cannot affect live Bitcoin Core behavior or introduce a security issue.

This commit simply deletes unused helper functions and an unused variable from a single test file. It does not change any production code, network behavior, or wallet logic. There is no security issue here.

This commit simply removes two unused variables from a single test file. It does not change any production code, network behavior, or security logic. There is no security relevance.

This commit removes unused helper code from a single Bitcoin Core functional test file. It deletes three methods/variables that are no longer referenced after an earlier commit. There is no change to production code, network behavior, or wallet logic, and no security relevance.

This commit removes a single unused variable from Bitcoin Core's test framework. It is a cleanup change with no effect on live Bitcoin node software or user funds, and no security relevance.

This commit simply removes an unused helper class from Bitcoin Core's test framework. It is a routine code cleanup with no effect on the actual Bitcoin network software or its security.

This commit simply removes an optional Python linting tool called Vulture from Bitcoin Core's continuous integration setup. Vulture was used to detect unused ('dead') Python code in the project's own scripts. Removing it does not change any code that runs the Bitcoin network or wallet, and it does not introduce a security vulnerability. It is a routine maintenance change.

This is a code cleanup (refactor) of an internal Bitcoin Core RPC helper. It rewrites how the gettxspendingprevout command walks through a list of outpoints and builds its answer, but it does not change what the command does or what data it returns. There is no security-relevant change visible in the diff.

This commit simply updates the version numbers of third-party GitHub Actions used to save and restore build caches during automated testing. There is no change to Bitcoin Core's actual code, consensus rules, wallet behavior, or network logic. It is a routine maintenance update to the continuous integration (CI) configuration.

This commit simply pins a Python linting tool (vulture) to an older version in the continuous integration setup. It is a build/maintenance workaround, not a code change affecting Bitcoin Core's runtime behavior, consensus, networking, or wallet security.

This is a tiny quality-assurance change that adds a compiler-checked note saying the mempool mutex must be acquired after the main chain mutex. It does not change program behavior at runtime; it only helps automated tools detect potential lock-order mistakes during development. There is no direct security fix for users here.

This commit only adds a new test case to Bitcoin Core's functional test suite. It checks that a wallet transaction containing an oversized data output (OP_RETURN) is rejected from the mempool and that the wallet correctly reports the funds as 'nonmempool'. There is no change to production wallet, mempool, or consensus code, so it does not introduce or fix a live security issue.

This commit changes how Bitcoin Core wallets report balances for coins that are spent by transactions no longer in the memory pool. It adds a new 'nonmempool' balance category so users can see these amounts separately, rather than having them silently affect other balance figures. This is a transparency/accounting improvement, not a fix for a code execution or theft vulnerability.

This commit only adds a documentation comment explaining that the btck_WriteBytes callback should return 0 to indicate success. No code behavior was changed.

This commit only adds a release note describing a previously merged feature: the `dumptxoutset` RPC can now write its output to a named pipe on UNIX-like systems. There is no code change, no bug fix, and no security-related content in the diff.

This commit only adds a new automated test. It checks that a Bitcoin Core utility can convert the live UTXO set to an SQLite database when the data is fed through a named pipe (FIFO), without first writing a disk dump. There is no change to production code, no bug fix, and no security-relevant behavior.

This change lets Bitcoin Core's `dumptxoutset` RPC command write its UTXO snapshot directly to a named pipe (FIFO) instead of only to a regular file. Previously the command always wrote to a temporary file and then renamed it into place, which doesn't work for a pipe. The patch detects a named pipe and, if one is supplied, writes directly to it and skips the rename step. It also skips the 'file already exists' error for pipes because a pipe is a communication channel, not a stored file. This is a convenience feature for external tools, not a fix for a known security bug.

This commit removes a piece of bookkeeping data called m_starting_height that tracked a peer's reported block height when it first connected. The value is still logged once when the peer's version message is received, but it is no longer stored permanently in the peer's state or shown in other debug logs. There is no security issue here; it is a small cleanup/refactoring change.