Bitcoin Core

This commit only edits documentation. It removes detailed macOS fuzzing setup instructions and replaces them with a note that macOS fuzzing is not officially supported, recommending Linux instead. No code, build scripts, or security behavior changed.

This commit changes the bitcoin-cli -addrinfo command so it reports the full set of addresses known to the node, not just the subset previously filtered for quality and recency. The change is purely informational: it makes the displayed statistics more accurate and useful, but does not alter peer selection, network behavior, or any security-sensitive logic.

This commit updates the Bitcoin Core continuous integration (CI) configuration to use a newer version of Apple's Xcode development tools (16.2 instead of 16.0) when building and testing on macOS. It is a routine infrastructure/maintenance change with no apparent security relevance.

This commit adds an internal sanity check inside Bitcoin Core's transaction memory pool (mempool) self-check routine. It verifies that a newly introduced feerate diagram data structure stays within expected size bounds. The change is defensive and only affects debug/self-check code, not normal network operation. There is no indication it fixes an active security vulnerability or that it is exploitable by an attacker.

This commit only updates the explanatory comments at the top of the mempool header file. No code, logic, or data structures were changed. It is a documentation-only edit and has no security relevance.

This commit adds an internal consistency check inside Bitcoin Core's memory pool validation routine. It verifies that two different ways of ranking transactions by mining priority produce the same order. It is a defensive assertion, not a fix for a known bug or vulnerability, and it does not change network behavior.

This commit adjusts a startup configuration check for Bitcoin Core's memory pool (mempool) size. It changes the internal sanity check so that the minimum allowed -maxmempool value is based on the newer 'cluster size limit' rather than the older 'descendant size limit', and it explicitly allows users to set -maxmempool=0 to disable the mempool. This is a routine consistency fix for configuration validation logic, not a security patch for an exploitable vulnerability.

This commit only changes a test file. It makes an existing functional test for package Replace-By-Fee (RBF) use slightly larger transaction clusters (3 transactions per cluster instead of 2). There is no change to production code, so it cannot directly affect live Bitcoin nodes or introduce a security vulnerability.

This commit only updates documentation in a Markdown file describing how Bitcoin Core accepts groups (packages) of transactions. It removes outdated descriptions of ancestor/descendant limit checks and CPFP Carve Out behavior, and updates the package replacement rule wording. No code, logic, or behavior changes are present in the diff.

This commit adds calls to a background graph-maintenance routine (TxGraph::DoWork) after three kinds of mempool changes: applying a batch of new transactions, handling a blockchain reorganization, and processing a newly found block. It also defines a constant telling the graph how much cleanup work to do each time. The change looks like a performance or consistency fix: without these calls, the in-memory transaction graph might not be updated promptly, possibly leading to stale data, incorrect fee estimates, or degraded mempool behavior. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

This commit only renames CI (Continuous Integration) job names and a configuration script filename to clarify that they are for Windows builds using the older MSVCRT runtime. It does not change any actual build commands, compiler flags, source code, or runtime behavior. There is no security issue here.

This commit simply undoes a previous user-interface tweak for Linux Wayland users. The original workaround tried to force a Bitcoin Core window to the front by temporarily making it stay-on-top. Removing it restores the older, simpler window-raising behavior. There is no security issue visible in this change.

This change only adds an installation instruction file to Linux release packages. It does not modify any executable code, network behavior, or security-sensitive logic.

This commit simply adds one line to Bitcoin Core's automated CI (continuous integration) workflow so that the GUI unit tests for the Windows build are executed alongside existing tests. It is a testing infrastructure change, not a code change to the Bitcoin software itself, and has no direct security relevance.

This commit is a routine cleanup of Bitcoin Core's continuous integration (CI) scripts. It removes an old option that let CI jobs use BusyBox utilities instead of GNU tools, because a dedicated Alpine Linux CI job now covers BusyBox testing. It also removes a now-unused temporary directory for executables and enables stricter shell error handling in one script. There is no user-facing change, no change to the Bitcoin node software, and no security relevance.

This commit only shortens the display name of one automated testing job in the project's GitHub Actions configuration. It removes the words 'no depends' from a CI job label. There is no code change, no security fix, and no functional impact on the Bitcoin Core software or its users.

This commit only changes code-formatting rules and reorders one test file's #include lines accordingly. It has no effect on program behavior or security.

This commit is a minor documentation cleanup in Bitcoin Core's CI (continuous integration) README. It removes an unnecessary 'bash -c' wrapper from example shell commands, showing users they can pass environment variables directly to 'env' instead. There is no security-relevant change to the software itself.

This commit simply changes where Bitcoin Core's build system downloads some Qt source files from one official Qt location (code.qt.io) to another official mirror (GitHub's raw content server). The downloaded files are still verified by fixed SHA-256 hashes, so even if the new host were malicious, the build would reject tampered files. There is no security vulnerability here.

This commit fixes a minor developer-facing bug in how Bitcoin Core parses text-based wallet descriptors. A recent code change had made the parser accept raw character spans, which accidentally included the hidden null terminator at the end of C++ string literals. That caused the parser to reject valid descriptors with a misleading 'Invalid characters in payload' error. The fix switches the public API to use std::string_view, which does not include the trailing null byte, and adds a regression test. It is not a consensus or network security issue.

This commit updates the expat XML parsing library used by Bitcoin Core's build system from version 2.4.8 to 2.7.3. Expat is a widely-used library for processing XML data, and newer versions often fix security bugs found in older releases. The change also removes an old build patch and a workaround that were only needed for the older expat version. However, the commit message itself does not say this is a security fix, and no specific vulnerability is mentioned.

This is a test-only helper script that downloads old Bitcoin Core release binaries for testing. The change simply retries a failed download once after a 12-second wait. It is not a security fix and does not affect the Bitcoin Core software users run.

This commit updates the libxcb library used in Bitcoin Core's build dependencies from version 1.15 to 1.17.0. It also removes an obsolete build option and adjusts a patch that removes an unneeded pthread-stubs dependency so it also covers more operating systems. This is a routine dependency maintenance change, not a fix for a known Bitcoin Core security bug.

This commit updates a build dependency called xcb_proto from version 1.15.2 to 1.17.0 inside Bitcoin Core's dependency system. It only changes a version number, download URL extension, and the cryptographic hash used to verify the downloaded file. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies can sometimes include upstream security fixes.

This commit only changes code formatting rules. It tells the project's automated style tool (clang-format) to place constructor initializer list items on separate lines instead of packing them together. The only code change is a reformatting of one constructor in net.cpp to match the new style. There is no functional change to the Bitcoin software and no security impact.