BC
← All projectsBitcoin Core

Bitcoin Core

The Bitcoin network's reference node and wallet implementation.

BitcoinSupply chainNormal
Repository coverage

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

402security candidates730second-pass queue3152AI analyses
171commits · 30 days
325commits · 60 days
1193commits · 180 days
2758commits · 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.

73/100 average clarity
1453Strong · 80–100
1227Adequate · 60–79
715Thin · 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.
merge-script419112196589
Antoine Poinsot25422169
Ava Chow21874203071
MarcoFalke41923411074
fanquake24521230058
Lőrinc18121177081
Hennadii Stepanov25120221066
rkrux57957074
Sjors Provoost89889074
Sebastian Falbesoner33733073
David Gumberg55655072
Pieter Wuille95595066
Analysis record

Published AI watches

Last scanned 28 minutes ago

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

Merge bitcoin/bitcoin#36704: doc: fix docs and enable `-Wdocumentation-pedantic`

This commit only changes documentation comments and enables a stricter compiler warning for documentation style. It does not alter any executable code, so it cannot introduce or fix a security vulnerability on its own.

0afaa731by Hennadii Stepanov+79−7716 files
No security note in commit
Low 41 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36040: Wallet: Don't backdate locktime rbf

This change fixes a privacy leak in Bitcoin Core's wallet. When users used the 'bumpfee' feature to replace a transaction with a higher fee, the replacement could sometimes end up with an older 'locktime' than the original transaction. Thi…

Privacy/fingerprinting issue in wallet transaction creationReplacement transaction locktime can be lower than original transaction locktimeAnti-fee-sniping random backdating can produce identifiable on-chain pattern
004cfb21by Ava Chow+171−86 files
Vendor flagged security relevance
Moderate 62 AI analysisMessage 86 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36342: wallet: reject recipient amounts above MAX_MONEY

This patch fixes a bug in Bitcoin Core's wallet transaction creation where extremely large output amounts could cause an integer overflow or even crash the node. Before the fix, a user could craft a transaction whose outputs added up to mo…

Integer overflow in recipient amount summationNode abort via failed assertion in coin selectionPossible creation of a transaction with wrapped/invalid total output value
8c360f08by Ava Chow+25−42 files
Vendor flagged security relevance
Low 49 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36637: torcontrol: send -torpassword hex-encoded to avoid escaping bugs

This change fixes how Bitcoin Core sends your Tor control password to the Tor daemon. Previously, the password was wrapped in quotes and only double-quote characters were escaped. If a password contained a backslash, Tor would misinterpret…

Improper escaping of protocol string (QuotedString)Potential Tor control command boundary confusionAuthentication bypass/failure risk for Tor control
6090f0afby Ava Chow+42−62 files
Vendor flagged security relevance
Low 30 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36387: wallet: rpc: Deprecate `encryptwallet` RPC for encrypting existing wallets.

This commit marks the existing 'recortar el video' feature as deprecated. It doesn't remove it, but it now shows a warning and requires a special flag to use. The change is meant to protect users from accidentally losing access to their bi…

Deprecation of risky wallet-encryption workflowKnown data-retention risk: unencrypted key material may remain on disk after late encryptionKnown backup/restore risk: post-encryption keys are not covered by pre-encryption backups
f98888efby Ava Chow+165−8819 files
Vendor flagged security relevance
Informational 21 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36087: util: Add and use AssertUnreachable

This is a code-cleanup change in Bitcoin Core. It replaces many uses of `assert(false)` and similar 'this should never happen' markers with a new macro called `AssertUnreachable()`. The goal is to make the code clearer for developers and a…

No security-relevant functional change: process still aborts on unreachable pathsRefactor only: replaces one abort mechanism with another equivalent oneAdds a new lint rule to enforce the preferred macro going forward
3ee664eaby Ryan Ofsky+274−26484 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36888: test: construct `coinselection_tests` output declaratively

This is a minor cleanup inside a single test file. It changes how a fake transaction output is built in a unit test so the empty script is written explicitly rather than created implicitly by resizing a list. The actual test behavior and t…

a690300eby merge-script+4−31 file
No security note in commit
Low 35 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36890: Update secp256k1 subtree to latest master

