Bitcoin Core

This commit only changes Bitcoin Core's continuous integration (CI) testing setup. It renames one CI job and adjusts build flags for an existing 32-bit (i686) test task so that it also exercises experimental kernel-related components. There is no change to the actual Bitcoin node code, consensus rules, wallet handling, networking, or any user-facing behavior.

This commit changes two Bitcoin Core continuous integration (CI) configuration files for macOS cross-compilation tasks. It switches the build to use the 'dev-mode' preset and explicitly disables USDT tracing, while keeping reduced symbol exports. There is no change to the actual Bitcoin node or wallet code that users run.

This commit changes Bitcoin Core's continuous integration (CI) settings for 32-bit ARM testing. It switches the build to use the 'dev-mode' preset and enables several experimental kernel-related components for testing. There is no code change that affects how Bitcoin Core runs in production, and nothing in the commit suggests a security fix or vulnerability.

This commit changes a Bitcoin Core continuous integration (CI) test job. It renames the Alpine Linux test task and switches its build configuration to use a developer preset that enables experimental kernel-related components. There is no change to the actual Bitcoin node software, wallet code, network handling, or any code that end users run. It is purely a testing/CI configuration adjustment.

This commit changes only a continuous integration (CI) configuration file for the s390x mainframe platform. It switches the build to use the developer preset and explicitly turns on experimental kernel-related build options for automated testing. There is no change to the Bitcoin Core software that users run, no bug fix, and no security-relevant code change.

This commit changes only a continuous integration (CI) test script. It switches the valgrind test job to use a developer build preset and explicitly turns on experimental Bitcoin kernel-related components for testing. There is no change to the actual Bitcoin Core software that users run, and nothing in the commit suggests a security fix or vulnerability.

This commit changes only the Bitcoin Core continuous integration (CI) test configuration. It turns on additional experimental kernel-related build options for the ThreadSanitizer (TSan) test job and switches it to use the developer-mode build preset. There is no change to the actual Bitcoin node code that users run, and nothing in the commit suggests a security vulnerability or fix.

This commit only changes Bitcoin Core's continuous integration (CI) testing configuration. It renames a CI job from 'MSan, depends' to 'MSan' and switches the build to use a 'dev-mode' preset that enables experimental kernel-related components for testing with MemorySanitizer (MSan). There is no change to the actual Bitcoin node or wallet code that users run, and nothing in the commit suggests a security vulnerability or fix.

This commit only adds a new test case to Bitcoin Core's test suite. It checks that when a block has no transactions, a helper function called TransactionMerklePath returns an empty path. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit only updates documentation. It changes the build instructions for Linux to recommend using the latest Debian stable or Ubuntu LTS release, and notes that older releases may need a newer compiler. There is no code change and no security fix or vulnerability introduced.

This commit only adds a release note document stating that the minimum supported GCC compiler version has been increased to 12.1. It contains no code changes and no security-related content.

This commit only changes Bitcoin Core's continuous integration (CI) testing configuration. It switches one CI job to use a development preset and turns on experimental kernel-related build options for testing purposes. There is no change to the actual Bitcoin software that users run, and no security issue is present.

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