Bitcoin Core

This is a routine subtree update that pulls in a new version of the libmultiprocess IPC helper library used by Bitcoin Core. The changes include bug fixes, new features (thread pools, unordered_set support, optional primitive fields), and code-quality improvements. The most security-relevant change is a fix for a crash during teardown: a remote 'destroy' RPC that fails after the peer disconnects could previously throw an exception out of a noexcept destructor, causing the program to abort. The patch now catches and logs that exception instead. Other changes harden error handling and thread-safety annotations but do not appear to introduce new vulnerabilities.

This is a cleanup change that removes support for older FreeBSD versions (before 14.0) from a single networking source file. It does not fix a security bug, add new behavior, or change how Bitcoin Core runs on currently supported systems. The only practical effect is that the code no longer contains special handling for FreeBSD 13.x, which is no longer a supported operating system release.

This is a cleanup change that removes a temporary compatibility fix for newer FreeBSD versions. The workaround was only needed because of a bug in FreeBSD's system headers, and that bug has now been fixed in supported FreeBSD releases. There is no security issue in the change itself.

This commit only updates three documentation files to clarify which versions of FreeBSD, NetBSD, and OpenBSD Bitcoin Core supports. No code was changed, and there is no security issue.

This commit simply removes an unnecessary C system header include (`<sys/types.h>`) from two files that already include `<ifaddrs.h>`. It is a code cleanup with no functional change and no security relevance.

This commit only updates release note wording for a previous feature change. It does not modify any executable code, network behavior, or data handling. There is no security issue here.

This change is a straightforward performance and disk-space optimization. It adds an option to disable LevelDB bloom filters for database instances that only scan through data with iterators, because bloom filters only help when looking up individual records directly. The txospenderindex is updated to use this new option. There is no security bug being fixed here.

This commit removes a fuzz-test helper that built a UniValue from hard-coded constants and replaces it with parsing a UniValue from random fuzz data. It only affects test code and does not change production behavior or fix a security vulnerability.

This commit only fixes two small mistakes in a documentation file: it removes an outdated note and corrects a JSON example from curly braces to square brackets. There is no code change and no security impact.

This commit only adds documentation: a new release-notes file describing a previously merged feature (`exportwatchonlywallet` RPC). There is no code change, no bug fix, and no security-relevant behavior change in this patch.

This commit is purely administrative: it adds a written policy telling contributors how they may use AI tools (like ChatGPT) when filing bug reports, feature requests, and pull requests. It does not change any Bitcoin software code, network rules, or security mechanisms. There is no security vulnerability here.

This commit adds a new Bitcoin Core feature that lets a user export a copy of their wallet containing only public information (watch-only). It creates a separate wallet file with descriptors, address book, transactions, and locked coins, but explicitly excludes private keys. The change is a feature addition, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that this is a security patch or that it addresses any reported security issue.

This commit adds a new wallet command called exportwatchonlywallet. It lets a user save a copy of their wallet that contains only public information—public descriptors, transactions, and address book data—without private keys. The change is purely additive and exposes no new security weakness based on the code shown.

This commit adds a new automated test file for the exportwatchonlywallet feature in Bitcoin Core. It does not change any production wallet code; it only verifies that exporting a watch-only wallet correctly preserves descriptors, address labels, transactions, locked coins, and settings. There is no security issue in the diff itself.

This is a documentation-only update to the Bitcoin Core offline-signing tutorial. It replaces instructions that used manual descriptor export/import with instructions that use a newer built-in RPC command (exportwatchonlywallet / restorewallet). No code behavior changed, and there is no security vulnerability in the commit.

This commit is a straightforward internal code cleanup: it moves the logic for listing wallet descriptors from the RPC command code into a reusable wallet helper function. There is no user-facing behavior change, no bug fix, and no security-relevant change visible in the diff.

This change fixes a wallet bug where a newly added descriptor's pre-existing cache was kept in memory but never saved to disk. If the cache is lost, the wallet may need to rescan the blockchain to recover key derivation data, causing delays or apparent balance issues. It is a data-durability fix rather than a remote-exploitable vulnerability.

This is a small Bitcoin Core wallet change that lets the wallet generate addresses from certain descriptors even when it does not have private keys and has already used up its pre-derived address range. It only affects descriptors that can expand entirely on their own (public-only, no cached data needed). The change is more of a correctness/availability fix than a security flaw, and there is no direct evidence in the commit that it fixes a vulnerability.

This commit adds a new helper method called CanSelfExpand() to Bitcoin Core's descriptor system. It lets the code ask whether a wallet descriptor can produce its Bitcoin address(es) on its own, without needing a saved cache or private keys. The change is mostly a new capability with matching tests; it does not by itself fix a known bug or change user-facing behavior, but it lays groundwork that could later be used to avoid loading private keys just to display addresses.

This commit simply updates the Boost dependency used by Bitcoin Core's build system from version 1.90.0 to version 1.91.0-1, including the new download URL and cryptographic hash. There is no indication in the commit itself that this fixes a security issue. It appears to be a routine dependency version bump.

This commit adds a safety check in Bitcoin Core when it talks to an external hardware wallet or signer tool. Previously, the software accepted whatever 'fingerprint' string the external tool returned. Now it requires that fingerprint to be exactly 8 hexadecimal characters. Without this check, a misbehaving or malicious signer could supply an oddly formatted fingerprint that might later confuse wallet logic, cause crashes, or be used to trick the user into pairing with the wrong device. The change is small and defensive: it rejects bad fingerprints early and throws a clear error.

This commit is a minor cleanup in Bitcoin Core's continuous integration (CI) configuration. It changes the way some on/off settings are written in shell scripts from quoted strings like "true" and "false" to unquoted true and false. There is no security issue here; it is purely a style or consistency improvement in test automation files.

This commit simply changes one CI (continuous integration) job to use a smaller GitHub Actions runner size, from 16x to 8x. It is a cost or resource tuning change with no security relevance.

This commit only adds new test code to Bitcoin Core. It checks that a locked wallet refuses an empty importdescriptors request, and that an unlocked wallet accepts one. There is no change to production wallet logic, so it does not fix or introduce a security issue on its own.

This commit only adds a release note explaining that a new index format uses slightly less disk space. It is documentation only and contains no code changes that could affect security.