Bitcoin Core

This commit is a minor linting fix. It adds a new test directory (src/ipc/test) to an internal script that checks whether Bitcoin's C++ test files use a specific Boost test macro correctly. It does not change any production code, wallet logic, networking, or consensus rules. There is no security issue here.

This commit is a minor cleanup of internal linting scripts. It moves one directory path into a shared list so that multiple code-style checkers can reuse it. There is no change to the Bitcoin software that users run, no change to security logic, and no security relevance.

This commit is a code cleanup that fixes inconsistent whitespace (tabs vs. spaces, trailing spaces) in several helper scripts and removes those files from a linting exclusion list. It does not change any program logic, behavior, or security settings.

This is a build-system tweak for Qt translation files. It explicitly tells the translation tool to use English as the target language instead of potentially defaulting to 'en_US'. There is no security issue here—it only affects how translation metadata is generated during compilation.

This commit changes how Bitcoin Core's user-interface text is sorted in translation files. It adds a build option to sort messages alphabetically within each context, which only affects the order of strings in the generated translation source file. There is no change to program behavior, logic, or security.

This commit changes how Bitcoin Core's translation files are generated. It removes source-code file references (line numbers and filenames) from the translation catalog to reduce unnecessary version-control noise. There is no security-relevant change to the running software, wallets, network, or consensus code.

This commit is a routine build-system cleanup. It removes an intermediate file-format conversion step used for translating the Bitcoin Core user interface into other languages. The project will now use Qt's native .ts translation files directly instead of first converting them to the XLIFF (.xlf) format. There is no security-relevant change here.

This commit is a pure code reorganization: it takes the existing logic that handles incoming network address messages and moves it into a new helper function called ProcessAddrs(). No behavior changes, security fixes, or new features are introduced.

This commit is a routine translation workflow update. It changes the file format used for Bitcoin Core's Qt translations from .xlf to .ts and updates the corresponding version slug from 031x to 032x. There is no security relevance.

This is a test-only change in Bitcoin Core. It improves a wallet rescan test so that it actually verifies the FastWalletRescanFilter is updated correctly during scanning. The previous test setup accidentally allowed the filter to be stale and still pass because a fixed non-range descriptor address matched every block. There is no change to production wallet code, so this does not directly fix a live security bug.

This commit removes three source-code files from a linting exclusion list. The lint check in question only enforces whitespace formatting rules. There is no change to Bitcoin Core's runtime behavior, consensus logic, networking, wallet, or any user-facing functionality. It is a pure code-quality tooling cleanup.

This commit fixes a Bitcoin Core fuzz test harness so that simulated peer nodes are marked as successfully connected. Without this flag, the test's code coverage was poor because the harness filtered out all fake nodes before running important connection-management logic. It is a test-only improvement with no effect on live Bitcoin node behavior or user funds.

This is a code-quality fix for Bitcoin Core's RPC help output. It changes how the documentation generator marks parts of the response as '...' (elided) so that the internal type checker can still verify the real data types. It does not change how transactions are decoded or how the network behaves, and it is not a security patch in the usual sense. The only user-visible change is a slightly clearer help message for the decodepsbt command.

This commit simply updates a build dependency, the Cap'n Proto library, from version 1.3.0 to 1.4.0 inside Bitcoin Core's build system. It changes the version number and the cryptographic checksum used to verify the downloaded source. There is no indication in the commit itself that this fixes a security problem, and no security advisory was provided. Dependency updates can sometimes include hidden security fixes, but this change alone does not show one.

This commit adds a build-time check that the compiler supports a modern C++ feature called CTAD (Class Template Argument Deduction). It does not change how Bitcoin Core runs, only how it is compiled. It is a defensive build-system improvement, not a security fix or vulnerability.

This commit only adds three documentation path strings to the build configuration file. It does not change any compiler behavior, security checks, or executable code. There is no security relevance visible in the diff.

This is a small test-only change in Bitcoin Core's Python testing framework. It moves where an internal networking event loop is created so it is created on the same thread that later runs it, rather than on the main test thread. The goal is to stop an intermittent crash/abort that happens on Windows when running functional tests. It does not change the Bitcoin node itself, consensus rules, wallet handling, or network protocol, and there is no indication it fixes a security vulnerability.

This is a minor test-only change that adds an extra command-line flag to silence false-positive memory-leak messages from the Windows debug runtime during internal Bitcoin Core tests. It does not change any production code, network behavior, or wallet logic, and it does not fix a security vulnerability.

This is a tiny test-only code cleanup. It swaps one way of choosing an older-style event loop on Windows for another equivalent way, because the old approach is being removed in newer Python versions. It does not change Bitcoin Core's production network code, consensus rules, wallet handling, or any user-facing behavior. There is no security issue here.

This commit only changes compiler warning settings. It adds a new warning flag that alerts developers when a switch statement already handles every possible case but also has an unnecessary default label. It does not change any program behavior or fix any security bug.

This commit is a code cleanup (refactor) that changes how switch statements are written so the compiler can warn developers if they forget to handle a new option in the future. It does not fix a security bug, change program behavior, or introduce a vulnerability. It only makes the code style more consistent and improves future maintainability.

This commit fixes a single-word typo in a documentation file. The text incorrectly said a server class was in the 'bitcoin-wallet' process when the surrounding explanation describes the 'bitcoin-node' process. There is no code change and no security relevance.

This commit only updates comments and an error message in test-related code. It does not change any program logic, so it cannot affect live Bitcoin Core behavior or introduce a security issue.

This commit simply deletes unused helper functions and an unused variable from a single test file. It does not change any production code, network behavior, or wallet logic. There is no security issue here.

This commit simply removes two unused variables from a single test file. It does not change any production code, network behavior, or security logic. There is no security relevance.