Bitcoin Core

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.

This commit only changes a test file. It removes the use of a deprecated RPC option and deletes test assertions that checked whether transactions were marked as replaceable. There is no change to the actual Bitcoin Core wallet or network code, and no security issue is evident.

This is a minor test-only cleanup. It removes a deprecated command-line flag and an obsolete field name from a single automated test script. There is no change to Bitcoin Core's actual wallet or network code, and no security relevance.

This is a routine test-only cleanup. A Bitcoin Core functional test was still starting one node with a deprecated RPC compatibility flag (-deprecatedrpc=bip125). The patch removes that flag and adjusts the test assertions to ignore the now-removed 'bip125-replaceable' field when comparing transaction lists. No production code, no wallet logic, and no network behavior changed.

This commit only changes a single test file. It removes the redundant '-walletrbf=1' startup flag from several test nodes because those older Bitcoin Core versions already default to that setting. There is no change to the actual Bitcoin Core wallet or network code, and no security issue is present.

This is a routine build cleanup. It removes one compiler-definition line that mapped an old LevelDB macro to the modern C++17 '[[fallthrough]]' attribute. The change is possible because the bundled LevelDB subtree was separately updated to use the modern attribute directly. There is no security-relevant change to runtime behavior.

This commit removes a compiler warning suppression from the LevelDB build settings in Bitcoin Core. It does not change any executable code, only build configuration. The change means the compiler may now warn about variables that could be used before being initialized in the bundled LevelDB library. By itself, this is a code-quality cleanup, not a fix for a known security bug.

This commit updates Bitcoin Core's embedded LevelDB copy. The most notable change is disabling an automatic database compaction feature that was triggered by read patterns. The commit also reverts a previous increase in memory-mapped file limits, fixes a compiler warning, and makes minor build and code cleanups. None of these changes fix a known active security vulnerability; they are maintenance and behavior-tuning changes.

This commit simply swaps the third-party service that provides fast cloud computers for running Bitcoin Core's automated tests, changing from Cirrus Runners to WarpBuild runners. It updates labels, environment variable names, and runner machine names, but does not change any Bitcoin code, wallet logic, networking, or cryptography. There is no security vulnerability here.

This commit simply removes a GitHub issue template and updates the contributor documentation to stop pointing to the 'good first issue' label. It is a documentation-only workflow change with no effect on Bitcoin Core's code, network behavior, or security.

This commit rewrites a CI helper script from Bash to Python. The script is only used in Bitcoin Core's automated testing environment to wrap test executables with Valgrind, a memory-error detection tool. There is no change to the Bitcoin software that users run, no network-facing code is affected, and no security vulnerability is fixed or introduced.

This is a harmless shell-script cleanup in Bitcoin Core's internal continuous integration (CI) setup. It adds a default empty value for an environment variable so that running the CI script locally no longer prints a warning. It does not change behavior, fix a vulnerability, or affect the Bitcoin software users run.

This is a routine test-only cleanup. It removes an obsolete command-line option (-walletrbf) and its associated deprecation warning from a backwards-compatibility test script. There is no change to the Bitcoin Core wallet or network code that end users run, and no security issue is present.

This commit only changes a single test file. It removes the use of a deprecated RPC option and deletes test assertions that checked a now-removed 'bip125-replaceable' field in wallet transaction output. There is no change to the actual Bitcoin Core wallet or node code that users run, so this cannot affect live wallets, funds, or network security.

This commit only removes a test case from Bitcoin Core's automated test suite. It deletes the part of a test that exercised the deprecated '-walletrbf' startup option and related opt-in RBF transaction behavior. There is no change to the actual Bitcoin Core wallet, node, or network code, and no security vulnerability is present in the diff.