Bitcoin Core

This commit only changes the user-facing help text for the `-loadblock` command-line option. It adds a note that the option cannot read obfuscated (scrambled) block files. There is no code behavior change, no bug fix, and no security-relevant change.

This commit is a simple internal code cleanup in Bitcoin Core. It removes a small wrapper class called ConnectTrace and replaces it with a plain list (std::vector) of connected blocks, renaming some variables for clarity. There is no change to network rules, transaction validation, wallet behavior, or any user-facing feature. It does not fix a bug or introduce a known security issue.

This commit only changes a test file. It improves an existing functional test that exercises a known undefined-behavior bug in Bitcoin Core's block index handling. The test now uses a separate node, creates a three-way block race instead of a two-way race, and triggers the bug more reliably across different C++ standard library implementations. It does not change production code, so it does not fix or introduce a vulnerability by itself.

This commit fixes a low-level memory-handling bug in Bitcoin Core's startup code. When loading the chain tip, the program was changing a value (nSequenceId) that is also used to sort a set of candidate blocks, while the block was still in that set. In C++, changing a sort key while an item is in a sorted set is 'undefined behavior'—the program may crash, corrupt data, or behave unpredictably. The fix moves the population of the candidate set to after all such changes are complete. A second, related problem existed with the experimental assumeutxo feature, where two separate chain states share the same block objects and could interfere with each other's candidate sets. The patch addresses both by clearing and repopulating candidate sets at safe points.

This commit fixes a test-only race condition during shutdown of benchmark and unit tests that use Bitcoin Core's index objects. It adds a missing Stop() call in one benchmark and removes unnecessary synchronization comments/calls in several tests. The issue is not exploitable by users or network attackers; it only affects internal test code and could cause flaky or incorrect test results, including a potential virtual-pointer (vptr) race during benchmark teardown.

This commit removes a redundant function call and its assertion from the snapshot activation code in Bitcoin Core. The commit message explains the call was doing nothing useful because an earlier step already set the same state. There is no security-relevant change visible in the diff or commit message.

This commit adds a new fuzz test to Bitcoin Core that checks whether PSBT (Partially Signed Bitcoin Transaction) data can be serialized and then deserialized back to the exact same bytes. It is a defensive test meant to catch future bugs where the software might write a PSBT format it cannot later read. The commit itself does not fix any active vulnerability; it adds a regression test.

This commit fixes a flaky automated test in Bitcoin Core. It replaces a complicated node restart/sync dance with a simpler helper that manually copies blocks between test nodes via RPC. There is no change to production code, no security fix, and no vulnerability.

This commit swaps the internal macro used to detect Windows builds in a third-party subprocess helper header. Previously the code checked for Microsoft Visual C++ or MinGW compilers to decide 'this is Windows'; now it uses the standard WIN32 macro. There is no change to actual program logic, only to the condition that selects Windows-specific versus Unix-specific code paths. It is a portability/build cleanup, not a security fix.

This commit updates Bitcoin Core's kernel test suite to use the project's own filesystem helpers and to include a Windows application manifest. It also makes the temporary test directories contain a corn emoji (🌽) to exercise Unicode path handling. The changes are test-only and defensive: they improve test coverage for non-ASCII paths on Windows, but do not fix a live vulnerability in production code.

This commit is a small code cleanup in Bitcoin Core. It replaces a hand-written equality check for a custom vector-like container (`prevector`) with a standard C++ library function (`std::ranges::equal`). There is no security-relevant change visible in the diff, and no security context is provided by the commit or any supplied references.

This is a documentation-only update to the Windows build instructions. It simply notes that compiling the graphical user interface (GUI) for Windows now requires GCC version 13 or newer. There is no code change, no bug fix, and no security issue.

This commit adds a build-system patch for the Qt library used by Bitcoin Core. The patch moves two compile-time type checks (static_asserts) from inside a C++ class definition to outside it, because a newer GCC 16 compiler flag reports that the checks were placed where they could give misleading errors during template selection (SFINAE warnings). It is a build/toolchain compatibility fix, not a change to Bitcoin Core's consensus, networking, wallet, or node logic.

This commit adds a build-system patch so Bitcoin Core's bundled Qt dependency can compile with the upcoming GCC 16 compiler. It is a backport of an upstream Qt fix that handles a change in how GCC 16 represents certain C++ comparison values internally. There is no indication this fixes a security vulnerability; it is purely a compatibility/build fix.

This commit adds four build-compatibility patches to the Qt source code that Bitcoin Core downloads and compiles. The patches fix C++ template/header ordering problems that cause errors or warnings when building with the upcoming GCC 16 compiler. These are compile-time hygiene fixes, not security bug fixes, and they do not change how Bitcoin Core behaves at runtime.

This commit updates the Qt graphical toolkit used by Bitcoin Core from version 6.7.3 to 6.8.3. It changes download URLs, checksums, build settings, and patches. The update itself is a routine dependency refresh, but any Qt upgrade can introduce or fix security issues in the user interface code. The commit does not mention any specific security problem, and the visible changes are mostly build-compatibility and reproducibility adjustments rather than obvious vulnerability fixes.

This is a one-line fix to a CMake build script that looks for the Qt GUI library. Previously, the build could proceed even if a required Qt component was missing, because the script only checked that Qt's main directory was set. Now it also checks that Qt was actually found. This prevents silent misconfiguration of the build, but it is a build-time correctness issue rather than a runtime vulnerability in Bitcoin Core itself.

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 commit updates the Bitcoin Core continuous integration (CI) system to use Clang 22 instead of Clang 21 for the clang-tidy static analysis task. It also adds an explicit path to the clang-tidy configuration file because the newer version no longer finds it automatically. This is a build/test infrastructure change with no effect on the Bitcoin Core software that users run.

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.