Bitcoin Core

This commit only updates the example text in a GitHub bug report template. It changes the placeholder operating system examples from older versions (MacOS Ventura 13.2 and Ubuntu 22.04 LTS) to newer versions (MacOS 26.0 and Ubuntu 26.04 LTS). There is no code change, no security fix, and no vulnerability.

This commit is a code cleanup (refactor) that changes how a lookup table of script verification flag names is created and accessed. It moves the table from a global variable constructed at program startup to a function that creates the table the first time it is called. There is no change to transaction validation rules, no bug fix, and no security-relevant behavior change.

This commit only changes a test file. It adds a new test scenario to make sure a previously fixed bug in block-download stalling logic stays fixed. There is no change to the actual Bitcoin Core node software, so it cannot directly affect live network security.

This commit only changes a test file. It replaces a hard-coded byte-count workaround with a cleaner check using existing peer information. There is no change to the actual Bitcoin Core software that users run, and no security issue is present.

This change fixes how Bitcoin nodes decide which blocks to ask peers for during initial sync or catch-up. Previously, the node could get stuck reviewing blocks it already had, fail to request new blocks it actually needed, and incorrectly label peers as slow (stallers). The patch makes the 'last common block' calculation follow the current chain tip and the peer's known chain more accurately. It is a robustness improvement to block download scheduling, not a direct theft or remote-code-execution bug.

This commit removes compiler warning suppressions from two test files. It is a code cleanup that reverts an earlier workaround for a Clang compiler warning about self-assignment (like x = x). It does not change any production code, network behavior, or wallet logic, and has no direct security impact on Bitcoin users.

This commit simply raises the minimum supported Clang compiler version from 16 to 17 and removes a now-unnecessary C++ deduction guide. It is a routine build-system/maintenance change with no security relevance.

This commit adds a new automated test for Bitcoin Core's developer testing tool called TestShell. It does not change any production code, network rules, or wallet behavior. It only runs in the project's own test environment and is not a security fix or vulnerability.

This commit only updates documentation for Bitcoin Core's test shell. It changes an example output to remove a wallet passphrase warning that is no longer returned, and removes a 'noshutdown' option from a table because that option was removed in an earlier commit. There is no code change and no security impact.

This commit simply bumps a GitHub Actions helper from version 4 to version 5 in the project's continuous-integration workflow. It is a routine dependency update with no visible security relevance in the diff itself.

This is a tiny CI (Continuous Integration) configuration fix. The GitHub Actions script was accidentally pointing to the wrong path for an environment file when computing a cache hash. As a result, changes to that environment file would not invalidate the build cache. It is not a vulnerability in Bitcoin Core itself and does not directly put user funds or node security at risk, but it could theoretically cause CI to reuse a stale dependency cache after an environment change.

This is a one-line fix in Bitcoin Core's dependency build system. When downloading a required library from a fallback mirror, the code was accidentally using the original download URL as the filename instead of the intended filename. This could cause the downloaded file to be saved under the wrong name, potentially leading to a failed or mismatched build. The change makes the fallback download use the correct filename.

This commit simply reverts a recent change to the download URL and checksum for the qrencode dependency used in Bitcoin Core's build system. It restores the older, original source URL and its corresponding hash. There is no security issue visible in the diff itself.

This commit undoes a recent change in the Bitcoin Core dependency build system. The original change made build stamps use a cryptographic hash to track downloaded packages; this reversion goes back to using the package file name. On its own, this is a build-system correctness/reliability change, not a clearly exploitable security vulnerability. It could, in unusual cases, make the build slightly more prone to re-downloading or cache-confusion issues if a package file name stays the same while its contents change, but no direct attack is demonstrated in the commit.

This commit adds a new automated build test that cross-compiles Bitcoin Core for Intel (x86_64) macOS, while renaming the existing macOS cross-compile test to target Apple Silicon (arm64). It only changes continuous integration configuration and documentation. There is no change to the Bitcoin Core software that users run, and no security issue is present.

This is a minor GitHub Actions workflow refactor. It changes one CI step from running inside the 'test' directory to running from the repository root by specifying the script path as './test/get_previous_releases.py'. The commit message explicitly states this does not change behavior and is only to allow re-use in other tasks. There is no security relevance.

This commit changes only a macOS CI fuzz-testing script. It adds a compiler flag that turns on extra safety checks in Apple's C++ standard library during automated fuzz testing. It does not change any production code, wallet logic, networking, or consensus behavior. There is no indication this fixes a security bug in Bitcoin Core itself; it is a testing-hardening configuration change.

This commit only adds documentation explaining how developers can update a code subtree (a bundled external library). It contains no code changes, no configuration changes, and no security fixes or functional behavior changes.

This is a routine subtree update for the libmultiprocess library used by Bitcoin Core. The bulk of the changes are developer-facing improvements: adding log levels, fixing typos, updating CI sanitizer settings, and adding tests. The most notable functional change is a fix for a crash that could occur when multiple IPC calls were made on the same thread at the same time. The fix makes the code throw a controlled 'thread busy' error instead of crashing. It is a stability/reliability improvement rather than a traditional security vulnerability fix.

This commit removes a single line from a Bitcoin Core continuous integration (CI) configuration file. The removed line forced the Windows cross-compilation CI task to run on the linux/amd64 platform. After the change, the CI task will use the CI runner's native platform instead. This is a build-infrastructure tweak with no apparent effect on the Bitcoin Core software that end users run.

This commit changes how Bitcoin Core opens files on Windows. Previously it used a Unicode-aware Windows function (`_wfopen`) that could handle non-English characters in file paths. Now it uses the older ANSI `fopen`, which only reliably supports a limited set of characters. On some Windows systems this could make file paths containing certain characters fail to open, potentially causing wallet or data file errors. It is not a direct remote exploit, but it is a reliability/security-adjacent change on Windows.

This commit removes a Windows-specific helper class that converted command-line arguments from Windows' native wide-character format to the standard character format used by the rest of the program. The change is a cleanup to avoid using a C++ standard library feature (`std::wstring_convert`) that is being phased out. It is not a security fix and does not appear to introduce a vulnerability; it simply changes how Windows command-line arguments are handled, likely relying on a newer mechanism elsewhere.

This commit changes how Bitcoin Core handles text encoding on Windows. It tells Windows programs to use UTF-8 (a universal character encoding) instead of older regional code pages, and adds the same declaration to several helper programs that were missing it. It also makes the main bitcoin program run a setup routine that was previously only used by other entry points. The change is primarily a robustness/correctness fix; it does not by itself create a vulnerability, but it removes a class of bugs where non-English characters in file paths, command-line arguments, or log messages could be misinterpreted. Those misinterpretations could, in some situations, contribute to security-relevant behavior such as wrong file access or corrupted data.

This commit changes how Bitcoin Core turns Windows system error numbers into human-readable text. It switches from the modern Unicode ('wide character') version of a Windows API to the older ANSI ('A') version. The change removes C++ standard-library helpers for converting between Unicode and UTF-8. The practical effect is that error messages on Windows may no longer display correctly for languages that need non-ASCII characters; it is not a direct remote-exploitable vulnerability.

This commit only updates a documentation template to state that the minimum supported Windows version is Windows 10 version 1903 (May 2019 Update). It does not change any code, build settings, or runtime behavior. The change is purely informational and has no security relevance on its own.