Bitcoin Core

This commit updates a build dependency called libxcb-util-wm from version 0.4.1 to 0.4.2 inside Bitcoin Core's 'depends' packaging system. It only changes the version number and the expected file hash (SHA-256) used to verify the downloaded source. There is no statement in the commit or supplied references saying this fixes a security problem, and no details about what changed in libxcb-util-wm 0.4.2 are provided. On its own, this looks like a routine dependency refresh rather than a confirmed security patch.

This commit simply updates a third-party graphics library used by Bitcoin Core's build system from version 0.1.5 to 0.1.6, along with its corresponding checksum. There is no indication in the commit itself that this fixes a security problem, and no security-relevant information is provided.

This commit updates the libxcb dependency used when building Bitcoin Core from source. It bumps the version from 1.14 to 1.15, switches the download archive format from .tar.xz to .tar.gz, updates the SHA-256 checksum, and refreshes a documentation link. There is no direct evidence in the commit that this fixes a specific security vulnerability, but dependency updates can include upstream security fixes.

This commit simply updates a dependency package version for libxcb-util-image from 0.4.0 to 0.4.1 in Bitcoin Core's build system, along with its corresponding SHA-256 hash. There is no indication in the commit itself of any security issue. It is a routine dependency bump.

This commit updates a dependency used by Bitcoin Core's build system from version 0.4.0 to 0.4.1 of libxcb-util-keysyms, a small helper library for X11 keyboard handling. The change itself is a routine version bump with a new checksum. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies can sometimes address bugs or security issues in the upstream library.

This commit updates a build dependency, libxcb-util, from version 0.4.0 to 0.4.1 in Bitcoin Core's packaging system. It only changes the version number and the expected file hash (SHA-256) used to verify the downloaded source. There is no direct evidence in the commit that this fixes a security vulnerability, but dependency updates can sometimes include upstream bug or security fixes. Without external references, the security relevance is unclear.

This commit simply bumps the version of a third-party graphics-related library (libxcb-util-renderutil) used when building Bitcoin Core's dependencies. The change updates the version number and its corresponding cryptographic hash so the build system downloads the newer release. There is no direct evidence in the commit that this fixes a security vulnerability, and the library is only used in build tooling for graphical wallet support, not in Bitcoin's core networking or consensus code.

This commit simply bumps the version of a third-party graphics-related library (libXau) used in Bitcoin Core's build dependencies from 1.0.9 to 1.0.12, updating the corresponding download hash. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.

This is a code cleanup (refactor) that changes how one internal data structure receives a known-valid block index. It replaces a raw pointer with a C++ reference because the value is never null. There is no functional change to how Bitcoin validates blocks, syncs headers, or handles network data, and no security vulnerability is fixed or introduced.

This commit fixes a test-only race condition in a Bitcoin Core functional test. It changes which node is checked first when verifying that a newly submitted block has propagated, so the test waits for the local node to update its own chain before checking that all nodes agree. There is no change to production code, no user-facing behavior change, and no security vulnerability in the Bitcoin Core software itself.

This commit is a one-word documentation cleanup. It removes the phrase '(default: none)' from the help text describing the -i2psam command-line option in Bitcoin Core. The actual behavior of the software does not change; only the user-visible description is slightly simplified for consistency with other options.

This commit adds a build-time patch for the Qt GUI toolkit used by Bitcoin Core's Windows builds. The patch fixes a visual/layout bug in the Windows 11 visual style where spinbox controls (number/date input fields with up/down buttons) could be sized incorrectly or have their user-set widths overridden. It is a cosmetic/user-experience fix, not a security patch.

This commit fixes a formatting inconsistency in how Bitcoin Core's wallet describes certain advanced 'miniscript' descriptors. When a user called the listdescriptors RPC, the same descriptor could contain a mix of 'h' and ''' markers for hardened derivation paths, depending on whether the key was inside a Taproot taptree or not. The patch makes the output uniform. It is a correctness/usability bug rather than a direct loss-of-funds vulnerability, but inconsistent descriptors can confuse downstream tools or users who compare or re-import descriptor strings.

This is a one-line documentation fix in a README file. It adds a missing '--platform=linux' flag to a Docker build command example used by developers running linting tools locally. There is no code change, no security vulnerability, and no risk to users.

This commit fixes a broken CI safety check. When Bitcoin Core moved from Cirrus CI to GitHub Actions, an automated check that verifies commit signatures on the official repository stopped running because it looked for an old environment variable that no longer existed. The patch introduces a new environment variable so the signature check runs again on non-pull-request pushes to the official bitcoin/bitcoin repository. It is a CI hardening fix, not a vulnerability in the Bitcoin software itself.

This is a routine internal cleanup of the Bitcoin Core continuous integration (CI) lint scripts. It renames an environment variable from a Cirrus-specific name to a provider-agnostic one and enables a stricter shell option for catching pipeline failures. There is no user-facing change and no security-relevant behavior change.

This change adjusts Bitcoin Core's GitHub Actions CI workflow so that build caches are only saved when running on the repository's default branch (e.g., 'master'). Previously, caches could be saved from non-default branches too. The patch is a hardening measure: it reduces the risk that a malicious or compromised branch could poison shared CI caches used by later builds. It is not a fix for an active exploit in Bitcoin Core's shipped software, but rather a defensive tightening of the project's own build infrastructure.

This commit only adds new automated tests for Bitcoin Core's mempool cluster features. It does not change any production code that runs on real Bitcoin nodes, so it cannot introduce a security vulnerability or directly fix one in the live software.

This commit adds new read-only ways to inspect Bitcoin's mempool through RPC: it exposes 'cluster' information for transactions, adds chunk-based fee/weight fields to existing mempool entries, and introduces a hidden diagnostic command that prints the mempool's feerate diagram. It is a feature/informational change, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that it addresses a security bug or was triggered by a security report.

This commit only updates a documentation file describing Bitcoin Core's mempool replacement policy. It removes outdated rules and adds notes about newer 'feerate diagram' checks and cluster mempool behavior. There are no code changes, no executable changes, and no security fix or vulnerability introduced.

This commit only changes a test file (miniminer_tests.cpp) so that existing unit tests still pass after a new mempool 'cluster limit' rule was introduced. It does not change any production code that runs on real Bitcoin nodes, so it cannot directly affect live network security or be exploited by attackers.

This commit is a test-only change. It expands Bitcoin Core's fuzz testing for the transaction memory pool (mempool) to cover more behaviors like eviction, expiry, reorg handling, and block template creation. It also adds a sanity check inside the mempool's own consistency verification code. There is no indication this fixes a security vulnerability or changes production network behavior.

This commit fixes Bitcoin Core's own internal test and fuzzing helpers so they stop trying to add fake transactions to the test mempool in ways that break the real mempool policy rules. It does not change production network code, wallet behavior, or consensus rules. The change only affects test utilities and one fuzz target, making the tests more realistic and preventing false fuzz failures.

This commit is a code cleanup in Bitcoin Core's memory pool (mempool). It removes duplicate bookkeeping: parent/child relationships between transactions used to be tracked both inside each mempool entry object and inside a newer 'txgraph' module. The change makes txgraph the single source of truth for those relationships. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability; it appears to be a refactoring to simplify data structures and reduce maintenance risk.

This commit rewrites an internal Bitcoin Core function called GatherClusters so it uses a newer transaction graph (txgraph) implementation instead of manually walking parent/child relationships. The change is a refactor that preserves the same 500-entry DoS limit but moves where and how that limit is enforced. There is no direct evidence in the commit that this fixes a security bug, but refactors of mempool cluster logic can affect denial-of-service protections.