Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a code cleanup change that turns on a static-analysis rule to prevent a specific C++ coding pattern (anonymous namespaces in header files) and updates two headers to comply. It does not change how Bitcoin Core behaves at runtime an…
No security-relevant code changeNo memory safety, cryptography, consensus, or network changesTooling-only refactor (clang-tidy configuration)
This commit only adds new test cases to Bitcoin Core's functional test suite. It does not change any production wallet, node, or RPC code. The tests verify that the importdescriptors RPC reports errors in the right order, rejects bad times…
This change is purely a code cleanup: it moves two internal helper functions of a Bitcoin Core cache class into the private section of the class and removes a duplicate 'private:' label. There is no change to what the code does, no bug fix…
This Bitcoin Core change tightens how three RPC commands (scantxoutset, scanblocks, deriveaddresses) handle the value null when it is passed for optional parameters. Previously, explicitly passing null could be treated differently from sim…
RPC parameter validation changeNull value handling changeAddition of explicit error checks for missing required contextual parameters
This commit is a code cleanup: it turns on a clang-tidy style check called 'misc-definitions-in-headers' and suppresses that check around a large inline implementation block in a benchmark header. There is no change to Bitcoin's runtime be…
This commit only changes a linting configuration file for the project's code style checker. It enables a rule that prevents anonymous namespaces from being used in header files, which is a code-quality and build-hygiene practice. There is …
No security-relevant signals in the diff or commit message.Change is purely a static-analysis/linting configuration update.
This commit is a straightforward code cleanup: it replaces a small custom helper named IntIdentity with the standard C++20 std::identity from the <functional> header. The behavior of the ConvertBits function is unchanged; only the implemen…
This commit only adds a new automated test to Bitcoin Core. It checks that when a user asks the wallet to import multiple descriptors at once, the list of results comes back in the same order as the original request, including any error me…
This commit only adds new automated tests for the Bitcoin Core wallet's importdescriptors RPC. It checks that the command correctly rejects requests with a missing or invalid timestamp. No production wallet code is changed, so this cannot …
No changes to consensus, networking, wallet logic, or cryptographyOnly functional test code is modifiedAdded assertions are for expected error handling paths
This is a minor code cleanup that removes one unused header file include and swaps another for a more specific one. It does not change any program behavior or fix any security issue.
This commit is a routine code cleanup: it adjusts which C++ header files are included in several consensus-related source files and turns on a stricter compiler hygiene check (Include What You Use, or IWYU) for the src/consensus directory.…
This is a small fix to a Bitcoin Core fuzz test (an automated internal testing harness), not to the live network code. The fuzzer was sometimes creating fake P2P messages larger than the real protocol allows and passing them into a test he…
Test-only fuzz harness hardeningOversized message guard added before ReceiveMsgFrom() in fuzz targetNo change to production P2P message acceptance logic
This commit simply removes one failing test configuration (RISC-V 32-bit bare metal) from the project's GitHub Actions CI matrix because it was failing. It is a routine CI maintenance change with no security implications.
This change adds checksum verification to the build system's downloads of Apple, FreeBSD, NetBSD, and OpenBSD software development kits (SDKs). Before this patch, those SDK archives were downloaded at build time and extracted without confi…
Adds cryptographic digest verification for downloaded SDK archivesRemoves unchecked extraction of remote SDK archives in CIHardens CI supply chain for macOS/BSD cross-builds
This is a routine maintenance update to Bitcoin Core's continuous integration (CI) system. It changes the version number of the NetBSD operating system used for cross-compilation testing from a release candidate (11.0_RC6) to the final rel…
This commit only changes a test file and build configuration. It removes the option to skip a test when the system cannot detect total RAM, and instead requires the RAM detection to succeed. It does not change any production wallet, networ…
This commit is a simple automated rename of a constant from MIN_DB_CACHE to MIN_DBCACHE_BYTES across five files. The value stays the same (4 MiB), and no behavior changes. It is a code-cleanup/refactoring change with no security relevance.
This commit adds a new public API knob to the Bitcoin Core 'libbitcoinkernel' library so that programs using the kernel can choose how much memory to use for the chainstate database cache. It also enforces minimum and maximum size limits. …
New configurable cache-size API with explicit min/max validationReplaces hard-coded DEFAULT_KERNEL_CACHE with caller-supplied valueAdds unit tests for out-of-range rejection and 32-bit upper-bound rejection
This commit is a small code cleanup: it moves two constants that define the minimum and maximum size of the database cache (dbcache) into a shared kernel header so that both the node and kernel code use the same limits. There is no change …
This is a small code cleanup change in Bitcoin Core. It removes a misleading alias named DEFAULT_DB_CACHE and replaces it with the underlying name DEFAULT_KERNEL_CACHE in a few places. The behavior of the program is unchanged; only the nam…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-prioritylogging: Protect ShrinkDebugFile by m_csby Anthony Towns · 72e92d67 · May 15, 2026 · 2 filesMessage 60 · AdequateLow 32Details
Commit message · Anthony Towns
logging: Protect ShrinkDebugFile by m_cs
We should not be logging while shrinking the debug file, so make sure that's true by using our mutex.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Low 32/100
This commit fixes a potential crash or data corruption bug in Bitcoin Core's debug log handling. The ShrinkDebugFile() function, which trims the large debug.log file down to size, was not using the same lock (mutex) that protects normal logging. That meant logging could happen at the same time the file was being shrunk, possibly causing the program to behave incorrectly or crash. The fix wraps the shrink operation in the logging mutex and changes one internal warning call so it works while that lock is held.
Lower-prioritydoc: Move mutex and thread section into guideline sectionby MarcoFalke · faf6afd9 · May 15, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · MarcoFalke
doc: Move mutex and thread section into guideline section
Previously, they have been in the "Tips and tricks" section, which seems a bit off.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit is a pure documentation reorganization. It moves the 'Locking/mutex usage notes' and 'Threads' sections from the 'Tips and tricks' area into a new 'Development guidelines' section in the developer notes. No code, logic, or security behavior changed.
Valgrind is often used as a sanitizer, so move it closer to the Sanitizer section.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
defensive validationdocumentation-only discount
AI analysis · Informational 15/100
This commit simply moves the existing Valgrind documentation section to a different place in the developer notes file. No code, configuration, or behavior changed. It is purely a documentation reorganization.
Doxygen is about the C++ comment style, so move the Python section to have all C++ style sections in one flow.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit simply moves a documentation section about Python coding style to a different place in the developer notes. It is a non-functional, move-only change with no security relevance.
* Remove the explicit modernize-use-nullptr rule mention, which has not been needed for years. * Encourage devs to refer to the upstream clang-tidy rules documentation. * Move NOLINTNEXTLINE(misc-no-recursion) into a subsection under the new clang-tidy section.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only reorganizes developer documentation about code style and the clang-tidy checking tool. It removes an outdated note, moves a recursion-related note into a new subsection, and adds a link to upstream clang-tidy documentation. No program code was changed, so there is no security impact.
Lower-prioritydoc: Fix to use lower-case anchors in links to C++ Core Guidelinesby MarcoFalke · fa9c2dde · May 15, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · MarcoFalke
doc: Fix to use lower-case anchors in links to C++ Core Guidelines
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only fixes the capitalization of web link anchors in developer documentation. It changes three URLs from upper-case anchors (like #Renum-caps) to lower-case anchors (like #renum-caps) so the links work correctly. There is no change to any program code, no security issue, and no risk to users.
cmake: Check dependencies after build option interaction
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit reorganizes the CMake build scripts so that dependency checks happen after build options have been finalized. It is a build-system correctness and maintainability improvement, not a security fix. There is no indication it addresses a vulnerability or changes runtime behavior of Bitcoin Core.
Lower-prioritybench: add benchmark for GetMappedAS()by 0xb10c · 096bb0b5 · May 15, 2026 · 2 filesMessage 86 · StrongInformational 15Details
Commit message · 0xb10c
bench: add benchmark for GetMappedAS()
With #28792 merged, we can use the embedded ASMap file to benchmark the IP -> ASN lookups. Before, this would have been cumbersome as it required having a real, external ASMap file. We want to benchmark against a real file, as a smaller test file has significantly faster lookups.
The benchmarks cover individual IP address lookups of mapped and unmapped IPv4 and IPv6 addresses along with a multi-IP lookup. For the IPs we assume to be mapped, we assert that they are mapped. Updating the embedded ASMap file might change the benchmark results slightly as some lookups will be a bit faster and others slower.
Co-authored-by: Fabian Jahr <fjahr@protonmail.com> Co-authored-by: Lőrinc <pap.lorinc@gmail.com>
86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100
This commit only adds a new performance benchmark for an existing IP-to-ASN lookup feature. It does not change any production code, network behavior, or security logic. There is no security issue here.
Security candidatei2p: clean up SAM error loggingby takeshikurosawaa · b6c36704 · May 15, 2026 · 1 fileMessage 73 · AdequateLow 35Details
Commit message · takeshikurosawaa
i2p: clean up SAM error logging
SESSION CREATE requests can contain the I2P private key. Keep using the redacted request text in error messages, and avoid echoing raw SAM replies in the generic reply error path.
This keeps the error useful while avoiding logging either the private-key-bearing request or unescaped router-controlled reply bytes. No network behavior change is intended.
73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
secret or key material
AI analysis · Low 35/100
This commit tightens up error messages in Bitcoin Core's I2P (anonymous networking) code. Previously, error messages could accidentally include the full text of a SAM request that may carry the user's I2P private key, or the full raw reply from an I2P router. The patch keeps the error useful by still referencing the redacted request, but stops echoing the sensitive request body and unescaped router replies into logs. It is a defensive information-disclosure fix, not a change to network behavior.
test: avoid non-loopback network traffic from node_init_tests/init_test
The test calls: `AppInitMain()` -> `StartMapPort()` -> `StartThreadMapPort()` -> `ThreadMapPort()` -> `ProcessPCP()` -> `PCPRequestPortMap()` -> `CreateSock()` and on the returned value from `CreateSock()` it calls the `Connect()` method.
Thus, change `BasicTestingSetup::BasicTestingSetup()` to set `-natpmp` to 0. This way `node_init_tests/init_test` or other tests will not do network activity due to `ThreadMapPort()`.
Also add a comment about `natpmp=0` in `test/functional/test_framework/util.py`.
Also set `-dnsseed=0` in `BasicTestingSetup::BasicTestingSetup()` to avoid DNS queries.
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 23/100
This is a test-hardening change, not a fix for an exploitable vulnerability in live Bitcoin Core. The patch stops automated tests from accidentally sending real network traffic (router NAT-PMP packets and DNS queries) to non-localhost destinations. It does not change how normal node software behaves when users run it.
Lower-priorityp2p: Release m_peer_mutex early in InitiateTxBroadcastToAllby MarcoFalke · fa2afba2 · May 15, 2026 · 2 filesMessage 50 · ThinInformational 23Details
Commit message · MarcoFalke
p2p: Release m_peer_mutex early in InitiateTxBroadcastToAll
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 23/100
This change refactors how Bitcoin Core sends transaction announcements to all connected peers. Previously, the code held a broad internal lock (m_peer_mutex) while iterating over every peer and preparing messages. The patch copies the peer list under the lock, then releases the lock before doing the slower per-peer work. This reduces the chance of lock contention and removes a known ThreadSanitizer suppression for a deadlock in Chainstate::ConnectTip. It is a robustness improvement, not a fix for an exploitable vulnerability.
AI review queueddoc: external signer: update interface, --stdin flag, IPC-command signtx, contains updates from #33947by Danny van Heumen · 3381855e · May 14, 2026 · 1 fileMessage 58 · ThinInformational 15Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathdocumentation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates documentation for Bitcoin Core's external signer feature. It renames a command from 'signtransaction' to 'signtx', documents a new required '--stdin' flag, adds '--chain' flag details, and fixes examples. No actual code was changed, so this cannot directly introduce or fix a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only adds documentation: a new release-notes file explaining that an obscure build-system environment variable was removed and how users can still disable git detection. There is no code change, no bug fix, and no security-relevant behavior change in the commit itself.
Lower-prioritycmake: Skip using git when building from source tarball or as subprojectby Hennadii Stepanov · b71cd5c1 · May 14, 2026 · 2 filesMessage 50 · ThinInformational 18Details
Commit message · Hennadii Stepanov
cmake: Skip using git when building from source tarball or as subproject
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 18/100
This commit changes Bitcoin Core's build system so it does not try to use Git when compiling from a source tarball or when Bitcoin Core is included as a subproject inside another project. It uses Git's 'export-subst' feature to detect tarball builds. There is no security vulnerability here; it is a build-system robustness improvement.
This functionality is now covered by the `CMAKE_DISABLE_FIND_PACKAGE_Git` variable.
Note for reviewers: consider reviewing with `git diff -w`.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100
This commit removes an old environment variable used during Bitcoin Core's build process and replaces its behavior with a standard CMake option. It is a routine build-system cleanup with no security relevance.
cmake, refactor: Move `find_package(Git)` to `src/CMakeLists.txt`
This change allows the use of the `CMAKE_DISABLE_FIND_PACKAGE_Git` variable to explicitly disable git usage.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100
This is a harmless build-system cleanup. It moves the CMake command that looks for the Git program from one internal script into another, and passes the discovered Git path explicitly. There is no security issue here.
fuzz: Fix txorphan timeout by limiting block weight
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidence
AI analysis · Informational 17/100
This change only affects an internal fuzz test (automated randomized testing) for orphan transaction handling. It prevents the fuzz test from creating unrealistically huge blocks that could cause the test to time out. There is no change to production Bitcoin node code, so real users or the live network are not affected.
Lower-priorityci: Use path with spaces on windows as wellby MarcoFalke · 7777a92a · May 14, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · MarcoFalke
ci: Use path with spaces on windows as well
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This change only updates Bitcoin Core's internal Windows CI (continuous integration) scripts to run tests inside a temporary folder whose name contains spaces. It is a testing-infrastructure tweak with no effect on the Bitcoin software users run, on network consensus, or on wallets.
Lower-priorityci: Put space and non-ASCII char in scratch dirby MarcoFalke · fac6c427 · May 14, 2026 · 4 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke
ci: Put space and non-ASCII char in scratch dir
Also, add a missing quote around -DCMAKE_INSTALL_PREFIX to avoid word splitting. Otherwise, cmake would warn:
Also, allow spaces in the debug log file regex in a test. Otherwise, the test would fail:
``` TestFramework (ERROR): Unexpected exception: Traceback (most recent call last): File "./test/functional/test_framework/test_framework.py", line 142, in main self.run_test() ~~~~~~~~~~~~~^^ File "./test/functional/feature_logging.py", line 40, in run_test self.nodes[0].assert_start_raises_init_error([f"-debuglogfile={invalidname}"], exp_stderr, match=ErrorMatch.FULL_REGEX) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "./test/functional/test_framework/test_node.py", line 743, in assert_start_raises_init_error self._raise_assertion_error( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ 'Expected message "{}" does not fully match stderr:\n"{}"'.format(expected_msg, stderr)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "./test/functional/test_framework/test_node.py", line 229, in _raise_assertion_error raise AssertionError(self._node_msg(msg)) AssertionError: [node 0] Expected message "Error: Could not open debug log file \S+$" does not fully match stderr: "Error: Could not open debug log file /Users/runner/work/bitcoin-core-with-ci/bitcoin-core-with-ci/repo_archive/ci/scratch_ ₿🧪_/test_runner/test_runner_₿_🏃_20260218_095938/feature_logging_31/node0/regtest/foo/foo.log" ```
Also, add missing quotes in a test. Otherwise, the test would fail:
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
defensive validationfuzzing or regression evidence
AI analysis · Informational 15/100
This commit changes Bitcoin Core's continuous integration (CI) test setup to use a temporary directory name containing a space and non-ASCII characters (₿🧪). It also fixes shell quoting in CI scripts and two functional tests so they work correctly when paths contain spaces or special characters. There is no security vulnerability being fixed or introduced here; it is purely a hardening of the test infrastructure to catch quoting bugs in the future.
The ci fails when $FILE_ENV is not set, so fail early with a clearer error message by setting nounset:
> bash: FILE_ENV: unbound variable
63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Informational 16/100
This is a minor improvement to Bitcoin Core's internal continuous integration (CI) script. It makes the script fail earlier and with a clearer error message if a required environment variable is missing. It does not change how Bitcoin nodes run, how wallets work, or how transactions are validated. There is no security vulnerability being fixed here.
AI review queuedRemove opt-in RBFby Pol Espinasa · 90eda67b · May 13, 2026 · 4 filesMessage 51 · ThinInformational 23Details
Commit message · Pol Espinasa
Remove opt-in RBF
Remove the option to signal or not signal for BIP 125 (Opt-in Full Replace-By-Fee). By removing the option in the GUI it will fallback to the wallet configuration which by default is true unless the user changed it using CLI.
51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This commit removes the on/off checkbox in the Bitcoin Core desktop wallet that let users choose whether a transaction should signal 'Replace-By-Fee' (RBF). After the change, the GUI simply follows the wallet's configuration setting instead. It is a user-interface simplification, not a fix for a software vulnerability.
Lower-prioritydoc: Document minimum versions for Xcode CLT and MSVCby MarcoFalke · fa3d7ce1 · May 13, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · MarcoFalke
doc: Document minimum versions for Xcode CLT and MSVC
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit only updates documentation and build error messages to state the minimum supported versions of Apple's Xcode Command Line Tools (16.2) and Microsoft's Visual C++ compiler (18.3). It does not change any executable code, cryptographic logic, network behavior, or security-sensitive functionality. There is no security issue here.
Security candidatetest: Check that MuSig2 signing does not reuse noncesby Ava Chow · 2ef6679c · May 13, 2026 · 1 fileMessage 87 · StrongInformational 12Details
Commit message · Ava Chow
test: Check that MuSig2 signing does not reuse nonces
Run each MuSig2 operation twice to check that new nonces are generated and used throughout signing.
87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 12/100
This commit only adds a new test to Bitcoin Core's functional test suite. It runs each MuSig2 signing operation twice and checks that different nonces and partial signatures are produced each time. There is no change to wallet or consensus code, so it does not fix or introduce a vulnerability by itself. It is a defensive regression test aimed at catching nonce-reuse bugs in the future.
Lower-prioritymining: drop unused include_dummy_extranonce optionby Sjors Provoost · 8544537f · May 13, 2026 · 16 filesMessage 83 · StrongInformational 15Details
Commit message · Sjors Provoost
mining: drop unused include_dummy_extranonce option
The previous commit made CreateNewBlock() ignore the include_dummy_extranonce flag (OP_0 is now appended only at heights <= 16 to satisfy bad-cb-length, regardless of caller-supplied options).
Remove the now-unused field from BlockCreateOptions and clean up all the call sites that still set it (RPC, bench, fuzz, test setups).
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidence
AI analysis · Informational 15/100
This commit is a routine cleanup: it removes an option called include_dummy_extranonce that no longer does anything. The previous commit already made the block-building code ignore this flag, so this change only deletes leftover references in tests, benchmarks, RPC code, and fuzz targets. There is no security-relevant behavior change.
AI review queuedmining: only pad with OP_0 at heights <= 16by Sjors Provoost · 58eeab79 · May 13, 2026 · 13 filesMessage 90 · StrongInformational 18Details
Commit message · Sjors Provoost
mining: only pad with OP_0 at heights <= 16
Drop the include_dummy_extranonce branch from the OP_0 padding condition in CreateNewBlock(), so that the dummy extraNonce is only appended when consensus actually requires it (heights <= 16, where the BIP34 height push alone would yield a 1-byte scriptSig and trigger bad-cb-length).
The include_dummy_extranonce option struct field is now unused by the miner and is removed in the next commit. Callers still set it, so that this commit compiles.
Regenerate the hardcoded coinbase / block hashes throughout the unit and functional test suites and update the regtest assumeutxo snapshot in chainparams.
Additional side-effects:
- Without the dummy extranonce, coinbase scriptSigs are 1 byte shorter at heights > 16, making every block 1 byte smaller. This shifts where block files wrap and therefore where pruning boundaries land.
- feature_assumeutxo malleation cases: - case 1: error message changes due to UTXO reordering, similar to 8f2078af6a55448c003b3f7f3021955fbb351caa - case 4: the corruption byte is swapped from \x82 to \x83 because \x82 happened to be the actual value at that offset in the new snapshot.
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This Bitcoin Core change removes an unnecessary extra zero byte (OP_0) from newly mined coinbase transactions after block height 16. That byte was originally added to satisfy a minimum coinbase script length rule, but only heights 1-16 actually need it. The change is a cleanup that makes blocks one byte smaller and updates many hardcoded test hashes accordingly. It does not fix a vulnerability and does not appear exploitable.