Bitcoin Core

This is a small test-only change that lets Bitcoin Core's internal test tools recognize the illumos operating system (reported as 'sunos5') when listing network addresses and interfaces. It does not change the Bitcoin node software itself, does not touch wallet or consensus code, and has no direct security relevance.

This is a small test-only change. A helper function used by Bitcoin Core's automated tests is being updated to no longer claim OpenBSD as a supported platform, because OpenBSD does not include the 'lsof' tool that the function relies on. It does not change the Bitcoin Core software that users run, nor does it fix or introduce a security vulnerability.

This commit simply updates the FreeBSD build documentation to add the `lsof` utility to the list of packages needed to run the test suite. It is a documentation-only change with no code modifications and no security implications.

This is a harmless test-suite maintenance change. It adds a helper that skips certain Bitcoin Core functional tests on non-Linux systems when the 'lsof' tool is missing. It does not change the actual Bitcoin node software, network rules, wallet handling, or any code that processes untrusted data.

This commit only changes a test file. It strengthens an existing test for the Bitcoin Core HTTP server so it can better catch a race condition where the server might stop reading new requests from a connection. The commit itself does not change the actual server code, so it is not a fix—it is a test that checks whether a previously suspected race condition is truly fixed.

This is a test-only change. It updates a single unit test file to run the HTTP request handler on a separate worker thread instead of handling it synchronously. There is no change to production code, no security fix, and no vulnerability.

This commit only adds new unit tests for the Bitcoin Core HTTP server. It creates a fake network socket that sometimes returns a 'try again' error, then verifies the server retries and still sends all replies. No production code is changed, so it cannot introduce a security vulnerability or fix one in running software.

This commit fixes a subtle timing bug in Bitcoin Core's built-in HTTP server. Under a specific race between a worker thread preparing a response and the I/O thread sending data, a connection could get permanently stuck waiting to write even though there was nothing left to send. Once stuck, the server would stop reading new requests from that client, effectively hanging the connection. The fix moves the 'ready to send' flag update under the same lock as the send buffer and protects reads of that flag with a separate lock to avoid deadlocks.

This commit adds an empty placeholder for OpenBSD linker flags in the dependency build system. It is a build configuration change with no functional or security effect visible in the diff.

This commit adds a new automated build test for Bitcoin Core that cross-compiles for OpenBSD. It downloads official OpenBSD system files from the OpenBSD project's own download server and sets up the build environment. There is no change to the Bitcoin Core software itself, no user-facing feature, and no security fix or vulnerability.

This commit is a straightforward internal cleanup in Bitcoin Core's wallet code. It replaces a single mixed-purpose data field called vOrderForm with two clearer fields: one for BIP 21 payment messages and one for BIP 70 payment requests. The change preserves existing wallet data and behavior, and does not appear to fix or introduce a security vulnerability.

This is a routine code cleanup in Bitcoin Core's wallet. It changes how optional 'message' fields from payment URIs are passed through the wallet when committing a transaction, replacing a generic 'order form' container with explicit named parameters. There is no security fix or vulnerability here.

This commit fixes a small cleanup issue in Bitcoin Core's internal fuzz testing code. Fuzz tests are automated tools that feed random data into functions to find bugs; they are not part of the live Bitcoin network software. The change saves the original socket-creating function before replacing it with a fake one, then restores it afterward. This prevents one fuzz test from accidentally leaving its fake socket in place for later tests. There is no indication this affects real users, wallets, nodes, or the live Bitcoin network.

This is a straightforward code cleanup change that renames three internal status labels (INFO, WARN, ERR) to different capitalisation (Info, Warn, Error) because one of those names clashed with a system macro on illumos operating systems when running tests. It does not change program logic, user-facing behaviour, or security properties. It only prevents a possible build failure on an uncommon platform.

This commit is a simple rename of three internal constants used by Bitcoin Core's socket-handling code. The old names (RECV, SEND, ERR) clashed with a macro named ERR on illumos-based operating systems, preventing the software from compiling. The new names (RecvEvent, SendEvent, ErrorEvent) avoid that clash. There is no change to program logic, behavior, or security.

This is a simple code cleanup change: a local constant named ERR inside one function was renamed to accept_error because it happened to have the same name as a class-level constant. The rename avoids confusion for programmers but does not change any program behavior or fix a security problem.

This is a routine Continuous Integration (CI) configuration update. It changes the version of the Linux container used for one automated test job and adds a compiler flag to work around a known build issue. There is no change to the Bitcoin Core software that users run, and no security vulnerability is being fixed or introduced.

This commit simply makes an existing command-line option, -logratelimit, visible in the normal help output. It does not change how the option works, what it protects against, or any code behavior. It is a documentation/usability change only.

This commit is a code-quality refactor, not a security fix. It replaces raw 4-byte fingerprint arrays with a named std::array type (KeyFingerprint) and adds helper methods to copy fingerprints safely. The behavior of fingerprint handling is unchanged; the change only makes the code easier to maintain and less prone to future mistakes.

This is a small bug fix in Bitcoin Core's internal benchmarking header (nanobench). The code intended to create three empty placeholder slots in some performance-counter buffers, but accidentally created a single slot containing the number 3. Under normal use this gets corrected before it matters, but a default-constructed object could read past the single element. It is a correctness/reliability fix in benchmark tooling, not a network-facing security vulnerability.

This commit adds a new automated test that starts the Bitcoin GUI in a headless mode and checks it can be shut down by a remote command. It also makes a small code change so the GUI does not try to load custom fonts when running in the minimal headless Qt platform. There is no security vulnerability here; it is purely a testing and robustness improvement.

This commit is a minor cleanup of the CMake build script used to locate the QR code encoding library. It removes an unnecessary helper function and simplifies how the library target is created. There is no indication this change fixes or introduces a security problem.

This is a minor cleanup change in Bitcoin Core's build system. It removes an unused 'pkgconfig' metadata directory left over after building the qrencode (QR code generation) dependency. There is no security issue here.

This commit removes an optional way CMake can locate the QR code library (libqrencode). Previously, the build system could use pkg-config to find the library's location and version. Now it will rely only on CMake's standard search paths. There is no security-relevant change here; it is a build-system simplification.

This commit is a documentation-only release note. It announces that two wallet commands, `send` and `sendall`, are no longer considered experimental. There is no code change, no bug fix, and no security issue in the commit itself.