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
172commits · 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 17 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.

Security candidateMerge bitcoin/bitcoin#36676: cli: respect -rpcclienttimeout even when sendingby merge-script · 0f27bed5 · Oct 28, 2026 · 1 fileMessage 91 · StrongLow 34Details
Commit message · merge-script

Merge bitcoin/bitcoin#36676: cli: respect -rpcclienttimeout even when sending

e5d9a7e04b50c723aeb65984e5048ffd098f6737 cli: fail to send a request when the socket does not become writable (Antoine Poinsot)

Pull request description:

The move away from libevent introduced a small regression in this regard. In #36299, we switched the timeout to apply per socket wait, but continued on to another socket wait in case of timeout, instead of returning. See commit message for details.

In general, we also shouldn't ignore `Sock::Wait`'s errors and timeouts by silently retrying forever.

Fix these issues by returning instead when `Sock::Wait` times out or returns an error. ~~Tentative bot functional test for this in second commit that appears to be robust enough.~~

ACKs for top commit:
jpk68:
ACK e5d9a7e04b50c723aeb65984e5048ffd098f6737
l0rinc:
tested ACK e5d9a7e04b50c723aeb65984e5048ffd098f6737
pinheadmz:
ACK e5d9a7e04b50c723aeb65984e5048ffd098f6737

Tree-SHA512: f662e911fbba2d2a97e9d9ba559e8cfd8fd163a08ba8ff812f969c9ea42f0d24d5e013a558a2b488c346f9d5611a2faba0e2ade780ba9b290124fb441ac771ff

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Low 34/100

This patch fixes a bug in bitcoin-cli (the command-line tool used to talk to a Bitcoin node) where the -rpcclienttimeout setting was not being respected while sending a request. Previously, if the network socket was not ready to send data, the tool would wait, time out, then silently try again in an infinite loop. Now it correctly gives up and reports failure. This is primarily a reliability and user-expectation bug rather than a direct theft-of-funds vulnerability.

Lower-priorityMerge bitcoin/bitcoin#36098: fuzz: add corpus reachability checksby merge-script · b1172114 · Oct 28, 2026 · 14 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36098: fuzz: add corpus reachability checks

b3e4cdcf020c6be28e929e6d8b2d29dc372008df fuzz: track complete v1 transport messages (Hao Xu)
454f917d020ccdfca7793ad23c131cbcfba9e1f2 fuzz: track compact block reachability (Hao Xu)
96ab84c13e9a8053ceb9e26aff507f4a47dfd30d fuzz: track valid transaction packages (Hao Xu)
bb09525fee68d95aed68076f7148f6a474dc042c fuzz: track valid ephemeral packages (Hao Xu)
84ec1276cbeeb65a9e150d7927973bd518f00c34 fuzz: track tx_pool acceptance (Hao Xu)
e2ba005dade7e0558692bd7c8a956e94136761be fuzz: track tx_pool_standard acceptance (Hao Xu)
0302981df8366f70c2d69c8754a3925e8356783c fuzz: track successful UTXO snapshot activation (Hao Xu)
56a89c4e1d88ad34016d4ac8fe7ccfd51c9972ad fuzz: track successful mempool loads (Hao Xu)
1a1ef162bf89e649bbf4c94474ff4433379e03de fuzz: track successful block policy estimator reads (Hao Xu)
5e8da56fbef21cc1bae4621efdcbf4d594425cd3 fuzz: track p2p handshake reachability (Hao Xu)
193101ba20121149dba00474e753868e651dd423 fuzz: track process_message reachability (Hao Xu)
9cc79514d181c0dee3d51a5aba0eac11b45e6d83 fuzz: track process_messages reachability (Hao Xu)
bcf97a3cc487a082231cae9d7a0fa42e21ec2b8e fuzz: add reachability goal tracking (Hao Xu)

Pull request description:

This is a follow-up to #35482.

