Bitcoin Core

This commit only deletes release-note documentation files from the Bitcoin Core repository and moves them to the project's wiki. No program code, configuration defaults, or executable behavior was changed. It is purely a documentation housekeeping step before creating a new release branch.

This commit only changes Bitcoin Core's continuous integration (CI) test scripts. It adds the Python pycapnp package to several CI environments so that inter-process communication (IPC) tests run on more platforms. There is no change to the Bitcoin software that users run, and no security vulnerability is present in the diff.

This commit adds a small in-memory cache to Bitcoin Core's wallet so it can remember whether a transaction spends coins that belong to the wallet, instead of recalculating that fact every time it is needed. It is a performance and code-clarity change, not a fix for a known security bug. There is no evidence in the commit or supplied references that this addresses an active vulnerability.

This commit only adds a new automated test for Bitcoin Core's wallet behavior regarding 'anchor outputs'—a special zero-value or tiny output type used in some transaction protocols. It does not change any production wallet, node, or consensus code. The test verifies that the wallet can detect anchor outputs during a blockchain rescan but cannot spend them. There is no security vulnerability here.

This commit changes the Bitcoin Core wallet's 'sendall' RPC command so that instead of relying on an internal assumption that every coin's size is known, it explicitly checks whether the final transaction size can be calculated and throws a clear error if it cannot. Previously, the code used a non-fatal assertion that could be skipped in release builds, potentially allowing the command to proceed with an invalid or unknown transaction size when the wallet contained descriptors it could not fully solve.

This commit fixes a wallet accounting bug. Previously, Bitcoin Core's wallet decided whether a transaction came from the user by checking whether the total value of its inputs was greater than zero. That approach missed inputs that are worth exactly zero (so-called 'dust' outputs). After the change, the wallet checks each input individually to see if it is known to the wallet, so even zero-value outputs are correctly recognized as spent. This is mainly a correctness fix for tracking tiny outputs and could affect how transactions are labeled, but it does not appear to be a direct theft-of-funds vulnerability.

This commit adds a new automated test to Bitcoin Core's test suite. It checks that when a private key or descriptor is imported into a wallet, transactions already known to the wallet can change their 'from me' status, which affects whether the gettransaction RPC shows a 'fee' field and 'send' category. The commit itself is only a test file change and does not modify production wallet code.

This commit updates the internal tuning numbers used by Bitcoin Core's header synchronization feature. It pushes the expected network date forward by about six months and raises the minimum chain-work header count to reflect blockchain growth. There is no security vulnerability here; it is routine maintenance to keep the DoS-protection parameters aligned with the current and projected state of the network.

This commit updates routine network statistics in Bitcoin Core's chain parameters. It refreshes the recorded time, total transaction count, and transaction rate for mainnet, testnet, signet, and regtest networks based on recent blockchain data. There is no security issue here—this is normal maintenance data that helps the software estimate sync progress and blockchain size.

This commit adds a safety check in Bitcoin Core's network message handling for a specific message type (GETBLOCKTXN). After reading the message, it verifies that a list of transaction indexes is strictly increasing. This is a defensive coding change: it does not fix a known exploit, but adds an assertion to catch invariant violations that could theoretically lead to incorrect behavior or crashes in compact block reconstruction. The change is small and uses the non-fatal Assume() macro, meaning a violation in release builds may not necessarily stop execution.

This commit adds a new automated fuzz test for a Bitcoin Core data-formatting helper called DifferenceFormatter. It does not change any production code, network behavior, or wallet logic. It only adds a test file and registers it in the build system. There is no security fix or vulnerability present in the diff.

This commit only changes a fuzz test file used for automated testing of Bitcoin Core's wallet fee logic. It adds a helper that simulates a higher minimum mempool fee during the test so the fuzzer can exercise more code paths. There is no change to production wallet or mempool code, and no security issue is present in the diff.

This commit is a small cleanup inside a fuzz test (automated randomized testing) for Bitcoin Core's wallet fee logic. It creates a dedicated test helper class so the fuzz harness can safely set and reset the fee estimator. There is no change to production code, no user-facing behavior change, and no security fix.

This commit only changes a fuzz test file. It introduces a fake/mock version of Bitcoin Core's fee estimator so the wallet fuzz test can control its outputs. There is no change to production code, no user-facing behavior change, and no security fix or vulnerability.

This commit removes a now-impossible error path in Bitcoin Core's wallet code. Legacy (non-descriptor) wallets have already been removed from the codebase, so the check that rejected adding descriptors to a legacy wallet was unreachable 'dead code.' The change replaces that check with an internal assertion, which only affects debug builds and only crashes the program if an invariant that should never happen is violated. There is no security vulnerability here.

This commit only fixes documentation comments in three source files. It corrects broken Doxygen tags (e.g., 'param@[in]' to '@param[in]'), removes redundant parameter descriptions, fixes a typo ('an specific' to 'a specific'), and clarifies a phrase. No executable code was changed, so it cannot affect program behavior or security.

This commit only adds a new functional test to Bitcoin Core. It does not change any production code, consensus rules, or network behavior. The test verifies that an invalid-but-relayable block with a malformed witness nonce is rejected over the peer-to-peer network, and that a corrected version is accepted. There is no security vulnerability being fixed here.

This is a small internal cleanup in Bitcoin Core's wallet code. It removes a special flag called ISMINE_USED that was only used to decide whether to count already-used addresses when calculating balances. The same behavior is now controlled by a simple true/false parameter called avoid_reuse. There is no direct security bug being fixed here; it is a refactoring change that makes the code easier to understand and maintain.

This commit cleans up the Bitcoin Core wallet code by removing an old 'spendable' flag that is no longer meaningful for modern descriptor wallets. For these wallets, every coin the wallet knows about is considered spendable, so the flag was redundant. The change also removes a small wrapper function and updates the listunspent RPC to always report 'spendable' as true. It is a code-simplification refactor, not a fix for an active security bug.

This commit is a routine internal code cleanup in Bitcoin Core's wallet module. It removes an old enum type called isminetype and replaces it with a simple true/false (bool) value, because the wallet no longer distinguishes between different kinds of 'mine' statuses—only 'mine' and 'not mine' remain. The change touches many files but does not alter what the wallet does; it only simplifies how the code expresses the same behavior.

This commit is a simple code cleanup: it removes an unused 'is_mine' output parameter from a wallet address lookup function and updates all callers. There is no security-relevant change; the removed parameter was never used, and the remaining behavior is unchanged.

This commit removes a Python helper script used during the build process and replaces it with equivalent logic written directly in CMake. It is a build-system cleanup that drops a Python dependency for generating translation string files. There is no indication this change fixes or introduces a security vulnerability.

This commit changes a Bitcoin Core fuzz test (an automated test that feeds random data to a piece of code to find crashes or bugs). It removes a 'const' restriction so the test can create a fresh, configurable memory pool (mempool) for each fuzz run, and sets fee-related options from the fuzz input. It is a test-only change and does not alter the behavior of the actual Bitcoin node software that users run.

This commit is a build-system cleanup. It replaces the use of the external 'sed' tool with built-in CMake commands when processing a translation file. There is no security-relevant change to Bitcoin's runtime behavior, networking, wallet handling, or consensus logic.

This commit is a routine build-system cleanup for Bitcoin Core's Qt GUI translation tooling. It moves the logic for finding translatable source files out of the CMake configuration step and into a separate script that runs only when developers explicitly build the 'translate' target. There is no change to how Bitcoin handles money, network messages, wallets, or private keys, and no security issue is evident.