Bitcoin Core

This commit is a straightforward cleanup of Bitcoin Core's macOS build scripts. It moves repeated LLVM/clang toolchain setup code from two separate scripts into a single shared function, with no change to the actual commands or build behavior. There is no security issue visible in the diff.

This commit adds a new menu item in the Bitcoin Core desktop wallet that lets users export a 'watch-only' copy of their wallet. A watch-only wallet can see transactions and balances but cannot spend funds. The change only wires up an existing export function to the graphical user interface; it does not appear to fix a bug or introduce a security vulnerability.

This commit only adds a release note describing a new graphical menu option in the Bitcoin Core wallet. It documents a feature that lets users create a watch-only wallet file from an existing descriptor wallet, matching an existing RPC command. There is no code change and no security issue.

This commit only adds a short release note describing a new wallet-migration user-interface option. There is no code change, no bug fix, and no security-related content in the diff.

This commit adds a user-facing checkbox in the Bitcoin Core desktop wallet that lets someone choose whether to automatically load a wallet after migrating it from an older format. Previously the wallet was always loaded. The change is a usability improvement, not a security fix, and does not introduce any obvious vulnerability.

This commit is a small internal code cleanup in Bitcoin Core. It removes the ability of a utility called LineReader to accept raw byte buffers, and updates two network components (Tor control connection and HTTP server) to use ordinary std::string buffers instead. There is no indication in the commit that this fixes a security vulnerability; it appears to be a refactoring to simplify the code and make buffer handling more consistent.

This is a small internal code cleanup in Bitcoin Core. It rewrites a helper class called LineReader so it works directly with string data instead of converting bytes to strings back and forth. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This is a small code cleanup in Bitcoin Core's line-reading utility. It changes how the reader strips newline characters from input lines. The old code tried to remove both '\n' and '\r' from the end of a line after the fact; the new code builds the line without the '\n' in the first place and only strips a trailing '\r' if present. The commit message frames this as a correctness improvement for single-character '\r' line endings. There is no direct evidence in the commit or supplied references that this fixes an active security vulnerability.

This commit adds a helper function in Bitcoin Core's graphical user interface code that safely connects a Qt signal to an anonymous function (lambda). It wraps the function so that if it throws an exception, the error is caught and reported instead of crashing the program. It also updates an existing error-printing helper to handle cases where there is no named receiver object. This is a defensive code-quality improvement, not a fix for an active security vulnerability.

This change fixes a minor bug in Bitcoin Core's RPC command `addnode`. Previously, if a user passed an empty or whitespace-only address, Bitcoin Core would add it to its persistent 'try to connect' list and keep retrying forever, even though the address could never work. Now it immediately rejects the bad input with a clear error message. It is a hardening fix rather than a serious security vulnerability.

This change fixes a minor startup bug in Bitcoin Core where an empty -addnode setting (for manually adding network peers) would create a useless peer record that the software tried to connect to over and over. Now empty or whitespace-only values are skipped, and a warning is logged. It is a hardening/cleanup fix rather than a serious security vulnerability.

This commit simply removes an unused import statement from a Guix build manifest file. It is a minor cleanup with no functional or security effect on the Bitcoin Core software itself.

This is a build-system hardening change for Bitcoin Core. It tells the compiler to hide inline C++ functions from the list of symbols exported by shared libraries and executables. This reduces the attack surface by making fewer internal functions visible to outside code, but it is not a fix for a known exploitable bug.

This commit only adds a single sentence to a project policy document (doc/AI_POLICY.md), telling contributors not to list AI agents as authors or co-authors of commits. It makes no code changes and has no direct security effect on the Bitcoin Core software.

This commit is a code cleanup that changes many internal class constants from 'static const' to 'static constexpr'. In modern C++, constexpr constants are automatically inlined and avoid certain linker errors when used in specific ways. There is no functional change to Bitcoin's behavior, no bug fix, and no security-relevant change.

This commit only adds a new automated test file and registers it in the test runner. It does not change any production code in Bitcoin Core, so it cannot introduce a security vulnerability or fix one directly. The test verifies existing behavior around how many inbound peer connections a node accepts and when it drops connections.

This commit only updates two documentation files to reflect that the default value for the -maxconnections setting changed from 125 to 200. It does not change any code, configuration defaults, or network behavior. There is no security issue here.

This Bitcoin Core commit increases the default maximum peer connections from 125 to 200 and reserves half of inbound slots for block-relay-only peers that don't forward ordinary transactions. It also adds eviction logic so that when a new transaction-relaying inbound peer arrives and the node is at capacity, it tries to disconnect an existing transaction-relaying peer instead of a block-relay-only peer. The change is described by the authors as a network-capacity improvement, not a security fix, but it can make certain denial-of-service and eclipse-style attacks harder by diversifying peer types and limiting how many transaction-relaying inbound peers an attacker can occupy.

This commit adds a new user-configurable setting called -inboundrelaypercent to Bitcoin Core. It lets node operators choose what percentage of incoming peer connections are allowed to relay transactions, instead of being hard-coded to 50%. The change itself is a feature/configuration tweak, not a fix for an active security bug. It could indirectly affect resource usage or network behavior if set unwisely, but it does not introduce a clear vulnerability.

This commit only adds a new automated test to Bitcoin Core. It checks that when the node is full of block-only peers (peers that do not relay transactions), an incoming connection is rejected rather than incorrectly kicking out a block-only peer. There is no code change to the actual Bitcoin node behavior—only a test is added.

This Bitcoin Core patch fixes a small logic gap in peer-to-peer connection management. When a node supports bloom filters, a peer could switch itself into transaction-relaying mode at runtime without the node checking whether it already had too many transaction-relaying peers. The fix makes the node run its existing eviction check in those two cases, so an over-limit peer can be disconnected. The change is defensive and does not appear to enable remote crashes or theft of funds, but it could let a single peer occupy a limited tx-relay slot that the node otherwise tries to protect.

This commit changes the Bitcoin Core build setup for Guix (a reproducible build system) by adding '--disable-nls' when compiling the base GCC compiler used in the build process. NLS stands for Native Language Support, which provides translated error messages and other locale-dependent features. Disabling it makes the compiler toolchain leaner and more deterministic, reducing the chance that translated messages or locale-dependent behavior could subtly change build outputs. There is no direct security vulnerability being fixed here; it is a hardening/reproducibility improvement to the build environment.

This commit adjusts the build settings used to compile the Windows version of Bitcoin Core's toolchain. It copies some hardening and cleanup options from the Linux build configuration to the Windows (MinGW) build configuration, and reorders others. There is no direct evidence this fixes an active security vulnerability; it appears to be a build-hardening and consistency improvement.

This commit changes how Bitcoin Core's reproducible build system compiles its own copy of the GCC compiler. It adds a flag that removes unused support for 'transactional memory' from a low-level compiler helper library. This is a build-hardening/size-reduction change, not a fix for an active security bug. There is no evidence it addresses a known vulnerability or changes how Bitcoin nodes process data.