CommitWatch RSS
BC
← All projectsBitcoin Core

Bitcoin Core

The Bitcoin network's reference node and wallet implementation.

BitcoinSupply chainNormal
Source repository ↗
Repository coverage

2902 commits in the local evidence base

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.

254security candidates607second-pass queue2881AI analyses
191commits · 30 days
482commits · 60 days
1502commits · 180 days
2875commits · 365 days
Backfill bands
Aug 5 → Feb 61351 seen45 candidatesComplete
Feb 6 → Jun 61033 seen63 candidatesComplete
Jun 6 → Jul 6281 seen11 candidatesComplete
Jul 6 → Aug 5207 seen5 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

70/100 average clarity
939Strong · 80–100
1188Adequate · 60–79
687Thin · 40–59
88Opaque · 0–39
6security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Antoine Poinsot22422170
Ava Chow15750157064
MarcoFalke41021406074
Lőrinc17721177081
fanquake22719226057
Hennadii Stepanov20914208063
rkrux57957074
Sjors Provoost89889074
Sebastian Falbesoner33733073
David Gumberg55655072
Pieter Wuille95595066
Hodlinator66566076
Analysis record

Published AI watches

Last scanned 29 minutes ago

Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35928: doc: mention -DWITH_ZMQ=ON in macOS build guide

This is a one-line documentation update to the macOS build guide. It adds a note telling users to pass a specific CMake option if they want ZeroMQ notification support. There is no code change and no security impact.

8397e09eby merge-script+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35482: fuzz: exercise the transaction-handling path in process_message(s)

This commit only changes Bitcoin Core's internal fuzz testing code. It makes the fuzz tests exercise more of the transaction-handling code path by toggling Initial Block Download mode and resetting the mempool between test runs. There is n…

No production code modifiedNo consensus, validation, net_processing, or wallet logic changedOnly fuzz test harnesses and test utilities affected
f11dc617by merge-script+105−798 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35914: test, fuzz: Remove unused variables

This commit removes unused variables from Bitcoin Core's test and fuzzing code. It is a cleanup/refactoring change with no effect on the live network software or user funds. It does not fix or introduce any security vulnerability.

d36bf709by merge-script+1−138 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35896: refactor: Default uint256::operator==, add operator<=>

This commit is a routine code cleanup in Bitcoin Core. It switches the uint256 equality and comparison operators to use standard C++20 defaults, removes an old custom Compare() helper, and marks an internal assertion-failure function as ne…

ed2c59abby merge-script+99−245 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 96 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35872: rpc: avoid descriptor range counter overflow

This update fixes a counting bug in several Bitcoin Core RPC commands that scan descriptors. When a user requested a descriptor range ending at the maximum allowed value (2,147,483,647), the internal counter used a smaller integer type and…

Signed integer overflow in descriptor expansion loopCrash/undefined behavior on maximum-range descriptor scansAuthenticated RPC surface affected (scantxoutset, scanblocks, getdescriptoractivity, utxoupdatepsbt, descriptorprocesspsbt)
b388674aby Ava Chow+3−12 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35842: rpc: Properly make RPCResult::Type::ANY non-test-only

This is a small cleanup and documentation fix for Bitcoin Core's RPC help system. It removes a comment that incorrectly said a certain output type was 'for testing only' and makes the help text properly display those outputs. There is no d…

No memory safety, cryptography, consensus, or authorization changes observedChange is confined to RPC help/schema metadata generationComment-only/type-label change from 'for testing only' to general use
c36ffd87by merge-script+42−364 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35895: refactor: Enable clang-tidy rule to reject anon namespace in header

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)
c4fbd3c7by merge-script+9−123 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35630: test: Add importdescriptors rpc error test coverage

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…

465196d0by merge-script+77−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35180: coins: group private cache helpers

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…

c940fd75by merge-script+13−141 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35582: rpc: reject null for optional parameters

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
3db96eb5by merge-script+18−75 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Enable misc-definitions-in-headers

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…