This is a routine subtree update for the secp256k1 cryptographic library inside Bitcoin Core. It pulls in several upstream fixes, most of which are build-system cleanups, test improvements, and API hardening. The most user-visible changes …

Silent Payments API no longer aborts on empty input/output arrays; returns 0 per documented behaviorSilent Payments label-tweak overflow now rejected with ARG_CHECK instead of being silently handledecmult_const gains a _ge variant that clears intermediate Jacobian coordinates to reduce secret leakage
c3d1b4c0by merge-script+902−49134 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36867: test: remove legacy wallet leftovers from wallet functional tests

This commit only cleans up Bitcoin Core's own functional test suite. It removes unused multisig test code, fixes outdated docstrings, and drops a no-longer-needed command-line flag in test scripts. None of these changes affect the actual B…

c138ff92by merge-script+40−923 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36914: test: simplify wallet_basic and rpc_getblockfilter tests

This commit only cleans up two internal test scripts for the Bitcoin Core project. It replaces a manual network disconnect/reconnect pattern with a simpler way to create an unconnected block header, and removes a hard-coded number in favor…

079437ccby merge-script+6−112 files
No security note in commit
Informational 15 AI analysisMessage 82 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: Drop hard-coded magic 3

This is a tiny code cleanup in a Bitcoin Core test file. It replaces the hard-coded number 3 with the actual number of test nodes, making the test slightly easier to maintain. It does not change any real Bitcoin Core software behavior and …

1eeeee49by MarcoFalke+3−31 file
No security note in commit
Informational 20 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36864: rpc: deprecate iswatchonly field of getaddressinfo

This change hides an old, always-false field called 'iswatchonly' from the getaddressinfo API response unless the user explicitly asks for deprecated features. It is a routine cleanup, not a security fix, and does not change how wallets or…

66531447by merge-script+16−34 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36868: test: remove unused nodes and restarts from wallet tests

This commit only cleans up Bitcoin Core's own automated test suite. It removes unused test nodes and an unnecessary double restart in a few wallet-related test scripts. There is no change to the actual Bitcoin node software that users run,…

0fb50460by merge-script+24−324 files
No security note in commit
Moderate 68 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36894: net_processing: set fDisconnect instead of calling DisconnectNode

This change fixes a bug where Bitcoin Core would disconnect every peer sharing the same IP address when one peer misbehaved. The problem is especially bad for users connecting through Tor, because all Tor traffic exits through a small set …

Denial of service via shared IP disconnectTor exit-node IP collision exploited to disconnect honest peersPeer-to-peer network isolation of inbound connections
6832a273by merge-script+5−53 files
Vendor flagged security relevance
Moderate 62 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

net_processing: set fDisconnect instead of calling DisconnectNode

This commit fixes a bug where Bitcoin Core would disconnect every peer sharing the same IP address when one of them misbehaved. Because Tor exit nodes share a single IP address among many users, a malicious user could deliberately misbehav…

Denial-of-service via shared IP disconnectTor exit-node IP collision exploited to disconnect honest peersPeer-disconnection logic changed from subnet match to single-node flag
d63068c5by Eugene Siegel+5−53 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36875: scripted-diff: Drop `IWYU pragma: keep` from build config includes

This change is purely a code-cleanup and linting improvement. It removes repetitive 'IWYU pragma: keep' comments from build-config header includes and instead marks the generated config header itself with a single 'always_keep' pragma. The…

1fbb5253by merge-script+67−7265 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36451: refactor: Use NotNull for CreateNewBlock and pimpls

This is a code cleanup change that makes the type system express 'this pointer can never be null' for several internal objects and for block templates. It removes redundant null checks and adds helper functions to create such non-null poin…

No security-relevant bug is patchedChange is purely a type-system refactorRemoves dead null-check error paths rather than adding safety checks
8130b3b8by Ryan Ofsky+78−5230 files
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36848: test: drop flaky "server too slow" check from interface_http.py

This commit only changes a test file to make a timing check less strict. It removes an upper-bound timing assertion that was causing false test failures on slow CI machines. There is no change to Bitcoin Core's actual network or wallet cod…

