RB
← All projectsRust Bitcoin

rust-bitcoin

Rust library for Bitcoin data structures, serialization, consensus encoding, and scripts.

BitcoinCryptographic librariesNormal
Repository coverage

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

612security candidates555second-pass queue2330AI analyses
153commits · 30 days
280commits · 60 days
977commits · 180 days
2058commits · 365 days
Backfill bands
Aug 5 → Feb 6787 seen32 candidatesComplete
Feb 6 → Jun 6878 seen53 candidatesComplete
Jun 6 → Jul 6211 seen15 candidatesComplete
Jul 6 → Aug 5184 seen2 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.

68/100 average clarity
702Strong · 80–100
1135Adequate · 60–79
582Thin · 40–59
151Opaque · 0–39
20security 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.
Andrew Poelstra407139251391
Mitchell Bagot659200654068
Tobin C. Harding42167411063
jrakibi1015096069
satsfy (Renato Britto)652235065
Nick Johnson19621190060
Jamil Lambert, PhD12619117062
Fmt Bot351532045
Trevor Arjeski111111069
Shing Him Ng31731056
Martin Habovstiak31629069
Ismail Daif22622050
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7220: refactor(bip32)!: replace KeySource with KeyOrigin

This is a routine code cleanup in a Bitcoin library. It renames a simple data container from KeySource to KeyOrigin and gives it named fields (fingerprint and path) instead of numbered tuple slots (.0 and .1). The serialized format is inte…

6bb507b2by Andrew Poelstra+84−33 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto dep

This change is a routine internal cleanup: the key_expression crate stops depending directly on the secp256k1 cryptography library and instead uses a re-export provided by another internal crate called crypto. No user-facing behavior, type…

d193efc5by Andrew Poelstra+7−107 files
No security note in commit
Informational 17 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Forward serde feature to network

This is a small Cargo.toml fix in a Rust Bitcoin subcrate. When the optional 'serde' feature was enabled on the key_expression crate alone, it did not also enable serde on the network crate. That meant a type called NetworkKind could not b…

806f1e1fby bytescape30+1−11 file
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7223: build(deps): bump taiki-e/install-action from 2.87.9 to 2.87.13

This is a routine update to a GitHub Actions helper used in automated testing workflows. It bumps the version of taiki-e/install-action, which downloads and installs Rust developer tools during CI runs. There is no change to the actual Bit…

