Bitcoin Core

This commit is a purely cosmetic cleanup of a single file. It only removes trailing whitespace and converts tab characters to spaces in the assembly code comments and formatting of src/crypto/sha256_sse4.cpp. No program logic, instructions, constants, or behavior was changed.

This commit simply updates Bitcoin Core's documentation and one CI test script to say the minimum supported GCC/G++ compiler version is now 12 instead of 11. It does not change any wallet, network, or consensus code. There is no security issue in this change itself.

This commit adds a simple read-only helper function (accessor) to a mempool data structure. It exposes a value that was already being computed internally, but does not change any behavior, fix any bug, or introduce any obvious security issue.

This commit is a small, clean code refactor. It extracts an existing calculation—taking the larger of a transaction's weight and its sigop-based adjusted weight—into a new reusable helper function, and adds a related utility for converting fee rates. There is no change in behavior or security fix visible in the diff.

This commit adds a new internal transaction graph object (TxGraph) inside Bitcoin Core's memory pool (mempool). It is a small, structural code change that initializes the graph and includes its memory usage in accounting. There is no direct evidence in the commit or supplied references that this fixes or introduces a security vulnerability.

This is a routine internal code refactoring in Bitcoin Core. It changes how memory-pool transaction entries are constructed so they inherit from a new transaction-graph reference type. There is no user-visible behavior change, no bug fix, and no security-relevant change evident in the commit.

This is a small internal code-quality change in Bitcoin Core's memory pool (mempool) data structure. It removes an explicit-copy helper and makes the object movable instead of copyable. There is no direct evidence this fixes an exploitable security bug; it is best understood as a defensive cleanup that prevents accidental expensive or incorrect copying of mempool entries.

This is a one-line change inside a test file that removes a compiler warning. It swaps a pointer cast to char* for a direct iterator-based copy when building fake network message data for unit tests. There is no change to production code and no security-relevant behavior change.

This commit removes a convenience function called btck_chain_get_tip from the Bitcoin Core libbitcoinkernel API. The function simply returned the current tip of the blockchain, but the project decided it was redundant because callers can get the same information by combining two other existing functions. The change is a small API cleanup with no security relevance.

This commit removes a redundant function that fetched the very first (genesis) block from a blockchain API. The same result can already be obtained through an existing general-purpose function. The change is a routine code cleanup with no security implications.

This is a test-only code cleanup. It changes one test file to use a C++ reference instead of a pointer when accessing an internal object, and removes two compiler warning workarounds from the continuous-integration scripts. There is no change to the live Bitcoin Core software that users run, and no security fix or vulnerability is described.

This commit only adds a documentation sentence pointing readers to existing developer notes about coverage builds for fuzz testing. It changes no code, build scripts, or configuration.

This commit fixes a typo in the NetBSD build documentation. The correct command to install packages with pkgin is 'pkgin install <package>', not 'pkgin <package>'. It does not change any code, build scripts, or runtime behavior.

This commit only removes a now-outdated sentence from five documentation files. The sentence told readers that some tests are skipped if Python 3 is missing, but that is no longer true after other recent changes. No code, build scripts, tests, or configuration were modified.

This is a straightforward code cleanup: a single missing C++ standard library header, <exception>, was added to a wrapper header file. It does not change program behavior, fix a crash, or address any security issue. It simply ensures the header compiles correctly on its own in all build configurations.

This is a tiny code cleanup in a CI (Continuous Integration) helper script. It replaces the hardcoded build directory name 'build' with a variable named 'build_dir' set to 'ci_build'. There is no security relevance; it is purely a refactor to make the script easier to maintain.

This is a routine cleanup of Bitcoin Core's internal continuous integration (CI) script. It replaces a long list of build options with a single shorthand preset ('dev-mode') and adds a compiler warning tolerance flag. There is no user-facing change, no network code change, and no security-relevant behavior change.

This commit changes one line in a Bitcoin Core continuous integration (CI) script. It replaces a manually written list of build options with a pre-defined developer-mode preset so that the automated code-quality (clang-tidy) job also covers the project's new kernel code. There is no change to the software users run, no bug fix, and no security-relevant behavior change.

This commit is a code cleanup that replaces several hand-written internal-error messages with a single standard macro. It does not change what the program does, only how error messages are formatted. There is no security issue here.

This is a documentation and code-cleanup change only. It removes an outdated compiler-lint suppression comment and slightly reformats a macro that throws an error when unreachable code is reached. There is no functional change to Bitcoin Core's behavior, and no security issue is introduced or fixed.

This change adjusts how Bitcoin Core is packaged for Linux so that the libgcc runtime library is bundled directly into the released binaries instead of being expected to come from the user's operating system. It also removes checks that previously ensured the released binaries only relied on specific system versions of libgcc. The goal is to make the official Linux releases work on a wider range of older or differently-configured distributions without requiring a particular libgcc to be installed. It is a build/packaging improvement rather than a fix for an active software bug or exploit.

This commit changes Bitcoin Core's Guix build setup so that a reproducibility patch for the GCC compiler is also applied when building Linux binaries, not just Windows ones. The patch strips out architecture-specific Guix store paths from debug symbols and now also from libunwind, making the resulting binaries more deterministic across different build machines. It is a build-hygiene/reproducibility fix, not a runtime security patch.

This is a small code cleanup change. It removes an unused optional parameter from a helper function that calculates the witness Merkle root for a Bitcoin block. All callers were already passing a special 'not used' value (nullptr), so the behavior of the program does not change. There is no security bug being fixed here.

This is a small code cleanup in Bitcoin Core's merkle tree calculation. It removes two unused parameters (`proot` and `pmutated`) from an internal helper function because the only place that called it always passed `nullptr` for both. There is no security issue here—just simplification of the code.

This is a small internal code cleanup in Bitcoin Core's merkle tree calculation. It changes one function so that a list of hash values is passed by reference instead of by pointer, removing optional null-pointer checks that were no longer needed. There is no change to network behavior, consensus rules, or user-visible security.