Bitcoin Core

This is a minor internal cleanup in Bitcoin Core's Python test runner. It replaces a regular Python list used as a FIFO queue with a purpose-built deque, which avoids a theoretical slowdown when popping items from the front. The change only affects test infrastructure, not the live Bitcoin node software, and the commit message explicitly states behavior is unchanged.

This commit simplifies the internal copy behavior of a core Bitcoin data type (arith_uint256) by letting the compiler generate default copy routines instead of hand-written loops. The change is framed as a performance/cleanup improvement and includes a compile-time check that the type remains trivially copyable. There is no indication this fixes a security bug or introduces a vulnerability.

This is a Bitcoin Core continuous integration (CI) script change. It switches the LLVM source checkout from trying to match the locally installed clang version to always using a fixed tag (llvmorg-21.1.1). The commit message says this avoids intermittent CI issues. There is no change to the Bitcoin Core software that users run, no wallet or consensus code is touched, and no security vulnerability is described.

This commit only adds extra test cases and assertions for how Bitcoin Core handles script verification flags. It does not change any production code that processes real transactions, so it cannot introduce a security vulnerability or fix one in live software.

This commit changes Bitcoin Core's continuous integration (CI) configuration for GitHub Actions. It adds a per-job option to override which cache provider is used for Docker setup, specifically setting a 32-bit ARM job to use GitHub Actions' native cache instead of Cirrus Labs' cache. This is a build-infrastructure tweak with no apparent effect on the Bitcoin software users run, on their funds, or on network security.

This is a routine internal cleanup of Bitcoin Core's GitHub Actions CI configuration. It renames a workflow output from a true/false string ('use-cirrus-runners') to a provider name string ('provider' with values 'gha' or 'cirrus') and updates the action that reads it. The commit message explicitly says it is a refactor to avoid relying on the string 'false' being treated as truthy in future evaluations. There is no change to Bitcoin Core's actual code, consensus rules, wallet handling, networking, or any user-facing behavior.

This commit is a straightforward code cleanup: it replaces a confusing boolean parameter called main_only with a clearer enum named Level (with values TOP and MAIN) throughout the transaction-graph code. The behavior of the program is unchanged; only the names and call sites are updated to make the code easier to read and maintain.

This commit is a user-experience improvement, not a security fix. It adds a percentage-complete indicator to the log message shown while Bitcoin Core reindexes old block files. Before, users only saw which file was being processed; now they can see roughly how many files remain. There is no change to security-sensitive logic.

This change alters the Bitcoin Core debug console's text box so that when a user copies selected text, only plain text is placed on the clipboard. Previously, Qt's default behavior could convert the selection into HTML and Markdown formats, which the commit message describes as 'pathological.' The concern is that an attacker who can control text shown in the debug console (for example, error messages or RPC output) might be able to inject malicious content that, if copied and pasted elsewhere, could execute commands or leak data through rich-text features. The patch removes that rich-text conversion entirely.

This commit changes a Bitcoin Core continuous integration (CI) script so that a code-cleanup tool called Include What You Use (IWYU) treats its findings as hard errors for two source directories (`crypto` and `index`), while keeping them as warnings everywhere else. It is a build/development hygiene change, not a fix for a security vulnerability or a change to the Bitcoin protocol or wallet code.

This commit is a routine code cleanup that adjusts which header files are included in the `index` directory of Bitcoin Core. It does not change program behavior, fix a bug, or address a security issue. It simply makes the include lists more precise so the code compiles cleanly with include-what-you-use tooling.

This commit adds a placeholder manual page file for the bitcoin binary. It contains only documentation text and instructions for generating real manpages later. There is no executable code, no configuration change, and no security relevance.

This commit is a routine code cleanup that adjusts which header files are included in the cryptographic source files. It does not change any program logic, algorithms, or security behavior. The goal is to make the include lists match what the compiler actually needs, which helps maintainability and tooling but has no direct security impact.

This is a small change to Bitcoin Core's continuous integration (CI) script. It stops applying a temporary code patch to the LevelDB database library during one specific CI job (the 'tidy' job). The patch was a workaround for undefined behavior (reading uninitialized memory) in LevelDB. The tidy job only checks code style and include-usage issues, so it doesn't need the patch. The underlying undefined behavior in LevelDB is not fixed by this commit; it just changes when the workaround is applied.

This commit simply adds the 'bitcoin' binary to a developer script that automatically generates manual pages. It is a build/maintenance tooling change with no security relevance.

This commit simply changes the displayed major version number of Bitcoin Core from 29 to 30 in the build configuration. It is a routine development bookkeeping change with no security relevance.

This commit only deletes a documentation file (a release note fragment). It does not change any code, so it cannot introduce or fix a security bug by itself. The deleted text described an earlier overflow bug in an index feature, but that bug was already addressed in a previous code change referenced by the release note.

This commit only adds a new test to Bitcoin Core's test suite. It verifies that a Bitcoin node correctly disconnects a peer that sends an unexpected duplicate 'blocktxn' message after a compact block reconstruction already failed. There is no change to production node code, so this commit does not introduce or fix a live security vulnerability by itself.

This change fixes a bug in how Bitcoin Core handles repeated compact-block transaction messages from peers. In debug builds, receiving multiple blocktxn messages for the same block could trigger an internal consistency check (Assume) crash because the code tried to look up information from a header that had already been cleared. The patch detects the empty-header situation, marks the peer as misbehaving, and returns early instead of crashing. It is a robustness fix that prevents a debug-only crash and tightens handling of misbehaving peers.

This commit fixes a formatting bug in benchmark output. The SHA256AutoDetect function returns a string describing which CPU-accelerated SHA-256 implementations are active. That string previously used commas, which broke CSV-formatted benchmark reports because commas are the field separator. The patch swaps commas for semicolons so benchmark CSV files parse correctly. It is a data-formatting fix, not a security fix.

This is a build-system fix for Bitcoin Core's Guix reproducible-build process. Some internal helper programs were moved into a 'libexec' folder, but the release build script was still only stripping debug symbols from the 'bin' folder. The patch adds 'libexec' to the list of directories processed so those helper binaries are also split from their debug symbols, keeping release binaries smaller and consistent with the rest of the build.

This commit is a routine update of the non-English user-interface translations for the Bitcoin Core Qt (graphical) wallet. It adds, removes, and reorders translated text strings and drops a number of very low-translation-coverage locale files. There is no executable code change, no change to wallet logic, networking, consensus, or cryptography, and no security-relevant behavior is introduced or fixed.

This commit only deletes release-note documentation files from the Bitcoin Core repository and moves them to the project's wiki. No program code, configuration defaults, or executable behavior was changed. It is purely a documentation housekeeping step before creating a new release branch.

This change makes Bitcoin Core shut down faster when a network port-mapping feature (PCP/NAT-PMP) fails during startup. Previously, the retry loop kept waiting for responses even after the user asked the program to quit, causing a long delay. There is no security vulnerability being fixed here—only a responsiveness/usability improvement.

This commit removes an unnecessary std::move in a database write and adjusts a fuzz test variable to silence a clang-tidy warning. There is no security issue in the diff itself; it is a code-quality cleanup.