fa93132dby MarcoFalke+3−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Enable clang-tidy rule to reject anon namespace in header

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.
fa5ca877by MarcoFalke+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Use C++20 std::identity over IntIdentity

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…

fafe5042by MarcoFalke+4−111 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 87 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: test the result order of a multiple import request is correct

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…

3ac8b806by Pol Espinasa+40−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 87 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: test invalid or missing timestamp throws importdescriptors

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
e4732bf0by Pol Espinasa+28−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Remove unused #include in common/system

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.

fa7304f3by MarcoFalke+1−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

iwyu: Fix warnings in `src/consensus` and treat them as errors

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.…

13b53f8bby Hennadii Stepanov+42−79 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: don't connman.ReceiveMsgFrom oversized msg

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
bb19f1daby Greg Sanders+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 97 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: Temporarily remove riscv32 config from GHA matrix

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.

fa06ea42by MarcoFalke+0−61 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 90 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: verify cross-build SDK archives

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
873550beby Lőrinc+25−126 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityqt: Added test coverage for qt gui#901 console history filterby WakeTrainDev · 310e4979 · Nov 12, 2025 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · WakeTrainDev

qt: Added test coverage for qt gui#901 console history filter

68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only adds new automated test cases for the Bitcoin Core Qt console's command-history filtering feature. It checks that sensitive wallet commands (like createwallet and migratewallet) are displayed in shortened form in the console history. There is no change to production code and no security fix or vulnerability.

Lower-prioritycmake: Specify Windows plugin path in `test_bitcoin-qt` propertyby Hennadii Stepanov · 0dd8d5c2 · Nov 12, 2025 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Hennadii Stepanov

cmake: Specify Windows plugin path in `test_bitcoin-qt` property

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 change moves the location where a Qt plugin path is set for Windows testing from the CI workflow file into the CMake test configuration. It is a build/test infrastructure cleanup to make tests run more reliably in the Windows CI environment. There is no indication it fixes a security vulnerability.

AI review queuedscripted-diff: fix leftover references to `policy/fees.h`by ismaelsadeeq · b0a38871 · Nov 12, 2025 · 6 filesMessage 83 · StrongInformational 15Details
Commit message · ismaelsadeeq

scripted-diff: fix leftover references to `policy/fees.h`

-BEGIN VERIFY SCRIPT-
git grep -l "policy\/fees\.h" | xargs sed -i "s/policy\/fees.h/policy\/fees\/block_policy_estimator.h/g"
-END VERIFY SCRIPT-

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a simple cleanup: it updates comments and documentation strings that still pointed to an old file path (`policy/fees.h`) after that file was apparently moved or split. The actual code behavior does not change at all. There is no security issue here.

Lower-prioritydepends: drop qtbase-moc-ignore-gcc-macro.patch qt patchby fanquake · 3e9aca6f · Nov 12, 2025 · 3 filesMessage 73 · AdequateInformational 15Details
Commit message · fanquake

depends: drop qtbase-moc-ignore-gcc-macro.patch qt patch

Looks like this was fixed in 6.5 or 6.6, via
https://codereview.qt-project.org/c/qt/qtbase/+/492580.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit removes a build-system patch that Bitcoin Core used to apply to Qt during compilation. The patch told Qt's meta-object compiler (moc) to ignore a GCC internal macro. The commit message says the underlying Qt bug was fixed in Qt 6.5 or 6.6, so the patch is no longer needed. There is no direct evidence in the commit of a security vulnerability in Bitcoin Core itself.

Lower-priorityci: Rewrite lint task Bash snippet to Pythonby MarcoFalke · fac4f6de · Nov 12, 2025 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Rewrite lint task Bash snippet to Python

The Bash snippet was shorter, but relying on implicit word splitting
(see the shellcheck SC2086 warning).

For example, the DOCKER_BUILD_CACHE_ARG shlex.split is now done
identical to how ci/test/02_run_container.py does it.

