Bitcoin Core

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.

This commit only changes a single test file. It removes the use of the deprecated '-walletrbf' startup option and its associated deprecation warning from the wallet_bumpfee.py functional test. There is no change to production wallet code, no bug fix, and no security issue.

This commit only changes Bitcoin Core's own test code. It removes the obsolete -walletrbf startup option from two functional tests and adds a missing PSBT v2 field (fallback locktime) to a test helper that creates blank PSBTs. There is no change to production wallet or node code, so it does not affect real users' funds, transactions, or network security.

This commit only changes a test script to make it run faster. It swaps one internal test helper for another equivalent one when sending transactions during a crash-recovery test. There is no change to the actual Bitcoin Core software that users run, and no security relevance.

This is a minor cleanup commit in Bitcoin Core's test code only. It replaces a manual time-comparison helper with a direct comparison and removes some code-comment markers related to include-file management. There is no change to production code, no security fix, and no vulnerability.

This commit is a simple code cleanup in a test file. It merges three nearly identical helper functions into one shared method used by Bitcoin Core's automated compact block tests. There is no change to the actual Bitcoin network software or its security behavior.

This commit is a build-system housekeeping change for Bitcoin Core's Guix reproducible-build tooling. It takes one large package list file (manifest.scm) and splits it into two smaller files: one used when compiling the software (manifest_build.scm) and one used when applying release signatures (manifest_codesign.scm). The scripts that invoke Guix are updated to point at the correct new file. There is no change to the Bitcoin Core node software, wallet logic, or network behavior, and nothing in the commit suggests a security vulnerability or fix.

This commit updates a build dependency called python-signapple, which is used to create and verify digital signatures on macOS Bitcoin binaries. It also adds environment variables so the tool can find OpenSSL libraries during the Guix reproducible build process. There is no direct evidence in the commit that this fixes an exploitable security flaw in Bitcoin Core itself; it appears to be a build tooling/maintenance change.

This commit adds a new internal 'submitBlock' method to Bitcoin Core's Mining interface, used by external mining software (like Stratum v2 servers) to submit fully assembled blocks for validation. It is a feature addition that mirrors the existing submitblock RPC. There is no direct evidence in the commit of a security vulnerability, but it exposes block submission over the IPC interface, which carries the same general risks as any block-submission path: a compromised or buggy caller could submit invalid or duplicate blocks. The implementation explicitly rejects duplicates and requires a complete block, including coinbase witness data when needed.

This commit only adds new automated tests for the Bitcoin Core IPC mining interface. It does not change any production node code, consensus rules, or network behavior. The tests verify that a new submitBlock IPC method correctly accepts valid blocks and rejects invalid, duplicate, or malformed ones. There is no security vulnerability here.

This commit is a straightforward internal code reorganization (refactor) in Bitcoin Core. It moves the logic for submitting a newly mined block into a shared helper function called SubmitBlock(). The actual behavior of block submission does not change; the code just becomes cleaner and easier to reuse for future features like IPC (inter-process communication). There is no security bug being fixed and no new attack surface introduced.

This is a tiny code cleanup in Bitcoin Core's wallet setup. It changes how the deprecated '-walletrbf' setting is read so the value is fetched once and reused, rather than checked for existence and then fetched separately. There is no security issue here.