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 43 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-priorityMerge bitcoin/bitcoin#36573: test: cover gettxspendingprevout error without txospenderindexby merge-script · 9c79f555 · Oct 20, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36573: test: cover gettxspendingprevout error without txospenderindex

edf0d13ad5ff9035ad7a0ff7bc38610edb952b2d test: cover gettxspendingprevout error without txospenderindex (mercie-ux)

Pull request description:

Add functional coverage for the `gettxspendingprevout` error raised when `mempool_only=false`, no matching spend is in the mempool, and `txospenderindex` is unavailable.

The combined unit and functional coverage report shows this throw in `src/rpc/mempool.cpp` is never reached:
https://github.com/bitcoin/bitcoin/blob/71fa0439278f1d11c9a1aabe67312dcdf1cc8757/src/rpc/mempool.cpp#L1080

The existing test already queries node2 without the index, but `mempool_only` defaults to `true` in that case, so the error is only reachable when `mempool_only=false` is passed explicitly.

The test now checks both sides on node2 with `mempool_only=false`: it succeeds while the spends are still in the mempool, and raises the error once they are mined.

ACKs for top commit:
Hamza1610:
ACK https://github.com/bitcoin/bitcoin/commit/edf0d13ad5ff9035ad7a0ff7bc38610edb952b2d
vicjuma:
ACK edf0d13ad5ff9035ad7a0ff7bc38610edb952b2d
sedited:
ACK edf0d13ad5ff9035ad7a0ff7bc38610edb952b2d

Tree-SHA512: 13cd8422a7573a52dea0683b611cd27333944f690f4bc88fbac08f85a976e6cd63bd76acba81a1440631ba2ba84532407c8c4f715f294acf892fbc3ed67eb45c

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#36177: net: fix startup failures from stale Tor examplesby merge-script · 06edf059 · Oct 20, 2026 · 4 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36177: net: fix startup failures from stale Tor examples

6c7c27f615a5b74e0aa921b8f103bf468a510aac doc: use onion in proxy help and examples (Lőrinc)
fd65406b39a844d2093c33e7662f79be2857d197 net: preserve network name case in proxy errors (Lőrinc)
b0375749d4d4763efa95be2f0b0bcbe20e7d9a78 refactor: share proxy network parsing (Lőrinc)
332c3e8e3e176b6d7e83960325ca3d8d1859d7eb test: characterize proxy network name errors (Lőrinc)

Pull request description:

**Problem:** #34031 removed `tor` as a network name, but the `-proxy` help and Tor documentation still advertise it, and following those examples fails at startup.
The proxy option also maintains its own network-name mapping while `-onlynet` and `getnodeaddresses` use the shared parser.

**Fix:** Reuse the shared parser and canonical network names for `-proxy`, and document `onion` consistently. Unsupported network names are now echoed as supplied, matching the other interfaces, while accepted names remain case-insensitive.

ACKs for top commit:
jpk68:
ACK 6c7c27f615a5b74e0aa921b8f103bf468a510aac
vasild:
ACK 6c7c27f615a5b74e0aa921b8f103bf468a510aac
sedited:
ACK 6c7c27f615a5b74e0aa921b8f103bf468a510aac

Tree-SHA512: db85dd5fb207fa7ca00dd4e9b4ec2ab32282248c8276faf4958af5c2c34aac6c5880b2d83380b29bb2bb111f9b910acda3f5d462426005faba9813c336b4cba2

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#35321: p2p: Misbehave on invalid compact block in optimistic reconstructionby merge-script · 0a8e904c · Oct 20, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#35321: p2p: Misbehave on invalid compact block in optimistic reconstruction

b9788a5a10bd7edf87072c9d719b81ebbaea9fc1 test: disconnect receiving invalid cmpctblock on optimistic path (ViniciusCestarii)
0e68ef04f7048df5c949392b6cf4e9698c6c79ad p2p: misbehave on invalid compact block in optimistic reconstruction path (ViniciusCestarii)

Pull request description:

When `InitData` returns `READ_STATUS_INVALID` (the peer sent malformed data) during optimistic compact block reconstruction. Call Misbehaving instead of silently ignoring it, consistent with the primary compact block handling path.

Removes the TODO added in 7017298eb2.

ACKs for top commit:
davidgumberg:
reACK https://github.com/bitcoin/bitcoin/commit/b9788a5a10bd7edf87072c9d719b81ebbaea9fc1
w0xlt:
reACK b9788a5a10bd7edf87072c9d719b81ebbaea9fc1
instagibbs:
ACK b9788a5a10bd7edf87072c9d719b81ebbaea9fc1

Tree-SHA512: ff8319bc4cf81e5abbd394bec27e9335063a3e3a60dea164d0a436f47a110c9ba74dbc89cd05b12fd223d93781f651b4f3791089e15d479d25858c201bfd34de

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
AI review queuedMerge bitcoin/bitcoin#36553: test: Add missing sync_mempools in wallet_conflicts.pyby merge-script · 020fcb28 · Oct 20, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36553: test: Add missing sync_mempools in wallet_conflicts.py

fa1061481bb1cb6bb7d5ca7ea6674f349f2baed8 test: Add missing sync_mempools in wallet_conflicts.py (MarcoFalke)
fa3986f5c1d512f5e8a320ccbbd84bde3c9e2575 test: Remove redundant sync call after self.generate called sync_all (MarcoFalke)

Pull request description:

Fix https://github.com/bitcoin/bitcoin/actions/runs/38882212577/job/116911393791?pr=36545#step:11:3700:

```
2026-10-16T09:48:01.724540Z TestFramework (INFO): Test a scenario where a transaction has a mempool conflict
2026-10-16T09:48:02.100649Z TestFramework (INFO): Test scenario where a mempool conflict is removed
2026-10-16T10:28:02.397150Z TestFramework (ERROR): Unexpected exception:
Traceback (most recent call last):
File "/home/runner/work/_temp/test/functional/test_framework/test_framework.py", line 146, in main
self.run_test()
~~~~~~~~~~~~~^^
File "/home/runner/work/_temp/build_ ₿🧪_/test/functional/wallet_conflicts.py", line 38, in run_test
self.test_mempool_conflict()
~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/home/runner/work/_temp/build_ ₿🧪_/test/functional/wallet_conflicts.py", line 202, in test_mempool_conflict
self.generate(self.nodes[2], 1)
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
File "/home/runner/work/_temp/test/functional/test_framework/test_framework.py", line 668, in generate
sync_fun() if sync_fun else self.sync_all()
~~~~~~~~~~~~~^^
File "/home/runner/work/_temp/test/functional/test_framework/test_framework.py", line 750, in sync_all
self.sync_mempools(nodes)
~~~~~~~~~~~~~~~~~~^^^^^^^
File "/home/runner/work/_temp/test/functional/test_framework/test_framework.py", line 743, in sync_mempools
raise AssertionError("Mempool sync timed out after {}s:{}".format(
...<2 lines>...
))
AssertionError: Mempool sync timed out after 2400s:
{'ed4cecf5b16f82ce48b2c56b6a20feac3f83e6043b262a74f356e07a451dda34'}
{'47de6fdef43b22320dc0114c2104e3dee58de9591799ff5e48ff29efaa5cf88f', 'ed4cecf5b16f82ce48b2c56b6a20feac3f83e6043b262a74f356e07a451dda34'}
{'ed4cecf5b16f82ce48b2c56b6a20feac3f83e6043b262a74f356e07a451dda34'}
```

by adding the missing `sync_mempools`.

ACKs for top commit:
fanquake:
ACK fa1061481bb1cb6bb7d5ca7ea6674f349f2baed8

Tree-SHA512: 526a216228f87976c5a41b8fffb8eab0728d23c70c642a54ed2f2cc58c93875119c5c294b151bab5ff70994f657091a6db879f4aae63b0cde356466685fcd084

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

This commit fixes a flaky automated test in Bitcoin Core. It adds missing mempool synchronization calls in a wallet-conflict test and removes a couple of redundant block-sync calls. There is no change to production code, no security vulnerability, and no risk to users' funds or node safety.

Lower-priorityMerge bitcoin/bitcoin#36559: test: zero-pad the port in feature_anchors' expected hexby merge-script · d0d1e49c · Oct 19, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36559: test: zero-pad the port in feature_anchors' expected hex

2f7622e3f6f7ef431a7d5ec522958da62f33cec4 test: zero-pad the port in feature_anchors' expected hex (Kevin Ravensberg)

Pull request description:

`feature_anchors.py` builds the expected `anchors.dat` substring from each peer's port with `hex(port)[2:]`, which is not zero-padded. The port is serialized as two bytes, so for ports below 4096 the expected string is one hex digit short and `assert ip_port in anchors_hex` fails.

This only shows up with a non-default port range, for example when avoiding local listeners:

```
TEST_RUNNER_PORT_MIN=1100 test/functional/feature_anchors.py
```

fails on master with `AssertionError` at the `assert ip_port in anchors_hex` line and passes with this change; the default range still passes.

---
Disclosure: AI (Claude Fable 5.1) was used to find this issue and to draft this PR.

ACKs for top commit:
l0rinc:
lightly tested ACK 2f7622e3f6f7ef431a7d5ec522958da62f33cec4
maflcko:
lgtm ACK 2f7622e3f6f7ef431a7d5ec522958da62f33cec4
sedited:
ACK 2f7622e3f6f7ef431a7d5ec522958da62f33cec4

Tree-SHA512: 28de13992b009d771d84c1095be529b70bc5283d9bf13310a1d521cf53bf48e6da998c79507ee2d949796f422911266084968aae8d33dffb6429c0b92c53c963

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#36407: test: make orphanage_dos_many fill the orphanageby merge-script · a7a584fc · Oct 19, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36407: test: make orphanage_dos_many fill the orphanage

86ff13a0af0679ee0c725bac9c64c3e373cb0283 test: make orphanage_dos_many fill the orphanage (Ferdinando Ametrano)

Pull request description:

`test_orphanage_dos_many` checks that a normal peer's orphan survives while DoS peers flood the orphanage. I found that the orphanage never fills: the 60 peers send the same 51 orphans as `tx`, and a `tx` already held as an orphan is dropped in `ReceivedTx` without recording its sender. The orphanage peaks at 152 announcements against a limit of 3000, so nothing is evicted.

Here the first peer sends the orphans and the other 59 announce them by `inv`, which does add them as announcers. The test now asserts that the orphanage holds 3000 announcements, instead of asserting on what it sends. It takes about as long as before.

If `LimitOrphans` is changed to evict the normal peer's orphan first, the test used to pass and now fails. (`test_orphanage_dos_large` already catches that change.)

Found while porting these tests to https://github.com/btclib-org/bitcoin-node-tests.

*Made with my usual tools: a computer, the Internet and an LLM. The mistakes, as usual, are all mine.*

ACKs for top commit:
instagibbs:
ACK 86ff13a0af0679ee0c725bac9c64c3e373cb0283
naiyoma:
tACK 86ff13a0af0679ee0c725bac9c64c3e373cb0283

Tree-SHA512: 8bf3bd5a2db6f8e52aa02edcbfcd60e1afeaeb4d44acc9798ab0a2c0e53bd4567250be0fad0e358d7adb70e2264842362377e7c5004661c3ebd2e6d0b8236f4d

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
AI review queuedMerge bitcoin/bitcoin#36341: wallet: return error from bitcoin-wallet createby merge-script · ebb53105 · Oct 19, 2026 · 2 filesMessage 81 · StrongInformational 24Details
Commit message · merge-script

Merge bitcoin/bitcoin#36341: wallet: return error from bitcoin-wallet create

f64d33672fe1488b49254a634cbecfd9ce4ca179 wallet: return error from bitcoin-wallet create (Kanan)

Pull request description:

`bitcoin-wallet create` exits with status 0 even when the wallet couldn't be created:

```
$ bitcoin-wallet -regtest -wallet=w1 create # first time, ok
$ bitcoin-wallet -regtest -wallet=w1 create
Failed to create database path '.../regtest/wallets/w1'. Database already exists.
$ echo $?
0
```

In `ExecuteWalletToolFunc` the `create` branch only does something when `MakeWallet` succeeds and then falls through to `return true`. The other commands (`info`, `dump`, `createfromdump`) all return false on failure. So scripts that check the exit code think the wallet was created.

This returns false when `MakeWallet` fails, the same way `info` does. The added check in `tool_wallet.py` runs `create` on the existing wallet `foo` and expects exit code 1. It fails on master (`not(0 == 1)`) and passes with the fix.

ACKs for top commit:
maflcko:
lgtm ACK f64d33672fe1488b49254a634cbecfd9ce4ca179
sedited:
ACK f64d33672fe1488b49254a634cbecfd9ce4ca179