c8ee144aby Andrew Poelstra+2−22 files
No security note in commit
Informational 20 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7224: build(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0

This is a routine update to a GitHub Actions helper used only in automated security-scanning workflows. The new version adds minor improvements, including respecting proxy settings and verifying downloaded files with checksums. It does not…

Dependency bump of a third-party GitHub Action used in CI onlyUpstream release notes mention generic security improvements (checksum verification, npm install defaults, NO_PROXY)No CVE, advisory, or vendor security disclosure is present in the commit or supplied references
7bc9d696by Andrew Poelstra+2−22 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising crates

This commit removes automatic serde (serialization/deserialization) code generation from several Rust Bitcoin library crates and replaces it with hand-written implementations. The stated goal is to reduce dependencies and make the code eas…

Manual serde implementations replace derived ones, increasing the surface area for serialization-format bugsNo validation logic changes are visible in the diffNo mention of security fixes, CVEs, or vulnerability reports in commit message or PR description
9eeb7774by Andrew Poelstra+219−4110 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7205: Manual update to rustc stable (to 1.100.0)

This commit updates the project's automated Rust compiler version from 1.99.1 to 1.100.0 and adjusts a CI cache cleanup script to match a new directory layout used by Cargo 1.100. It is purely an infrastructure/maintenance change to keep a…

44e6f0caby Andrew Poelstra+8−22 files
No security note in commit
Informational 18 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leak

This is a build-system improvement, not a code change. It updates a CI helper tool and makes the automated API-checking job fail if a private internal crate accidentally becomes part of the public API. That prevents future leaks of interna…

CI guardrail added to prevent private dependency leaks into stable crate public APIsTool bump enables detection of re-exported private dependenciesNo source-code vulnerability is patched
be14c72eby Andrew Poelstra+7−12 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructors

This is a minor internal code cleanup in the Rust Bitcoin library. It changes how two functions (Xpriv::decode and Xpub::decode) build their error messages when an input is the wrong length. The behavior is the same before and after; only …

271f662aby Andrew Poelstra+8−61 file
No security note in commit
Informational 24 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`

This is a routine API cleanup, not a security fix. The change removes one way of naming a Bitcoin unit ('MicroBitcoin' / 'uBTC') and keeps the equivalent 'bits' form. Any code that previously used the old name will fail to compile or fail …

No security signal: public API deprecation and enum variant removalNo memory safety, cryptographic, or consensus code modifiedError message change is informational only
d0602195by Andrew Poelstra+53−403 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal types

This commit is a code cleanup and feature-gating refactor for the rust-bitcoin library's key_expression crate. It makes more BIP32 (Bitcoin wallet key derivation) types available when the 'alloc' memory allocator feature is disabled, and s…

Refactor of error types and parsing paths for Xpriv/Xpub base58 decodingSwitch from unbounded base58 decode to fixed-size array decode (78 bytes)Removal of explicit length-check error path in favor of decoder-reported length error
c3d27d5dby Andrew Poelstra+60−823 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7039: primitives: Fix daily Miri cron failures with measured test gating

This change only adds `#[cfg_attr(miri, ignore)]` annotations to a handful of slow unit tests so they are skipped when run under Miri, a Rust interpreter used for detecting undefined behavior. It does not change any production code, consen…

1dc09077by Andrew Poelstra+6−03 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7182: Update local dependencies

This commit only updates version numbers in package configuration files (Cargo.toml) for internal dependencies so that all crates in the project require the same minimum versions of shared libraries. There are no code changes, no bug fixes…

06f41225by Andrew Poelstra+7−75 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7179: build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9

This is a routine update to a GitHub Actions helper used in automated testing workflows. It changes which version of a third-party tool-installer action is used, but only for installing the cargo-mutants testing tool. There is no indicatio…

4fda66b5by Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This commit updates the version of a helper tool called cargo-binstall used in two automated GitHub workflows. The change only affects internal build/CI tooling and does not alter the rust-bitcoin library code that users install or run. Th…

53eae24dby Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security scanning workflow. It changes one pinned commit hash to a newer version of the same action. There is no indication this introduces…

4bb555f0by Andrew Poelstra+1−11 file
No security note in commit
Informational 15 AI analysisMessage 81 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Flatten BIP32 decode error construction

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how an error message is built when decoding BIP32 extended keys, switching from one nested construction style to two chained calls. The actual behavior and returne…

c31c11e0by Adewale Ijalana+8−61 file
No security note in commit
Low 36 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7168: units: add `visit_units` in optional serde visitors

This commit fixes a bug in how optional Bitcoin amount and fee-rate values are read from JSON when those fields are inside a flattened struct and the value is null. Previously, the code would error out because it did not handle a special s…

Deserialization failure in optional numeric types under serde flattenMissing serde visitor method (visit_unit) causing runtime errorsRegression test added for null handling in flattened structs
47340d2fby Andrew Poelstra+79−03 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump github/codeql-action/upload-sarif

This is a routine dependency update by Dependabot, bumping the version of a GitHub-provided action used to upload security scan results. There is no indication of a security vulnerability in the project itself or in this change.

fe755619by dependabot[bot]+1−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This is a routine automated update by Dependabot that changes the version of a GitHub Action used to install Rust tools in two CI workflows. There is no indication of a security issue in the commit itself, and no verified security referenc…

2ccb0029by dependabot[bot]+2−22 files
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 rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructorsby Andrew Poelstra · 271f662a · Nov 13, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructors

c31c11e0635791bfb871c0f7f42035ddc292070c key_expression: Flatten BIP32 decode error construction (Adewale Ijalana)

Pull request description:

This PR is in relation to the error-handling pattern proposed in [#6539](https://github.com/rust-bitcoin/rust-bitcoin/issues/6539.)

Replace nested error construction with chained map_err calls in
Xpriv::decode and Xpub::decode.


ACKs for top commit:
tcharding:
ACK c31c11e0635791bfb871c0f7f42035ddc292070c
apoelstra:
ACK c31c11e0635791bfb871c0f7f42035ddc292070c; successfully ran local tests


Tree-SHA512: ca7860eb90ea7daaf3201512d6e5e09ce508623fbb586484741d972b4c9a63144eb77d036642f712c38137d7db87af5910671b74d50d4f58f982dd7349d97d7b

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
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a minor internal code cleanup in the Rust Bitcoin library. It changes how two functions (Xpriv::decode and Xpub::decode) build their error messages when an input is the wrong length. The behavior is the same before and after; only the style of the code changed. There is no security issue.

Security candidateMerge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`by Andrew Poelstra · d0602195 · Nov 13, 2026 · 3 filesMessage 93 · StrongInformational 24Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`

f70e925b7a8ee164f8809f26a45b5dd8301a4bf4 units: remove Denomination::MicroBitcoin (satsfy (Renato Britto))

Pull request description:

Forward note: the goal of this PR is ending [the `MicroBitcoin` discussion](https://github.com/rust-bitcoin/rust-bitcoin/issues/3865#issuecomment-6671175891) with NACKs or ACKs already.

This PR makes `MicroBitcoin` (uBTC) and micro sign forms parse into `Bit`. `Bit` and `MicroBitcoin` are the same 100 sat unit. The issue is these two variants, of equal magnitude, prevent use from using a derived `Ord` in `Denomination` and make `Eq` misleading, as well as be confusing and ugly. This is our chance to fix it, we can always add later after 1.0, but never remove.

Quick history on the subject:
- Not much reason was provided for adding `MicroBitcoin` in [#270](https://github.com/rust-bitcoin/rust-bitcoin/pull/270). Came with no rationale, neither variant is mentioned in the review, and every thread that mentioned that touched this did so tangentially, because it was about something else. The idea of dropping it has been [floated](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605422418) [around](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605438327) [before](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605424530).
- Issue [#729](https://github.com/rust-bitcoin/rust-bitcoin/issues/729) plural and singular forms accepted inconsistently
- Issue [#2820](https://github.com/rust-bitcoin/rust-bitcoin/issues/2820) / PR [#2870](https://github.com/rust-bitcoin/rust-bitcoin/pull/2870) removed MilliSatoshi, Nano and Pico as breaking
- Issue [#3865](https://github.com/rust-bitcoin/rust-bitcoin/issues/3865) should stable crates derive Ord on enums
- PR [#3866](https://github.com/rust-bitcoin/rust-bitcoin/pull/3866) / PR [#3934](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934) derive vs manual Ord, both closed without Ord
- Issue [#3941](https://github.com/rust-bitcoin/rust-bitcoin/issues/3941) / PR [#3943](https://github.com/rust-bitcoin/rust-bitcoin/pull/3943) µBTC spelling in docs and parsing
- Issue [#6353](https://github.com/rust-bitcoin/rust-bitcoin/issues/6353) (still open) Ord blocked by duplicate magnitude

Using GitHub code search, I cannot find any big project using either [`Bit`](https://github.com/search?type=code&q=%2FDenomination%3A%3ABit%5Cb%2F%20language%3ARust%20NOT%20path%3Aamount.rs) or [`MicroBitcoin`](https://github.com/search?type=code&q=%2FDenomination%3A%3AMicroBitcoin%5Cb%2F%20language%3ARust%20NOT%20path%3Aamount.rs) outside rust-bitcoin forks.

Arguments for:
- [BIP 176](https://github.com/bitcoin/bips/blob/master/bip-0176.mediawiki) (Status: Complete) declare that bits is "the standard term for 100 satoshis".
- Bitcoin Core has relabelled µBTC to bits in https://github.com/bitcoin/bitcoin/pull/12035 two weeks after the BIP. Today [`bitcoinunits.cpp`](https://github.com/bitcoin/bitcoin/blob/d0f6d9953a15d7c7111d46dcb76ab2bb18e5dee3/src/qt/bitcoinunits.cpp#L36-L47) has one unit, long name `µBTC (bits)`, short name `bits`.
- Electrum has [`BTC, mBTC, bits, sat`](https://github.com/spesmilo/electrum/blob/master/electrum/util.py#L101-L103), but no µBTC.
- Coinbase shipped a [bits display option](https://www.coinbase.com/blog/its-bits) in 2014.
- Modern wallets dropped the unit altogether. [BlueWallet](https://github.com/BlueWallet/BlueWallet/blob/master/models/bitcoinUnits.ts) and Sparrow offer BTC and sats only. When users ask for it back they ask for bits, [sparrow#777](https://github.com/sparrowwallet/sparrow/issues/777) "to match Bitcoin Core (and most other wallets)", [btcpayserver#250](https://github.com/btcpayserver/btcpayserver/issues/250).
- The [Bitcoin Design Guide](https://bitcoin.design/guide/designing-products/units-and-symbols/) writes it "μBTC (bits)" and names the row `bit`.
- The [Bitcoin wiki](https://en.bitcoin.it/wiki/Units) marks `bit` as the frequent name for the micro-bitcoin.
- No wallet prints `uBTC`, which is what our `MicroBitcoin` displays as.

Arguments against:
- [BIP 177](https://github.com/bitcoin/bips/blob/master/bip-0177.mediawiki#addressing-alternative-approaches) (Status: Draft) refutes BIP 176 as "the Bits Proposal". However, it never direclty mentions µBTC, or develop it as an alternative.
- Blockstream [GDK](https://github.com/Blockstream/gdk/blob/master/docs/source/gdk-json.rst) offers both `"ubtc"` and `"bits"` as separate display units, same duplication we have.

This decision is arbitrary and causes us annoyance. I believe we can just declare that `bits` is the "consensus" name for this unit, no need to carry these 2 around. We can always add MicroBitcoin later, post 1.0. And, given the slowness, by the time these BIP discussions conclude, we may even be launching units 2.0.0+ already, so we can do another breaking change.

By ACKing this, you would be making a pragmatic decision in perfect agreement with the current BIP consensus (which may change later).


ACKs for top commit:
tcharding:
ACK f70e925b7a8ee164f8809f26a45b5dd8301a4bf4
Kixunil:
ACK f70e925b7a8ee164f8809f26a45b5dd8301a4bf4


Tree-SHA512: 46ce47703a80f9316d9402fa3ce696842ca71c653383a369750a218e9f00d4290b99338cec0023a148a9674fc9b34dabbf0215d273ed4f54144d7a8db493a5db

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryaccess controlconsensus or confidential-proof validationmerge-commit duplicate discount
AI analysis · Informational 24/100

This is a routine API cleanup, not a security fix. The change removes one way of naming a Bitcoin unit ('MicroBitcoin' / 'uBTC') and keeps the equivalent 'bits' form. Any code that previously used the old name will fail to compile or fail to parse those strings, but there is no vulnerability being fixed and no new attack path being opened.

Lower-priorityAutomated update to rustc stable-1.100.0by Update Stable Rustc Bot · 62e72d6e · Nov 13, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Update Stable Rustc Bot

Automated update to rustc stable-1.100.0

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7159: p2p: add defensive check to unbounded Unknown buffering, add more error variantsby Andrew Poelstra · 21e19791 · Nov 10, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7159: p2p: add defensive check to unbounded Unknown buffering, add more error variants

ec4fa1639e887e5c4dc2c167b568eaa8dc93e438 p2p: remove the Empty variant in favor of 7 explicit ones (Nick Johnson)
cf306aadb8470c32a9d1cf33fbd3ed6f94a3995f p2p: give the network message error explicit variants (Nick Johnson)
732c9c925c750b8a184d925a3d3e4a3ca67e4a28 p2p: add a defensive fail safe for unbounded Unknown buffering (Nick Johnson)

Pull request description:

Follow up to #7155. The first commit adds a defensive check to the unbounded buffering introduced in #7155. The higher level V1 and V2 decoders should still do the framing, this is just to protect against bad implementations. I don't think the cost is too high assuming the `Unknown` path is relatively cold.

Adding an error variant for this failure case made me realize the errors of the decoders left a lot to be desired. So added variants for the failures and routed them up.


ACKs for top commit:
tcharding:
ACK ec4fa1639e887e5c4dc2c167b568eaa8dc93e438
apoelstra:
ACK ec4fa1639e887e5c4dc2c167b568eaa8dc93e438; successfully ran local tests


Tree-SHA512: 08ee9866a7e910a9b261e5e38dd729e900903b1cb3412eb0c6ff9a3676879880e8440d91fe3a46737fd22dcdb90128e2d8afaedefd3637450b4009c0445f179d

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 rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal typesby Andrew Poelstra · c3d27d5d · Nov 10, 2026 · 3 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal types

9b23b16241fc6ddaca5c55f2a85e9b2f160993f6 Remove unused errors and variants (Mitchell Bagot)
b48052c31731e6ce21dd9e5ae7bfbddd4de83bbd Ungate FromStr and Display for Xpriv and Xpub (Mitchell Bagot)
1f13455f1fd6cba340ea3cbfcee49ad5a6410de0 Gate individual items in bip32 instead of whole module (Mitchell Bagot)
df894f30da75b858fb0925de02e5dc2e51b4c05e Add optional feature gate to impl_array_newtype macro (Mitchell Bagot)

Pull request description:

The key_expression crate currently gates all functionality on alloc. However, most of the bip32 module does not depend on alloc, outside of a few types. Instead of gating the entire module on alloc, only the inner types and functionality that truly depend on alloc should be gated. With the new base58 functionality, this can be achieved with minimal changes.

Adjust gating to only gate minimal types and functionality on alloc.
Adjust FromStr+Display on X key types to use no-alloc base58.
Adjust ParseXp*Error types to support no-alloc base58 errors.


ACKs for top commit:
tcharding:
ACK 9b23b16241fc6ddaca5c55f2a85e9b2f160993f6
apoelstra:
ACK 9b23b16241fc6ddaca5c55f2a85e9b2f160993f6; successfully ran local tests


Tree-SHA512: 1df13fcc0af1412ffe8e077cb76cb47a3f797b70837ffdfb52f3ede963c1910a78c672139cb6b8901f8f767ce3ddcb3ad2e49996734af369f0da796ef2b6eca6

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
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit is a code cleanup and feature-gating refactor for the rust-bitcoin library's key_expression crate. It makes more BIP32 (Bitcoin wallet key derivation) types available when the 'alloc' memory allocator feature is disabled, and switches Xpriv/Xpub string parsing to use a no-alloc base58 decoder. There is no direct security vulnerability visible in the diff; it is primarily a maintainability and no-alloc compatibility improvement.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7039: primitives: Fix daily Miri cron failures with measured test gatingby Andrew Poelstra · 1dc09077 · Nov 10, 2026 · 3 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7039: primitives: Fix daily Miri cron failures with measured test gating

2c096d0b41b8da11e4909186ecaa8282330cf06f primitives: Gate Miri tests by measured cost, not buffer size (bytescape30)

Pull request description:

Close #6982

This PR gates Miri tests by their measured cost under Miri instead of by buffer size:

#[cfg_attr(miri, ignore)] is already an established pattern in this crate for exactly this situation

<details><summary>Measurements</summary>

| Test | Wall time | Peak RSS | Gated |
|---|---|---|---|
| `decode_max_serialized_size` | ~51-54 min | ~1.66 GB | yes |
| `block_decoder_rejects_aggregate_weight_over_limit` | ~2.7 s | ~305 MB | **no** |
| `accept_transaction_at_maximum_block_weight` | ~57-62 s | ~760-822 MB | yes |
| `reject_transaction_exceeding_maximum_block_weight` | ~59-62 s | ~616-665 MB | yes |
| `decode_rejects_witness_over_limit_due_to_aggregate_data` | ~5.1-5.3 min | ~1.34-1.38 GB | yes |
| `decode_rejects_witness_over_limit_due_to_prefix_overhead` | >12 h (killed) | not measured | yes |
| `block_rejects_oversized_trailing_coinbase_witness_item` | ~54.8 min | ~1.56 GB | yes |
| `compute_wtxid_commits_to_oversized_witness_elements` | ~4.8 min | ~290 MB | **no** |

</details>


ACKs for top commit:
satsfy:
ACK 2c096d0b41b8da11e4909186ecaa8282330cf06f
tcharding:
ACK 2c096d0b41b8da11e4909186ecaa8282330cf06f
apoelstra:
ACK 2c096d0b41b8da11e4909186ecaa8282330cf06f; successfully ran local tests
Kixunil:
ACK 2c096d0b41b8da11e4909186ecaa8282330cf06f


Tree-SHA512: 6398d9004a0212ded0b4bd0d1ae067c5ebc0c07b41376adbcec37a316bc4202505ebfe27f018ab5a80a428030db930b3bf96bef983a46b3416a2dc592e78ac2c

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 change only adds `#[cfg_attr(miri, ignore)]` annotations to a handful of slow unit tests so they are skipped when run under Miri, a Rust interpreter used for detecting undefined behavior. It does not change any production code, consensus logic, or public APIs. The purpose is to stop daily automated Miri CI jobs from timing out or being killed due to extremely long-running tests. There is no security impact on users of the library.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7182: Update local dependenciesby Andrew Poelstra · 06f41225 · Nov 9, 2026 · 5 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7182: Update local dependencies

3996a94275afe7a8e596e69fb6ad7909582d6e3a Update encoding dependency (Tobin C. Harding)
83e16194c99d0ecbb7e3e0346fed42c5473d4219 Update hashes dependency (Tobin C. Harding)

Pull request description:

Transient dependencies have to have the same or lower version and since `primitives` depends on `hashes 1.1.0` and `encoding 1.3.0` all crates higher up the stack have to have the same minimum.

Update all required manifests.


ACKs for top commit:
apoelstra:
ACK 3996a94275afe7a8e596e69fb6ad7909582d6e3a; successfully ran local tests


Tree-SHA512: 8018ff7e16d34c52222e23d2b7f54f9f173b0863d5de635de42392823ccca89eaf9dc9cabae90201c8e982d81533f70f3d994e8dee89965c2214c408b3fcc942

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 only updates version numbers in package configuration files (Cargo.toml) for internal dependencies so that all crates in the project require the same minimum versions of shared libraries. There are no code changes, no bug fixes, and no security-related content in the commit message or diff.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7173: Automated weekly update to rustc (to nightly-2026-11-07) on masterby Andrew Poelstra · 04562f10 · Nov 9, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7173: Automated weekly update to rustc (to nightly-2026-11-07) on master

61d93c0fe218601757176ce4768db96107ef0dc6 Automated update to rustc nightly-2026-11-07 (Update Nightly Rustc Bot)

Pull request description:

Automated update to Cargo.toml workspace metadata by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action


ACKs for top commit:
tcharding:
ACK 61d93c0fe218601757176ce4768db96107ef0dc6
satsfy:
ACK 61d93c0fe218601757176ce4768db96107ef0dc6


Tree-SHA512: 255e6de99f650baa7e08f67c0ff1e60ff73ac03c500bb7f50b8628652106b7fe4e9149a5f676ef4e3b8cfdabbbeb2f7f51ea4830c66b29d7c97f41f3af03c08a

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 rust-bitcoin/rust-bitcoin#7172: Release tracking PR: `chacha20-poly1305` 0.3.0by Andrew Poelstra · 34de2971 · Nov 9, 2026 · 5 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7172: Release tracking PR: `chacha20-poly1305` 0.3.0

b00a27145180445dada778be787a20d27cf8c78a chacha20_poly1305: bump version to 0.3.0 (Nick Johnson)

Pull request description:

Closes #7170


ACKs for top commit:
apoelstra:
ACK b00a27145180445dada778be787a20d27cf8c78a; successfully ran local tests


Tree-SHA512: b054d30ef25ef1cdde09134a6dfa261ada8f351214600a374d97354902bf077265cc22c6b2e4bddef21ca7d7677d0514fc434931da558bdee6c022b4e0d88c7d

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 rust-bitcoin/rust-bitcoin#7179: build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9by Andrew Poelstra · 4fda66b5 · Nov 9, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7179: build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9

054e0d73c502cfdb702ca57d96ea798555ec96a3 build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.4 to 2.87.9.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p>
<blockquote>
<h2>2.87.9</h2>
<ul>
<li>
<p>Update <code>oxfmt@latest</code> to 1.82.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.9.2.</p>
</li>
<li>
<p>Update <code>kache@latest</code> to 0.18.0.</p>
</li>
<li>
<p>Update <code>d2@latest</code> to 0.9.0.</p>
</li>
<li>
<p>Update <code>bpf-linker@latest</code> to 0.11.1.</p>
</li>
</ul>
<h2>2.87.8</h2>
<ul>
<li>
<p>Update <code>shfmt@latest</code> to 3.14.1.</p>
</li>
<li>
<p>Update <code>release-plz@latest</code> to 0.3.162.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.26.0.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.57.4.</p>
</li>
<li>
<p>Update <code>cargo-llvm-cov@latest</code> to 0.9.1.</p>
</li>
<li>
<p>Update <code>cargo-crap@latest</code> to 0.5.0.</p>
</li>
<li>
<p>Update <code>cargo-binstall@latest</code> to 1.23.0.</p>
</li>
</ul>
<h2>2.87.7</h2>
<ul>
<li>
<p>Update <code>wasm-bindgen@latest</code> to 0.2.128.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.10.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.5.2.</p>
</li>
<li>
<p>Update <code>rclone@latest</code> to 1.75.1.</p>
</li>
</ul>
<h2>2.87.6</h2>
<ul>
<li>
<p>Update <code>rafn@latest</code> to 0.1.6.</p>
</li>
<li>
<p>Update <code>editorconfig-checker@latest</code> to 3.11.3.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.57.1.</p>
</li>
<li>
<p>Update <code>convco@latest</code> to 0.7.2.</p>
</li>
</ul>
<h2>2.87.5</h2>
<ul>
<li>
<p>Update <code>vacuum@latest</code> to 0.30.3.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.9.</p>
</li>
<li>
<p>Update <code>typos@latest</code> to 1.50.1.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this file.</p>
<p>This project adheres to <a href="https://semver.org">Semantic Versioning</a>.</p>
<!-- raw HTML omitted -->
<h2>[Unreleased]</h2>
<h2>[2.90.3] - 2026-11-08</h2>
<ul>
<li>
<p>Update <code>yq@latest</code> to 4.54.2.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.39.3.</p>
</li>
<li>
<p>Update <code>syft@latest</code> to 1.57.0.</p>
</li>
<li>
<p>Update <code>rclone@latest</code> to 1.76.0.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.30.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.11.3.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.17.0.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.6.6.</p>
</li>
</ul>
<h2>[2.90.2] - 2026-11-06</h2>
<ul>
<li>
<p>Update <code>trivy@latest</code> to 0.76.2.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.10.0.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.10.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.11.2.</p>
</li>
<li>
<p>Update <code>mdbook-d2@latest</code> to 0.3.10.</p>
</li>
<li>
<p>Update <code>cargo-zigbuild@latest</code> to 0.24.1.</p>
</li>
<li>
<p>Update <code>cargo-tarpaulin@latest</code> to 0.37.6.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.6.5.</p>
</li>
</ul>
<h2>[2.90.1] - 2026-11-04</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taiki-e/install-action/commit/c3ec0de9ae7f1019cea21aa96aa0a895b9552063"><code>c3ec0de</code></a> Release 2.87.9</li>
<li><a href="https://github.com/taiki-e/install-action/commit/d02aebd50f4b1a0621b3c44dc1a2b7f3f61ff8cb"><code>d02aebd</code></a> Update zizmor manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/3d0eb19ef046fd21f9b4dc6b0fc30d171f13033a"><code>3d0eb19</code></a> Update uv manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/65ddcfa24277c2ff2dc7fb01237e8e7f6fe41480"><code>65ddcfa</code></a> Update tombi manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b89e7fc94c8c0376338394d0880d5754a0158bfa"><code>b89e7fc</code></a> Update release-plz manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/376cef3d9362f17fe5cf9c3fde1bf62a83e8dbc4"><code>376cef3</code></a> Update <code>oxfmt@latest</code> to 1.82.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/f59b306e71ab373b0c7c127527fe7b03270a0776"><code>f59b306</code></a> Update <code>mise@latest</code> to 2026.9.2</li>
<li><a href="https://github.com/taiki-e/install-action/commit/e7645b1489fda5fc5735cd55bb54a31ad0514aa7"><code>e7645b1</code></a> Update kingfisher manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/a11264fead47aa030dc0707eab90f992579b9f16"><code>a11264f</code></a> Update <code>kache@latest</code> to 0.18.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/78328ffc219bcc9e18006466c41f32625576b520"><code>78328ff</code></a> Update <code>d2@latest</code> to 0.9.0</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/e67fa11c4b9316fa714ddf0abed07a0c3143b95b...c3ec0de9ae7f1019cea21aa96aa0a895b9552063">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=taiki-e/install-action&package-manager=github_actions&previous-version=2.87.4&new-version=2.87.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>


ACKs for top commit:
tcharding:
ACK 054e0d73c502cfdb702ca57d96ea798555ec96a3
apoelstra:
ACK 054e0d73c502cfdb702ca57d96ea798555ec96a3; successfully ran local tests


Tree-SHA512: 226abbe652dea3ccfc02b3dd4b02928208ab13f80d72a0a89a3e5ca77e495024e5a4a856376e2d5398b2c5b01d3362f92b2f93a85519c9a298a51d94956e2cfc

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
documentation-only discountautomated dependency-update discountmerge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine update to a GitHub Actions helper used in automated testing workflows. It changes which version of a third-party tool-installer action is used, but only for installing the cargo-mutants testing tool. There is no indication this affects the actual rust-bitcoin library code, user-facing behavior, or introduces a security vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0by Andrew Poelstra · 53eae24d · Nov 9, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

2ccb002995982586511810e1d726e23b8017e361 build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0 (dependabot[bot])

Pull request description:

Bumps [cargo-bins/cargo-binstall](https://github.com/cargo-bins/cargo-binstall) from 1.22.0 to 1.23.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/cargo-bins/cargo-binstall/releases">cargo-bins/cargo-binstall's releases</a>.</em></p>
<blockquote>
<h2>v1.23.0</h2>
<p><em>Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for <code>cargo install</code> in most cases. Install it today with <code>cargo install cargo-binstall</code>, from the binaries below, or if you already have it, upgrade with <code>cargo binstall cargo-binstall</code>.</em></p>
<h4>In this release:</h4>
<ul>
<li>prefix human-readable logs with cargo-binstall (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2575">#2575</a> <a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2645">#2645</a>)</li>
</ul>
<h4>Other changes:</h4>
<ul>
<li>Upgrade dependencies</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/b874e25ea559687bec77e281e9b271aa1367b624"><code>b874e25</code></a> release: cargo-binstall v1.23.0 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2655">#2655</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/92a3953f1755f3d00440b0114b709417f02325a0"><code>92a3953</code></a> chore: release (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2648">#2648</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/5baa19648a0d200b36a812f563a83ebfd2e06820"><code>5baa196</code></a> fix: prefix human-readable logs with cargo-binstall (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2645">#2645</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/bbdafe4f550ab376e1ef06325461f613d9a24851"><code>bbdafe4</code></a> build(deps): bump astral-tokio-tar from 0.6.4 to 0.7.0 in the deps group (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2654">#2654</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/9ef12faecb70a6811561bc924b14c09230a9b77e"><code>9ef12fa</code></a> dep: Upgrade transitive dependencies (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2653">#2653</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/5aafaaca52423a22d83a812fa3ca77492e2895db"><code>5aafaac</code></a> dep: Upgrade transitive dependencies (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2647">#2647</a>)</li>
<li>See full diff in <a href="https://github.com/cargo-bins/cargo-binstall/compare/75b4bfae1b2c753a6806bbce6e6cb89b602de33c...b874e25ea559687bec77e281e9b271aa1367b624">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cargo-bins/cargo-binstall&package-manager=github_actions&previous-version=1.22.0&new-version=1.23.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>


ACKs for top commit:
tcharding:
ACK 2ccb002995982586511810e1d726e23b8017e361
apoelstra:
ACK 2ccb002995982586511810e1d726e23b8017e361; successfully ran local tests


Tree-SHA512: ed7a238f71936e1bd306cc090a15d3e00803f76e6dfdfb5ea913e347364c0828097efe2941218ffc1929220fa11415d09c5cac5b030a4fdd70a2536699abd62e

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
access controldocumentation-only discountautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit updates the version of a helper tool called cargo-binstall used in two automated GitHub workflows. The change only affects internal build/CI tooling and does not alter the rust-bitcoin library code that users install or run. There is no indication this update fixes a security issue or introduces a vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0by Andrew Poelstra · 4bb555f0 · Nov 9, 2026 · 1 fileMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

fe755619b3416a1a6d26677ec52d95fcd2959aa7 build(deps): bump github/codeql-action/upload-sarif (dependabot[bot])

Pull request description:

Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.37.9 to 4.38.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/releases">github/codeql-action/upload-sarif's releases</a>.</em></p>
<blockquote>
<h2>v4.38.0</h2>
<ul>
<li>On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. <a href="https://redirect.github.com/github/codeql-action/pull/4124">#4124</a></li>
<li>The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native <code>linux-arm64</code> CodeQL bundle when available. <a href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.0">2.27.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4129">#4129</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action/upload-sarif's changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p>
<h2>[UNRELEASED]</h2>
<p>No user facing changes.</p>
<h2>4.39.3 - 04 Nov 2026</h2>
<ul>
<li>Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. <a href="https://redirect.github.com/github/codeql-action/pull/4283">#4283</a></li>
</ul>
<h2>4.39.2 - 03 Nov 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.4">2.27.4</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4284">#4284</a></li>
<li><em>Upcoming breaking change</em>: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. <a href="https://redirect.github.com/github/codeql-action/pull/4266">#4266</a></li>
<li>Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See <a href="https://github.blog/changelog/2026-10-19-codeql-changes-for-macos-27-xcode-27-and-swift-6-4/">this blog post for more information</a>. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the <a href="https://docs.github.com/en/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning">Tool Status Page</a>. This check will be rolled out following this release of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/4221">#4221</a></li>
<li>The undocumented TRAP cache cleanup feature that could be enabled using the <code>CODEQL_ACTION_CLEANUP_TRAP_CACHES</code> environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The <code>analyze</code> Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the <code>trap-caching: false</code> input to the <code>init</code> Action. <a href="https://redirect.github.com/github/codeql-action/pull/4243">#4243</a></li>
</ul>
<h2>4.39.1 - 21 Oct 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.3">2.27.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4256">#4256</a></li>
</ul>
<h2>4.39.0 - 15 Oct 2026</h2>
<ul>
<li><em>Breaking change</em>: Bump the minimum required CodeQL bundle version to 2.20.7. <a href="https://redirect.github.com/github/codeql-action/pull/4205">#4205</a></li>
<li>The <code>codeql-action/analyze</code> step now validates that a correct argument for the <code>checkout_path</code> input has been provided. The <code>checkout_path</code> input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by <code>codeql-action/init</code>, then the CodeQL Action now produces a warning. <a href="https://redirect.github.com/github/codeql-action/pull/4148">#4148</a></li>
<li>Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. <a href="https://redirect.github.com/github/codeql-action/pull/4206">#4206</a></li>
<li>The <code>codeql-action/start-proxy</code> step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as <code>codeql-action/init</code>. This primarily benefits customers who are using GitHub instances other than <code>github.com</code> where the <code>codeql-action/start-proxy</code> step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. <a href="https://redirect.github.com/github/codeql-action/pull/4198">#4198</a></li>
</ul>
<h2>4.38.3 - 08 Oct 2026</h2>
<ul>
<li><em>Upcoming breaking change</em>: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. <a href="https://redirect.github.com/github/codeql-action/pull/4188">#4188</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.2">2.27.2</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4203">#4203</a></li>
<li>Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4184">#4184</a></li>
</ul>
<h2>4.38.2 - 24 Sept 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.1">2.27.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4160">#4160</a></li>
</ul>
<h2>4.38.1 - 18 Sept 2026</h2>
<ul>
<li>The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4146">#4146</a></li>
</ul>
<h2>4.38.0 - 09 Sept 2026</h2>
<ul>
<li>On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. <a href="https://redirect.github.com/github/codeql-action/pull/4124">#4124</a></li>
<li>The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native <code>linux-arm64</code> CodeQL bundle when available. <a href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.0">2.27.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4129">#4129</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/github/codeql-action/commit/b96794f015dfd88f77b49b1c93e0fa7110f94c63"><code>b96794f</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4131">#4131</a> from github/update-v4.38.0-7e08580a9</li>
<li><a href="https://github.com/github/codeql-action/commit/02d5093871674ea20274117103ce3038c73c77ef"><code>02d5093</code></a> Update changelog for v4.38.0</li>
<li><a href="https://github.com/github/codeql-action/commit/7e08580a93dc4e4b9dda167e364577035cf504c6"><code>7e08580</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4130">#4130</a> from github/henrymercer/workflow-runner-sizing</li>
<li><a href="https://github.com/github/codeql-action/commit/bfcc52b4f5d98468a5993daa0bf0e4fb3f3ed698"><code>bfcc52b</code></a> Run slow macOS checks on larger runners</li>
<li><a href="https://github.com/github/codeql-action/commit/8c251e757c0260283fc50214a06ac768b61d3af4"><code>8c251e7</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4129">#4129</a> from github/update-bundle/codeql-bundle-v2.27.0</li>
<li><a href="https://github.com/github/codeql-action/commit/0b7ca400df35985869d4b9146a067865d4115da1"><code>0b7ca40</code></a> Add changelog note</li>
<li><a href="https://github.com/github/codeql-action/commit/40484b339517c6bcf00f81eebc95ca041ddca505"><code>40484b3</code></a> Update default bundle to codeql-bundle-v2.27.0</li>
<li><a href="https://github.com/github/codeql-action/commit/977e6ceaea7361825998245d787fa3b4d6b9e5df"><code>977e6ce</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4124">#4124</a> from github/henrymercer/toolcache-bundle-cleanup</li>
<li><a href="https://github.com/github/codeql-action/commit/40a6b3824794ae1156e1a5320d32e364bf1dcebc"><code>40a6b38</code></a> Address toolcache cleanup review feedback</li>
<li><a href="https://github.com/github/codeql-action/commit/deece8f852f048bc3f52fd42c9cc7a99b1ebb252"><code>deece8f</code></a> Apply suggestion from <a href="https://github.com/henrymercer"><code>@​henrymercer</code></a></li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/cdf488f595d80d6e07e03d4674febd5ab45fa938...b96794f015dfd88f77b49b1c93e0fa7110f94c63">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github/codeql-action/upload-sarif&package-manager=github_actions&previous-version=4.37.9&new-version=4.38.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>


ACKs for top commit:
tcharding:
ACK fe755619b3416a1a6d26677ec52d95fcd2959aa7
apoelstra:
ACK fe755619b3416a1a6d26677ec52d95fcd2959aa7; successfully ran local tests


Tree-SHA512: ed0741d0197f6a000929d349fe407e97bfbfcb3bdcdeae7d2d2578c7206ef389eb0f3e145afe6e7f75d569acce5c59773acb46f4dd51713b67839f142ff34a5f

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
access controldefensive validationdocumentation-only discountautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security scanning workflow. It changes one pinned commit hash to a newer version of the same action. There is no indication this introduces a vulnerability or fixes one; it is normal dependency maintenance.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7162: ci: take commit baseline from merge parentby Andrew Poelstra · 8061db5d · Nov 9, 2026 · 2 filesMessage 100 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7162: ci: take commit baseline from merge parent

cda30cd42053a96c19c170910d6cd7f30ee6d62f ci: take baseline from merge base (satsfy (Renato Britto))

Pull request description:

`pull_request.base.sha` may not updated when master moves ([docs](https://docs.github.com/en/enterprise-server@3.17/pull-requests/how-tos/create-pull-requests/changing-the-base-branch-of-a-pull-request)), and we rely on it so that old PRs got master's changes reported as their own API diffs and semver breaks. By doing it with a `HEAD^1`, it picks the master commit the PR was merged onto.


ACKs for top commit:
tcharding:
ACK cda30cd42053a96c19c170910d6cd7f30ee6d62f
apoelstra:
ACK cda30cd42053a96c19c170910d6cd7f30ee6d62f; successfully ran local tests


Tree-SHA512: 71b0941d18acec31452906f8a51ff681b991179ea43770243d0ea61243304f19bbeae74b7a78c72730c1551892e24774c745c61a6f7e803d22d6830906a49074

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
documentation-only discountmerge-commit duplicate discount
Security candidatekey_expression: Flatten BIP32 decode error constructionby Adewale Ijalana · c31c11e0 · Nov 9, 2026 · 1 fileMessage 81 · StrongInformational 15Details
Commit message · Adewale Ijalana

key_expression: Flatten BIP32 decode error construction

Replace nested error construction with chained map_err calls in
Xpriv::decode and Xpub::decode.

This separates XkeyDecodeError construction from its wrapping in
XprivDecodeError and XpubDecodeError, improving readability and
following the error-handling pattern proposed in #6539.

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
secret or key materialcryptography-sensitive path
AI analysis · Informational 15/100

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how an error message is built when decoding BIP32 extended keys, switching from one nested construction style to two chained calls. The actual behavior and returned error values remain the same. There is no security fix or vulnerability here.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7169: units: use `utxo_prev_block_mtp` for relative time locksby Andrew Poelstra · 608085fc · Nov 9, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7169: units: use `utxo_prev_block_mtp` for relative time locks

0d28907821582e7c06fd2b462c03ffde76ca2e74 units: correct relative locktime error docs (jrakibi)
d6eedc900fff3345f3fac159eca2e777b081dd9d units: use utxo_prev_block_mtp for relative time locks (jrakibi)

Pull request description:

`utxo_mined_at` suggests we are referring to the MTP of the block containing the UTXO. According to BIP68, it is the MTP of the preceding block.

Rename `utxo_mined_at` to `utxo_prev_block_mtp` to make this clear.

Also fix the error docs to use `chain_tip_height` and `chain_tip_mtp`.


ACKs for top commit:
tcharding:
ACK 0d28907821582e7c06fd2b462c03ffde76ca2e74
apoelstra:
ACK 0d28907821582e7c06fd2b462c03ffde76ca2e74; successfully ran local tests


Tree-SHA512: 0a5e69fd65e31dcbd50038c6efd056e8aa7ef6bd25f3ec07952021560b7287d339d3a5c71fbed1a4697fb69d2e4c3de788602d65b9e93119f811e69f0b82c013

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 rust-bitcoin/rust-bitcoin#7168: units: add `visit_units` in optional serde visitorsby Andrew Poelstra · 47340d2f · Nov 8, 2026 · 3 filesMessage 100 · StrongLow 36Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7168: units: add `visit_units` in optional serde visitors

26946ac108c196aaddf040e5d61b5aa6fff9e12d units: test optional serde fields through flatten (satsfy (Renato Britto))
8eda9b9672b4aea9fa1d84f00a58a9b538dab38d units: add visit_unit in optional serde visitors (satsfy (Renato Britto))

Pull request description:

Supersedes https://github.com/rust-bitcoin/rust-bitcoin/pull/1472

So deserializing an `Option<Amount>`, `Option<SignedAmount>` or `Option<FeeRate>` through one of our `opt` serde modules failed when the field was inside a `#[serde(flatten)]` struct and the value read was `null` (as often happen in optional fields). This is because `flatten` put a JSON `null` as a serde unit in the buffer, making serde calls `visit_unit()`, which `opt` visitors did not implement, producing an error. Outside `flatten` the same field works because the format calls `visit_none` directly.

This PR the `visit_unit` fns. The test is similar to what #1472 has, which first presented the problem in 2022.


ACKs for top commit:
tcharding:
ACK 26946ac108c196aaddf040e5d61b5aa6fff9e12d
apoelstra:
ACK 26946ac108c196aaddf040e5d61b5aa6fff9e12d; successfully ran local tests


Tree-SHA512: 57a1777a7ab97237f3d9ca90707b5e892d724a080dc363e863ff790293952cc47e528b188da60132a20e7a118ae26b3ec7c3ae94304d390c13a777503153bcc7

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

This commit fixes a bug in how optional Bitcoin amount and fee-rate values are read from JSON when those fields are inside a flattened struct and the value is null. Previously, the code would error out because it did not handle a special serde 'unit' representation that serde uses during flattening. The fix adds handlers that treat that unit as None, and adds a test to prevent regression. It is a correctness/robustness fix rather than a typical security vulnerability, but it could cause unexpected deserialization failures in applications relying on these types.

AI review queuedbuild(deps): bump github/codeql-action/upload-sarifby dependabot[bot] · fe755619 · Nov 8, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump github/codeql-action/upload-sarif

Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.37.9 to 4.38.0.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/cdf488f595d80d6e07e03d4674febd5ab45fa938...b96794f015dfd88f77b49b1c93e0fa7110f94c63)

---
updated-dependencies:
- dependency-name: github/codeql-action/upload-sarif
dependency-version: 4.38.0
dependency-type: direct:production
update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine dependency update by Dependabot, bumping the version of a GitHub-provided action used to upload security scan results. There is no indication of a security vulnerability in the project itself or in this change.

AI review queuedbuild(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0by dependabot[bot] · 2ccb0029 · Nov 8, 2026 · 2 filesMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

Bumps [cargo-bins/cargo-binstall](https://github.com/cargo-bins/cargo-binstall) from 1.22.0 to 1.23.0.
- [Release notes](https://github.com/cargo-bins/cargo-binstall/releases)
- [Changelog](https://github.com/cargo-bins/cargo-binstall/blob/main/release-plz.toml)
- [Commits](https://github.com/cargo-bins/cargo-binstall/compare/75b4bfae1b2c753a6806bbce6e6cb89b602de33c...b874e25ea559687bec77e281e9b271aa1367b624)

---
updated-dependencies:
- dependency-name: cargo-bins/cargo-binstall
dependency-version: 1.23.0
dependency-type: direct:production
update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that changes the version of a GitHub Action used to install Rust tools in two CI workflows. There is no indication of a security issue in the commit itself, and no verified security references were provided.

AI review queuedbuild(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9by dependabot[bot] · 054e0d73 · Nov 8, 2026 · 2 filesMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.4 to 2.87.9.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/e67fa11c4b9316fa714ddf0abed07a0c3143b95b...c3ec0de9ae7f1019cea21aa96aa0a895b9552063)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.87.9
dependency-type: direct:production
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot of a third-party GitHub Action used in the project's CI workflows. It changes the pinned version of taiki-e/install-action from 2.87.4 to 2.87.9 in two workflow files. There is no indication in the commit or supplied references that this update fixes or introduces a security issue.

Security candidateMerge rust-bitcoin/rust-bitcoin#7125: refactor(bip32)!: make xkey fields private and add checked partsby Andrew Poelstra · c532ab9c · Nov 8, 2026 · 5 filesMessage 91 · StrongLow 37Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7125: refactor(bip32)!: make xkey fields private and add checked parts

87512bb4790f13618fd68ebb84696c89ef621574 refactor(bip32)!: make extended-key fields private (Trevor Arjeski)
de4857e2c942ee2a747ae2e43eebb5606079c244 feat(bip32): add checked extended-key parts APIs (Trevor Arjeski)
0a180f7a662b98f05f9486297ad767ace9a3e60a fix(bip32): make Xpriv debug redaction consistent (Trevor Arjeski)

Pull request description:

Continuation of my (slow) refactor of the bip32 module.

- Add public-field `XprivParts` and `XpubParts`, checked `from_parts`,
and `to_parts`.
- Add metadata getters and make `Xpriv`/`Xpub` fields private.
- Share master-metadata validation through `InvalidXkeyPartsError`.
- Use fixed private-key redaction in `Xpriv` and `XprivParts` debug
output, with and without `std`. Metadata remains visible. This was
fixed years ago in `secp256k1`.
- Re-export `secp256k1` for consumers constructing parts.
- Migrate the BIP32 example and update API documentation and changelogs.


ACKs for top commit:
apoelstra:
ACK 87512bb4790f13618fd68ebb84696c89ef621574; successfully ran local tests; yeah, I think this is a reasonable API


Tree-SHA512: e15554a84daa2c48edd5caf6404858670737266ed3e9a0efb6e7d43d686d51a76d4dc3e346be2ed10987c606755e0fb6976e4ed62f501dd97986616ed7b2594a

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
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Low 37/100

This commit is a routine API refactor, not a security fix. It makes the internal fields of Bitcoin extended keys (Xpriv/Xpub) private so callers can no longer directly mutate them, adds checked constructors that validate master-key metadata, and ensures debug logs always hide the private key. These are defensive hardening changes that reduce the chance of future misuse, but they do not patch an active vulnerability.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7156: hashes: skip initial scalar step when there are no leftoversby Andrew Poelstra · b6f7083f · Nov 8, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7156: hashes: skip initial scalar step when there are no leftovers

92b353906de90f8317aee6806dc8ea272b07b72d hashes: skip initial scalar step when there are no leftovers (jrakibi)

Pull request description:

Follow up to https://github.com/rust-bitcoin/rust-bitcoin/pull/7149

When `input()` starts with no leftovers, we can skip the initial scalar step by checking self.leftovers_len > 0 before filling the buffer.

For 128 byte input, the old code uses scalar for the first 16 bytes, then SIMD for the next 4 * 16 bytes, and the remaining 48 bytes scalarly.

Instead, process the whole input with two SIMD groups: 4 * 16 + 4 * 16 bytes.

The benchmark on ARM64 shows about 16% improvement for the 128byte case.

```
chacha20poly1305/encrypt_no_aad/128
Before: [466.03 ns 469.44 ns 473.74 ns]
After: [391.62 ns 393.18 ns 395.12 ns]
Change: [-16.761% -16.232% -15.780%]
```


Full benchmark:

| Benchmark | Before | After | Delta |
|---|---:|---:|---:|
| encrypt_no_aad/128 | 468.04 ns | 392.06 ns | −16.23% |
| encrypt_with_aad/128 | 494.99 ns | 417.76 ns | −15.60% |
| decrypt_ok/128 | 485.40 ns | 418.60 ns | −13.76% |
| encrypt_no_aad/1024 | 1.049 µs | 0.986 µs | −5.98% |
| encrypt_with_aad/1024 | 1.081 µs | 1.046 µs | −3.23% |
| decrypt_ok/1024 | 1.094 µs | 1.002 µs | −8.35% |
| encrypt_no_aad/16384 | 12.888 µs | 12.831 µs | −0.44% |
| encrypt_with_aad/16384 | 12.886 µs | 12.900 µs | +0.10% |
| decrypt_ok/16384 | 12.775 µs | 12.725 µs | −0.39% |
| encrypt_no_aad/65536 | 50.908 µs | 50.955 µs | +0.09% |
| encrypt_with_aad/65536 | 53.127 µs | 50.725 µs | −4.52% |
| decrypt_ok/65536 | 51.647 µs | 50.772 µs | −1.69% |


ACKs for top commit:
rustaceanrob:
ACK 92b353906de90f8317aee6806dc8ea272b07b72d
apoelstra:
ACK 92b353906de90f8317aee6806dc8ea272b07b72d; successfully ran local tests


Tree-SHA512: 7d9ec6aff214ee9a8f6d97eb5e18fecdbd94d1a384b0d4728bfbe23e0004202f9c7c6201b6fd3bf542b77c3363af40dfd6f4eb206c68a371cf965912643a1643

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 rust-bitcoin/rust-bitcoin#7092: primitives: Document the unusual additional `script` moduleby Andrew Poelstra · 8006dc53 · Nov 8, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7092: primitives: Document the unusual additional `script` module

3bfb42fc65978ca0ee5e4813d312a8c9bbcdacf1 primitives: Document the unusual additional `script` module (Tobin C. Harding)

Pull request description:

Save the next guy 3 minutes having to figure this out.


ACKs for top commit:
Abeeujah:
ACK 3bfb42fc65978ca0ee5e4813d312a8c9bbcdacf1
apoelstra:
ACK 3bfb42fc65978ca0ee5e4813d312a8c9bbcdacf1; successfully ran local tests


Tree-SHA512: 257b27045af40d7df7cc57036685210aa1d1670e076371c98b988cd8d873a8c1eeefe7e67031c70669611bc71815d2c061369fe3fe85273d8f64ad1e05778967

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 rust-bitcoin/rust-bitcoin#7178: Automated nightly rustfmt (2026-11-08)by Andrew Poelstra · bef1eac7 · Nov 8, 2026 · 6 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7178: Automated nightly rustfmt (2026-11-08)

72798f2d0b0d5eef273077556b125b63e1642132 2026-11-08 automated rustfmt nightly (Fmt Bot)

Pull request description:

Automated nightly `rustfmt` changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action


ACKs for top commit:
apoelstra:
ACK 72798f2d0b0d5eef273077556b125b63e1642132; successfully ran local tests
tcharding:
ACK 72798f2d0b0d5eef273077556b125b63e1642132


Tree-SHA512: 0ef44f4e149ee88448e11f0a0b5dceba3f3c6ddb7aa1da972c4838d3d08a5244db41328214de80cbac8fe81e84aac90fcd242dc7bf02389f5ca739905035223f

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-priority2026-11-08 automated rustfmt nightlyby Fmt Bot · 72798f2d · Nov 8, 2026 · 6 filesMessage 45 · ThinTriage 0Details
Commit message · Fmt Bot

2026-11-08 automated rustfmt nightly

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateMerge rust-bitcoin/rust-bitcoin#7128: units: use checked subtraction/addition assignment for NumOpResultby Andrew Poelstra · defb97db · Nov 6, 2026 · 3 filesMessage 100 · StrongModerate 62Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7128: units: use checked subtraction/addition assignment for NumOpResult

201eca08c7f57d0e24ea54336476ec6857473a8b units: use impl_checked_assign! macro for amount and SignedAmount (jrakibi)
2013eb88f6bb5a0fd15846801398b72d7ff2ac82 units: test NumOpResult += and -= overflow (jrakibi)
054045b4d1daf52656e54b32de780ad975696828 units: use checked addition assignment for NumOpResult (jrakibi)
76036ac493b69812f4908ca69bc435e5305b83f3 units: use checked subtraction assignment for NumOpResult (jrakibi)

Pull request description:

`NumOpResult` is supposed to prevent overflow, as mentioned in the docs.

However, addition and subtraction assignment (`+=` and `-=`) currently use the wrapped type regular subtraction/addition instead of **_checked_** subtraction/addition. This can silenly wrap in release builds whilekeeping the result `Valid`.

This change adds checked addition and subtraction for `FeeRate`, `Weight`, `u64`, and `i64`.
`Amount` and `SignedAmount` already handle overflow correctly, so we only change the implementation for these four types.

This is a breaking change since we replace the generic impl with implementations for the four types mentioned above.

Found while auditing `units` crate with Codex.


ACKs for top commit:
Kixunil:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b
tcharding:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b
apoelstra:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b; successfully ran local tests


Tree-SHA512: e221721d0a0c44814aa2321d19f6b62e92d7d98bb11a4ac4b3d90b6e2bd45d761d4075e207c556e861e158974122f2e6199a4b637c08843c039fc5b765c822b5

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✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Moderate 62/100

This commit fixes a bug in the rust-bitcoin library's 'units' crate where the += and -= operators on a special result type (NumOpResult) could silently wrap around on overflow in release builds, instead of reporting an error as documented. The patch replaces the wrapping behavior with checked arithmetic for several numeric types including fee rates, weights, block intervals, and raw integers. It is a defensive fix that prevents incorrect values from being treated as valid.