Moreover, the Python will hopefully be easier to modify in the future,
as the dev notes recommend Python over Bash.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit rewrites a small GitHub Actions CI step from Bash to Python. It does not change what the CI step does; it only changes how the command is built and executed. The rewrite fixes a shell-script lint warning about unsafe word splitting and makes the code easier to maintain. There is no security vulnerability here.

Lower-priorityci: Rewrite Bash to check inputs to Pythonby MarcoFalke · fa0d37a5 · Nov 12, 2025 · 1 fileMessage 72 · AdequateInformational 16Details
Commit message · MarcoFalke

ci: Rewrite Bash to check inputs to Python

This is shorter and easier to read. Also, according to the dev notes,
Bash should not be used.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 16/100

This is a minor cleanup of a GitHub Actions workflow file. It rewrites a simple input-validation check from Bash to Python, with no functional change to what values are accepted or how the action behaves. There is no security issue visible in the change.

Lower-prioritydepends: drop unused qt patchby fanquake · 0da5a827 · Nov 12, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · fanquake

depends: drop unused qt patch

This hasn't been applied since 5e794e62024eef612e1fbb71c76ea54d17435c14,
but the patch was never removed.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit simply deletes an old, unused patch file from the build system. The patch was no longer being applied to Qt, so removing it has no effect on the compiled Bitcoin Core software and does not change any security behavior.

Lower-priorityci: [refactor] Use --preset=dev-mode in mac_native taskby MarcoFalke · fae83611 · Nov 12, 2025 · 2 filesMessage 89 · StrongInformational 15Details
Commit message · MarcoFalke

ci: [refactor] Use --preset=dev-mode in mac_native task

Also shorten the name, because it is usually truncated anyway in the web
view.

USDT remains disabled explicitly.

89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
AI analysis · Informational 15/100

This is a routine cleanup of Bitcoin Core's continuous integration (CI) configuration for macOS. It replaces a long list of build options with a pre-defined 'dev-mode' preset and shortens the job name shown in GitHub's web interface. There is no change to the actual Bitcoin software that users run, and no security relevance.

AI review queuedci: [refactor] Base nowallet task on --preset=dev-modeby MarcoFalke · fadb67b4 · Nov 12, 2025 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · MarcoFalke

ci: [refactor] Base nowallet task on --preset=dev-mode

This makes it clearer what pieces are disabled over the full dev-mode.

The wallet remains explicitly disabled.

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a routine internal cleanup of Bitcoin Core's continuous integration (CI) testing setup. It renames a test job from 'No wallet, libbitcoinkernel' to 'No wallet' and switches its build configuration to use a standard developer preset while still explicitly turning off the wallet. There is no change to the actual Bitcoin node software that users run, and nothing in the commit suggests a security issue.

Lower-priorityci: Enable bitcoin-chainstate and test_bitcoin-qt in win64 taskby MarcoFalke · 6666980e · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable bitcoin-chainstate and test_bitcoin-qt in win64 task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
test_bitcoin-qt ..................... ON

IPC and USDT remain explicitly disabled.

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 15/100

This commit only changes Bitcoin Core's continuous integration (CI) settings for Windows builds. It turns on two extra test executables in the automated build/test pipeline and renames a CI job. There is no change to the actual Bitcoin node, wallet, or network code that users run, so it does not create a security vulnerability or fix one.

Lower-prioritykernel: add btck_block_tree_entry_equalsby stickies-v · 096924d3 · Nov 12, 2025 · 4 filesMessage 58 · ThinInformational 15Details
Commit message · stickies-v

kernel: add btck_block_tree_entry_equals

BlockTreeEntry objects are often compared. By exposing an equality
function, clients don't have to implement more expensive
comparisons based on height and block hash.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit adds a new public helper function that lets outside code compare two block tree entries to see if they point to the same block. It is a pure API convenience addition with no bug fix, behavior change, or security-sensitive logic.

