Bitcoin Core

This commit simply adds a standard copyright and license notice to the top of a generated source file. It is a legal/documentation change, not a security fix or code behavior change.

This commit only adds standard copyright notice comments to the top of two test-only source files. It makes no changes to program logic, data handling, or network behavior, and therefore has no security relevance.

This commit simply restores a copyright and explanatory comment block at the top of a source file. It is a documentation-only fix with no effect on program behavior, security, or network safety.

This commit only updates copyright header wording in two test files, changing '2024-Present' and '2022-' to '2022-present' for consistency. It does not change any executable code, network behavior, or security logic.

This commit updates the version of the Cap'n Proto library used in Bitcoin Core's build system from 1.2.0 to 1.3.0, along with its corresponding checksum. It is a routine dependency bump with no direct code changes to Bitcoin Core itself. There is no explicit security claim in the commit, and no verified references were provided to indicate this fixes a known vulnerability.

This commit only adds a new automated test file to Bitcoin Core. It checks that a node correctly tells its peers about its own external IP address after connecting and again later. There is no change to the actual Bitcoin network code, only new test code.

This commit is a documentation-only change for the Bitcoin Core RPC command `listtransactions`. The author noticed an unexpected behavior while testing another change and updated the help text so users can see it. No code behavior was changed, and there is no security fix or vulnerability here.

This commit only adds new test cases to a JSON test data file for Bitcoin Core's script validation tests. It does not change any production code, cryptographic checks, or network rules. The new tests verify that invalid public key formats are correctly rejected, which improves code coverage but introduces no security change by itself.

This change fixes a logic bug in Bitcoin Core's peer-to-peer block downloading. After a node finishes validating an 'assumeutxo' snapshot, it was still refusing to download blocks from peers whose best chain did not include the snapshot block—until the node was restarted. The fix removes that unnecessary restriction once validation is complete, allowing normal block downloads to resume. It is a network-efficiency and robustness fix rather than a direct theft-of-funds vulnerability.

This commit simply bumps the GitHub Actions 'checkout' step from version 5 to version 6 in the project's continuous integration (CI) workflow file. It does not change any Bitcoin Core source code, consensus rules, wallet logic, or network behavior. There is no indication of a security fix or vulnerability.

This commit is a routine tooling change for Bitcoin Core. It adds the clang-format package to a CI environment, runs clang-format after an automated include-sorting tool, and changes a formatting configuration option so that #include statements are regrouped and sorted. There is no change to the actual Bitcoin software logic, network behavior, or wallet handling, so it does not affect users' funds or node security.

This commit adds a new automated CI (Continuous Integration) job that runs a tool called Include What You Use (IWYU) to check that source files include only the headers they actually need. It also makes minor supporting changes: adding a CI configuration, installing the IWYU tool, adjusting build scripts, adding a mapping file for IWYU, and removing an unused <tuple> header from one source file. There is no change to Bitcoin Core's runtime behavior, consensus rules, networking, wallet logic, or any user-facing functionality. It is purely a code-quality and tooling improvement.

This is a one-character CMake build-system fix. The developer corrected the name of an internal test target from 'mptests' to 'mptest' so that automated testing (ctest) can find and run it. It has no effect on the Bitcoin network, wallets, consensus rules, or user-facing security.

This is a tiny CMake build-system change. It removes the EXCLUDE_FROM_ALL flag from a static library so that a code-generation target is built when needed. There is no indication this affects runtime security, wallet funds, network consensus, or user data.

This commit only changes a patch file used by the continuous-integration (CI) 'include what you use' (IWYU) linting tool. It tells the linter to recommend C++ standard headers (like <cstdio>) instead of C-style headers (like <stdio.h>) when reviewing Bitcoin Core source code. The change does not alter any compiled Bitcoin Core code, runtime behavior, or network protocol, so it has no direct security impact on users running Bitcoin Core.

This commit is a build-tooling change only. It adds a patch for the Include What You Use (IWYU) static-analysis tool used in Bitcoin Core's continuous integration (CI). The patch forces IWYU to suggest C++ #include statements using angle brackets (<...>) instead of quoted local paths ("..."). There is no change to Bitcoin Core's actual consensus, networking, wallet, or node code, and no security-relevant behavior is modified.

This commit changes Bitcoin Core's logging system so that when the optional -logsourcelocations setting is enabled, log lines show only the simple function name (e.g., 'ProcessMessage') instead of the full C++ function signature (e.g., 'void ProcessMessage(...)'). It introduces a small wrapper class around std::source_location to allow overriding the function name with the __func__ macro. There is no security fix here; it is a user-facing log-format cleanup.

This commit is a portability fix for compiler warnings about missing braces when initializing IPv6 address constants. It introduces platform-specific macros so the code compiles cleanly on illumos and Microsoft Visual C++ without changing behavior. There is no security issue here.

This commit is a documentation-only cleanup. It replaces an outdated example fuzz target name (address_deserialize_v2) with the current name (address_deserialize) in a user guide and a code comment. No executable code, logic, or security behavior is changed.

This commit simply moves a constant named MAX_BLOCK_TIME_GAP from one source file (src/chain.h) to another (src/qt/bitcoingui.cpp). The value and its meaning stay exactly the same. It is a code-cleanup change with no functional or security effect.

This is a small cleanup in Bitcoin Core's internal test helper code. It changes how an error message is re-raised so that Python no longer prints a confusing 'another exception occurred' chain when a test node fails to start. There is no change to the Bitcoin network protocol, wallet handling, consensus rules, or any production code.

This commit only adds a new automated test to Bitcoin Core's internal quality-assurance suite. It checks that a helper function used during testing raises exactly one exception when a node startup error does not occur within the expected timeout. There is no change to production code, no user-facing behavior change, and no security vulnerability being fixed.

This is a minor improvement to a Bitcoin Core test script. It adds clearer debug logging when a test child process produces the expected output, and it handles the edge case where a timeout occurs with no captured output. There is no change to the actual Bitcoin Core software that users run, and no security issue is present.

This is a small test-code cleanup that moves a helper for calculating RPC timeout into a reusable mixin. It does not change Bitcoin Core's production code, network behavior, or wallet security. There is no vulnerability here.

This is a tiny fix to a Bitcoin Core internal QA test script. A previous change tried to make a subprocess error message readable by enabling text mode, but Python still stores the output as bytes in TimeoutExpired exceptions. The patch adds an explicit .decode('utf-8') so the test's debug printout works instead of crashing with a bytes/string formatting error. It only affects test failure diagnostics, not live Bitcoin node code, wallets, consensus, or network behavior.