Tree-SHA512: aa2404a4bea38ca53da989d0b09e13a6b48dccfd49fa0e70a268c325241226693a8ca6ef94fb35cc0cca2cc66a066dcf90adfc254e972e4b9b23c047adefaf3f

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This is a small reliability fix for the bitcoin-wallet command-line tool. Previously, when you tried to create a wallet that already existed, the tool printed an error message but still exited with status 0, which is the code normally used for success. Scripts and automated tools checking the exit code would therefore incorrectly think the command succeeded. The patch makes the tool return a non-zero exit code on failure, matching the behavior of other wallet tool commands. There is no security vulnerability allowing theft, remote attack, or code execution.

Security candidateMerge bitcoin/bitcoin#36339: wallet: avoid int overflow in listtransactionsby merge-script · 3983b582 · Oct 19, 2026 · 2 filesMessage 96 · StrongHigh 74Details
Commit message · merge-script

Merge bitcoin/bitcoin#36339: wallet: avoid int overflow in listtransactions

9cff82fd5b15bc2aa2c7778b61212876433a8219 wallet: avoid int overflow in listtransactions (Kanan)

Pull request description:

`listtransactions` adds `count` and `skip` as `int`. Each one is checked to be non-negative, but their sum can still go past INT_MAX:

```
bitcoin-cli -regtest listtransactions "*" 2147483647 1
```

On master this crashes the node. The overflowed sum is negative, so the loop stops after the first entry. The clamp after the loop overflows the same way and doesn't fix `nCount`, so `push_backV` gets an iterator range about 2^31 elements before `rend()`. UBSan reports `signed integer overflow: 1 + 2147483647` at transactions.cpp:584, and ASan then reports a BUS error in `UniValue::push_backV`.

This parses `count` and `skip` as `uint32_t` through `self.Arg` (which also handles the defaults and rejects negative values, so the manual checks go away) and adds them up in 64 bits, where the sum can't overflow. The functional test calls `listtransactions` with count + skip above INT_MAX and up to UINT32_MAX and checks the results match a normal-sized request. It times out on master (the node crashes) and passes with the fix. I also ran it on an ASan/UBSan build.

`listrawtransactions` counts differently and isn't affected.

ACKs for top commit:
maflcko:
lgtm ACK 9cff82fd5b15bc2aa2c7778b61212876433a8219
sedited:
ACK 9cff82fd5b15bc2aa2c7778b61212876433a8219

Tree-SHA512: 0068951efb724cf5551238de1c6b5d254b66594f9fe8878cf5bb49026e1624a8db6dc87eee23dfed38fc7620cef2933817e82ceb7f8072f8f89911f50af2e607

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
memory safetysigning or wallet pathmerge-commit duplicate discount
AI analysis · High 74/100

This patch fixes a bug in Bitcoin Core's `listtransactions` RPC command. When a user asked for a very large number of transactions plus a large skip value, the wallet code added two integers together and overflowed, producing a negative number. That negative number was then used as a memory range, causing the node to crash. The fix reads the values as unsigned 32-bit integers and adds them in 64-bit arithmetic so the sum cannot overflow, and removes the now-redundant manual negative checks.

Lower-prioritynet: enforce timeout interval for paused send peersby Antoine Poinsot · cc2534cd · Oct 19, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Antoine Poinsot

net: enforce timeout interval for paused send peers

No need to waste a connection slot on a peer that is so slow to read as to not
drain our send buffer down to the 1MB threshold within 20 minutes.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMerge bitcoin/bitcoin#36295: refactor: Remove args-wrappers in favor of naked value_or()by merge-script · 01b51c0f · Oct 19, 2026 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36295: refactor: Remove args-wrappers in favor of naked value_or()

60e95b412c999aa9efe561c99994f8e53d5ab4f6 args: Remove wrapper-functions in favor of naked optional::value_or() (Hodlinator)

Pull request description:

Decreases complexity at the foundation at the only cost of a change to `ArgsManager::GetPathArg_()` and slightly more verbose code in one leaf; src/qt/optionsmodel.cpp.

Also represents slight decrease in complexity of pending PR #31260 which has an extra `GetPtr()` function for disambiguating between overloaded functions.

Original thread: https://github.com/bitcoin/bitcoin/pull/31260#discussion_r3861455984

