Bitcoin Core

This commit only adds and reorganizes automated tests for the wallet's coin-selection algorithm. It does not change any production code that handles Bitcoin transactions, keys, networking, or consensus rules. There is no security vulnerability here.

This commit only adds new test cases for an existing coin-selection algorithm called SRD (Single Random Draw). It does not change any production wallet code, network rules, or consensus behavior. The change is purely in the test suite and verifies that SRD succeeds for simple, realistic selection targets. There is no security issue here.

This commit only changes test code for Bitcoin Core's coin selection logic. It moves and expands tests that check what happens when a wallet doesn't have enough funds to make a transaction. No production wallet code is changed, so this cannot directly affect real users' funds or transaction behavior.

This commit only changes test code. It updates the list of transaction fee rates used in wallet coin-selection unit tests to reflect a recent lowering of Bitcoin Core's default minimum fee rate and to cover more edge cases. No production code is modified, so this has no direct security impact on running Bitcoin nodes or wallets.

This commit only changes Bitcoin Core's internal coin-selection unit tests. It refactors how test parameters are initialized so that the fee rate can be passed in directly, and it makes sure one group of failure tests uses the same parameters as the rest of the test loop. There is no change to production wallet code, network behavior, or consensus rules, and no security issue is introduced or fixed.

This commit removes a temporary test-only workaround that allowed a less informative error message on macOS when a specific build option (REDUCE_EXPORTS) was used. The underlying problem was fixed in a separate library, so the test no longer needs to accept the degraded message. It is purely a cleanup of test code and does not change any production Bitcoin Core behavior.

This is a test-only code cleanup. It moves the setup of a shared test fixture from the entire test suite down to individual test cases, so future tests added to these files won't automatically inherit an expensive 100-block chain setup unless they actually need it. There is no change to production Bitcoin Core code, no bug fix, and no security vulnerability.

This commit only changes Bitcoin Core's internal unit tests. It swaps a heavier test helper (TestingSetup) for a lighter one (BasicTestingSetup) in six test files where the full setup was unnecessary. There is no change to the actual Bitcoin node software that users run, so it cannot affect live networks, wallets, or transactions.

This commit updates an internal Bitcoin Core library called libmultiprocess. The main functional change is replacing a raw exception throw with a 'recoverable' exception throw when an IPC server request fails unexpectedly. This is a hardening improvement that may prevent a crashed request from tearing down the whole process. The rest is version bookkeeping and a test timeout increase.

This commit only adds new automated tests to Bitcoin Core. It checks that the built-in HTTP server already rejects oversized HTTP headers and request bodies, including when data is sent using chunked transfer encoding. There is no change to the actual server code, so this is a test-only improvement rather than a fix for a live vulnerability.

This commit is a bulk cleanup of Bitcoin Core's Python functional tests. It mechanically replaces plain `assert x == y` statements with a project-specific `assert_equal(x, y)` helper. The change only affects test code, not the Bitcoin node software that users run, so it cannot directly impact live Bitcoin operations, wallets, or consensus. It improves the quality of test failure messages but introduces no security vulnerability and fixes no exploitable bug.

This commit only adds missing Python imports for a helper function named assert_equal in test files. It does not change how Bitcoin Core runs, validates transactions, or handles user funds. It is a routine test-code cleanup with no security relevance.

This commit only changes test code. It replaces loose truthiness checks (like `assert x` or `assert not x`) with stricter equality checks (`assert_equal(x, True/False)`) in two Python test files. It does not change any production Bitcoin Core code, so it cannot directly affect live wallets, nodes, or transactions.

This commit only changes test code. It replaces plain Python assert statements with a custom assert_equal helper in two test files. There is no change to Bitcoin Core's production code, network behavior, wallet logic, or consensus rules, so it has no security impact on users.

This commit only changes Bitcoin Core's internal test code. It rewrites some test assertions by hand so that a later automated cleanup can safely convert them. There is no change to the actual Bitcoin node software that users run, so it cannot affect live wallets, transactions, or network security.

This commit only changes Bitcoin Core's internal test code. It splits combined `assert` statements into separate assertions so that when a test fails, the error message points to the exact condition that failed. There is no change to the actual Bitcoin node software that users run, and no security vulnerability is being fixed.

This commit only changes test code. It replaces plain Python `assert x == y` checks with a helper called `assert_equal` in a handful of test files. The reason is cosmetic/preparatory: some test lines contain inline comments, list literals, or descriptor strings with `#` characters, so they need to be converted by hand before a later automated rewrite can safely convert the rest. There is no change to Bitcoin Core's actual node or wallet logic, so it cannot affect live users, funds, or network security.

This commit only rewrites a handful of test-file assertions from the form 'x equals a or x equals b' to the equivalent form 'x is in the set (a, b)'. It does not change any production code, does not alter what the tests check, and has no security relevance for running Bitcoin software.

This commit only adds a new automated test. It checks that Bitcoin Core's HTTP server does not wrongly close a long-running RPC connection while the server is still actively working on a delayed response. There is no change to production code, no bug fix, and no security patch.

This commit is a routine cleanup of a single test file in Bitcoin Core. It rewrites the functional test that checks HTTP server behavior, wrapping raw HTTP client code into a helper class and adding a few extra sanity checks. There is no change to the actual Bitcoin node software, no bug fix, and no security-relevant behavior change.

This commit only expands a Bitcoin Core test so it also runs on macOS and BSD systems, not just Linux. It adds a helper that uses the lsof command to find which network addresses a test node is listening on. There is no change to the actual Bitcoin node software that users run, and no security bug is being fixed or introduced.

This commit only changes Bitcoin Core's internal test code. It expands an existing test so it can run on macOS and BSD systems, and adds a helper function that reads network interface information from the operating system. There is no change to the actual Bitcoin node software that users run, and nothing in the commit introduces a security vulnerability or fixes one.

This commit removes a special exception that previously let RISC-V builds skip a check for unwanted exported symbols. The change makes the build-time symbol check apply equally to RISC-V binaries, slightly tightening release-build quality controls. It is not a fix for an active vulnerability in running Bitcoin software.

This commit updates the version of binutils (a set of tools used to build Bitcoin Core's release binaries inside a reproducible build environment called Guix) from 2.44 to 2.46.0. It is a routine build-system dependency bump. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability, introduces a known exploit, or changes any runtime code that end users interact with.

This is a small code cleanup that removes an unused parameter from an internal function. The function previously received a 'BlockManager' object but did not actually use it. The change only adjusts the function signature and the two places that call it. There is no security fix here.