Bitcoin Core

This commit is a pure build-system and file relocation cleanup. It moves the bitcoin_ipc_test library definition and its associated test files from src/test/ to src/ipc/test/ so the Cap'n Proto compiler can use simpler relative import paths. No runtime behavior of Bitcoin Core changes, and no security vulnerability is introduced or fixed.

This commit only adds a new test case to Bitcoin Core's automated test suite. It demonstrates an existing behavior of the CoinGrinder coin-selection algorithm: if too many combinations must be tried, the algorithm stops before finding a valid solution. The commit does not change any production wallet code, so it cannot by itself introduce a security vulnerability or fix one in live software.

This commit is a build-system cleanup for Bitcoin Core's Guix reproducible-build scripts. It moves the '-static-libstdc++' linker flag from the general host linker flags into the CMake executable-only linker flags, so the static C++ standard library is linked only for executables and not accidentally applied elsewhere. There is no security-relevant change here.

This commit is a simple code cleanup in Bitcoin Core's test suite. It moves a helper function that creates a deliberately broken transaction from one test file into a shared test library so other tests can reuse it. No production code, network rules, or wallet behavior are changed.

This is a tiny, non-functional code cleanup in Bitcoin Core's public C kernel API header. It changes one function parameter from a plain unsigned integer to a named enumeration type, and fixes a grammar typo in a comment. There is no security relevance.

This commit only updates two Windows build instruction documents to mention a standard CMake help command. It does not change any program code, build scripts, or configuration logic, and has no security relevance.

This is a minor code cleanup (refactor) that changes how a diagnostic helper passes a C++ standard library object. It does not fix a security bug, change behavior, or introduce a vulnerability. The accompanying build-script changes only suppress a compiler warning that newer compilers would not emit anyway.

This is a routine code-quality change that swaps the old way of recording file, line, and function names in assertion helpers for a modern C++ standard feature. It fixes a compiler warning that could appear when assertions are used in certain contexts, but it does not change what the program does or fix any security bug.

This commit is a code cleanup: it removes an unused 'nullptr witness' code path from a Bitcoin Core function that counts signature operations in SegWit transactions. The change does not alter behavior in normal operation because the nullptr path was never reached. It is not a security fix.

This commit changes how Bitcoin Core's test files are copied into the build directory during compilation. It replaces a broad 'grab everything recursively' approach with explicit lists of file types per folder. There is no security vulnerability here; it is a build-system cleanup that makes the test setup more predictable and avoids accidentally linking unexpected files.

This commit simply removes two unused helper functions from Bitcoin Core's test code. The helpers relied on an old wallet command that no longer works and were only used for another removed test feature. There is no security issue here.

This is a minor code cleanup change. It removes a comment marker used by an automated linting tool (clang-tidy) because the tool no longer needs it. The actual code behavior is unchanged.

This commit changes the build setup for Bitcoin Core's Linux releases so that a GCC component called libsanitizer is not compiled. The change is purely a build-compatibility fix: newer versions of glibc (the GNU C library) cause libsanitizer to fail to compile, so the Bitcoin Core developers disabled it because they do not need it for their release builds. There is no indication this fixes a security vulnerability in Bitcoin Core itself.

This commit is a routine build-system cleanup. It moves existing inter-process communication (IPC) test files from one directory to another and updates CMake instructions accordingly. No production code, no security-sensitive logic, and no bug fixes are present.

This commit only adds a new automated testing job to Bitcoin Core's continuous integration (CI) pipeline. It runs the existing fuzz tests under MemorySanitizer (MSan), a tool that detects use of uninitialized memory. The change does not modify Bitcoin Core's actual source code, network behavior, or wallet logic, so it cannot directly introduce or fix a security vulnerability in the software users run.

This commit simply updates the version of a testing tool (LLVM's libc++) used in automated continuous integration builds from 21.1.1 to 21.1.5. It does not change any Bitcoin Core code that runs on user machines, and there is no indication it fixes a security issue.

This commit only adds plain-English documentation to a header file. It describes what the bitcoinkernel library is for and warns that the API is unstable and not yet released. No code behavior changed.

This commit removes a temporary build setting that forced the Bitcoin Core kernel library to expose all of its internal symbols. Now that the library's public API has been defined, the project can rely on normal symbol-hiding rules when users build with reduced exports. This is a hardening and cleanup change, not a fix for an active security bug.

This commit rewrites an internal, experimental Bitcoin Core developer utility called bitcoin-chainstate so that it uses only the public libbitcoinkernel C++ API instead of internal Bitcoin Core code. It is a refactoring and build-system change. There is no indication it fixes or introduces a security vulnerability.

This commit adds new public programming interfaces (APIs) to the Bitcoin Core 'kernel' library so that developers can inspect transaction inputs, outpoints, and transaction IDs. It is a feature addition, not a fix for a security bug. The code does not change consensus rules, network behavior, or wallet handling. The new functions are covered by tests that verify they work correctly.

This commit adds new read-only ways for external programs using the Bitcoin Core kernel library to ask about blocks by their hash or height, and to compare block hashes. It is a straightforward expansion of the library's C API and its C++ wrapper, accompanied by tests. There is no indication it fixes a bug or closes a security hole.

This commit adds a new public programming interface (API) to the Bitcoin Core 'kernel' library that lets external callers read 'undo' data—renamed here as 'spent outputs'—from disk. Undo data records which previous coins were consumed by transactions in a block. It is normally used internally during chain reorganizations, but the change exposes it for external indexing and silent-payment scanning. The change is a feature addition, not a fix for a known vulnerability, and the commit message does not describe it as security-relevant.

This commit adds new read-only functions to Bitcoin Core's libbitcoinkernel library so external programs can walk backward through the blockchain from the current tip and read raw block data from disk. It is a feature addition, not a fix for a known security problem. There is no evidence in the commit or supplied references that it addresses a vulnerability.

This commit adds a new public API function that lets users serialize a Bitcoin block to raw bytes through a callback. It also adds a C++ wrapper method and uses both in existing tests to verify that the validation interface reports the same block bytes that were originally submitted. There is no security fix here—this is a feature addition for testing and API completeness.

This commit adds new read-only functions to Bitcoin Core's public kernel library so outside programs can ask 'Was this block valid?' and 'Why was it invalid?' when they receive a callback. It does not change any validation rules, fix a bug, or alter how Bitcoin itself processes blocks. It is a straightforward API expansion with no apparent security relevance.