e1a27bbbby merge-script+6−61 file
No security note in commit
Informational 20 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36488: rpc: wallet: Schedule mixed-case confTarget option deprecation

This commit is a routine cleanup, not a security fix. It removes support for an old, confusingly-named option ('confTarget') in two Bitcoin wallet commands (bumpfee and psbtbumpfee), leaving only the clearer 'conf_target' name unless the u…

8b0b5775by merge-script+24−34 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36408: test: allow 3 bytes of fee overestimate in assert_fee_amount

This is a tiny change to a Bitcoin Core test helper that makes fee-checking tests slightly more tolerant. It is not a security fix and does not affect production wallet code or consensus rules. It simply reduces how often an extremely rare…

dd9d016bby merge-script+3−21 file
No security note in 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-priorityrefactor: Annotate `MakeAndPushFeature` with `[[maybe_unused]]`by Hennadii Stepanov · 0238aebf · Aug 3, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · Hennadii Stepanov

refactor: Annotate `MakeAndPushFeature` with `[[maybe_unused]]`

This is a follow-up to bitcoin/bitcoin#35221. The `MakeAndPushFeature`
member function template has no callers yet, which triggers
`-Wunused-template` now that Clang 23 enables it as part of `-Wall`.

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

This is a one-line compiler warning fix. A developer added a marker telling the compiler that a newly-added helper function may not be used yet, so Clang 23 stops complaining about it. There is no change to program behavior, no bug fix, and no security relevance.

Lower-priorityguix: move python-minimal to GUI buildby fanquake · b75eb938 · Aug 3, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · fanquake

guix: move python-minimal to GUI build

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a build-system housekeeping change. It moves the Python package dependency from the non-GUI build manifest to the GUI build manifest in Bitcoin Core's Guix reproducible-build setup. There is no indication this fixes or introduces a security vulnerability; it simply makes sure the right build environment includes Python only when needed for GUI packaging.

Lower-priorityguix: remove -Werror=devby fanquake · 101400b2 · Aug 3, 2026 · 3 filesMessage 71 · AdequateInformational 15Details
Commit message · fanquake

guix: remove -Werror=dev

Otherwise the build will fail with warnings about missing Python (removed
in the next commit). However the non-gui build does not need Python.

Note that #25573 contains the same change, because the use of -static-pie
causes warnings when combined with our/CMakes own PIE handling.

71/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit removes a strict compiler/build flag (-Werror=dev) from Bitcoin Core's Guix build scripts. The flag previously turned CMake developer warnings into fatal errors. It was removed because an upcoming change (removing Python from non-GUI builds) would trigger a harmless warning. This is a build-system maintenance change, not a security fix.

AI review queuedci, iwyu: Enforce warning-free `src/common`by Hennadii Stepanov · 50145f62 · Aug 3, 2026 · 22 filesMessage 68 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci, iwyu: Enforce warning-free `src/common`

Fix all IWYU warnings in `src/common` and treat them as errors in CI.

Additionally, ensure that our drop-in header replacements are used
instead of system headers:
- `<util/check.h>` instead of `<cassert>`
- `<util/time.h>` instead of `<chrono>`

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a routine code cleanup commit. It adjusts which C++ header files are included in the `src/common` part of Bitcoin Core so that an automated tool called Include What You Use (IWYU) reports no warnings. It also tells the continuous integration system to treat any future IWYU warnings in this area as errors. There is no change to program behavior, no bug fix, and no security-relevant change.

Lower-prioritylint: document CI lief version requirementby fanquake · 8221d714 · Aug 3, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · fanquake

lint: document CI lief version requirement

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 one-line comment to a requirements file used by the continuous integration (CI) linting system, noting that the pinned lief version should match the version used in Guix. It does not change any code, dependency version, or configuration that affects the Bitcoin Core software users run.

Lower-prioritylint: re-add guix scripts to mypy lintingby fanquake · 594a02c3 · Aug 3, 2026 · 3 filesMessage 81 · StrongInformational 15Details
Commit message · fanquake

lint: re-add guix scripts to mypy linting

These were no-longer being linted after #32458.

