Bitcoin Core

This commit is a test-only code cleanup. It moves the setup of a fake SOCKS5 proxy server used in automated tests into a shared helper function and lets the operating system pick an available network port instead of guessing one. It does not change any production Bitcoin Core code or fix a security vulnerability.

This commit removes a single 'friend' relationship between two wallet classes in Bitcoin Core. It is a code-cleanup change that reduces unnecessary access to private members; it does not fix a bug or vulnerability and has no direct security impact.

This is a small fix in Bitcoin Core's 'sendall' wallet RPC command. The bug meant that when a user explicitly set a transaction as non-replaceable, the wallet skipped its normal anti-fee-sniping protection. Anti-fee-sniping is a privacy/defense mechanism that uses the current block height as a transaction 'locktime' to make transactions look more similar and slightly harder to target. The fix changes the input sequence number used in that case so the protection still runs even when RBF is disabled.

This commit is a code-quality cleanup: it adjusts which C++ header files are included in many source files under src/script and related areas, and tells the continuous-integration (CI) tool to treat 'include-what-you-use' (IWYU) warnings as errors for those files. There is no functional change to how Bitcoin validates transactions, scripts, or signatures, and no security fix or vulnerability is described.

This commit simply changes the Bitcoin Core GitHub Actions CI configuration to use 'ubuntu-latest' instead of the specific 'ubuntu-24.04' label for fallback runners. It is a routine infrastructure consistency change with no direct security relevance to the Bitcoin software itself.

This commit is a trivial documentation update inside a configuration file for code editors. It changes a comment from referencing 'Cirrus' (a former CI service) to 'ci.yml' (the current CI filename). There is no code change, no security fix, and no user-facing behavior change.

This commit only rewords a code comment in a header file. It changes 'Should only be used for tests / benchmarks' to 'Should only be disabled for tests / benchmarks' to make the documentation clearer. No code behavior changed, and there is no security issue.

This is a one-line fix inside a Bitcoin Core functional test. After restarting a test node, the test wallet's view of available coins is refreshed so the rest of the test can spend them correctly. It does not change production wallet, node, or consensus code, and has no security relevance for real users.

This is a small hardening change in Bitcoin Core's block-building code. It adds internal safety checks (assertions) to make sure a configuration value called block_max_weight has been converted from an optional value to a plain number before it is used in limit comparisons. The change does not by itself fix a known exploitable bug, but it guards against a class of programming mistakes where an unset value could silently behave as zero and cause incorrect block-size decisions.

This is a small test-only code change in Bitcoin Core. It updates a single unit test to use a helper function that merges mining options instead of using a raw mining arguments object directly. There is no change to production code, no network behavior change, and no security fix.

This is a small cleanup in Bitcoin Core's test suite. It replaces a locally-defined timeout value with a shared class attribute that has the exact same value. The commit message explicitly says it does not change behavior, and the diff confirms that: the same timeout formula is used, just in one place instead of two.

This commit only changes a fuzz test file. Fuzz tests are automated tools that throw random inputs at code to find bugs. The change adds three new random settings to the test and adds two assertions to verify those settings are stored correctly. There is no change to the actual Bitcoin network code that users run, so this cannot directly affect live nodes or wallets.

This commit only changes a fuzz test file. A fuzz test is an automated testing harness that throws random inputs at code to find bugs. The change adds an assertion that after setting network activity on or off, reading the value back matches what was set. It removes a redundant read at the end of the test. There is no change to production Bitcoin networking code, so this does not fix or introduce a security issue in the live software.

This commit adds a safety check to Bitcoin Core's code that creates master cryptographic keys from a seed. The BIP32 standard says seeds must be 16 to 64 bytes long, but the function previously accepted any length, including empty seeds. The fix rejects out-of-range seeds with an internal assertion. It is a hardening change rather than a fix for an active exploit path, because callers in the current codebase already supply valid-length seeds.

This commit only reformats the Unix build instructions documentation. It compresses long lists of Linux package installation commands into a single table and removes an Arch Linux example. No program code, build scripts, or dependencies were changed, so it has no security relevance.

This commit adds a new way for external mining software connected to Bitcoin Core over IPC to look up transactions in the memory pool by their witness transaction ID (wtxid). It mirrors an existing transaction lookup by regular transaction ID (txid) and includes tests. There is no indication in the commit that this fixes a security bug; it appears to be a normal feature addition.

This commit adds a new inter-process communication (IPC) method that lets an external mining process ask the Bitcoin Core node to look up raw transactions in the memory pool by their transaction IDs. It is a straightforward read-only lookup: found transactions are returned, missing ones come back as empty/null. There is no obvious security flaw in the change itself, but it does slightly expand what the IPC mining interface can access.

This is a minor test-only cleanup change. It adds three lines to a Bitcoin Core functional test so that the test restarts and reconnects its internal test node after checking some command-line option overrides. There is no change to production code, no wallet or network behavior change for real users, and no security issue.

This commit fixes a serialization edge case in Bitcoin Core's inter-process communication (IPC) layer. Previously, a null (empty) transaction reference could not be sent across the IPC boundary in a list of transactions because the Cap'n Proto protocol cannot distinguish between an empty data field and a null value. The fix treats empty transaction data as null, and adds a safety check so that submitting a mining solution with an empty coinbase is rejected instead of potentially causing a crash or undefined behavior.

This commit adds a new way to look up transactions in Bitcoin Core's memory pool (mempool) using the transaction's witness hash (wtxid), in addition to the existing lookup by regular transaction hash (txid). It also adds a unit test to verify both lookup methods work. There is no indication this change fixes a security vulnerability; it appears to be a normal feature or code-quality improvement.

This commit adds a new automated test to Bitcoin Core that checks whether very old-style wallets (those created before a 2012-era change) can still be successfully migrated to the modern wallet format. It does not change any production wallet code; it only adds a test that deliberately corrupts a test wallet file to simulate an ancient wallet and then verifies migration still works.

This patch fixes a bug where migrating very old Bitcoin wallets would fail entirely. The problem was that the migration code required a 'best block locator' record that did not exist in wallets created before that feature was added. The fix makes that record optional: if it is missing, migration continues and writes an empty locator to the new wallet files, which simply causes them to rescan the blockchain on next load. There is no attacker-controlled path here; it is a robustness fix for a user-initiated wallet migration.

This commit only rewords the 'Getting Started' section in the project's CONTRIBUTING.md documentation. It removes a link to 'up for grabs' issues and adds guidance about finding good first issues. There are no code changes and no security relevance.

This commit removes three comment lines that told a static-analysis tool (ShellCheck) where to find two helper scripts. The actual script behavior is unchanged; it still loads the same two files. There is no security issue here.

This commit is a straightforward internal cleanup of the Bitcoin Core Guix build scripts. It changes how directory paths are computed by adding an optional BASE argument to helper functions, replacing a temporary environment-variable trick. There is no change to how Bitcoin validates transactions, handles network data, or stores wallets, and nothing in the commit suggests a security fix or vulnerability.