(Rebased it onto the current base commit of #31260 and rebased #31260 on top of that, removed `GetPtr()`, and confirmed it still compiles: https://github.com/hodlinator/bitcoin/tree/pr/31260_no_GetPtr).

ACKs for top commit:
l0rinc:
lightly tested code review ACK 60e95b412c999aa9efe561c99994f8e53d5ab4f6
maflcko:
review ACK 60e95b412c999aa9efe561c99994f8e53d5ab4f6 🔊
sedited:
ACK 60e95b412c999aa9efe561c99994f8e53d5ab4f6

Tree-SHA512: 5833dbe4cd10bf82ec4808abae82f664ec6fb012e483aa12e16551c488449cd827e01355f1d6794df25c1c80ce1db316ebd5960390ae8dcd0e284b2aa32cfde9

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
Security candidateMerge bitcoin/bitcoin#36231: test: add pow tests covering live mutantsby merge-script · 368c1382 · Oct 19, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36231: test: add pow tests covering live mutants

e6975adf58c354dbd167b419ad7aadc7b8053af6 test: cover non-retarget heights in PermittedDifficultyTransition (ViniciusCestarii)
a9873943e259b23884fb4295591a82168c831026 test: cover lower bound rounding in PermittedDifficultyTransition (ViniciusCestarii)
7834db23914a3faa3660cb609144cd1c345a1ef3 test: cover negative timespan in CalculateNextWorkRequired (ViniciusCestarii)
1811735255b98257e7bf385325599c8d9bb69ad0 test: cover first block time selection in GetNextWorkRequired (ViniciusCestarii)

Pull request description:

Kills 4 live mutants on pow.cpp found with https://github.com/ViniciusCestarii/mutant-harness. The first 2 affect consensus. The third affect header sync and could stall IBD. The forth cover header sync hardening against DoS. They are:

pow.cpp (killed by 1811735255b98257e7bf385325599c8d9bb69ad0):

```diff
diff --git a/src/pow.cpp b/src/pow.cpp
index 9a9f4e5..9872b2c 100644
--- a/src/pow.cpp
+++ b/src/pow.cpp
@@ -44,7 +44,7 @@ unsigned int GetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHead
const CBlockIndex* pindexFirst = pindexLast->GetAncestor(nHeightFirst);
assert(pindexFirst);

- return CalculateNextWorkRequired(pindexLast, pindexFirst->GetBlockTime(), params);
+ return CalculateNextWorkRequired(pindexLast, pindexFirst->GetMedianTimePast(), params);
}

unsigned int CalculateNextWorkRequired(const CBlockIndex* pindexLast, int64_t nFirstBlockTime, const Consensus::Params& params)
```

pow.cpp (killed by 7834db23914a3faa3660cb609144cd1c345a1ef3):

```diff
diff --git a/src/pow.cpp b/src/pow.cpp
index 9a9f4e5..1917b7b 100644
--- a/src/pow.cpp
+++ b/src/pow.cpp
@@ -53,7 +53,7 @@ unsigned int CalculateNextWorkRequired(const CBlockIndex* pindexLast, int64_t nF
return pindexLast->nBits;

// Limit adjustment step
- int64_t nActualTimespan = pindexLast->GetBlockTime() - nFirstBlockTime;
+ uint32_t nActualTimespan = pindexLast->GetBlockTime() - nFirstBlockTime;
if (nActualTimespan < params.nPowTargetTimespan/4)
nActualTimespan = params.nPowTargetTimespan/4;
if (nActualTimespan > params.nPowTargetTimespan*4)
```

pow.cpp (killed by a9873943e259b23884fb4295591a82168c831026):

```diff
diff --git a/src/pow.cpp b/src/pow.cpp
index 9a9f4e5..028fa9f 100644
--- a/src/pow.cpp
+++ b/src/pow.cpp
@@ -124,11 +124,8 @@ bool PermittedDifficultyTransition(const Consensus::Params& params, int64_t heig
smallest_difficulty_target = pow_limit;
}

- // Round and then compare this new calculated value to what is
- // observed.
- arith_uint256 minimum_new_target;
- minimum_new_target.SetCompact(smallest_difficulty_target.GetCompact());
- if (minimum_new_target > observed_new_target) return false;
+ // Compare this new calculated value to what is observed.
+ if (smallest_difficulty_target > observed_new_target) return false;
} else if (old_nbits != new_nbits) {
return false;
}
```

pow.cpp (killed by e6975adf58c354dbd167b419ad7aadc7b8053af6):

```diff
diff --git a/src/pow.cpp b/src/pow.cpp
index 9a9f4e5..ef2e788 100644
--- a/src/pow.cpp
+++ b/src/pow.cpp
@@ -129,8 +129,6 @@ bool PermittedDifficultyTransition(const Consensus::Params& params, int64_t heig
arith_uint256 minimum_new_target;
minimum_new_target.SetCompact(smallest_difficulty_target.GetCompact());
if (minimum_new_target > observed_new_target) return false;
- } else if (old_nbits != new_nbits) {
- return false;
}
return true;
}
```

Recommend reviewing per commit.

ACKs for top commit:
brunoerg:
ACK e6975adf58c354dbd167b419ad7aadc7b8053af6
sedited:
ACK e6975adf58c354dbd167b419ad7aadc7b8053af6

Tree-SHA512: da29cf0226393a870e5c0bb8b228143abf124a905c70caf1006830854a9ac1f26b087a0c65570c8c0661d5a8db67ff91c22accb1d7ed5d4f5d1597ef1d66fe5a

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
defensive validationconsensus or confidential-proof validationmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit only adds new test cases to Bitcoin Core's proof-of-work test file. It does not change any production code. The tests are designed to detect if future code changes accidentally break subtle consensus rules around difficulty retargeting. There is no vulnerability being fixed here.

Lower-priorityMerge bitcoin/bitcoin#36438: test: a switch to tx relay via filterclear can trigger evictionby merge-script · e921dfaa · Oct 19, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36438: test: a switch to tx relay via filterclear can trigger eviction

7dc0e8174c7d9180c606c45b91ed21155943fa6b test: a switch to tx relay via filterclear can trigger eviction (Bruno Garcia)

Pull request description:

This PR adds a test case that checks that a switch to tx relay via `filterclear` can trigger eviction.

It kills the following mutant (https://mutanthub.space/mutants/3746):
```diff
diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index 96caf9050f..d9019db877 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -5312,7 +5312,6 @@ void PeerManagerImpl::ProcessMessage(Peer& peer, CNode& pfrom, const std::string
}
pfrom.m_bloom_filter_loaded = false;
pfrom.m_relays_txs = true;
- MaybeDisconnectForTxRelayCapacity(pfrom, msg_type);
return;
}

```

ACKs for top commit:
mercie-ux:
ACK 7dc0e8174c7d9180c606c45b91ed21155943fa6b
Naomi-Gift:
tACK 7dc0e8174c7d9180c606c45b91ed21155943fa6b
Ayoazeez26:
tACK 7dc0e8174c7d9180c606c45b91ed21155943fa6b
ViniciusCestarii:
tACK 7dc0e8174c7d9180c606c45b91ed21155943fa6b
sedited:
ACK 7dc0e8174c7d9180c606c45b91ed21155943fa6b

Tree-SHA512: b3771a7fe478bb9d84e88c69763ea9f5c9eb72ade7a19886b6b4c9bd1fab79f6248e744d537c3839af325f937d801f04fa15c6ea5e56226666544c2aa1c5b86e

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#36541: test: Small p2p_node_network_limited.py cleanupsby merge-script · 61933456 · Oct 19, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36541: test: Small p2p_node_network_limited.py cleanups

fadcd0b64e3982a9c42a54faa0a3be8ab58caa04 test: Remove confusing ensure_for (MarcoFalke)
fa13e8954d2d6c01104083d45e0fe113ffcb9175 test: Fix block height typos in test logs (MarcoFalke)

Pull request description:

Fix a pre-existing typo and https://github.com/bitcoin/bitcoin/pull/36446#discussion_r4267602616

ACKs for top commit:
mercie-ux:
ACK fadcd0b64e

Tree-SHA512: 75097368b8e5d46c568a487935ff68b10d8dd32eefa1059036895e60ce2dff7edd927afe6f24364e2477062bf2b993e934be47f39e2e8df314ace8b7415e7e58

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#36422: test: check unconnecting headers don't reset the getheaders rate limitby merge-script · 6301d464 · Oct 19, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36422: test: check unconnecting headers don't reset the getheaders rate limit

a7acf277dc39011b5d06234e8d6e12d8c31c1678 test: check unconnecting headers don't reset the getheaders rate limit (Bruno Garcia)

Pull request description:

Since 9f66ac7cf1, only empty headers, headers that connect to the block index, or a valid low-work sync continuation count as a response to an outstanding getheaders. Part 5 of p2p_sendheaders always sends an empty headers message before each unconnecting header, so nothing checked that an unconnecting header on its own leaves m_last_getheaders_timestamp alone.

It adds a test case that sends an unconnecting header again right after the previous getheaders and check that no new getheaders goes out. Then advance mocktime past `HEADERS_RESPONSE_TIME` and check that a getheaders is sent again.

It kills the mutant https://mutanthub.space/mutants/3744.

ACKs for top commit:
ViniciusCestarii:
tACK a7acf277dc39011b5d06234e8d6e12d8c31c1678
frankomosh:
ACK a7acf277dc39011b5d06234e8d6e12d8c31c1678

Tree-SHA512: 147cac08a879a34831859069dfa9efd0ceb300dfd7ec8ace7809c93d8182f4d74d9879518dbe8122c376b5185067508a00939cab8768c03b57eea63f416cdd5a

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#36159: http: Improve HTTPRemoteClient::MaybeDisconnect()by merge-script · bb19150a · Oct 19, 2026 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36159: http: Improve HTTPRemoteClient::MaybeDisconnect()

2abf671d2e14b5ceb91fb570258945b41ef78299 http: Flatten control flow in HTTPRemoteClient::ShouldDisconnect() (Hodlinator)
5b98d56c93badc46f7a6f195887c7f2328cbe8fe test: Verify behavior of HTTPRemoteClient::ShouldDisconnect() (Hodlinator)
59a3e8803c1ce5360a24fdbe5fef7a72512f76d5 refactor: Switch client idle timeout to mockable clock (Hodlinator)
5fba3308338643395e2c1261a519222c491da90c refactor: Rename MaybeDisconnect() to ShouldDisconnect() and make it const (Hodlinator)
cb8f4b0a303c3dbb18a313da6cb5bd3492243fb8 http: Add log message for remaining case where we set m_disconnect = true (Hodlinator)

Pull request description:

### Issues

#35182 had 1 case where we flag a client for disconnect where we do not log the reason.

#35829 introduced the somewhat poorly named non-`const` `HTTPRemoteClient::MaybeDisconnect()`. It also lacks testing.

The control-flow in `MaybeDisconnect()/ShouldDisconnect()` is somewhat complex. https://github.com/bitcoin/bitcoin/pull/35829#discussion_r3846342291

### Commits solving these issues in same order

* http: Add log message for remaining case where we set `HTTPRemoteClient::m_disconnect = true`
* refactor: Rename `MaybeDisconnect()` to `ShouldDisconnect()` and make it `const`
* refactor: Enable mocking the time around `ShouldDisconnect()`
* test: Add test for behavior of `ShouldDisconnect()`
* refactor: Flatten control flow in `ShouldDisconnect()`

ACKs for top commit:
pinheadmz:
ACK 2abf671d2e14b5ceb91fb570258945b41ef78299
winterrdog:
reACK 2abf671d2e14b5ceb91fb570258945b41ef78299
sedited:
ACK 2abf671d2e14b5ceb91fb570258945b41ef78299

Tree-SHA512: eb5d16d50f80fb31abc21134dddba9b23469b57a4846f2f80fd882e83e87f3c29b076d0f4a871ff6f7f629c2037e7a45fff27ac370314ba69ba7832d4f3a1c58

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#36524: common: drop locale setting hackby merge-script · 276db20b · Oct 19, 2026 · 3 filesMessage 71 · AdequateTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36524: common: drop locale setting hack

43bb5e3c467f38566f7d7271b0030ef4af1cf78c doc: add release note for #36524 (fanquake)
cbd2964db77437a2043b04895b24487939739bd5 common: drop locale setting hack (fanquake)
1164c77d2d4b166af69bd55a87ee9b6d072a9b09 test: run GUI nodes in Dutch with -lang (stickies-v)

Pull request description:

This was added to work around `boost::filesystem` throwing when the environments locale was invalid. Boost.Filesystem has been removed, and `std::filesystem` doesn't use the locale on POSIX (and bitcoind never calls `setlocale`).

Qt calls `setlocale(LC_ALL, "")` on startup, and falls back to `C.UTF-8` if the locale isn't `UTF-8`.

Alternative to #36399, which extends the hack further.

ACKs for top commit:
maflcko:
review ACK 43bb5e3c467f38566f7d7271b0030ef4af1cf78c 🚂
stickies-v:
ACK 43bb5e3c467f38566f7d7271b0030ef4af1cf78c
sedited:
ACK 43bb5e3c467f38566f7d7271b0030ef4af1cf78c

Tree-SHA512: f67d0ba67f57333906970b32f607c859c6bc9fc1462a62cf4687817acb922e72f9ac8f2cfc828fbb1d60f91d90152b28a738f37439c5c7fdd1f38e70eb2feb74

71/100 · AdequateMessage 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! Contains work-in-progress language
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36368: bitcoin-tx: reject in and outscript arguments with too many separatorsby merge-script · fe52f520 · Oct 19, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36368: bitcoin-tx: reject in and outscript arguments with too many separators

2fef1db4f88a02efd666da41bc3641345940669d bitcoin-tx: reject in and outscript arguments with too many separators (Bruce0X)

Pull request description:

`outscript=VALUE:SCRIPT[:FLAGS]` only reads the flags when there are exactly three fields (bitcoin-tx.cpp:482). With a trailing or extra `:` the flags are silently dropped:

```
$ bitcoin-tx -create outscript=0:OP_DROP:S nversion=1
010000000001000000000000000017a91471ed53322d470bb96657deb786b94f97dd46fb158700000000 # P2SH, as requested
$ bitcoin-tx -create outscript=0:OP_DROP:S: nversion=1
0100000000010000000000000000017500000000 # bare OP_DROP output, exit code 0
```

So a typo gives a transaction paying to the raw script instead of the P2SH/P2WSH wrapper, with no error. `outpubkey` and `outaddr` already reject extra fields with "TX output missing or too many separators".

This rejects `outscript` arguments with more than three fields, and `in=TXID:VOUT[:SEQUENCE_NUMBER]` arguments with more than three fields (which were accepted the same way), both with a general "Invalid format, expected ..." error. `bitcoin-util-test.json` gets a case for each; they fail on master (exit code 0) and pass with the fix, and `tool_utils.py` passes.

AI tools were used to help find this issue and to prepare the patch and test.

ACKs for top commit:
maflcko:
lgtm ACK 2fef1db4f88a02efd666da41bc3641345940669d
cyb3ralbert:
tested ACK 2fef1db4f88a02efd666da41bc3641345940669d
sedited:
ACK 2fef1db4f88a02efd666da41bc3641345940669d

Tree-SHA512: 5c27fd78c530d50de4ffb6c2a0f74ab44a7acc0c7cd1703776d4a50108a3279acc32240e0e84c2d9912159acdda600937bc1e4e7270f29d9cf2b592ee0ce850b

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
AI review queuedMerge bitcoin/bitcoin#36545: test: Fix intermittent issue in p2p_initial_headers_sync.pyby merge-script · 71fa0439 · Oct 19, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · merge-script

Merge bitcoin/bitcoin#36545: test: Fix intermittent issue in p2p_initial_headers_sync.py

fad7637529426f058a3c2409dd137009b14622a4 test: Fix intermittent issue in p2p_initial_headers_sync.py (MarcoFalke)

Pull request description:

Fixes https://github.com/bitcoin/bitcoin/actions/runs/38697071260/job/116296055487?pr=36537#step:11:5104:

```
test 2026-10-15T07:19:58.731108Z TestFramework (INFO): Check that noban peer1 is not disconnected
test 2026-10-15T07:19:58.731159Z TestFramework.p2p (DEBUG): Send message to 127.0.0.1:12392: msg_ping(nonce=00000000)
test 2026-10-15T07:19:58.731184Z TestFramework.p2p (DEBUG): Send message to 127.0.0.1:12392: msg_ping(nonce=00000002)
node0 2026-10-15T07:19:58.731236Z (mocktime: 2026-10-15T07:48:45Z) [http.01] [httpserver.cpp:1318] [MaybeSendBytesFromBuffer] [http] Sent 148 bytes to client 127.0.0.1:57508 (id=0)
node0 2026-10-15T07:19:58.731307Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [logging/timer.h:58] [Log] [lock] ContendedLock: lock contention connman.m_nodes_mutex, ./net.h:1876 started
node0 2026-10-15T07:19:58.731317Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [logging/timer.h:58] [Log] [lock] ContendedLock: lock contention connman.m_nodes_mutex, ./net.h:1876 completed (0μs)
node0 2026-10-15T07:19:58.731332Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net_processing.cpp:3836] [ProcessMessage] [net] received: ping (8 bytes) peer=0
node0 2026-10-15T07:19:58.731338Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net.cpp:4220] [PushMessage] [net] sending pong (8 bytes) peer=0
node0 2026-10-15T07:19:58.731365Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net.cpp:4220] [PushMessage] [net] sending ping (8 bytes) peer=0
test 2026-10-15T07:19:58.731377Z TestFramework.p2p (DEBUG): Received message from 127.0.0.1:12392: msg_pong(nonce=00000000)
node0 2026-10-15T07:19:58.731388Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net_processing.cpp:6499] [SendMessages] Timeout downloading headers from noban peer, not disconnecting peer=0
node0 2026-10-15T07:19:58.731402Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net.cpp:4220] [PushMessage] [net] sending ping (8 bytes) peer=1
node0 2026-10-15T07:19:58.731421Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net.cpp:4220] [PushMessage] [net] sending getheaders (69 bytes) peer=1
node0 2026-10-15T07:19:58.731441Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net_processing.cpp:6151] [SendMessages] [net] initial getheaders (0) to peer=1
node0 2026-10-15T07:19:58.731461Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net_processing.cpp:3836] [ProcessMessage] [net] received: ping (8 bytes) peer=0
node0 2026-10-15T07:19:58.731466Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net.cpp:4220] [PushMessage] [net] sending pong (8 bytes) peer=0
test 2026-10-15T07:19:58.731579Z TestFramework.p2p (DEBUG): Received message from 127.0.0.1:12392: msg_ping(nonce=a011607af5f6e69c)
test 2026-10-15T07:19:58.731607Z TestFramework.p2p (DEBUG): Send message to 127.0.0.1:12392: msg_pong(nonce=a011607af5f6e69c)
test 2026-10-15T07:19:58.731633Z TestFramework.p2p (DEBUG): Received message from 127.0.0.1:12392: msg_pong(nonce=00000002)
node0 2026-10-15T07:19:58.731777Z (mocktime: 2026-10-15T07:48:45Z) [http] [httpserver.cpp:971] [Receive] [http] Received 339 bytes from 127.0.0.1:57508 (id=0): total=3476 buffered=339
node0 2026-10-15T07:19:58.731798Z (mocktime: 2026-10-15T07:48:45Z) [http] [httpserver.cpp:1135] [TryReadRequest] [http] Received a POST request for / from 127.0.0.1:57508 (id=0)
node0 2026-10-15T07:19:58.731833Z (mocktime: 2026-10-15T07:48:45Z) [http.00] [rpc/request.cpp:246] [parse] [rpc] ThreadRPCServer method=getpeerinfo user=__cookie__ id=32
node0 2026-10-15T07:19:58.732118Z (mocktime: 2026-10-15T07:48:45Z) [http.00] [httpserver.cpp:637] [Send] [http] HTTPResponse (status code: 200 size: 2260) added to send buffer for client 127.0.0.1:57508 (id=0)
test 2026-10-15T07:19:58.732309Z TestFramework (INFO): Check that exactly 1 of {peer1, peer2} receives a getheaders
test 2026-10-15T07:19:58.732370Z TestFramework (ERROR): Unexpected exception:
Traceback (most recent call last):
File "/home/runner/work/_temp/test/functional/test_framework/test_framework.py", line 146, in main
self.run_test()
~~~~~~~~~~~~~^^
File "/home/runner/work/_temp/build_ ₿🧪_/test/functional/p2p_initial_headers_sync.py", line 182, in run_test
self.test_noban_peer_timeout()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/home/runner/work/_temp/build_ ₿🧪_/test/functional/p2p_initial_headers_sync.py", line 177, in test_noban_peer_timeout
self.assert_single_getheaders_recipient([peer1, peer2])
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/home/runner/work/_temp/build_ ₿🧪_/test/functional/p2p_initial_headers_sync.py", line 66, in assert_single_getheaders_recipient
assert_equal(count, 1)
~~~~~~~~~~~~^^^^^^^^^^
File "/home/runner/work/_temp/test/functional/test_framework/util.py", line 95, in assert_equal
raise AssertionError("not(%s)" % " == ".join(str(arg) for arg in (thing1, thing2) + args))
AssertionError: not(0 == 1)
test 2026-10-15T07:19:58.733190Z TestFramework (DEBUG): Closing down network thread
node0 2026-10-15T07:19:58.733256Z (mocktime: 2026-10-15T07:48:45Z) [http.00] [httpserver.cpp:1318] [MaybeSendBytesFromBuffer] [http] Sent 2260 bytes to client 127.0.0.1:57508 (id=0)
test 2026-10-15T07:19:58.733311Z TestFramework.p2p (DEBUG): Received message from 127.0.0.1:58180: msg_ping(nonce=39768d79544b5e40)
test 2026-10-15T07:19:58.733337Z TestFramework.p2p (DEBUG): Send message to 127.0.0.1:58180: msg_pong(nonce=39768d79544b5e40)
test 2026-10-15T07:19:58.733367Z TestFramework.p2p (DEBUG): Received message from 127.0.0.1:58180: msg_getheaders(locator=CBlockLocator(vHave=[7041830694386478471858881810674310864173988660927928131397671070347943617030]), stop=0000000000000000000000000000000000000000000000000000000000000000)
node0 2026-10-15T07:19:58.733447Z (mocktime: 2026-10-15T07:48:45Z) [msghand] [net_processing.cpp:3836] [ProcessMessage] [net] received: pong (8 bytes) peer=0
test 2026-10-15T07:19:58.733502Z TestFramework.p2p (DEBUG): Closed connection to: 127.0.0.1:58180
node0 2026-10-15T07:19:58.733536Z (mocktime: 2026-10-15T07:48:45Z) [net] [net.cpp:2236] [SocketHandlerConnected] [net] socket closed, disconnecting peer=1
node0 2026-10-15T07:19:58.733546Z (mocktime: 2026-10-15T07:48:45Z) [net] [net.cpp:567] [CloseSocketDisconnect] [net] Resetting socket for peer=1
node0 2026-10-15T07:19:58.733596Z (mocktime: 2026-10-15T07:48:45Z) [net] [net_processing.cpp:1859] [FinalizeNode] [net] Cleared nodestate for peer=1
test 2026-10-15T07:19:58.783870Z TestFramework (INFO): Not stopping nodes as test failed. The dangling processes will be cleaned up later.
```

Diff to reproduce:

```diff
diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index beec44f55d..85b1e88161 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -87,2 +87,3 @@
#include <span>
+#include <thread>
#include <typeinfo>
@@ -5233,2 +5234,7 @@ void PeerManagerImpl::ProcessMessage(Peer& peer, CNode& pfrom, const std::string
MakeAndPushMessage(pfrom, NetMsgType::PONG, nonce);
+ // TEMPORARY: widen the p2p_initial_headers_sync race window after
+ // its second, nonzero ping has been sent but before SendMessages().
+ if (nonce != 0) {
+ std::this_thread::sleep_for(std::chrono::milliseconds{90});
+ }
}
```

Cmd to reproduce:

```
./bld-cmake/test/functional/test_runner.py $(for i in {1..20}; do echo -n "p2p_initial_headers_sync.py ";done) -j $( nproc )
```

(fails before this pull and passes after)

ACKs for top commit:
Crypt-iQ:
tACK fad7637529426f058a3c2409dd137009b14622a4
l0rinc:
lightly tested ACK fad7637529426f058a3c2409dd137009b14622a4

Tree-SHA512: 701c9d75ed68e806f95ddef34b59abbd943288be8f957708d112f9e02e7b370f10f267c1a22946dc38dc6ff20665fdd0ceda19ebfed18660ae6ebbcc779fc90b

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 discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit fixes a flaky automated test in Bitcoin Core. The test sometimes failed because it checked too quickly whether a network message had been sent. The fix makes the test wait until exactly one peer has received the expected message. There is no change to the actual Bitcoin node software that users run, so this has no security impact on real networks or wallets.

Lower-priorityMerge bitcoin/bitcoin#36552: refactor: drop lifetimebound `__has_attribute` checkby Hennadii Stepanov · 924f4c4a · Oct 16, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Hennadii Stepanov

Merge bitcoin/bitcoin#36552: refactor: drop lifetimebound `__has_attribute` check

84f8bfb9abc284e5f951264af4cdef7176db649b refactor: drop lifetimebound __has_attribute check (fanquake)

Pull request description:

`[[clang::lifetimebound]]` has been available since Clang 7.

ACKs for top commit:
maflcko:
lgtm ACK 84f8bfb9abc284e5f951264af4cdef7176db649b
stickies-v:
ACK 84f8bfb9abc284e5f951264af4cdef7176db649b
hebasto:
ACK 84f8bfb9abc284e5f951264af4cdef7176db649b.

Tree-SHA512: 32db50e12e15fc7b5a4744ac98c171a9003a8c552080b46746dacca3ce5a755347946e25f497ec167897fda51a3189c2055eb8a8d4835341c548dfc2991b2b3a

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
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36439: test: poll more frequently in sync helpers and RPC connection waitby merge-script · b13ba1a7 · Oct 16, 2026 · 2 filesMessage 100 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36439: test: poll more frequently in sync helpers and RPC connection wait

8898f832d9d86d5a6a8ad8719e1009c702bbf4bd test: poll more frequently in sync helpers and RPC connection wait (ViniciusCestarii)

Pull request description:

Tested on my x86-64 machine:

- Wall time (-j=18): 110.8s to 96.4s (−13%)
- Accumulated: 1715s to 1369s (−20%)

Also compared the CI on my fork (time for test_runner.py runtime):

- macOS native: [1287s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758264512#step:9:4745) to [1175s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791769239#step:9:4744) (-9%)
- 32 bit ARM: [776s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758264778#step:10:6336) to [690s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791769348#step:10:5806) (-11%)
- Windows native, VS: [1456s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758264639#step:14:1486) to [1252s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791768933#step:14:1486) (-14%)
- previous releases: [930s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758264815#step:10:5510) to [786s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791769195#step:10:6016) (-15%)
- No wallet: [614s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758264997#step:10:5421) to [572s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791769524#step:10:5813) (-7%)
- Alpine (musl): [1958s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37308619216/job/111758265011#step:10:5041) to [1970s](https://github.com/ViniciusCestarii/bitcoin/actions/runs/37318654530/job/111791769871#step:10:5489) (+0.6%)

Sanitizer jobs are left out because they vary too much between runs.

Alpine (musl) uses --usecli, so more frequent poll creates a new bitcoin-cli process each time, making it not faster with these changes. Also tried locally with --usecli: from 2060s to 2051s accumulated.

ACKs for top commit:
maflcko:
review ACK 8898f832d9d86d5a6a8ad8719e1009c702bbf4bd 👪

Tree-SHA512: f27f7636c5e6d678f9105189a910a2653fac9b5ca4dfdb132eec70cec5eea6489a8f7b8ced122fe95a080a57f325eb0ba230f6e6a21af3db8a402b117e77619a

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
defensive validationmerge-commit duplicate discount
Lower-priorityrefactor: drop lifetimebound __has_attribute checkby fanquake · 84f8bfb9 · Oct 16, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · fanquake

refactor: drop lifetimebound __has_attribute check

`[[clang::lifetimebound]]` has been available since Clang 7.

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityMerge bitcoin/bitcoin#35724: cmpctblock: Improve logging of `cmpctblock` message reconstruction statistics [part of prefill series]by merge-script · 89a3a13c · Oct 16, 2026 · 4 filesMessage 81 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#35724: cmpctblock: Improve logging of `cmpctblock` message reconstruction statistics [part of prefill series]

4f5ce816db1055b8d885113397c7215dc7af3c83 cmpctblock: log: Print sizes of all tx types and prefill redundancies (David Gumberg)
577eb5610e16b094672066016f6dc19b96c58486 cmpctblock: log: Log extrapool separately from mempool (David Gumberg)
a6cc3f30ef48e36e8262387a24af5f8dbb27289c cmpctblock: log: debuglevel=trace print TXID's of all missing tx'es. (David Gumberg)

Pull request description:

Split from #35558, this makes it easier to observe compact block reconstruction performance by:

- At debuglevel=trace logging all missing TX's in a CMPCTBLOCK, and all missing TX's requested from us.
- Logging the sizes and counts of tx's used from the prefill, mempool, and extrapool.
- Logging the sizes and sources of redundant transactions in the prefill section of received `CMPCTBLOCK`s.

ACKs for top commit:
0xB10C:
reACK 4f5ce816db1055b8d885113397c7215dc7af3c83
w0xlt:
reACK 4f5ce816db1055b8d885113397c7215dc7af3c83
andrewtoth:
reACK 4f5ce816db1055b8d885113397c7215dc7af3c83
optout21:
ACK 4f5ce816db1055b8d885113397c7215dc7af3c83
sedited:
utACK 4f5ce816db1055b8d885113397c7215dc7af3c83

Tree-SHA512: c8b42dbc52b86fd69d62b24f7a052e9692c1131cfd20b82fd0aa4a7d3300badde9e6665f9c2fe4e69cb1e43faf30e65b103646fc327360bcba43919570f9ef46

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
merge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36522: test: check MIN_PEER_PROTO_VERSION peers are not disconnectedby merge-script · 38ac0d53 · Oct 16, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36522: test: check MIN_PEER_PROTO_VERSION peers are not disconnected

5b07c48b8387f387530a90ce5b4a1224b6703aa3 test: check MIN_PEER_PROTO_VERSION peers are not disconnected (Greg Sanders)

Pull request description:

Kills mutant https://bitcoincore.space/src/net_processing.cpp#3442

```
diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index 61b8a4ecd8..73c91a5bd6 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -3647,7 +3647,7 @@ void PeerManagerImpl::ProcessMessage(Peer& peer, CNode& pfrom, const std::string
return;
}

- if (nVersion < MIN_PEER_PROTO_VERSION) {
+ if (nVersion <= MIN_PEER_PROTO_VERSION) {
// disconnect from peers older than this proto version
LogDebug(BCLog::NET, "peer using obsolete version %i, %s", nVersion, pfrom.DisconnectMsg());
pfrom.fDisconnect = true;
```

ACKs for top commit:
maflcko:
lgtm ACK 5b07c48b8387f387530a90ce5b4a1224b6703aa3
brunoerg:
ACK 5b07c48b8387f387530a90ce5b4a1224b6703aa3

Tree-SHA512: 2919287941128c0b1aec545cc6c21d3e44d185bd00bc120ee3e62cbded794aea31f54d44a5b5e340c9091206c0d3b826c91d2a62a76ba226cbd15641c3157948

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#36514: ci: Remove confusing -DBUILD_BENCH=ON -DBUILD_FUZZ_BINARY=ON from CONFIG_ALLby merge-script · 49b4b4ad · Oct 16, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36514: ci: Remove confusing -DBUILD_BENCH=ON -DBUILD_FUZZ_BINARY=ON from CONFIG_ALL

fa13e6e1751a4df4867f3fb742e12b5df749d4a8 ci: Refactor BITCOIN_CONFIG_ALL into array (MarcoFalke)
fac89d44e30f1b4028440ebad92ea42e8c02afb0 ci: Remove confusing -DBUILD_BENCH=ON -DBUILD_FUZZ_BINARY=ON from CONFIG_ALL (MarcoFalke)

Pull request description:

(see commit msg for details)

ACKs for top commit:
fanquake:
ACK fa13e6e1751a4df4867f3fb742e12b5df749d4a8

Tree-SHA512: 79f1a1a6c26ec50f105d3a9a7efbfe5737d13bc57799ec4ef0066fb53de9582d463ede097c7929ffaad76c4dfdfa51047307425a9f7f07528e59d782a8db0092

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
fuzzing or regression evidencemerge-commit duplicate discount
Lower-priorityMerge bitcoin/bitcoin#36544: test: Fix intermittent issue in p2p_eviction.pyby merge-script · 87fbedf5 · Oct 16, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · merge-script

Merge bitcoin/bitcoin#36544: test: Fix intermittent issue in p2p_eviction.py

fa9a9657506dc742e657b2a288baed84873304f1 test: Fix intermittent issue in p2p_eviction.py (MarcoFalke)

Pull request description:

Fixes https://github.com/bitcoin/bitcoin/issues/36533 by waiting for the socket to actually close on the Python side.

A diff to reproduce (with a minimal fix commented out) is in the issue thread.

The fix here rhymes on the minimal fix.

ACKs for top commit:
ViniciusCestarii:
tACK fa9a9657506dc742e657b2a288baed84873304f1

Tree-SHA512: 1b185844acde6d8d93548f85709fa04d0b5ce5a25dd128699f2d6a197e373b80b039e6f168669624ad3d088e24fba48f628ed149760914a4afc135cfd0d9cc06

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