Bitcoin Core

This is a fix for a flaky Bitcoin Core functional test, not a security vulnerability in the live Bitcoin network or wallet software. The test was creating and immediately destroying an unused worker thread, which could trigger a race condition or null pointer dereference during testing. The patch avoids the problematic helper function and directly creates the needed connection. It does not affect production code paths.

This change simply makes the Bitcoin Core build system more forgiving when compiling Qt-related dependencies. If a previous build was interrupted, the directories it needs to create might already exist; the new commands won't fail in that case. It is a build reliability fix, not a security fix.

This commit only adds documentation to a user guide about how operating-system swapping can slow down Bitcoin Core. It is a non-code change with no security implications.

This commit only cleans up an unused helper functions in a test file and fixes a grammar typo in a comment. It does not change any production code, network behavior, or wallet logic, so it has no security relevance.

This commit only changes a single functional test file. It reduces the number of blocks generated in a test from 500 to 200 and unloads a wallet earlier to make the test run faster and produce fewer chain notifications. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit is a documentation-only update to the Bitcoin Core dependencies guide. It fixes links, adds a missing dependency entry for libmultiprocess, and clarifies that Cap'n Proto is used for inter-process communication (IPC). No code was changed, so there is no direct security impact.

This commit is a one-line documentation fix. It marks the 'fee' field in the getblock RPC help output as optional, matching the actual behavior where the field is omitted when block undo data is not available. There is no code behavior change and no security impact.

This commit only adds documentation. It creates a release note explaining that the default database cache size setting (-dbcache) has been raised from 450 MB to 1024 MB on systems with at least 4 GB of RAM. There is no code change, no bug fix, and no security issue in this commit itself.

This is a one-line documentation update that adds a reference to Miniscript expressions in the descriptors documentation. It does not change any code, executable logic, or configuration. There is no security relevance.

This commit fixes a single grammar typo in a documentation file, changing 'first 32 bit' to 'first 32 bits'. It does not change any code, executable logic, or security behavior.

This commit only updates the documentation file doc/descriptors.md. It adds hyperlinks to the relevant Bitcoin Improvement Proposals (BIPs) for each descriptor type and makes minor formatting changes (for example, adding a space in 'BIP174' to 'BIP 174'). No code, logic, or behavior of the Bitcoin Core software was changed. There is no security impact.

This commit only edits documentation. It removes a list of Bitcoin Core RPC commands that support output descriptors and shortens the introduction. No code, RPC behavior, or security logic was changed.

This commit only updates documentation. It adds two lines to the descriptors.md file explaining that the musig() expression is supported in output descriptors for MuSig2 key aggregation. There is no code change, no bug fix, and no security issue.

This is a one-line documentation update that corrects the described default value of a memory-cache setting. It does not change any code, behavior, or configuration. There is no security issue.

This is a tiny user-interface change in Bitcoin Core's settings screen. It makes the displayed default database cache size match the value calculated by a shared helper function, instead of a hardcoded constant. There is no security issue visible in the change.

This change simply raises the default database cache size for Bitcoin Core from 450 MB to 1,024 MB on 64-bit computers that have at least 4 GB of RAM. It is a performance tuning change, not a security fix. There is no indication it addresses a vulnerability or was triggered by a security report.

This commit fixes a programming bug in Bitcoin Core's descriptor code where a vector was reserved but never resized before being written to. Using std::transform with providers.begin() on an empty vector causes undefined behavior because it writes past the end of the vector. The fix uses std::back_inserter to safely append elements. The bug could cause crashes or memory corruption when cloning certain wallet descriptors, but it is not a remote exploit by itself.

This commit fixes a simple oversight: the bitcoin-gui program was missing a factory method that creates the 'mining' interface. Because that interface was absent, some internal code paths—such as the waitforblockheight RPC—did not work when running inside bitcoin-gui, even though they worked in bitcoind, bitcoin-qt, and bitcoin-node. The patch adds the missing one-line method and its header include. It is a functionality bug, not an obvious security vulnerability, but any broken RPC path can have downstream reliability or, in rare cases, security-adjacent effects.

This commit is a code cleanup that splits the existing JSON-RPC request handling into a new helper function called ExecuteHTTPRPC. The commit message explicitly says behavior is not changing, and the diff shows the same logic being moved around rather than added or removed. There is no indication of a security fix or vulnerability.

This commit adds a small helper function that makes it easier for simple Bitcoin tools (like command-line utilities) to connect to other Bitcoin processes over IPC without needing to write boilerplate setup code. It does not change existing behavior or fix any bug; it is purely a code organization and convenience addition.

This commit only adds new automated tests for the bitcoin-cli command-line tool's IPC (inter-process communication) connection feature. It does not change any production code, so it cannot introduce a security vulnerability or fix one in the software users run.

This change makes Bitcoin Core handle two specific invalid -ipcconnect socket path cases more gracefully. Previously, a socket path that was too long or pointed to a non-directory component would crash the process with a fatal error. Now, when the connection type is set to 'auto', these cases are treated like a missing or refusing socket, and the program simply returns null instead of crashing. The commit message says this is mainly to avoid CI test failures caused by long data directory paths, not to fix a security vulnerability.

This commit adds a new command-line option to bitcoin-cli that lets it talk to a local Bitcoin node over a local inter-process communication (IPC) socket instead of the usual network HTTP connection. It is a feature addition, not a fix for a known bug or vulnerability. The change is opt-in at build time and runtime, and it does not appear to introduce an obvious security flaw, but it does add new code paths for authentication and transport that need careful review.

This commit adds a new way for local programs to talk to Bitcoin Core: instead of connecting over a regular network port, they can connect through a Unix socket file using a feature called -ipcbind. The commit itself is a building block for a later change that will let bitcoin-cli use this socket. The code exposes the same RPC commands that already exist, but over the local socket. The commit also updates the help text to warn that any local process that can reach the socket gets unauthenticated RPC access, so the socket file's permissions matter.

This commit adds a new automated fuzz test for Bitcoin Core's wallet migration feature. It does not change production wallet code; it only adds test code that feeds random inputs to the existing migration function to help find bugs. There is no indication this commit fixes or introduces a security vulnerability.