Bitcoin Core

This commit changes a single test file to generate a random private key instead of using a hardcoded one. It is a test-only cleanup with no effect on the actual Bitcoin Core software users run.

This commit is a test-only cleanup. It replaces hardcoded example Bitcoin extended keys (xprv/xpub) and addresses in a functional test with freshly generated keys and programmatically derived addresses. There is no change to production wallet code, consensus rules, or network behavior, so it does not introduce or fix a security vulnerability.

This is a pure code cleanup change in Bitcoin Core's wallet RPC documentation. It moves repeated documentation fields for the getaddressinfo command into a shared helper function so the OpenRPC metadata and help text stay in sync. There is no functional change, no bug fix, and no security relevance.

This commit is a documentation cleanup. It removes libevent from build instructions and dependency lists because Bitcoin Core no longer uses libevent. It also updates a code comment in the wallet encryption file to remove an outdated reference to a macOS/libevent bug, explaining instead that the timeout is clamped to prevent overflow. There are no code behavior changes and no security fix.

This commit removes libevent from the Bitcoin Core build system and deletes the associated helper header and unit tests. It is a dependency cleanup, not a security fix. There is no indication in the commit that this addresses a vulnerability.

This commit removes the libevent dependency from Bitcoin Core's vcpkg package manager configuration. It is a build-system cleanup change, not a security fix. The removed override was previously pinning an older libevent version to avoid a known build issue, but that issue is no longer relevant because libevent is no longer used via vcpkg at all.

This commit removes the libevent dependency from Bitcoin Core's build system ('depends'). It deletes the build recipe, patches, and references to libevent in makefiles and documentation. There is no direct code change to Bitcoin Core's runtime behavior, and nothing in the commit indicates a security vulnerability or fix. It is a build-maintenance change.

This commit only adds new automated tests for Bitcoin Core's wallet migration feature. It checks that when a wallet is migrated with the 'load_wallet=False' option, the wallet is not automatically loaded afterward, settings are updated correctly, and auxiliary wallet names are reported. There is no change to production wallet code, so this commit does not introduce or fix a security vulnerability on its own.

This commit adds a new optional 'load_wallet' argument to the 'migratewallet' RPC command in Bitcoin Core. It lets users choose whether the wallet should be automatically loaded after migration, defaulting to true to preserve existing behavior. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a usability or workflow improvement.

This commit only adds a release note describing a previously merged feature. It does not change any code, configuration, or behavior. There is no security issue in this commit itself.

This Bitcoin Core change lets users migrate old-style wallets to the newer descriptor format without automatically loading the migrated wallet afterward. The main goal is to support pruned nodes, which previously could not migrate because loading the wallet required full block history. The patch also removes the old wallet from the startup list when migration is done without loading. There is no obvious security bug here; it is a feature/robustness improvement.

This commit adds new test code to Bitcoin Core's fuzzing harness for the network connection manager. It exercises the AddLocalServices and RemoveLocalServices functions, which control what network service flags a node advertises. The change is purely a test/fuzzing addition and does not modify production code.

This commit only adds extra consistency checks (assertions) inside an existing fuzz test for Bitcoin Core's network connection manager. It does not change production code, network behavior, or wallet logic. There is no user-facing bug fix or security patch here.

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. It adds checks that verify how Bitcoin Core's connection manager handles manually added nodes. There is no change to production code, no fix for a real vulnerability, and no security risk to users.

This commit removes mutexes (thread-safety locks) from two internal Bitcoin Core fuzz-test helpers. Fuzz tests are automated test harnesses, not production code, and the commit explains that the locks were unnecessary because fuzz targets run sequentially within a single process. There is no indication this change affects real Bitcoin Core users or introduces a security vulnerability.

This commit only changes a fuzz test (an automated testing harness) for Bitcoin Core's database wrapper. It reduces how many read operations each simulated worker thread performs during the test, which makes the test run faster, and increases the maximum number of database entries back to a previous value to keep test coverage. There is no change to production code, no user-facing behavior change, and no security fix.

This small change reorders two operations in the `importdescriptors` wallet command. Previously, the wallet first waited until it was caught up to the latest block, then tried to reserve a rescan. Now it reserves the rescan first, then waits to catch up. The likely goal is to prevent a race where another process starts a rescan in between those two steps, which could cause the import to proceed without the expected rescan or with conflicting rescan state. The practical security impact is limited and situational.