Bitcoin Core

This is a small fix to a Bitcoin Core fuzz test (an automated testing harness, not production code). The test was using an outdated size check after the real mempool code switched from measuring transaction size in 'vsize' to measuring it in 'weight'. The change tightens a guard so the fuzzer stops adding transactions before hitting an internal integer limit. It does not change how real nodes handle transactions and is not a vulnerability in live Bitcoin Core.

This is a one-line change inside a Bitcoin Core unit test file. It updates a test assertion to use the newer 'cluster size limit' constant instead of the older 'ancestor size limit' constant when checking that a deliberately oversized placeholder transaction is recognized as too large. The change only affects test code and does not alter any production behavior, network rules, or security logic.

This commit is a simple renaming of internal function names and variables in Bitcoin Core's block-building code. It changes words like 'package' to 'chunk' to match terminology used elsewhere in the project. No behavior changes, no security fixes, and no bug fixes are visible in the code.

This commit removes two size-based controls from Bitcoin Core's memory pool (mempool) settings: the maximum virtual-byte size of an ancestor package and of a descendant package. It is a code cleanup that follows earlier work to replace those limits with a single 'cluster size' limit. There is no indication in the commit that this fixes a security bug; it appears to be a refactoring change.

This is a tiny code-comment and compile-time sanity-check update in Bitcoin Core's TRUC transaction policy. It changes which default mempool limit is referenced in a static_assert, switching from ancestor/descendant size limits to the newer cluster size limit. There is no runtime behavior change, no bug fix for active code, and no disclosed security relevance.

This is a small code cleanup change. It adds a new accessor method to retrieve a fee rate and uses it in one place when building blocks. There is no security-relevant change visible in the diff.

This commit updates internal compile-time sanity checks for Bitcoin Core's package transaction limits. It replaces checks based on older 'ancestor/descendant' mempool limits with checks based on newer 'cluster' limits. The change is defensive: it ensures that when users submit groups (packages) of related transactions, the configured limits won't accidentally reject transactions that should be acceptable. There is no direct evidence in the commit that this fixes an active security bug or vulnerability.

This commit simply deletes two unused constant definitions from a header file. These constants were leftover default values for mempool ancestor and descendant size limits. They had no effect on running code because nothing referenced them. There is no security issue.

This commit only changes help text and adds warning messages for two command-line options that no longer affect how Bitcoin Core handles transactions. It does not fix a security bug, change network behavior, or introduce a vulnerability. It is a user-facing cleanup to prevent confusion after an earlier redesign replaced ancestor/descendant size limits with new cluster limits.

This commit simplifies how Bitcoin Core removes transactions from the memory pool when they are included in a newly mined block. It replaces a small two-step staging process with a direct call to the underlying removal function. The change appears to be a straightforward code cleanup with no obvious security impact, though it removes a thin abstraction layer that previously ensured removal events were recorded consistently.

This is a small internal code cleanup in Bitcoin Core's transaction memory pool. It rewrites a helper function called GetChildren so that it no longer builds a temporary set to remove duplicate child transactions; instead it uses a lightweight 'epoch' marker to skip duplicates. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This Bitcoin Core commit rewrites the mempool cleanup logic that runs during blockchain reorganizations. It replaces an older set-based approach with a newer graph-based method for finding all transactions that must be removed because an ancestor became invalid. The change also adds a test for a tricky edge case where a transaction's child is only invalidated because its parent no longer spends a mature coinbase output. The commit itself does not describe a security bug, but the rewrite touches consensus-adjacent mempool code and improves test coverage for a previously untested scenario.

This commit is a simple automated rename of a test helper function from AddToMempool to TryAddToMempool across test and benchmark files. It does not change any behavior, logic, or security properties of the Bitcoin Core software. The function body remains identical and the change only affects internal test/bench code, not production network code.

This commit refactors how Bitcoin Core removes a transaction and all of its dependent transactions from the memory pool (mempool). It replaces an older, more manual descendant-finding method with a newer graph-based helper. The change is described as a simplification. There is no direct evidence in the commit that this fixes a security bug, but any change to mempool removal logic carries a small risk of introducing or masking consistency issues.

This is a routine code cleanup: a function called RemoveStaged had an extra parameter (updateDescendants) that was no longer used, so it was removed from the function definition and every place that called it. There is no security-relevant change here.

This is a small CMake build-system change. It makes the optional test suite for an experimental library (BUILD_KERNEL_TEST) automatically disabled when the library itself (BUILD_KERNEL_LIB) is not being built. Previously, the test option could be left on independently, which could cause a build configuration error. There is no runtime security issue here.

This commit changes Bitcoin Core's Windows build configuration so that the optional ZeroMQ notification feature is enabled by default in the Windows CMake presets. It also updates CI and documentation to match. There is no security-relevant code change here; it is purely a build-system consistency fix to align Windows builds with the existing default in the dependency manifest.

This is a documentation-only change that adds a new Windows cross-compilation target to the build instructions. It does not modify any executable code, build scripts, or configuration logic. There is no security relevance.

This is a minor cleanup to Bitcoin Core's continuous integration (CI) configuration. It removes one redundant line that explicitly set compiler names for a Windows cross-compilation job, because the build system already figures out those names automatically. There is no security relevance.

This commit only renames a GitHub Actions CI job and adds a comment to make clear that the workflow tests a maximum of 6 ancestor commits. There is no code, build, or runtime change, and no security issue is introduced or fixed.

This commit only changes the error message/name returned when a tapscript transaction provides an empty public key. The actual consensus rule—rejecting empty public keys in tapscript—already existed. The change makes debugging and testing clearer by giving this failure its own distinct error code instead of reusing a more general one. It does not alter what transactions are accepted or rejected by the network.

This commit tightens a build-time check used in Bitcoin Core's reproducible Guix build process. It removes several common system symbols (like 'environ' and '_environ') from a list of exports that the build script is allowed to ignore. The change itself does not fix a vulnerability in running Bitcoin Core software; it is a hardening of the release-build verification tooling to catch accidental symbol exports earlier. There is no claim in the commit that this resolves a security bug.

This commit only adds documentation comments to a build script. It lists which versions of two graphics-related system libraries (libfontconfig and libfreetype) are expected on Ubuntu 22.04 for the Bitcoin Qt wallet application. No code behavior was changed, so there is no security issue in this patch itself.

This commit updates the FreeType font-rendering library used in Bitcoin Core's build dependencies from version 2.11.0 to 2.11.1. It changes the download URL, archive format, and verification hash, and adjusts a small build patch. FreeType is a widely used library for drawing text, and newer point releases often include bug fixes. The commit itself does not say whether this fixes a security issue, and no security references were provided.

This commit is a straightforward logging cleanup. It changes many messages from the generic LogPrintf to a new LogWarning helper, which is designed for severe-but-non-fatal problems. The wording of the messages is mostly unchanged, and no program logic, permissions, or security behavior is modified. It is not a security fix.