Lower-priorityci: Enable experimental kernel stuff in i686 taskby MarcoFalke · faff7b23 · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in i686 task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

IPC remains explicitly disabled.

100/100 · StrongMessage clarity
✓ 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 15/100

This commit only changes Bitcoin Core's continuous integration (CI) testing setup. It renames one CI job and adjusts build flags for an existing 32-bit (i686) test task so that it also exercises experimental kernel-related components. There is no change to the actual Bitcoin node code, consensus rules, wallet handling, networking, or any user-facing behavior.

Lower-priorityci: Enable experimental kernel stuff in mac-cross tasksby MarcoFalke · fa1632ee · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in mac-cross tasks

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

USDT remains explicitly disabled.

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 15/100

This commit changes two Bitcoin Core continuous integration (CI) configuration files for macOS cross-compilation tasks. It switches the build to use the 'dev-mode' preset and explicitly disables USDT tracing, while keeping reduced symbol exports. There is no change to the actual Bitcoin node or wallet code that users run.

Lower-priorityci: Enable experimental kernel stuff in armhf taskby MarcoFalke · fad10ff7 · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in armhf task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

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 15/100

This commit changes Bitcoin Core's continuous integration (CI) settings for 32-bit ARM testing. It switches the build to use the 'dev-mode' preset and enables several experimental kernel-related components for testing. There is no code change that affects how Bitcoin Core runs in production, and nothing in the commit suggests a security fix or vulnerability.

Security candidateci: Enable experimental kernel stuff in Alpine taskby MarcoFalke · fa9d67c1 · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in Alpine task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

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
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit changes a Bitcoin Core continuous integration (CI) test job. It renames the Alpine Linux test task and switches its build configuration to use a developer preset that enables experimental kernel-related components. There is no change to the actual Bitcoin node software, wallet code, network handling, or any code that end users run. It is purely a testing/CI configuration adjustment.

Lower-priorityci: Enable experimental kernel stuff in s390x taskby MarcoFalke · fab3fb83 · Nov 12, 2025 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in s390x task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

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 15/100

This commit changes only a continuous integration (CI) configuration file for the s390x mainframe platform. It switches the build to use the developer preset and explicitly turns on experimental kernel-related build options for automated testing. There is no change to the Bitcoin Core software that users run, no bug fix, and no security-relevant code change.

Lower-priorityci: Enable experimental kernel stuff in valgrind taskby MarcoFalke · fa7da8a6 · Nov 12, 2025 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in valgrind task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

The GUI and USDT remain disabled explicitly.

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 15/100

This commit changes only a continuous integration (CI) test script. It switches the valgrind test job to use a developer build preset and explicitly turns on experimental Bitcoin kernel-related components for testing. There is no change to the actual Bitcoin Core software that users run, and nothing in the commit suggests a security fix or vulnerability.

Lower-priorityci: Enable experimental kernel stuff in TSan taskby MarcoFalke · fa9c2973 · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in TSan task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

The GUI remains disabled explicitly.

100/100 · StrongMessage clarity
✓ 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 15/100

This commit changes only the Bitcoin Core continuous integration (CI) test configuration. It turns on additional experimental kernel-related build options for the ThreadSanitizer (TSan) test job and switches it to use the developer-mode build preset. There is no change to the actual Bitcoin node code that users run, and nothing in the commit suggests a security vulnerability or fix.

Lower-priorityci: Enable experimental kernel stuff in MSan taskby MarcoFalke · fad30d43 · Nov 12, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in MSan task

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

The GUI remains disabled explicitly.

100/100 · StrongMessage clarity
✓ 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 15/100

This commit only changes Bitcoin Core's continuous integration (CI) testing configuration. It renames a CI job from 'MSan, depends' to 'MSan' and switches the build to use a 'dev-mode' preset that enables experimental kernel-related components for testing with MemorySanitizer (MSan). There is no change to the actual Bitcoin node or wallet code that users run, and nothing in the commit suggests a security vulnerability or fix.

