Bitcoin Core

This commit only adds new regression tests for Bitcoin Core's PSBT (Partially Signed Bitcoin Transaction) combine/merge logic. It checks that custom 'proprietary' data fields are preserved when two PSBTs are merged at global, input, and output levels. There is no production code change, no bug fix, and no security patch in the diff itself.

This commit fixes a bug in Bitcoin Core's handling of PSBTs (Partially Signed Bitcoin Transactions). When two PSBTs were combined, the software correctly kept 'unknown' extra data but accidentally discarded 'proprietary' custom data fields added by wallets or tools. The patch makes sure proprietary fields are preserved during merging, preventing potential loss of transaction metadata that some wallets rely on.

This commit only changes comments in a single header file. It documents that a database wipe must be followed by importing blocks, and that a function can return null when no block headers are loaded. There are no code changes and no security fix.

This commit adds a new helper function called UrlEncode that converts text into URL-safe format, plus tests for it. The function is not used anywhere in the actual program yet, so it cannot directly affect live behavior or introduce a practical security flaw. It is a routine, standard implementation following RFC 3986.

This commit changes a CI (Continuous Integration) script used during Bitcoin Core's automated testing. It adds a compiler warning suppression for 'unused free functions' in addition to the existing suppression for 'unused member functions'. This only affects how intermediate commits in a pull request are validated, not the actual Bitcoin software that users run. There is no security issue here.

This commit is a routine code cleanup. It adds missing header file includes for logging and removes one unnecessary include. There is no functional code change and no security issue.

This is a routine internal code cleanup in Bitcoin Core. It replaces an older logging helper function called LogAcceptCategory with newer, more specific helper functions (ShouldDebugLog and ShouldTraceLog). The behavior of the program is intended to remain exactly the same; only the names of the functions used to decide what to log have changed. There is no indication this fixes or introduces a security vulnerability.

This commit is a simple internal cleanup: it swaps the full logging header file for a smaller, more focused one in many source files. There is no change to program behavior, no bug fix, and no security relevance.

This commit is a straightforward internal code cleanup in Bitcoin Core's logging system. It replaces one generic helper function with two more specific ones (one for debug logs, one for trace logs) and updates the macros that use them. There is no change to user-facing behavior, no bug fix, and no security relevance visible in the code.

This commit is a simple code cleanup: it moves a helper function that converts a log category name into an internal flag from the global namespace into the Logger class. There is no change in behavior, no user-visible effect, and no security relevance.

This is a simple code cleanup change that renames an internal logging helper macro from LogPrintLevel_ to detail_LogWithSrcLoc. The macro does exactly the same thing as before; only its name changed. There is no security issue here.

This commit is a code cleanup, not a security fix. It introduces a cleaner way for Bitcoin Core developers to mark certain important log messages as exempt from automatic rate-limiting. The rate-limiting protection itself already existed; this change just makes the code easier to read and maintain. There is no indication it fixes a known vulnerability.

This commit fixes a potential crash or data corruption bug in Bitcoin Core's debug log handling. The ShrinkDebugFile() function, which trims the large debug.log file down to size, was not using the same lock (mutex) that protects normal logging. That meant logging could happen at the same time the file was being shrunk, possibly causing the program to behave incorrectly or crash. The fix wraps the shrink operation in the logging mutex and changes one internal warning call so it works while that lock is held.

This commit is a pure documentation reorganization. It moves the 'Locking/mutex usage notes' and 'Threads' sections from the 'Tips and tricks' area into a new 'Development guidelines' section in the developer notes. No code, logic, or security behavior changed.

This commit simply moves the existing Valgrind documentation section to a different place in the developer notes file. No code, configuration, or behavior changed. It is purely a documentation reorganization.

This commit simply moves a documentation section about Python coding style to a different place in the developer notes. It is a non-functional, move-only change with no security relevance.

This commit only reorganizes developer documentation about code style and the clang-tidy checking tool. It removes an outdated note, moves a recursion-related note into a new subsection, and adds a link to upstream clang-tidy documentation. No program code was changed, so there is no security impact.

This commit only fixes the capitalization of web link anchors in developer documentation. It changes three URLs from upper-case anchors (like #Renum-caps) to lower-case anchors (like #renum-caps) so the links work correctly. There is no change to any program code, no security issue, and no risk to users.

This commit reorganizes the CMake build scripts so that dependency checks happen after build options have been finalized. It is a build-system correctness and maintainability improvement, not a security fix. There is no indication it addresses a vulnerability or changes runtime behavior of Bitcoin Core.

This commit only adds a new performance benchmark for an existing IP-to-ASN lookup feature. It does not change any production code, network behavior, or security logic. There is no security issue here.

This commit tightens up error messages in Bitcoin Core's I2P (anonymous networking) code. Previously, error messages could accidentally include the full text of a SAM request that may carry the user's I2P private key, or the full raw reply from an I2P router. The patch keeps the error useful by still referencing the redacted request, but stops echoing the sensitive request body and unescaped router replies into logs. It is a defensive information-disclosure fix, not a change to network behavior.

This is a test-hardening change, not a fix for an exploitable vulnerability in live Bitcoin Core. The patch stops automated tests from accidentally sending real network traffic (router NAT-PMP packets and DNS queries) to non-localhost destinations. It does not change how normal node software behaves when users run it.

This change refactors how Bitcoin Core sends transaction announcements to all connected peers. Previously, the code held a broad internal lock (m_peer_mutex) while iterating over every peer and preparing messages. The patch copies the peer list under the lock, then releases the lock before doing the slower per-peer work. This reduces the chance of lock contention and removes a known ThreadSanitizer suppression for a deadlock in Chainstate::ConnectTip. It is a robustness improvement, not a fix for an exploitable vulnerability.

This commit only updates documentation for Bitcoin Core's external signer feature. It renames a command from 'signtransaction' to 'signtx', documents a new required '--stdin' flag, adds '--chain' flag details, and fixes examples. No actual code was changed, so this cannot directly introduce or fix a security vulnerability.

This commit only adds documentation: a new release-notes file explaining that an obscure build-system environment variable was removed and how users can still disable git detection. There is no code change, no bug fix, and no security-relevant behavior change in the commit itself.