Bitcoin Core

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.

This commit only adds a new automated test for Bitcoin Core's Tor control feature. It checks that the program safely disconnects when a mock Tor server sends an extremely long response line. There are no changes to the actual Bitcoin Core program code, only to the test file.

This commit improves a fuzz test for Bitcoin Core's Tor control code and adds a small safety check in the real Tor control logic. The production change guards against an empty reply from Tor during the SAFECOOKIE authentication challenge, preventing a potential out-of-bounds read or crash. The rest of the change is test cleanup and expanded fuzzing coverage.

This commit is a straightforward internal code cleanup: it moves the Tor controller object from a single global variable into the per-node context structure. There is no change in user-facing behavior, no bug fix, and no security-relevant change visible in the diff.

This commit only adds a new automated test that simulates a Tor control server and checks that Bitcoin Core talks to it correctly. It does not change any production code, so it cannot introduce a security vulnerability or fix one.

This commit only adds a new automated test for Bitcoin Core's Tor control feature. It checks that the software correctly waits for a complete message before acting, rather than reacting to a partial message. There is no change to the actual Bitcoin Core program code that users run.

This commit only adds new automated tests for Bitcoin Core's Tor control feature. It checks that when creating a hidden service, the software requests a modern anti-DoS feature (proof-of-work defenses) and gracefully falls back if the Tor daemon does not support it. No production code is changed, so this cannot introduce a security vulnerability or fix one directly.

This commit rewrites how Bitcoin Core talks to the Tor control port. It replaces the libevent networking library with Bitcoin Core's own simpler socket wrapper and a dedicated control thread. The change is a refactor: it removes one external dependency and makes the code easier to test and reason about, but it also introduces new socket-handling code that must correctly manage reconnects, timeouts, partial reads, and shutdown. There is no direct evidence in the commit or supplied references that this fixes a known security bug, but any rewrite of network code carries a small risk of introducing subtle bugs.

This is a small internal code cleanup in Bitcoin Core's custom signal/slot system. It merges two separate shared pointers (one tracking whether a callback is still active, and one used as a construction tag) into a single shared pointer. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit simply removes a temporary build dependency on Boost headers from two internal build targets. It is a cleanup change with no visible security relevance.

This is a routine code cleanup commit. It replaces a full header include with a simple forward declaration in two interface header files. There is no security-relevant change and no indication of a vulnerability being fixed.

This commit replaces Bitcoin Core's use of the Boost signals2 library with a new, simplified in-house implementation called btcsignals. It is a code refactoring/reimplementation intended to reduce dependency on Boost. The change itself does not fix a known bug or vulnerability, but any reimplementation of a threading/callback mechanism carries risk of introducing subtle concurrency or lifetime bugs.

This is a small cleanup of a test file. It removes version-specific workarounds for older Boost library versions, keeping only the behavior needed for the newest Boost version. There is no security issue here.

This commit simply removes an unused software component (Boost.Signals2) from two dependency lists used to build Bitcoin Core. It is a cleanup change, not a security fix.

This commit is a routine cleanup of documentation and a linting script. It updates an example in the developer notes to reference the project's own signal library (btcsignals) instead of the old Boost signals2 library, and removes three Boost signals2 header paths from the list of expected Boost includes checked by a linter. There is no code behavior change and no security relevance.

This is a routine build cleanup. A developer removed two leftover references to the Boost C++ library from the project's build instructions because those parts of the code no longer use Boost. There is no security issue here.