Bitcoin Core

This is a routine code cleanup in Bitcoin Core's graphical user interface. It replaces a few internal helper function calls with their newer equivalents and removes the old, now-unused helper aliases. The commit message explicitly states this does not change behavior, and the diff shows identical logic with only renamed function calls.

This commit only updates the Windows build instructions document. It replaces manual download steps with commands using WinGet, a Microsoft package manager, and renumbers some sections. There are no code changes and no security implications.

This is a harmless internal cleanup of a performance benchmark. It swaps the test data used to measure a hex-encoding function from a real historical block file to computer-generated random bytes. There is no change to how Bitcoin Core handles real network data, no bug fix, and no security relevance.

This change is purely cosmetic: it stops Bitcoin Core from repeatedly printing the same router-related warning in the log. Home routers that don't support automatic port mapping now produce one warning instead of many, with later messages hidden behind a debug log level. There is no security vulnerability being fixed and no behavior of the network code is changed.

This commit fixes how two command-line settings, -rpcworkqueue and -rpcthreads, are read in Bitcoin Core's HTTP server. The old code used a method meant only for whole numbers (GetIntArg) but treated the result as a generic argument, which could lead to incorrect parsing or unexpected behavior. The new code uses the proper GetArg method and removes unnecessary newline characters from two log messages. There is no direct evidence in the commit that this was a security vulnerability, but misconfigured thread or queue limits could affect server stability or resource use.

This commit is a routine internal code cleanup in Bitcoin Core. It replaces a hardcoded integer-parsing helper with a generic template that can handle several integer sizes, and keeps the old function names as thin wrappers so existing code keeps working. There is no user-facing change and no security fix.

This commit only adds a new test to Bitcoin Core's functional test suite. It checks that network log messages include the peer number and peer address in a specific format before a planned formatting change. There is no change to production code, no bug fix, and no security-relevant behavior.

This commit is a straightforward code cleanup that changes how Bitcoin Core formats peer-related log messages. It introduces a helper function called LogPeer that consistently prints the peer ID and, when IP logging is enabled, the peer's address separated by a comma. There is no security vulnerability or behavior change beyond log message formatting.

This is a minor logging-only change. When Bitcoin Core logs debug messages about a peer, it now prints '<unknown-addr>' or '<no user agent>' instead of leaving the field blank when that information is missing. It does not change how the program behaves, only how two debug log lines look.

This commit is a cosmetic cleanup of debug log messages in Bitcoin Core. It removes extra spaces, fixes a couple of mismatched format specifiers (using %s instead of %i for a transaction ID), and makes a status string clearer. There is no security issue here.

This commit changes only a Bitcoin Core functional test file. It stops the test framework from automatically connecting test nodes to each other and marks each test node as having an explicit network bind. The change is purely about making an existing test more accurate and reliable; it does not touch production code or introduce any security issue.

This commit only changes a test script in Bitcoin Core. It updates the functional test feature_bind_port_discover.py to use dynamic ports instead of a hardcoded port, adds more test cases, and improves setup instructions. There is no change to the actual Bitcoin node software that users run, so it has no direct security impact on the network or wallets.

This change fixes a bug in Bitcoin Core where the software would not automatically discover and advertise its own internet-facing IP addresses when a user configured it to listen on all network interfaces using the specific syntax '-bind=0.0.0.0:port'. Without this discovery, the node could become harder for other peers to find and connect to, potentially reducing its connectivity and network resilience. The fix makes the discovery logic also check explicit bind and whitebind configurations for the 'any address' pattern, not just the general listen-on-any setting.

This commit changes a single user-interface label in the Bitcoin Core wallet program, replacing three separate dots ('...') with a single ellipsis character ('…'). It is a cosmetic translation/string cleanup and has no security relevance.

This is a build-system fix for Bitcoin Core's CMake configuration. It narrows an existing workaround so it only applies to older CMake versions. The change prevents a configuration error when cross-compiling Bitcoin for macOS from a non-Apple host, but only when using CMake versions below 4.2. There is no indication this affects running Bitcoin software or introduces a security vulnerability.

This commit only changes test-framework helper code. It improves error messages shown when a Bitcoin RPC call fails during automated testing, so developers get more useful diagnostics instead of a blank message. It does not touch the live Bitcoin node software, wallet handling, consensus rules, or network code, so it cannot directly affect real users' funds or node security.

This commit only adds a release note documenting that two old Bitcoin Core features, the `-paytxtxfee` startup option and the `settxfee` RPC, have been removed after being deprecated. It is a documentation-only change and does not modify any code.

This commit removes two old Bitcoin Core fee-setting mechanisms: the command-line option `-paytxfee` and the RPC command `settxfee`. These had already been marked as deprecated. Users must now set fees per transaction using explicit options like `fee_rate` instead of a global default. There is no security vulnerability here; it is a planned API cleanup that may break old scripts or workflows that still rely on the removed options.

This change moves a one-time initialization flag from a header file into a source file. The warning suggested that, because the flag was defined in a header, it could end up duplicated when Bitcoin's kernel library is linked into other programs. That duplication could mean the intended single initialization runs more than once, potentially creating multiple memory managers instead of one shared instance. The patch is a defensive fix; there is no direct evidence it is currently exploitable as a security vulnerability.

This change only adjusts compiler warning settings for the Bitcoin Core kernel build. It adds a new warning flag for newer Clang compilers to detect duplicated symbols between the kernel library and downstream users. There is no functional code change, no bug fix, and no security vulnerability being addressed.

This commit adds a new read-only helper called PeekCoin() to Bitcoin Core's coin-cache system. Unlike the existing GetCoin(), PeekCoin() looks up a coin through layers of cache without writing the result into parent caches. The stated purpose is to avoid polluting the main UTXO cache when validating blocks that might turn out to be invalid. It is a defensive, non-breaking code-quality change with no direct vulnerability fix described.

This Bitcoin Core change fixes how the coin cache behaves when a new block fails validation. Previously, the same cache used for the main chain was temporarily used during block validation, which could leave behind entries from invalid blocks. Now a separate overlay view is used, so failed blocks don't pollute the main cache. The commit adds a test proving that an invalid block no longer leaves its inputs in the cache. This is a correctness and denial-of-service hardening fix rather than a direct theft bug.

This commit is a test-only code cleanup. It moves a block of verification code from the middle to the end of a fuzz-testing function so that a future test can check that the underlying coin database is not modified before a specific write operation. No production code, network behavior, or wallet logic is changed, and there is no security fix.

This commit adds a new read-only overlay for Bitcoin Core's coin cache system. It lets the software look up transaction inputs during block validation without writing those lookups into the main in-memory cache. The goal is to avoid polluting the cache with data from blocks that might turn out to be invalid, and to prepare for future multi-threaded input fetching where worker threads should not change shared state. The change itself is defensive infrastructure, not a fix for an active bug or vulnerability.

This commit adds a new automated fuzz test for a Bitcoin Core component called CoinsViewOverlay. Fuzz tests feed random or semi-random inputs to code to catch bugs early. The change only touches test code and does not alter the behavior of the main Bitcoin node software. There is no indication it fixes a live security issue or introduces a vulnerability.