suppress `[union-attr]` warning. i.e:
```bash
contrib/guix/symbol-check.py:309: error: Item "None" of "lief.PE.Binary | lief.ELF.Binary | lief.MachO.Binary | lief.COFF.Binary | None" has no attribute "format" [union-attr]
contrib/guix/security-check.py:284: error: Item "lief.COFF.Binary" of "lief.PE.Binary | lief.ELF.Binary | lief.MachO.Binary | lief.COFF.Binary | None" has no attribute "abstract" [union-attr]
```

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
AI analysis · Informational 15/100

This commit is a routine linting fix. It re-adds some Guix build helper scripts to the Python type-checker (mypy) configuration and adds two comment-only annotations to suppress false-positive type warnings. There is no change to Bitcoin Core's runtime behavior, consensus rules, wallet handling, or network code.

Lower-prioritydoc: Add doc/release-notes-35836.mdby MarcoFalke · ddddffda · Aug 3, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · MarcoFalke

doc: Add doc/release-notes-35836.md

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

This commit only adds a release note documenting a prior change: the `fundrawtransaction` RPC command no longer silently accepts a boolean value in its second argument and will now report an error instead. It is a documentation-only change with no code modifications, so it does not by itself introduce or fix a security vulnerability. The prior behavior it describes was a silent no-op fallback, which could be considered a minor API usability issue but not a direct security flaw.

Lower-prioritytest: give each ValidateInputsStandardness case its own scopeby JP · 756afe14 · Aug 2, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · JP

test: give each ValidateInputsStandardness case its own scope

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
defensive validation
AI analysis · Informational 15/100

This commit only restructures a single test file by wrapping each test case in its own code block (scope). It does not change any production code, network rules, or test behavior. There is no security impact.

Lower-prioritytest: fix wrong transaction in GetP2SHSigOpCount assertionby JP · 5559fa46 · Aug 1, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · JP

test: fix wrong transaction in GetP2SHSigOpCount assertion

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
AI analysis · Informational 15/100

This is a one-line fix inside a Bitcoin Core unit test. The test was checking the P2SH signature-operation count for the wrong transaction object: it used a transaction that still had its scriptSig, instead of the version where the scriptSig was intentionally removed. The assertion value was also wrong (20 instead of 0). The change only affects test code, not production consensus or networking logic, so it cannot be exploited by users or attackers.

Lower-priorityfuzz: Rework rpc fuzz targetby MarcoFalke · fa895bb7 · Aug 1, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · MarcoFalke

fuzz: Rework rpc fuzz target

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

This commit rewrites an internal fuzz-testing harness for Bitcoin Core's RPC interface. It changes how fake RPC arguments are generated so the test can feed more realistic JSON data (numbers, booleans, nested arrays/objects, raw JSON) directly into RPC handlers instead of converting everything from strings first. There is no change to the live Bitcoin node or wallet code that users run; only the test code is modified.

Lower-priorityp2p: reject empty getblocktxn requestsby furszy · 28641fd1 · Jul 31, 2026 · 2 filesMessage 68 · AdequateLow 31Details
Commit message · furszy

p2p: reject empty getblocktxn requests

A getblocktxn msg is only needed when at least one tx is
missing from a compact block. If no txs are missing, the
block can be reconstructed without sending the request.

This avoids reading the requested block from disk
unnecessarily and also alerts the peer operator about
their node's buggy behavior.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Low 31/100

This change makes Bitcoin Core disconnect any peer that sends a 'getblocktxn' message asking for zero transactions. Such a request is pointless because if no transactions are missing, the receiver already has everything it needs to reconstruct the block. The patch prevents the node from wastefully reading a block from disk and helps identify misbehaving or buggy peers. It is a hardening fix rather than a clear-cut exploit patch, and the commit message frames it as performance/robustness, not a security vulnerability.

Lower-priorityfuzz: cover the mempool interface for transaction announcementby Antoine Poinsot · dd256100 · Jul 31, 2026 · 1 fileMessage 75 · AdequateInformational 15Details
Commit message · Antoine Poinsot

fuzz: cover the mempool interface for transaction announcement