Add `ReachabilityGoal()` to aggregate whether selected conditions are reached across all inputs processed by a fuzz target. Goals are identified by source location and reported at shutdown. Setting `FUZZ_ENFORCE_REACHABILITY=1` makes the process fail if any registered goal was not reached.

Add goals for selected high-value paths, including IBD and non-IBD message processing, completed P2P handshakes and transport messages, successful estimator/mempool/snapshot operations, transaction and package acceptance, and compact block reconstruction.

### Testing

Built the fuzz binary and replayed the current qa-assets corpora for all instrumented targets with `FUZZ_ENFORCE_REACHABILITY=1`.

ACKs for top commit:
nervana21:
tACK b3e4cdcf020c6be28e929e6d8b2d29dc372008df
Crypt-iQ:
crACK b3e4cdcf020c6be28e929e6d8b2d29dc372008df
maflcko:
review ACK b3e4cdcf020c6be28e929e6d8b2d29dc372008df 🗨

Tree-SHA512: cefd313c15347c768f5c017c24c7dc2004b9bb44ff15106658f48c561dd3b59ae0350a90883594b736e90f791980492e017f89c626e83248ad72e64e06a72dcc

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
fuzzing or regression evidencemerge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36684: test: check AddToBlockIndex keeps first-seen header on equal workby merge-script · 4d99cc5c · Oct 28, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36684: test: check AddToBlockIndex keeps first-seen header on equal work

701545e5b5750aa24cfc87b2db93f4f81accb67c test: check AddToBlockIndex keeps first-seen header on equal work (Bruno Garcia)

Pull request description:

`BlockManager::AddToBlockIndex` only replaces best_header when the new header has strictly more chain work. Add a unit test that adds two sibling headers with equal work and checks that best_header keeps pointing to the first one.

