Bitcoin Core

This is a straightforward internal code cleanup in Bitcoin Core's inter-process communication (IPC) layer. It replaces direct use of raw socket identifiers with a new 'Stream' type alias so the code can work with an upcoming version of a supporting library that adds Windows support. No security bug is fixed or introduced in the visible changes.

This is a straightforward internal code cleanup in Bitcoin Core's inter-process communication (IPC) layer. It moves the executable name parameter from individual connect/listen/serve methods into the protocol object's constructor. The executable name is only used for logging and debugging to tell different processes apart. There is no change to security-sensitive behavior, no bug fix, and no externally reported issue.

This commit removes unnecessary mutexes (simple locking mechanisms) from two internal Bitcoin Core fuzz test files. Fuzz tests are automated testing tools, not part of the live Bitcoin network software. The change is a code cleanup: the developers concluded the locks were not needed because fuzz targets run one at a time within a single process. There is no indication this fixes a security vulnerability or affects real users.

This is a routine performance optimization in Bitcoin Core's transaction-cluster linearization code. It replaces dynamically-allocated vectors with fixed-size stack arrays to avoid repeated heap memory allocations. There is no security-relevant change: the algorithm, ordering logic, and dependency handling remain identical.

This is a routine performance improvement, not a security fix. It pre-allocates memory for an internal queue so the program doesn't waste time repeatedly resizing it while building a data structure. There is no user-facing or security-relevant change.

This is a small internal performance improvement in Bitcoin Core's transaction clustering code. It avoids doing the same bit-set intersection twice by saving the result of the first pass. There is no security-relevant change: no new behavior, no bounds check changes, no memory safety changes, and no externally reachable input handling.

This commit updates the Qt graphical toolkit used by Bitcoin Core from version 6.8.3 to 6.8.4 in the project's dependency build system. It also refreshes Bitcoin-specific patches, removes one now-unneeded build patch, and disables a new RISC-V vector optimization in the bundled libpng to avoid cross-compilation link failures. Qt 6.8.4 is a routine patch release by Qt, and the commit message frames this as a standard dependency update rather than a security fix. There is no direct evidence in the commit or supplied references that this resolves a known vulnerability in Bitcoin Core.

This commit is purely a code-style cleanup. It adds a space between the macro name LIMITED_WHILE and its opening parenthesis across many fuzz test files, plus a few tiny formatting fixes like removing a redundant semicolon and fixing indentation. No program behavior changes, no security fixes, and no production code is touched.

This commit only changes a code-formatting configuration file. It tells the project's automatic formatting tool (clang-format) to treat the custom LIMITED_WHILE macro the same way it treats a normal 'while' loop when laying out code. There is no change to program logic, no bug fix, and no security relevance.

This commit removes a temporary safety check in a fuzz test (automated randomized testing code) for Bitcoin Core's inter-process communication. The check avoided sending empty byte arrays because an external library had a bug that triggered undefined-behavior sanitizer warnings. The library bug is now fixed, so the workaround is no longer needed. This is a cleanup of test code, not a fix to production Bitcoin Core code, and it does not change how real users' transactions or wallets are handled.

This commit is a minor style cleanup inside a fuzz test (a test that feeds random data to software to find bugs). It replaces a loop that reads a number from fuzz input with a standard helper that reads a single true/false byte each iteration. There is no change to production Bitcoin Core code, no user-facing behavior change, and no security fix.

This commit updates a helper library (libmultiprocess) used by Bitcoin Core. The only code change replaces a raw memory copy with a safer standard-library copy in a routine that converts byte arrays for inter-process communication. The rest is version bookkeeping and new test coverage. There is no indication this fixes an active security vulnerability; it is a defensive cleanup to silence an undefined-behavior sanitizer warning.

This commit updates the version of a Python packaging tool called 'uv' used inside Bitcoin Core's automated code-checking container image, from version 0.10 to version 0.11. It is a routine dependency bump in the continuous-integration (CI) setup and does not change any Bitcoin protocol, wallet, or network code.

This commit simply updates the version of Ubuntu used by Bitcoin Core's automated linting (code style checking) container from 24.04 to 26.04. It is a routine CI/infrastructure maintenance change with no security relevance visible in the commit.

This commit simply updates the version of mypy, a Python type-checking tool used in the project's continuous integration (CI) linting pipeline, from 1.19.1 to 2.3.0. There is no indication of a security fix or vulnerability in the code itself.

This commit changes a single CI (continuous integration) configuration file for an OpenBSD cross-compilation test job. It disables building the Qt GUI library in that specific test job because the build tool llvm-ranlib does not support the '-t' option used by the build system. This is a build/test infrastructure workaround, not a change to Bitcoin Core's runtime code, consensus logic, wallet handling, or network behavior. It has no direct security relevance for users running Bitcoin Core.

This is a one-line build-system fix for a Bitcoin Core fuzz-testing target. It changes a CMake target name so the correct header paths are found when libmultiprocess is built externally instead of bundled. It does not change runtime behavior, consensus rules, or network code, and there is no security vulnerability being patched.

This commit simply updates the version of a build dependency (Cap'n Proto, a data serialization library used during compilation) from 1.4.0 to 1.5.0 in Bitcoin Core's dependency system. It changes only a version number and the corresponding cryptographic hash used to verify the downloaded source. There is no indication in the commit itself of any security bug, vulnerability, or malicious change.

This commit is a small internal cleanup in Bitcoin Core's benchmark code. It swaps a test-only mock wallet database helper for a real in-memory SQLite database helper in five benchmark files. There is no change to production wallet code, no change to how real user wallets are stored, and no security fix or vulnerability introduced.

This Bitcoin Core commit refactors how transactions are selected and sorted before being announced to network peers. It replaces an older in-place heap sort with a new mempool function that picks the best transactions by mining fee score while respecting dependency order. The change is a code-quality and performance improvement; there is no direct evidence in the commit or supplied references that it fixes a security vulnerability.

This commit introduces a brand-new, generic token-bucket utility class and a full set of unit tests for it. A token bucket is a common algorithm for rate limiting (controlling how often an action can happen). There is no change to existing network, wallet, consensus, or RPC behavior, and the commit message and diff do not describe any security fix or vulnerability.

This commit adds a new debug-only command-line option called -txsendrate that lets node operators change how many transaction announcements per second Bitcoin Core sends to inbound peers. The default behavior stays the same (14 transactions per second), and the setting is clamped between 1 and 1000. It is intended for testing and low-risk tuning, not for normal user operation.

This commit adds new read-only information fields to Bitcoin Core's getnetworkinfo RPC command. It exposes the configured transaction send rate and internal token-bucket statistics used to pace transaction announcements to peers. There is no code change that modifies behavior, permissions, or network processing; it only reports existing internal state to authorized RPC callers.

This commit only adds a new automated test file and registers it in the test runner. It does not change any production code in Bitcoin Core. The test verifies that transaction relay rate limiting (a feature controlled by the -txsendrate option) works as expected, including that replaced transactions are cleaned from the backlog. There is no security vulnerability or fix here.

This commit only adds a release note describing a previously made network change. It does not change any code, configuration defaults, or behavior. There is no security issue in this documentation patch itself.