Bitcoin Core

This commit removes an old automated test that checked whether the GCC compiler had a specific bug. The test no longer catches the bug in newer GCC versions, so the developers deleted it and updated a build-system comment to note which GCC versions are affected. There is no change to the actual Bitcoin Core program code or its security behavior.

This commit simply deletes a unit test that is no longer needed. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit removes a helper function that worked around a compiler/library bug in older versions of GCC. The project now requires a newer GCC version where the bug is fixed, so the workaround is no longer needed. There is no security issue here—this is routine code cleanup.

This commit adds a new compiler warning flag that flags trailing whitespace in source code. It is a code-style/build-hygiene change, not a security fix. There is no vulnerability being patched.

This commit changes Bitcoin Core's continuous integration (CI) settings for one automated testing job. It switches the build configuration to use a developer preset and enables experimental kernel-related components for testing. There is no change to the actual Bitcoin node software that users run, no bug fix, and no security patch.

This change loosens a strict rule in the Bitcoin Core kernel library so that callers can safely pass an empty data buffer even if its internal memory pointer happens to be null. Previously the library declared that certain pointers could never be null, which could cause crashes or undefined behavior when empty vectors produced null pointers. The patch now checks for the one truly invalid case—a null pointer paired with a non-zero length—and otherwise accepts null pointers when the length is zero.

This commit removes a build-system patch that forced Qt to avoid using newer native half-precision floating-point types. The change is a cleanup: Bitcoin Core no longer requires an old libgcc version, so the workaround is unnecessary. There is no direct security relevance in the diff itself.

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 only changes leading tabs to four spaces in a single generated header file. It is a pure whitespace/style cleanup with no functional change to the Bitcoin software.

This commit simply adds a small utility package called 'moreutils' to the software's automated testing and linting environment. It does not change any Bitcoin Core code that handles transactions, networking, wallets, or consensus. There is no security issue here.

This change simply tells the compiler to ignore a harmless style warning about extra spaces at the end of lines in files automatically generated by Qt's resource compiler. It does not fix a security bug or change any program behavior.

This commit adds a new compiler warning flag that flags leading whitespace characters that are spaces (rather than tabs). It is a code-style/build-hygiene change with no security relevance visible in the commit or supplied references.

This commit changes how Bitcoin Core's Qt graphical interface build system handles embedded resource files (like icons and translations). It switches from CMake's automatic Qt resource handling to an explicit Qt6 function call. There is no indication this is a security fix; it appears to be a routine build-system refactor for finer control over compilation.

This commit changes a single tab character to a space in a code comment within a third-party subprocess header file. It is purely a whitespace/cosmetic fix and has no effect on program behavior or security.

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.