Kills the following mutant (https://mutanthub.space/mutants/3806):
```diff
diff --git a/src/node/blockstorage.cpp b/src/node/blockstorage.cpp
index 2ee13aa417..aad52d6d61 100644
--- a/src/node/blockstorage.cpp
+++ b/src/node/blockstorage.cpp
@@ -246,7 +246,7 @@ CBlockIndex* BlockManager::AddToBlockIndex(const CBlockHeader& block, CBlockInde
pindexNew->nTimeMax = (pindexNew->pprev ? std::max(pindexNew->pprev->nTimeMax, pindexNew->nTime) : pindexNew->nTime);
pindexNew->nChainWork = (pindexNew->pprev ? pindexNew->pprev->nChainWork : 0) + GetBlockProof(*pindexNew);
pindexNew->RaiseValidity(BLOCK_VALID_TREE);
- if (best_header == nullptr || best_header->nChainWork < pindexNew->nChainWork) {
+ if (best_header == nullptr || best_header->nChainWork <= pindexNew->nChainWork) {
best_header = pindexNew;
}
```

ACKs for top commit:
maflcko:
lgtm ACK 701545e5b5750aa24cfc87b2db93f4f81accb67c
KY-U:
tACK https://github.com/bitcoin/bitcoin/commit/701545e5b5750aa24cfc87b2db93f4f81accb67c
ViniciusCestarii:
ACK 701545e5b5750aa24cfc87b2db93f4f81accb67c

Tree-SHA512: f170592615e85bb55827c0db4118adb4fe87e9edfb73112d420539d95541643939c6ef71b3304b58d5e917926e4b528b007585bcad163ae6109435f3a51f412b

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36683: doc: fix `v32.1` release notes archiveby merge-script · c3ca59ba · Oct 28, 2026 · 4 filesMessage 81 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36683: doc: fix `v32.1` release notes archive

41952c4730ef09fc335167c330d4bf82d38639bc doc: archive release notes for v29.5 (fanquake)
24d0af054a3ea09951088300f1606db769622595 doc: archive release notes for v30.4 (fanquake)
c8ff8e8eaddfefacd96ec52e067d645969723eab doc: archive release notes for v31.2 (fanquake)
1a45b913f399e513562b8e3d047bf37bca9745ee doc: archive v32.1 release notes (fanquake)

Pull request description:

Add `v31.2`, `v30.4`, `v29.5`.
Also adds #36678 to the `v32.1` archive.

ACKs for top commit:
instagibbs:
clACK 41952c4730ef09fc335167c330d4bf82d38639bc
willcl-ark:
ACK 41952c4730ef09fc335167c330d4bf82d38639bc

Tree-SHA512: 20cac436aefdcf9f3a3fb4be9ebb215db3768063a4e90e1495150ea8ac161cafe251db0d9e09c1428bfa4338c9867323b76cb0aa206faf582848c04a9251f065

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Security candidateMerge bitcoin/bitcoin#36678: doc: adapt release notes template to security disclosure policy updateby merge-script · f8c9f2b5 · Oct 28, 2026 · 1 fileMessage 86 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36678: doc: adapt release notes template to security disclosure policy update

ad68edfb92fba7603607a25d21de72c9f3b26fec doc: link to security disclosure policy in release notes template (Antoine Poinsot)
ae658dd8061b7b653cadaf5101fce1b9b2869ce3 doc: adapt release notes template to security disclosure policy update (Antoine Poinsot)

Pull request description:

Following the update to our security disclosure policy in https://github.com/bitcoin-core/bitcoincore.org/pull/1281, adapt the text related to vulnerability disclosures in the release notes empty template.

ACKs for top commit:
instagibbs:
reACK ad68edfb92fba7603607a25d21de72c9f3b26fec

Tree-SHA512: 75237d8c879a839568eda6100282fb76dbe43b94e9740b94850af70558dae9f451f7d60ca7aa5e8bebb42aa7f605376a563d4eb7440bf91a5a0446b8fadb7f63

86/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
explicit security languagedocumentation-only discountmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a documentation-only change to the empty release notes template. It updates the wording that describes how Bitcoin Core discloses security vulnerabilities, linking to the project's security policy. No code, no bug fix, no vulnerability is present in this commit.

Lower-prioritydoc: link to security disclosure policy in release notes templateby Antoine Poinsot · ad68edfb · Oct 28, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Antoine Poinsot

doc: link to security disclosure policy in release notes template

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydoc: archive release notes for v29.5by fanquake · 41952c47 · Oct 28, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · fanquake

doc: archive release notes for v29.5

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydoc: archive release notes for v30.4by fanquake · 24d0af05 · Oct 28, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · fanquake

doc: archive release notes for v30.4

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydoc: archive release notes for v31.2by fanquake · c8ff8e8e · Oct 28, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · fanquake

doc: archive release notes for v31.2

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydoc: archive v32.1 release notesby fanquake · 1a45b913 · Oct 28, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · fanquake

doc: archive v32.1 release notes

By adjusting the v32.0 archive.

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritydoc: adapt release notes template to security disclosure policy updateby Antoine Poinsot · ae658dd8 · Oct 27, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Antoine Poinsot

doc: adapt release notes template to security disclosure policy update

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
Security candidateMerge bitcoin/bitcoin#36529: test: measure rpcwaittimeout floor with monotonic timeby merge-script · aa76bd26 · Oct 27, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36529: test: measure rpcwaittimeout floor with monotonic time

dc27539d42bbfc04705d9ae1ea00cf70b046d8fa test: measure rpcwaittimeout floor with monotonic time (nervana21)

Pull request description:

Previously, `interface_bitcoin_cli.py` measured the `-rpcwaittimeout` wait floor with `time.time()`. `bitcoin-cli` arms that deadline with `std::chrono::steady_clock`, so a CI wall-clock step backward can make the elapsed time look short and cause the assert to fail.

Fix this by using `time.monotonic()` instead and using `-rpcwaittimeout=1`. The log line also now says "at least" so it matches the floor assert.

h/t ViniciusCestarii for suggesting `time.monotonic()` here.

ACKs for top commit:
maflcko:
lgtm ACK dc27539d42bbfc04705d9ae1ea00cf70b046d8fa
ViniciusCestarii:
ACK dc27539d42bbfc04705d9ae1ea00cf70b046d8fa

Tree-SHA512: 1213f786d21ce2fa0eb8f08a7c3c381a65dbfec3c4b534516b545e90ca661b0cda84de1482fb41cfe0e53b2a4dabc587f42701e8686b27455591859290c3a855

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit fixes a flaky automated test in Bitcoin Core. The test checks that bitcoin-cli waits at least the requested timeout before giving up when it cannot connect to the server. Previously the test used wall-clock time (time.time()), which can jump backwards if the computer's clock is adjusted, causing the test to fail even though nothing was wrong. The fix switches to monotonic time (time.monotonic()), which only moves forward, and shortens the timeout from 5 seconds to 1 second. There is no change to the actual Bitcoin Core software that users run, only to the test suite.

AI review queuedMerge bitcoin/bitcoin#36588: refactor: Enable more tidy bugprone checksby merge-script · 23288073 · Oct 27, 2026 · 5 filesMessage 100 · StrongInformational 18Details
Commit message · merge-script

Merge bitcoin/bitcoin#36588: refactor: Enable more tidy bugprone checks

facb2209061ce40f558d9e1feaaf8e9a627117e5 refactor: Enable bugprone-return-const-ref-from-parameter to find missing LIFETIMEBOUND annotations (MarcoFalke)
fa211896e55bba672646c9f7bcf7b18c408b8ced refactor: Enable some useful bugprone checks, which are clean right now (MarcoFalke)
faa76b44c6e4efa08179919e0c0cf68d32fe0b0e refactor: Enable bugprone-inaccurate-erase (MarcoFalke)
fafce023b3d006d1cc36369eb71e434a9147b56e refactor: Enable bugprone-string-literal-with-embedded-nul (MarcoFalke)
fab3062590eab577e0b3ab8b93d642c7026c0775 refactor: Enable bugprone-unused-raii (MarcoFalke)

Pull request description:

Enable some bugprone clang-tidy checks, which seem useful.

Apart from a test-only bug, they didn't find anything severe, but I think it still makes sense to enable them, so that it is easier to read the resulting code. Also, it is trivial to disable them, if they turn out annoying.

ACKs for top commit:
stickies-v:
re-ACK facb2209061ce40f558d9e1feaaf8e9a627117e5
hebasto:
ACK facb2209061ce40f558d9e1feaaf8e9a627117e5.

Tree-SHA512: 660e06ad581c662eeb23d35c729ca6f9dc5cae31f30b212cf543f1e4d59147f4ccf467fbeb4dbfbbbe47ed2acb4abac543a558a98dcf1ef1d4445847100846b2

100/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit turns on additional automated code-quality checks in Bitcoin Core's clang-tidy configuration and makes a handful of small, matching cleanups. It is a refactoring/tooling change, not a fix for an active security bug. The only runtime code changes are switching one Qt container erase call to a safer modern form and adding a lifetime annotation to a D-Bus operator. The rest are test-only adjustments to satisfy new static-analysis rules.

Security candidateMerge bitcoin-core/gui#955: qt: filter addhdkey from RPC console historyby Hennadii Stepanov · 631b0065 · Oct 27, 2026 · 2 filesMessage 96 · StrongModerate 51Details
Commit message · Hennadii Stepanov

Merge bitcoin-core/gui#955: qt: filter addhdkey from RPC console history

31467d59a5a8e6721af1dc5d6592fad31339bcb9 qt: filter addhdkey from RPC console history (Mateusz Klatt)

Pull request description:

Filters `addhdkey` arguments from RPC console history, consistent with other RPCs that handle private key material.

This prevents extended private keys from being retained in history. It also covers the mnemonic and passphrase inputs proposed in bitcoin/bitcoin#35857.

Adds a parser test verifying that the arguments are redacted.

## Motivation

`addhdkey` accepts a BIP 32 extended private key, but its arguments are currently retained in RPC console history, unlike other RPCs that handle private key material.

The same filter would also protect the mnemonic and passphrase inputs proposed in bitcoin/bitcoin#35857.

## Changes

- Add `addhdkey` to the RPC console sensitive-command filter.
- Add a parser test verifying that its arguments are redacted as `addhdkey(…)`.

## Tests

- `./build_gui/bin/test_bitcoin-qt` — all tests passed, including `RPCNestedTests::rpcNestedTests()`.

ACKs for top commit:
jpk68:
ACK 31467d59a5a8e6721af1dc5d6592fad31339bcb9
hebasto:
ACK 31467d59a5a8e6721af1dc5d6592fad31339bcb9, I have reviewed the code and it looks OK.

Tree-SHA512: e837f2ab0c3073266922fee8a72ab450830a4aa6193996ab7e72222738c8755bc3f073d155fddb827a5271821c3ac11e51053da422e6f09cac91b438d97b5f5e

96/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialaccess controlmerge-commit duplicate discount
AI analysis · Moderate 51/100

This update stops the Bitcoin Core graphical wallet from remembering the command-line arguments of a sensitive command called addhdkey. Previously, if a user typed addhdkey followed by their extended private key or recovery phrase into the built-in RPC console, that secret material would be saved in the console's command history. Other secret-handling commands were already filtered, but addhdkey was missed. The fix adds it to the same filter and includes a test that confirms the arguments are replaced with a redacted placeholder.

Security candidateMerge bitcoin/bitcoin#36674: Update leveldb subtree to latest masterby Hennadii Stepanov · 15ba4229 · Oct 27, 2026 · 1 fileMessage 81 · StrongInformational 23Details
Commit message · Hennadii Stepanov

Merge bitcoin/bitcoin#36674: Update leveldb subtree to latest master

e1dfb04fcf21649097b4c2d5cc651f83b9531fd3 Squashed 'src/leveldb/' changes from 53a1914e00..24a446f834 (fanquake)

Pull request description:

Includes:
* https://github.com/bitcoin-core/leveldb-subtree/pull/66

Used in #36623.

ACKs for top commit:
hodlinator:
ACK 8d3d929e4d77532faf25dd0ae3bcfa666e581e89
hebasto:
ACK 8d3d929e4d77532faf25dd0ae3bcfa666e581e89

Tree-SHA512: 829791aaf651787f2b7109ff51704971e30832738337a71705d6ff81c2d99037e2ba1670b3dad25077e3d14e10609a36206521fd773839189cef3f92a0e166ae

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Informational 23/100

This commit removes an unreachable 'return false;' statement from a LevelDB log-reading function. In some build configurations, compilers warn about code that can never execute; removing it silences those warnings and makes the function's actual control flow clearer. The change itself does not alter program behavior in normal operation.

Lower-prioritySquashed 'src/leveldb/' changes from 53a1914e00..24a446f834by fanquake · e1dfb04f · Oct 27, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · fanquake

Squashed 'src/leveldb/' changes from 53a1914e00..24a446f834

24a446f834 Merge bitcoin-core/leveldb-subtree#66: refactor: remove unreachable code
3c8ff755a3 refactor: remove unreachable code

git-subtree-dir: src/leveldb
git-subtree-split: 24a446f83477e8888b3ac92e7cf8d8fbf5f4b0c1

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityUpdate leveldb subtree to lastest masterby fanquake · 8d3d929e · Oct 27, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · fanquake

Update leveldb subtree to lastest master

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge bitcoin/bitcoin#36669: refactor: store positions as a 64 bits integer in flatfilesby merge-script · 2b5b6fe2 · Oct 26, 2026 · 9 filesMessage 100 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36669: refactor: store positions as a 64 bits integer in flatfiles

48092a9042d8fcfd6bb7ae5911a1d53b8746d546 flatfile: use 64-bit file positioning syscalls in Windows (Antoine Poinsot)
17556cb1f52fcbc807f65245101f72e8ec1573d8 flatfile: store position as a 64 bits integer (Antoine Poinsot)

Pull request description:

That field is the last 32-bit in flat files management that is only bounded indirectly by callers' usage (unlike the file number for instance). In the spirit of the ongoing effort to avoid unnecessarily using 32 bits integers or platform specific types (for instance #24214, #33724, #34109, #35097, #35616), i was scanning for fields it could be prudent to promote to prevent any possible future misuse. This one is a good candidate because it does not change on-disk representation, since we serialize positions as varints.

ACKs for top commit:
sedited:
tACK 48092a9042d8fcfd6bb7ae5911a1d53b8746d546
hebasto:
ACK 48092a9042d8fcfd6bb7ae5911a1d53b8746d546, I have reviewed the code and it looks OK.
instagibbs:
ACK 48092a9042d8fcfd6bb7ae5911a1d53b8746d546
l0rinc:
tested ACK 48092a9042d8fcfd6bb7ae5911a1d53b8746d546

Tree-SHA512: 0f7a8e5b14cd13b56eb9b663e8d17e03abf94da2662332a24c802fc9c608b9acb1bae01e476502228e4a2cc65332fddd934b96ec7bdbe14fadc9ba3db08b1542

100/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36667: net: enforce timeout interval for paused send peersby merge-script · 5da09030 · Oct 26, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36667: net: enforce timeout interval for paused send peers

cc2534cdf7b14d0f1a18928ebaab7f7fdd7e839e net: enforce timeout interval for paused send peers (Antoine Poinsot)

Pull request description:

Today it's possible to keep some peers running ancient versions paused for a long time. If such a peer is so slow to read as to not drain our send buffer down to the 1MB threshold within a reasonable time frame, we really shouldn't be wasting a connection slot on them. I picked 20 minutes as the reasonable time frame, since it's what we already use for ping timeouts today.

ACKs for top commit:
instagibbs:
ACK https://github.com/bitcoin/bitcoin/pull/36667/commits/cc2534cdf7b14d0f1a18928ebaab7f7fdd7e839e
sedited:
Re-ACK cc2534cdf7b14d0f1a18928ebaab7f7fdd7e839e
l0rinc:
tested ACK cc2534cdf7b14d0f1a18928ebaab7f7fdd7e839e

Tree-SHA512: 05e0ab6bc7908ea533612c5d4bf5757545936e18a056fa04448615ef096e9477f007bf241b311a888ef0570e31a227140305e4d4aec2687d2d88462df9bb2a1a

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36665: sock: align exception monitoring between poll() and select() backendsby merge-script · 21862329 · Oct 26, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36665: sock: align exception monitoring between poll() and select() backends

1e0c407377034e9cbb4d52f1f534c06cdf202a36 sock: align exception monitoring between poll() and select() backends (Antoine Poinsot)

Pull request description:

On non-Linux platforms, `WaitMany` monitors every socket for exceptional conditions, even when we are not looking to read from it. On Linux, it never monitors those.

Monitoring for certain socket events on some platforms but not others is inconsistent and surprising. In this instance it probably means these cases receive less testing as well, since they are ignored on our most well-tested platform.

Fix this issue by only monitoring for exceptional conditions (which is necessary to detect failed connection attempts early on Windows) for sockets we are also waiting to read from.

ACKs for top commit:
vasild:
ACK 1e0c407377034e9cbb4d52f1f534c06cdf202a36
sedited:
utACK 1e0c407377034e9cbb4d52f1f534c06cdf202a36
instagibbs:
ACK 1e0c407377034e9cbb4d52f1f534c06cdf202a36
pinheadmz:
ACK 1e0c407377034e9cbb4d52f1f534c06cdf202a36

Tree-SHA512: 58109efad8ad3bda6c76fa8fad8855e7337bbd54ca046b286940319de0a835d82a4eb66ccc052b23eb6a15840a90c4d29d2fd7345a6318471bc3d9826aab2d10

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36610: test: add `plyvel` to deps tableby merge-script · dd9d2b91 · Oct 26, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36610: test: add `plyvel` to deps table

a4d470e1e9a34ab05a48a25ed60d470a691785ac test: add plyvel to deps table (fanquake)

Pull request description:

Followup to #35395.

ACKs for top commit:
hebasto:
ACK a4d470e1e9a34ab05a48a25ed60d470a691785ac.

Tree-SHA512: 9c718e4b7af2897211784938aae807b9651982f6efd360572ba531a952ea0a50b3e87c2eb0f455febee1f538967734cea8fd4f1dada3be3f750b6997fd6e1fc0

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Security candidateMerge bitcoin/bitcoin#36624: test: Enable noban_tx_relay in a few more testsby merge-script · a773e1e3 · Oct 23, 2026 · 43 filesMessage 91 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36624: test: Enable noban_tx_relay in a few more tests

fa704c5d3cafcd768982a02c48c7c7d96d667fa1 test: Use faster noban_tx_relay in mempool tests (MarcoFalke)
fa6f7e36a8c27d8d4824c4dbec45abd405388abe test: [doc] Clarify noban_tx_relay comment (MarcoFalke)
faf2e3aba59b8023d84f09a68cc946f1ed3f526a test: Use proper noban permission for faster tx relay (MarcoFalke)

Pull request description:

For https://github.com/bitcoin/bitcoin/issues/19732 (see commit msgs for details)

ACKs for top commit:
ViniciusCestarii:
ACK fa704c5d3cafcd768982a02c48c7c7d96d667fa1
brunoerg:
ACK fa704c5d3cafcd768982a02c48c7c7d96d667fa1

Tree-SHA512: fa6906b4ef0a921fc321db6784173c2c0461e90b19d3a058cd5ac93e6ac953bfc75131740c534b18c133dd815a2d80f8846f3feed721457c30995bcfc0157472

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege statesigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit only changes Bitcoin Core's internal functional test suite. It replaces manual '-whitelist=noban@127.0.0.1' settings and verbose comments with a shared test flag called 'noban_tx_relay' to make automated tests run faster. There is no change to the actual Bitcoin node software that users run, and no security vulnerability is introduced or fixed.

Lower-prioritytest: Use faster noban_tx_relay in mempool testsby MarcoFalke · fa704c5d · Oct 23, 2026 · 4 filesMessage 82 · StrongTriage 0Details
Commit message · MarcoFalke

test: Use faster noban_tx_relay in mempool tests

Those tests do not check trickle relay delays or peer misbehavior

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Security candidatetest: [doc] Clarify noban_tx_relay commentby MarcoFalke · fa6f7e36 · Oct 23, 2026 · 39 filesMessage 90 · StrongInformational 15Details
Commit message · MarcoFalke

test: [doc] Clarify noban_tx_relay comment

The comment is verbose and there are many whitelist permissions like
`relay` or `mempool`, but this applies `noban` to in- and out-
connections.

A brief `self.noban_tx_relay = True # faster tx relay` covers the same
meaning with less confusion.

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
credential or privilege statesigning or wallet path
AI analysis · Informational 15/100

This commit only rewrites comments in Bitcoin Core's test suite. It replaces longer explanations about whitelisting peers with a shorter note that the setting is used for faster transaction relay. No actual code behavior changes, so it has no security impact.

Security candidatetest: Use proper noban permission for faster tx relayby MarcoFalke · faf2e3ab · Oct 23, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · MarcoFalke

test: Use proper noban permission for faster tx relay

A plain -whitelist=noban@127.0.0.1 misses the out connections.

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
credential or privilege statesigning or wallet path
AI analysis · Informational 15/100

This is a minor test-only change in Bitcoin Core's functional test suite. It replaces a manual whitelist flag with a built-in test framework option that achieves the same goal for both incoming and outgoing peer connections. There is no change to production code, no security fix, and no vulnerability.