Bitcoin Core

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.

This commit is a simple code cleanup in Bitcoin Core's Guix build scripts. It moves a helper function that builds directory paths from two separate scripts into a shared library file, and adds an optional suffix parameter so both scripts can use the same function. There is no change to how Bitcoin works, no security fix, and no vulnerability.

This commit is a simple code cleanup in Bitcoin Core's Guix build scripts. It removes two identical copies of a helper function and places a single shared copy in a common file. The function itself only builds a directory path string and does not change behavior. There is no security issue here.

This commit is a simple cleanup: it removes two identical copies of a small helper function from two build scripts and places a single shared copy in a common file that both scripts already use. The function itself just builds an output directory path string. There is no security-relevant change here.

This commit is a small code cleanup in the Bitcoin Core Guix build script. It removes a custom helper function called contains() and replaces it with a simpler approach using two separate lists of directory names. There is no security issue here; it is purely a refactoring change to make the build script easier to read and maintain.

This commit simply removes an unused helper function from a Guix build-attestation script. There is no change to how Bitcoin Core runs, no security fix, and no vulnerability introduced.

This is a small fix to a Bitcoin Core test script. The test deliberately crashes nodes to check that the database recovers correctly. The change adds a short wait after detecting a crash before restarting the node, preventing the test from trying to restart a node that has not fully shut down yet. It does not change the actual Bitcoin network software that users run, so it has no direct security impact on real Bitcoin nodes.

This change only adjusts Bitcoin Core's continuous integration (CI) test configuration. It tells the test runner to skip one specific test, feature_dbcrash.py, when running with certain command-line options because that test is extremely slow (about 47 minutes in one run). There is no code change that affects how Bitcoin nodes operate, and no security issue is present.

This is a fix for an unreliable test script, not a security fix in Bitcoin Core itself. The test intentionally crashes Bitcoin nodes to verify database crash recovery. When run with the --usecli option, the test sometimes failed because it only caught one type of error (OSError) but bitcoin-cli can raise a different error (CalledProcessError) when the node is temporarily unreachable. The change broadens the exception handling so the test can continue and verify the crash as intended. It does not change production code or introduce a vulnerability.

This is a test-only code cleanup. It changes how a Bitcoin Core functional test catches errors when submitting blocks to a test node that is intentionally being crashed. The test now catches any generic exception instead of a specific list of network/process errors, and relies on a separate helper to confirm the node actually crashed. It does not touch the live Bitcoin network code, consensus rules, or wallet handling.

This commit fixes a single grammar typo in release notes, changing 'this options' to 'this option'. It has no effect on software behavior or security.

This commit only adds a new automated test file and registers it in the test runner. It checks that two old wallet/RBF-related command-line options still behave as documented while they are being phased out. There is no change to the actual Bitcoin Core software that users run, so it cannot introduce a security vulnerability or fix one.