Bitcoin Core

This commit simply removes a code comment block that told a code-checking tool (clang-tidy) to ignore a minor style warning about how two boolean member variables are initialized. The actual code behavior is unchanged, so there is no security impact.

This is a build-system hardening change for a developer tool. It makes the clang-tidy program mandatory when configuring the bitcoin-tidy CMake project, so the build fails clearly if clang-tidy is missing instead of silently continuing with a placeholder 'NOTFOUND' path. It does not change Bitcoin Core's runtime behavior, consensus code, or network handling.

This is a routine cleanup change in Bitcoin Core's internal developer tooling. It removes one outdated header file from a custom clang-tidy plugin used during code review and builds. There is no security relevance: no production code, consensus logic, wallet handling, or network behavior is affected.

This is a small internal cleanup in Bitcoin Core's block-processing code. It removes an obsolete placeholder ('sentinel') entry that was kept in a list of connected blocks to support an old feature that no longer exists. The change simplifies the code but does not fix a security bug or change network behavior.

This commit only adds documentation (release notes) describing a prior change. It does not modify any executable code, network behavior, or security logic. There is no security issue in this commit itself.

This commit only adds new test cases to Bitcoin Core's unit tests. It checks that a function called ValidateInputsStandardness correctly returns specific error messages when transactions have unusual or non-standard inputs. There is no change to the actual network code, consensus rules, or wallet behavior—only more thorough testing of existing behavior.

This commit renames a Bitcoin Core internal function from AreInputsStandard to ValidateInputsStandardness and changes it from returning true/false to returning a structured result that includes an explanation of why an input was rejected. It does not change what transactions are accepted or rejected; it only improves the error messages returned to users and developers. There is no security vulnerability being fixed here.

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 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 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 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 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.