This adds coverage for the recently-added ExtractBestByMiningScoreWithTopology method.

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidence
AI analysis · Informational 15/100

This commit only adds new fuzz-test code for Bitcoin Core's mempool. It does not change any production networking, consensus, or wallet code, so it cannot directly affect live Bitcoin nodes or users' funds.

Lower-priorityp2p: reject filtered block inv early when bloom is disabledby furszy · 9871fb72 · Jul 31, 2026 · 2 filesMessage 85 · StrongLow 28Details
Commit message · furszy

p2p: reject filtered block inv early when bloom is disabled

A peer should not request filtered blocks from a node that
does not advertise NODE_BLOOM. Perform this check before
looking up the block to avoid an unnecessary disk read.

Note: currently, the request is ignored only after the
block has been read from disk, in the bloom filter
existence check.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI analysis · Low 28/100

This change makes Bitcoin Core disconnect a peer earlier when it asks for a 'filtered block' from a node that does not advertise bloom-filter support. Previously, the node would read the block from disk first and only then ignore the request. Now it rejects the request before doing any disk read. This is mainly a small performance/hardening improvement rather than a serious security fix.

Lower-priorityrefactor: split p2p_getdata.py in sub-casesby furszy · aaf94120 · Jul 31, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · furszy

refactor: split p2p_getdata.py in sub-cases

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a simple code cleanup in a test file. It takes an existing test and moves it into a separate helper method, then calls that method from the main test runner. There is no change to Bitcoin Core's actual network code, no bug fix, and no security-related behavior change.

Lower-priorityqa: Enable `interface_gui.py` on macOSby Hennadii Stepanov · 45f5609f · Jul 30, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

qa: Enable `interface_gui.py` on macOS

This is a follow-up to bitcoin/bitcoin#35551.

68/100 · AdequateMessage clarity
✓ 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 re-enables a GUI test on macOS by changing the visual style used during automated testing. It is a quality-assurance/testing change, not a security fix. There is no indication it addresses a vulnerability or changes how real users run Bitcoin Core.

AI review queuedwallet: Remove meaningless bool fallback in FundTransactionby MarcoFalke · fa7fe798 · Jul 30, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · MarcoFalke

wallet: Remove meaningless bool fallback in FundTransaction

The fallback was added in commit
af4fe7fd126eff2dd1942276ea91c8ab9dd717c6, more than a decade ago.

However, it is irrelevant, given that watch-only wallet is not a concept
anymore after commit 1337c72198a7d32935431d64e9e58c12f9003abc.

So remove the code.

Can be reviewed with the --ignore-all-space option.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit removes an old backward-compatibility feature in Bitcoin Core's wallet RPC command `fundrawtransaction`. Previously, callers could pass a plain `true` or `false` as the second argument, which was silently ignored. Now, passing a boolean triggers a clear JSON type error, and callers must use the normal options object. This is a cleanup change, not a security fix, but it makes the API stricter and easier to reason about.

AI review queuedguix: consolidate config flagsby fanquake · 683ae4c5 · Jul 29, 2026 · 6 filesMessage 35 · OpaqueInformational 15Details
Commit message · fanquake

guix: consolidate config flags

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a housekeeping change to Bitcoin Core's Guix build scripts. It only reorders and consolidates CMake configuration flags, and adds a couple of disabled test/build options. There is no change to the actual Bitcoin software code, no bug fix, and no security-related behavior change.

Lower-priorityguix: turn linux/win linker warnings into errorsby fanquake · b12a70f3 · Jul 29, 2026 · 3 filesMessage 98 · StrongInformational 20Details
Commit message · fanquake

guix: turn linux/win linker warnings into errors

Can do this now that the GUI has been split out.

