Bitcoin Core

This commit simply deletes two unused C++ macros (ENTER_CRITICAL_SECTION and LEAVE_CRITICAL_SECTION) from a header file. These macros were non-RAII manual locking helpers that had been replaced by safer scoped lock wrappers. There is no runtime behavior change, no bug fix, and no security vulnerability being patched.

This commit only updates documentation for building Bitcoin Core on Alpine and Arch Linux. It adds instructions to install the Cap'n Proto library, which is needed for a new optional inter-process communication (IPC) feature, and mentions how to disable that feature if not needed. There are no code changes and no security fix or vulnerability introduced.

This is a one-line documentation update for Fedora Linux build instructions. It adds an extra package name (capnproto-devel) so developers can compile Bitcoin Core's optional inter-process communication (IPC) feature. There is no code change, no bug fix, and no security issue in the commit itself.

This commit adds a new automated test for Bitcoin Core's coin statistics index. It checks that after a blockchain reorganization and an unclean shutdown, the index correctly rewinds to the last safely saved point. The commit itself is only a test file change and does not modify production code.

This change fixes a crash-and-restart bug in Bitcoin Core's index tracking. Previously, during a blockchain reorganization (a 'reorg'), an index could save its new position to disk before the main chain data was fully flushed. If the computer then shut down uncleanly, the index could point to blocks that had already been pruned away, leaving the index corrupted on restart. The fix removes that premature save so the index only commits its position when the main chain state is safely flushed.

This is a one-word documentation fix inside a code comment. A function parameter was renamed from 'pblock' to 'block_to_connect' in an earlier commit, and this change simply updates the surrounding comment to match. It does not alter any executable code, behavior, or security property.

This is a tiny documentation-only change. It removes asterisks from two rows in a markdown table so that the bitcoin-gui and bitcoin-node binaries are no longer marked as 'not installed by default.' There is no code change, no behavior change, and no security relevance.

This commit only fixes documentation comments in three source files. It corrects broken Doxygen tags (e.g., 'param@[in]' to '@param[in]'), removes redundant parameter descriptions, fixes a typo ('an specific' to 'a specific'), and clarifies a phrase. No executable code was changed, so it cannot affect program behavior or security.

This commit only adds a new functional test to Bitcoin Core. It does not change any production code, consensus rules, or network behavior. The test verifies that an invalid-but-relayable block with a malformed witness nonce is rejected over the peer-to-peer network, and that a corrected version is accepted. There is no security vulnerability being fixed here.

This is a small build-system fix for Bitcoin Core's fuzzing configuration. When developers build the project specifically for fuzz testing, the build previously failed because it required a library called capnp that is not needed for fuzzing. The change simply turns off the optional IPC (inter-process communication) feature during fuzzing builds so configuration succeeds. There is no runtime security issue, no vulnerability, and no change to how Bitcoin nodes or wallets behave.

This commit only updates a documentation link in the project's dependency list. It changes the hyperlink for the minimum required Cap'n Proto version from the upstream project's install page to a Bitcoin Core pull request that bumped the version. No code, build scripts, or dependency versions were changed.

This commit removes one library, libxcb-xinerama.so.0, from the list of shared libraries that Bitcoin Core's Guix reproducible-build process is allowed to link against. It is a build-hardening change: the release pipeline will now refuse to produce a binary that depends on that X11-related library. There is no direct evidence in the commit that this fixes an active vulnerability, only that it tightens the supply-chain/build policy.

This commit removes an optional X11 screen-extension feature (Xinerama) from the list of components built into Bitcoin Core's bundled copy of the libxcb library. The change is purely a build-system cleanup to avoid requiring a dependency that is no longer installed by default on modern Linux distributions. There is no security-relevant change here.

This commit only changes the wording of a user-facing deprecation warning and updates the matching test. It does not alter any behavior, logic, or security-sensitive code. There is no security issue here.

This commit is a routine internal code cleanup in Bitcoin Core's wallet module. It removes an old enum type called isminetype and replaces it with a simple true/false (bool) value, because the wallet no longer distinguishes between different kinds of 'mine' statuses—only 'mine' and 'not mine' remain. The change touches many files but does not alter what the wallet does; it only simplifies how the code expresses the same behavior.

This commit cleans up the Bitcoin Core wallet code by removing an old 'spendable' flag that is no longer meaningful for modern descriptor wallets. For these wallets, every coin the wallet knows about is considered spendable, so the flag was redundant. The change also removes a small wrapper function and updates the listunspent RPC to always report 'spendable' as true. It is a code-simplification refactor, not a fix for an active security bug.

This is a small internal cleanup in Bitcoin Core's wallet code. It removes a special flag called ISMINE_USED that was only used to decide whether to count already-used addresses when calculating balances. The same behavior is now controlled by a simple true/false parameter called avoid_reuse. There is no direct security bug being fixed here; it is a refactoring change that makes the code easier to understand and maintain.

This change replaces internal sanity checks (assertions) in Bitcoin Core's block-building code with clamping. Instead of crashing the program if a miner passes an out-of-range value, the code now silently adjusts the value to the nearest allowed limit. This is a robustness improvement that prevents a misconfiguration or unusual input from terminating the node, but it also means invalid settings are no longer loudly rejected.

This commit is a simple code cleanup: it removes an unused 'is_mine' output parameter from a wallet address lookup function and updates all callers. There is no security-relevant change; the removed parameter was never used, and the remaining behavior is unchanged.

This commit only changes a test file. It makes a unit test for log-rate-limiting run faster and more reliably by reducing the amount of test data and extending the time window. There is no change to the actual Bitcoin Core software that users run, and no security issue is introduced or fixed.

This commit is a routine regeneration of Bitcoin Core's English translation source files. It updates the list of user-visible text strings (error messages, warnings, labels) that translators can later translate into other languages. No program logic, security checks, or executable behavior was changed.

This is a small bug fix in the Bitcoin Core graphical wallet. Previously, the menu option that opens the debug log always looked for a file literally named 'debug.log', even if the user had started Bitcoin with a custom debug log filename. The change makes the menu use the actual configured filename. It is a correctness/usability fix, not a security vulnerability.

This commit removes a Python helper script used during the build process and replaces it with equivalent logic written directly in CMake. It is a build-system cleanup that drops a Python dependency for generating translation string files. There is no indication this change fixes or introduces a security vulnerability.

This commit changes a Bitcoin Core fuzz test (an automated test that feeds random data to a piece of code to find crashes or bugs). It removes a 'const' restriction so the test can create a fresh, configurable memory pool (mempool) for each fuzz run, and sets fee-related options from the fuzz input. It is a test-only change and does not alter the behavior of the actual Bitcoin node software that users run.

This commit only changes Bitcoin Core's own test code and test framework. It fixes how the test suite encodes the 'code separator position' used in Taproot signature hashing, switching from a signed 32-bit integer to an unsigned 32-bit integer. It also adds two new test cases that check what happens when an invalid code-separator position is used. There is no change to the actual consensus or networking code that runs on the Bitcoin network, so this does not create or fix a live security vulnerability in Bitcoin Core itself. It is a test-coverage improvement.