Lower-prioritytest: exercise TransactionMerklePath with empty block; targets the MerkleComputation empty-leaves path that was only reached by fuzz testsby frankomosh · ffcae82a · Nov 12, 2025 · 1 fileMessage 72 · AdequateInformational 12Details
Commit message · frankomosh

test: exercise TransactionMerklePath with empty block; targets the MerkleComputation empty-leaves path that was only reached by fuzz tests

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidence
AI analysis · Informational 12/100

This commit only adds a new test case to Bitcoin Core's test suite. It checks that when a block has no transactions, a helper function called TransactionMerklePath returns an empty path. There is no change to production code, no bug fix, and no security-relevant behavior change.

Lower-prioritydoc: Recommend latest Debian stable or Ubuntu LTSby MarcoFalke · fa9f29a4 · Nov 11, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · MarcoFalke

doc: Recommend latest Debian stable or Ubuntu LTS

45/100 · ThinMessage clarity
✓ 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 updates documentation. It changes the build instructions for Linux to recommend using the latest Debian stable or Ubuntu LTS release, and notes that older releases may need a newer compiler. There is no code change and no security fix or vulnerability introduced.

Lower-prioritydoc: Add GCC-12 min release notesby MarcoFalke · fa1711ee · Nov 11, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · MarcoFalke

doc: Add GCC-12 min release notes

45/100 · ThinMessage clarity
✓ 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 adds a release note document stating that the minimum supported GCC compiler version has been increased to 12.1. It contains no code changes and no security-related content.

Lower-priorityci: Enable experimental kernel stuff in G++-12 task (previous releases)by MarcoFalke · faa8be75 · Nov 11, 2025 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · MarcoFalke

ci: Enable experimental kernel stuff in G++-12 task (previous releases)

Base the task on --preset=dev-mode to ensure maximal coverage and add
the following:

bitcoin-chainstate (experimental) ... ON
libbitcoinkernel (experimental) ..... ON
kernel-test (experimental) .......... ON

Also, shorten the name, for a less cluttered web view.

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 15/100

This commit only changes Bitcoin Core's continuous integration (CI) testing configuration. It switches one CI job to use a development preset and turns on experimental kernel-related build options for testing purposes. There is no change to the actual Bitcoin software that users run, and no security issue is present.

Lower-prioritytest: Remove gccbug_90348 test caseby MarcoFalke · fabce97b · Nov 11, 2025 · 3 filesMessage 98 · StrongInformational 12Details
Commit message · MarcoFalke

test: Remove gccbug_90348 test case

The test case no longer detects this specific issue for GCC versions
12.1+, as explained in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90348 thread and in this
compiler-explorer playground:
https://godbolt.org/z/Y48osrjM8

So remove the test case and update the -fstack-reuse=none cmake
docstring with the underlying affected GCC versions, and the bug URL.

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 12/100

This commit removes an old automated test that checked whether the GCC compiler had a specific bug. The test no longer catches the bug in newer GCC versions, so the developers deleted it and updated a build-system comment to note which GCC versions are affected. There is no change to the actual Bitcoin Core program code or its security behavior.

Lower-prioritytest: Remove unused fs::create_directories testby MarcoFalke · fa3854e4 · Nov 11, 2025 · 1 fileMessage 98 · StrongInformational 15Details
Commit message · MarcoFalke

test: Remove unused fs::create_directories test

The test was added in commit ddb75c2e87a60ed24065bdf0c3bfabf4e058cef1.
After the create_directories wrapper removal, the test is redundant with
the unit test in the upstream stdlib. Also, there is a Bitcoin Core
functional test that covers this behavior in
test/functional/feature_dirsymlinks.py

So remove this unit test.

Finally, I could not find a real system that still ships a buggy stdlib
(v11.2) in their package manager. A stand-alone test is also available
in compiler-explorer under https://godbolt.org/z/aeMKraYrT.

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit simply deletes a unit test that is no longer needed. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.