riscv64-linux-gnu failus due to
https://github.com/boostorg/test/issues/345:
```bash
[102%] Linking CXX executable ../../bin/test_bitcoin
/gnu/store/r03804zpq5i6wsalx0yaqrr5jb7pqrmv-binutils-cross-riscv64-linux-gnu-2.46.0/bin/riscv64-linux-gnu-ld: CMakeFiles/test_bitcoin.dir/main.cpp.o: in function `boost::fpe::disable(unsigned int)':
/bitcoin/depends/riscv64-linux-gnu/boost/include/boost/test/impl/execution_monitor.ipp:1538:(.text+0x9dc8): warning: fedisableexcept is not implemented and will always fail
/gnu/store/r03804zpq5i6wsalx0yaqrr5jb7pqrmv-binutils-cross-riscv64-linux-gnu-2.46.0/bin/riscv64-linux-gnu-ld: CMakeFiles/test_bitcoin.dir/main.cpp.o: in function `boost::fpe::enable(unsigned int)':
/bitcoin/depends/riscv64-linux-gnu/boost/include/boost/test/impl/execution_monitor.ipp:1502:(.text+0x9d76): warning: feenableexcept is not implemented and will always fail
collect2: error: ld returned 1 exit status
```

Darwin could be done after something like
https://github.com/bitcoin/bitcoin/pull/35756.

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 20/100

This commit changes Bitcoin Core's build scripts so that linker warnings are treated as fatal errors during Linux and Windows release builds. It is a hardening of the build process, not a fix for a user-facing security bug. The change makes the build fail if the linker emits warnings, which helps catch build-time problems early. It is not something an attacker can directly exploit.

Lower-priorityguix: consolidate mingw-w64 toolchain setupby fanquake · 288f76ed · Jul 29, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · fanquake

guix: consolidate mingw-w64 toolchain setup

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a straightforward cleanup of Bitcoin Core's Windows build scripts. It moves duplicated toolchain setup code into a shared helper function, with no functional changes visible in the diff. There is no indication this affects runtime security, user funds, or network behavior.

Lower-priorityguix: consolidate gcc toolchain setupby fanquake · 665f11d0 · Jul 29, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · fanquake

guix: consolidate gcc toolchain setup

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine cleanup of the Bitcoin Core build scripts used for Guix (a reproducible build system). It moves duplicated GCC toolchain setup code from two separate files into a single shared function in setup.sh, with no functional changes visible in the diff. There is no indication this affects the security of Bitcoin Core itself or introduces a vulnerability.

Lower-priorityguix: consolidate LLVM toolchain setupby fanquake · cc9b0f22 · Jul 29, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · fanquake

guix: consolidate LLVM toolchain setup

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a straightforward cleanup of Bitcoin Core's macOS build scripts. It moves repeated LLVM/clang toolchain setup code from two separate scripts into a single shared function, with no change to the actual commands or build behavior. There is no security issue visible in the diff.

AI review queuedgui: Menu action for exporting a watchonly walletby Ava Chow · cb51f97f · Jul 28, 2026 · 4 filesMessage 45 · ThinInformational 17Details
Commit message · Ava Chow

gui: Menu action for exporting a watchonly wallet

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit adds a new menu item in the Bitcoin Core desktop wallet that lets users export a 'watch-only' copy of their wallet. A watch-only wallet can see transactions and balances but cannot spend funds. The change only wires up an existing export function to the graphical user interface; it does not appear to fix a bug or introduce a security vulnerability.

Lower-prioritydoc: Release note for export watchonly wallet gui actionby Ava Chow · 6573196e · Jul 28, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Ava Chow

doc: Release note for export watchonly wallet gui action

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 adds a release note describing a new graphical menu option in the Bitcoin Core wallet. It documents a feature that lets users create a watch-only wallet file from an existing descriptor wallet, matching an existing RPC command. There is no code change and no security issue.

AI review queuedadd release notesby Pol Espinasa · 4cea5957 · Jul 28, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Pol Espinasa

add release notes

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a short release note describing a new wallet-migration user-interface option. There is no code change, no bug fix, and no security-related content in the diff.

AI review queuedgui: Adds option to not load the wallet after migrationby Pol Espinasa · 492a715d · Jul 28, 2026 · 4 filesMessage 50 · ThinInformational 19Details
Commit message · Pol Espinasa

gui: Adds option to not load the wallet after migration

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit adds a user-facing checkbox in the Bitcoin Core desktop wallet that lets someone choose whether to automatically load a wallet after migrating it from an older format. Previously the wallet was always loaded. The change is a usability improvement, not a security fix, and does not introduce any obvious vulnerability.