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
279commits · 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 43 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#7103: Release tracking PR: ` crypto 0.4.0`by Andrew Poelstra · f0fdd87e · Nov 4, 2026 · 13 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7103: Release tracking PR: ` crypto 0.4.0`

56084202392abdffb4c6cb847bd0d80c11918e28 crypto: Bump version to 0.4.0 (Tobin C. Harding)
09cac23981e5acccf951f41e63cabc91c9f50d45 crypto: Update hashes dependency version (Tobin C. Harding)

Pull request description:

In preparation for release add a changelog entry, bump the version number, and update the lock files.


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


Tree-SHA512: 51465f4e7921bbe07842c045c97ea2d6cffa09b79abda267229ebc7c6fe43dc2330cd378118c67e9a9bae0fcbc94f1b99d01a199d1414bcb768a4b7e38e61269

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

This is a routine release-preparation commit for the bitcoin-crypto 0.4.0 crate. It bumps version numbers, updates dependency version pins, refreshes lock files, fills in the release date in the changelog, and replaces placeholder deprecation strings with the actual release version. There are no code behavior changes and no security fixes or security-relevant claims in the commit message or diff.

Security candidateMerge rust-bitcoin/rust-bitcoin#7150: crypto: drop error prefix, remove deprecated fnby Andrew Poelstra · 732c2692 · Nov 4, 2026 · 1 fileMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7150: crypto: drop error prefix, remove deprecated fn

d34f8f783f82f337aefc6678a244b2fc484c4b39 crypto: drop Invalid prefix from FromSliceError variants (satsfy (Renato Britto))
110d3e92517f0df80c70ce088454536d0c7cacfc crypto: remove deprecated TweakedKeypair::to_inner (satsfy (Renato Britto))

Pull request description:

Split out of https://github.com/rust-bitcoin/rust-bitcoin/pull/7140.

- Remove useless profix `Invalid` from `FromSliceError` variants.
- `TweakedKeypair::to_inner` is deprecated for `into_keypair` since 0.32.6.

Both of these trip clippy once the exported API is linted.


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


Tree-SHA512: 7dc9e7d2b3d7a70202644b1640da71ae9c47d3d890949b6ed97ab177b1e86dde19801c92ccd2a1e28623c4e7116541cf58b010f21513353b938d2c3647047756

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

This is a routine code cleanup merge. It renames error variants to remove the word 'Invalid' (for example 'InvalidLength' becomes 'Length') and removes a deprecated function that users were already told to stop using. There is no security fix or vulnerability here.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7148: build(deps): bump taiki-e/install-action from 2.86.8 to 2.87.4by Andrew Poelstra · 677e9232 · Nov 2, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

87f8832e8f86941d8c1b8504a901e33b867b1c7a build(deps): bump taiki-e/install-action from 2.86.8 to 2.87.4 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.86.8 to 2.87.4.
<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.4</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.8.</p>
</li>
<li>
<p>Update <code>protoc@latest</code> to 3.36.1.</p>
</li>
<li>
<p>Update <code>coreutils@latest</code> to 0.11.0.</p>
</li>
</ul>
<h2>2.87.3</h2>
<ul>
<li>
<p>Update <code>zizmor@latest</code> to 1.30.0.</p>
</li>
<li>
<p>Update <code>ubi@latest</code> to 0.12.0.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.25.8.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.16.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.1.0.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.57.0.</p>
</li>
</ul>
<h2>2.87.2</h2>
<ul>
<li>
<p>Update <code>typos@latest</code> to 1.50.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.5.0.</p>
</li>
<li>
<p>Update <code>shfmt@latest</code> to 3.14.0.</p>
</li>
</ul>
<h2>2.87.1</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.7.</p>
</li>
<li>
<p>Update <code>typos@latest</code> to 1.49.1.</p>
</li>
<li>
<p>Update <code>syft@latest</code> to 1.51.1.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.0.</p>
</li>
<li>
<p>Update <code>d2@latest</code> to 0.8.2.</p>
</li>
<li>
<p>Update <code>cargo-zigbuild@latest</code> to 0.23.3.</p>
</li>
<li>
<p>Update <code>cargo-rdme@latest</code> to 2.2.2.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.5.11.</p>
</li>
</ul>
<h2>2.87.0</h2>
<ul>
<li>
<p>Support <code>kache</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1980">#1980</a>, thanks <a href="https://github.com/ChrisJr404"><code>@​ChrisJr404</code></a>)</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.30.1.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.6.</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.89.0] - 2026-11-01</h2>
<ul>
<li>
<p>Support <code>yq</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2036">#2036</a>, thanks <a href="https://github.com/FirelightFlagboy"><code>@​FirelightFlagboy</code></a>)</p>
</li>
<li>
<p>Support <code>mold</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2044">#2044</a>, thanks <a href="https://github.com/FirelightFlagboy"><code>@​FirelightFlagboy</code></a>)</p>
</li>
<li>
<p>Fix an error when old cargo-binstall had already been installed at non-standard location. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2048">#2048</a>)</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.263.0.</p>
</li>
<li>
<p>Update <code>wasm-pack@latest</code> to 0.15.1.</p>
</li>
<li>
<p>Update <code>wasm-bindgen@latest</code> to 0.2.130.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.36.1.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.9.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.25.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.16.0.</p>
</li>
<li>
<p>Update <code>cargo-binstall@latest</code> to 1.26.2.</p>
</li>
</ul>
<h2>[2.88.1] - 2026-10-30</h2>
<ul>
<li>
<p>Update <code>wasmtime@latest</code> to 50.0.1.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.36.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.9.8.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.23.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.15.0.</p>
</li>
<li>
<p>Update <code>espup@latest</code> to 0.19.0.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taiki-e/install-action/commit/e67fa11c4b9316fa714ddf0abed07a0c3143b95b"><code>e67fa11</code></a> Release 2.87.4</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b2a993f9717f6183aa0414e61c39a77ba640b0d1"><code>b2a993f</code></a> Update <code>uv@latest</code> to 0.12.8</li>
<li><a href="https://github.com/taiki-e/install-action/commit/646c3cb94da594e9ad1ba71ce25af2b846a32592"><code>646c3cb</code></a> Update <code>protoc@latest</code> to 3.36.1</li>
<li><a href="https://github.com/taiki-e/install-action/commit/c7a42ecced74789ccdb74389f34cd393a1c6ea74"><code>c7a42ec</code></a> Update <code>coreutils@latest</code> to 0.11.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b585865916acbc68660bff68f147e29cdd51742f"><code>b585865</code></a> Update cargo-deb manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/0758d235715de2f3551eacc980d9ae8fce9342c3"><code>0758d23</code></a> Release 2.87.3</li>
<li><a href="https://github.com/taiki-e/install-action/commit/88efe43bfd45d48641dfceaa8d61d410c820021a"><code>88efe43</code></a> Update <code>zizmor@latest</code> to 1.30.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/2880e0286789726ce93d833e73f37a1465d1299a"><code>2880e02</code></a> Update uv manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/64a78f77b5812aa8c129138b11e9b96df3b9228f"><code>64a78f7</code></a> Update <code>ubi@latest</code> to 0.12.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/bc9ef8893585745dfab4c8f76b36bb67f1d2a47f"><code>bc9ef88</code></a> Update typos manifest</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/fcf5432d9f50d67e37ee6e29bdb7a224ff67b4a7...e67fa11c4b9316fa714ddf0abed07a0c3143b95b">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.86.8&new-version=2.87.4)](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:
apoelstra:
ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a; successfully ran local tests
satsfy:
ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a


Tree-SHA512: 46c9d828a9cd22092dd0c39aef65f4a6268d1140ea70091704d816021111359d5debb7fd2822e61dff4784025429372e40af39110a6ddb4b35317d5e696bb04a

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 Dependabot update that changes the version of a third-party GitHub Action (taiki-e/install-action) used in two automated workflow files. The action installs developer tools like cargo-mutants during CI testing. There is no indication in the commit or its description that this fixes a security vulnerability, and the change does not touch the project's actual Bitcoin library code.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7075: ci: cache dependency build artifacts in the Test jobby Andrew Poelstra · 21434579 · Nov 2, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7075: ci: cache dependency build artifacts in the Test job

14ac9eae30ef8f3d2907fc70507b4fb8b0e6393b ci: cache dependency build artifacts in the Test job (PeterXMR)

Pull request description:

Caches third-party build artifacts for the Test job, the remaining
dependency-caching item from #6951. The cache is saved only on pushes to
master and workspace artifacts are pruned before saving, so the cached
size stays limited to dependencies.

This patch was written with LLM assistance and reviewed by me.


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


Tree-SHA512: 81cc0238793654f98a3b6a512e3c42dc7def2620eb8bdb464e73b9c53ab9ead68ee0224668813de7516096bb7a8cc3190fdceb577420d1da1f0a6c53423670c2

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit only changes the project's GitHub Actions CI workflow to cache third-party dependency build artifacts during automated testing. It does not modify any library code, cryptographic logic, network handling, or user-facing behavior. There is no apparent security vulnerability introduced by this change.

Security candidateMerge rust-bitcoin/rust-bitcoin#6717: Release tracking PR: `primitives 0.104.0`by Andrew Poelstra · 4432f7c4 · Nov 2, 2026 · 11 filesMessage 100 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6717: Release tracking PR: `primitives 0.104.0`

8b07e38a1e23ceca780cb71ece6ca99f9ea003f0 primitives: Bump version to 0.104.0 (Tobin C. Harding)

Pull request description:

In preparation for release add a changelog, bump the version, update the lock files, and upgrade all crates to use the new version.

This is a release of what we have so that we can consider doing a `rust-bitcoin` release in series with the final push towards the last RC of primitives.


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


Tree-SHA512: eb171ff58e2982df1a37dc5aee0dade6d875b25a5b4e9845bd5efc206d904627992c99a6ab1be6e666c3bca621175db01fc8c4c6f626540e16460f5b5340c9d3

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

This is a routine release-management commit. It bumps the version of the `bitcoin-primitives` crate from 0.103.x to 0.104.0, updates dependency version numbers in other crates, refreshes lock files, and adds a changelog. There are no code logic changes in the diff itself.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7101: primitives: transaction's doc cleanupby Andrew Poelstra · b331b1ad · Nov 1, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7101: primitives: transaction's doc cleanup

cd78d76f18dbd4833e56cb5e565bff96c1014e95 primitives: fix errors and claims in transaction docs (satsfy (Renato Britto))
4714bd26ba7e71927908abdcb473acdd4c54c1ce primitives: use SegWit consistently in transaction module (satsfy (Renato Britto))
03bc4f655a2dc181f846207c7f3ad2079c8c97be primitives: fix punctuation in transaction module docs (satsfy (Renato Britto))
247b8aba2eb20ea6a6b73ebc5d4779cb8d7bdf58 primitives: fix rustdoc column width in transaction module (satsfy (Renato Britto))

Pull request description:

A follow-up of https://github.com/rust-bitcoin/rust-bitcoin/pull/7095#issuecomment-6405680894

Do a similar pass of that PR but for transaction module:
- Wrap to 100 columns.
- Fix punctuation.
- Spell SegWit consistently.
- Fix wrong claims.

I'm trying to keep the criteria consistent with tcharding's and jamil's previous doc fixes, another units docs PR that is coming and future primitives doc PRs.


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


Tree-SHA512: e496eaae3c85c6ec375dc0987eef0a1f04bc2b89d2f8e79b17c24b05b679ee66cff3cae4e306d22727091f0fdab398f5215dbe09eb18b4b6f47d67f3c04de368

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 is a documentation cleanup for the Bitcoin transaction module. It only changes comments, spelling consistency, line wrapping, and wording in documentation. No executable code was modified, so it cannot introduce a security vulnerability or fix one.

Security candidateMerge rust-bitcoin/rust-bitcoin#7126: Add `Vec` support to `XOnlyPublicKey` serde implsby Andrew Poelstra · 26728d51 · Oct 31, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7126: Add `Vec` support to `XOnlyPublicKey` serde impls

9b32af1e087e4b15b887354aadf60af365bb7668 Add vec support to XOnlyPublicKey serde impls (Mitchell Bagot)

Pull request description:

The recent XOnlyPublicKey serde modules have support for Option, but not for Vec. Since vectors are a standard thing to implement serde traits for, support for them should also be provided in the x_only_serde module.

Add vec submodules to support Vec<XOnlyPublicKey> in x_only_serde.

Contributes to #5787

Assisted by: Claude Opus 5.5


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


Tree-SHA512: a2d4eb6741ac40d6950e81bd268c0060981aae4c4cdd9273d93e33598a77c7d1465e63aaa90e96c36937367be128595d5bdc2f05b6bb8b16300d45ef191c6dfb

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

This commit adds new helper code for serializing and deserializing lists of Bitcoin x-only public keys using the serde framework. It is a feature addition, not a bug fix, and there is no indication it addresses a security vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7097: units: Match rustdoc heading of other 1.0 cratesby Andrew Poelstra · f015e2db · Oct 31, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7097: units: Match rustdoc heading of other 1.0 crates

6ea685ddeba97febf9f747c55fb594f49d2599c6 units: Match rustdoc heading of other 1.0 crates (Tobin C. Harding)

Pull request description:

Change the crate level header to match the format of `primitives` and `consensus_encoding`. Also use the first sentence from primitives docs but with `s/primitive/units`.

FWIW the heading comes from e86502cc49

Close: #7089


ACKs for top commit:
satsfy:
ACK 6ea685ddeba97febf9f747c55fb594f49d2599c6
apoelstra:
ACK 6ea685ddeba97febf9f747c55fb594f49d2599c6; successfully ran local tests


Tree-SHA512: b8f5e542d14fe3f11cd156e53978d79ae25f44727b79814e3a9b676fd9b11be51428c4529a80a7892be88a5343a0e975a8a383372ecaf63421f7ea5b09f14244

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

This commit is a documentation-only change. It updates the heading and first sentence of the crate-level documentation in the `units` crate to match the style used by other crates in the project. No code behavior was changed.

Security candidateMerge rust-bitcoin/rust-bitcoin#7139: ops: harden ci workflowsby Andrew Poelstra · fb0c6a07 · Oct 31, 2026 · 3 filesMessage 91 · StrongLow 37Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7139: ops: harden ci workflows

0c6f37729b8f003a3af10e9f8c0ed00a12876200 ops: harden ci workflows (Felipe Knorr Kuhn)

Pull request description:

Remove unnecessary write access, and tighten the actors and conditions for the labeler and ci failures workflows


ACKs for top commit:
satsfy:
tACK 0c6f377
apoelstra:
ACK 0c6f37729b8f003a3af10e9f8c0ed00a12876200; successfully ran local tests


Tree-SHA512: 3799e0045ca5b5f4a788bf372fc4cd6f9ab78f191b90fe85773064a2ad21974ca684baaba62a08b844e9f90d6c7887c2b03ba721274546587634c460cc12628e

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 validationboot or update pathdocumentation-only discountmerge-commit duplicate discount
AI analysis · Low 37/100

This commit tightens three GitHub Actions workflows to reduce the risk of supply-chain or repository-manipulation attacks. It removes an unused high-power permission (id-token: write), makes a CI-failure issue-matching script only trust issues created by the GitHub Actions bot, and validates data pulled from untrusted pull-request workflow artifacts before using it to label or comment on pull requests. These are defensive hardening changes rather than fixes for a known active exploit.

Security candidateMerge rust-bitcoin/rust-bitcoin#7136: Release tracking PR: `internals 0.8.2`by Andrew Poelstra · d7bfa112 · Oct 30, 2026 · 20 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7136: Release tracking PR: `internals 0.8.2`

bb78d8841f92d836b9db76721eee5d86155c69f2 internals: Bump version to 0.8.2 (Tobin C. Harding)

Pull request description:

We meant to release #6974 in 0.8.1 but messed it up.

In preparation for release add a changelog entry, bump the version, and update the lock files.


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


Tree-SHA512: 32dd46e95713907c47e00fc6cfbea35c115736e6c39ee986ecd26ca81717771d44432d08524299c92fa970a2f432729a81b6241c82d06e59ae86ec6b65e7583f

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

This commit is a routine release-tracking merge that bumps the version of the `bitcoin-internals` crate from 0.8.1 to 0.8.2 and updates all dependent crates' version requirements and lock files. It contains no code changes, bug fixes, or security patches in the diff itself. The changelog notes that the actual functional change (rejecting a plus sign in certain number parsers) was supposed to ship in 0.8.1 but was accidentally omitted, so this release merely corrects that packaging mistake.

Security candidateMerge rust-bitcoin/rust-bitcoin#7129: primitives: Tidy docsby Andrew Poelstra · d1519949 · Oct 30, 2026 · 7 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7129: primitives: Tidy docs

c9d0274b3e186b8cc772929b0fe82635f38f6620 primitives: Add missing SPDX header (Jamil Lambert, PhD)
3cb4f669b2cf00cdc5e733bee8791c1394f5fbbd primitives: Add missing blank lines (Jamil Lambert, PhD)
b024399973c72eee8adbebf41d071ddbe766f870 primitives: Tidy doc wording (Jamil Lambert, PhD)
7376de3fb60084dde8b282d141ce44a6cc56fd10 primitives: Remove stale note about old atomics (Jamil Lambert, PhD)
72ee0e660ff9ec886c771af8605de2c619a4dcc2 primitives: Fix Witness::from_slice panics docs (Jamil Lambert, PhD)
6cf1d9b55a1e4cbd9143572d5c94574e17482378 primitives: Add missing full stops to docs (Jamil Lambert, PhD)

Pull request description:

A handful of doc fixes. The details are in each of the commit logs.

Docs only changes.


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


Tree-SHA512: 2fafc38e83b07a69dc16f43aaa276ede5216435e1d6b01c0a3b1c468ee1765f0f84a1b5175b0afd816d8c35e70442da0920be9bb04b6d5a8eee6205ff5a74707

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

This commit is a documentation-only cleanup. It fixes typos, adds missing punctuation and blank lines, updates a panic description, removes a stale comment about old Rust atomics, and adds a missing SPDX license header. No executable code behavior was changed, so there is no security impact.

Security candidateinternals: Bump version to 0.8.2by Tobin C. Harding · bb78d884 · Oct 30, 2026 · 20 filesMessage 76 · AdequateInformational 15Details
Commit message · Tobin C. Harding

internals: Bump version to 0.8.2

We meant to release #6974 in 0.8.1 but messed it up.

In preparation for release add a changelog entry, bump the version,
and update the lock files.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is purely a release housekeeping change. It bumps the version number of the `bitcoin-internals` crate from 0.8.1 to 0.8.2, updates dependency references across the workspace, refreshes lock files, and adds a changelog entry. The actual code change being released (rejecting a plus sign in certain number parsers) was merged earlier in pull request #6974 and is not present in this diff.

Security candidateRemove unused errors and variantsby Mitchell Bagot · 9b23b162 · Oct 29, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused errors and variants

With the changes to the FromStr trait impls on Xpub and Xpriv, the
InvalidBase58PayloadLength error variants and inner error type are no
longer needed. As such, they can be dropped to clean up the errors.

Remove InvalidBase58PayloadLengthError and InvalidBase58PayloadLength
error variants from ParseXp*Error.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit removes unused error types and variants from the BIP32 key parsing code. It is a cleanup change with no functional behavior change and no security impact.

Security candidateUngate FromStr and Display for Xpriv and Xpubby Mitchell Bagot · b48052c3 · Oct 29, 2026 · 1 fileMessage 80 · StrongInformational 19Details
Commit message · Mitchell Bagot

Ungate FromStr and Display for Xpriv and Xpub

The Xpriv and Xpub types currently have FromStr and Display trait impls
gated on alloc, due to their use of unbounded base58 encoding/decoding.
By changing the error types, both traits can be trivially made no-alloc
for both of the types.

Adjust error types to DecodeCheckArrayError and ungate FromStr and
Display impls for Xpriv and Xpub.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
cryptography-sensitive path
AI analysis · Informational 19/100

This commit removes a feature gate so that two Bitcoin key types (Xpriv and Xpub) can be converted to and from their standard text representation even when the library is built without memory allocation support. It also swaps the underlying base58 error type to one that works in no-alloc builds. The change is a portability/cleanup refactor, not a fix for an active security bug.

Security candidateGate individual items in bip32 instead of whole moduleby Mitchell Bagot · 1f13455f · Oct 29, 2026 · 2 filesMessage 73 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Gate individual items in bip32 instead of whole module

The bip32 module in key_expression is currently completely gated on
alloc. Since much of its logic doesn't require alloc, the individual
parts that truly need it should be gated and the rest available without
alloc.

Gate only the individual parts of bip32 that need alloc on alloc and
ungate the top-level module.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Informational 18/100

This commit is a routine refactoring of feature-gating in the rust-bitcoin library. It makes more BIP-32 code available when the 'alloc' feature is disabled, by gating only the parts that truly need heap allocation rather than the whole module. There is no security fix or vulnerability here.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7116: primitives: Correct error messagesby Andrew Poelstra · 5d6ce144 · Oct 29, 2026 · 2 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7116: primitives: Correct error messages

3a1078c172ccb24bb8b4e42c0456337eae489f47 primitives: Tidy error message wording (Jamil Lambert, PhD)
fc419d5500371fc5e20fa978552704f199a9392a primitives: Fix TooLong outpoint error message (Jamil Lambert, PhD)

Pull request description:

`ParseOutPointError::TooLong` is returned when the whole string is longer than 75 characters but the message says "vout should be at most 10 digits", which is wrong when it is the txid part that is too long. And the invalid witness commitment message uses the field name `witness_root` which is inconsistent with other messages.

Describe the actual length check and make the wording consistent with the rest of the crate.


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


Tree-SHA512: c4d4481c5182f34120d0129bc21d071e00ef86c9eb82dd554b276ec8c7534ff725eb3fcf0bb889ee6e8feffd501b3e0cc9dccc0e8c256f3aec4704d84552a8dd

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 only fixes the wording of two user-facing error messages in the rust-bitcoin library. One message now correctly says an outpoint string is too long instead of incorrectly blaming the vout digit count. The other renames 'witness_root' to 'witness root' for consistency. There are no code logic, parsing, or cryptographic changes, and no security impact.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7117: primitives: Document omitted return conditionsby Andrew Poelstra · 3b8e3c85 · Oct 29, 2026 · 3 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7117: primitives: Document omitted return conditions

d2613e64e6e0a20f4baa84a8d87db6f7f3ec3207 primitives: Document the witness commitment check (Jamil Lambert, PhD)
2d80f4bb4a65a9c990fee065ded7423cabb8541e primitives: Document no-alloc Merkle root limit (Jamil Lambert, PhD)

Pull request description:

`TxMerkleNode::calculate_root` and `WitnessMerkleNode::calculate_root` return `None` for more than 32,767 transactions when `alloc` is disabled, but only the private `MerkleNode` trait says so. And `Block::check_witness_commitment` returns a `(bool, Option<WitnessMerkleNode>)` and the docs only describe the root.

Copy the no-alloc note to the public docs and describe both halves of the witness commitment result.

Docs only changes.


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


Tree-SHA512: 11aa3468e3cfd8d6fc36abf32bd91774864c27ef2adee4375d35718ee2844c387eaa85338ca3bd1d521eebb7fc5fdbd7f1cc6e80ce24398cc821519a76313eb1

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 only updates documentation comments in the rust-bitcoin library. It adds notes explaining when two Merkle-root calculation functions can return None (specifically when a no-memory-allocation build mode is used with very large transaction lists) and clarifies what the two parts of a witness-commitment check result mean. No code behavior was changed.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7112: units: remove `Amount::MAX_MONEY`by Andrew Poelstra · dafa5b06 · Oct 29, 2026 · 6 filesMessage 100 · StrongInformational 20Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7112: units: remove `Amount::MAX_MONEY`

71641e87aa0d7d9604d8ec920ba2aa3e3d5e2b93 units: remove Amount::MAX_MONEY (satsfy (Renato Britto))

Pull request description:

Now is the last call to judge the matter before units 1.0: In [#3693](https://github.com/rust-bitcoin/rust-bitcoin/pull/3693) we decided to keep both `MAX` and `MAX_MONEY` as synonyms. In [#4164](https://github.com/rust-bitcoin/rust-bitcoin/pull/4164#discussion_r1979441438) it was argued that `MAX` is the proper rusty name for it, something I agree. All these discussions ended at March 2025.

It seems like we are hedging between looking like core and looking rustonic on the `Amount::MAX` and `Amount::MAX_MONEY` issue.

I think we should just kill `MAX_MONEY` because:
1. DRY principle
2. Why are we afraid of looking different from core?
3. We can remove now and add later, but not easily later past 1.0.
4. We have `Weight::MAX`, `Sequence::MAX`, `SignedAmount::MAX`, `FeeRate::MAX`...
5. It just looks bad.


ACKs for top commit:
Kixunil:
ACK 71641e87aa0d7d9604d8ec920ba2aa3e3d5e2b93
apoelstra:
ACK 71641e87aa0d7d9604d8ec920ba2aa3e3d5e2b93; successfully ran local tests


Tree-SHA512: cdb3185b727392d72beb3201fac3d738800414458be41884a487bb7d293871f6643f1e716913354cda4e32aa7d6ef194f6d0ea9de90ad1cc4210953a85946d6c

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit is a routine API cleanup: it removes the duplicate constant name `Amount::MAX_MONEY` and keeps `Amount::MAX` as the single name for the maximum Bitcoin amount. The numeric value (21 million BTC) and all safety checks stay exactly the same. It is not a security fix and does not change how the library protects against invalid amounts.

Security candidateMerge rust-bitcoin/rust-bitcoin#7119: Use SegWit consistently in docs and commentsby Andrew Poelstra · 3b2ce682 · Oct 28, 2026 · 15 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7119: Use SegWit consistently in docs and comments

308092ef0202212bed7b679a7d91ad35dd1adddb Use SegWit consistently in docs and comments (Jamil Lambert, PhD)

Pull request description:

The codebase mostly writes SegWit but a number of docs, comments and test messages still use Segwit or segwit.

Capitalize the remaining prose occurrences. Identifiers and changelogs are left alone, as are the lines in `transaction.rs` and the tapscript type docs that are already changed by open PRs.

Assisted-by: Claude Opus 5.5


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


Tree-SHA512: 413f366296187df400d56d7b723df40f9d58776eac35b06cc157d70295b282155fa79a1a2ced4a9cfd4526b5592f2d5c98615dd814d04c1f5f99684f6cb41b92

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
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit only fixes capitalization of the term 'SegWit' in documentation, comments, and test messages across the rust-bitcoin codebase. No code behavior changes, no security fix or vulnerability introduced.

AI review queuedprimitives: Tidy doc wordingby Jamil Lambert, PhD · b0243999 · Oct 28, 2026 · 3 filesMessage 58 · ThinInformational 15Details
Commit message · Jamil Lambert, PhD

primitives: Tidy doc wording

Add the missing article to the script hash docs, describe
`OutPointDecoderError` the same way as the other decoder errors, and use
the third person for `cast_to_usize_if_valid`.

Assisted-by: Claude Opus 5.5

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only fixes minor grammar and wording in code documentation comments. It adds missing articles like 'the', standardizes how an error type is described, and changes a verb to third person. There are no code behavior changes, no bug fixes, and no security implications.

Security candidateMerge rust-bitcoin/rust-bitcoin#7114: bitcoin: move annex and code_separator_pos to the endby Andrew Poelstra · f127ba2a · Oct 28, 2026 · 2 filesMessage 81 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7114: bitcoin: move annex and code_separator_pos to the end

f7d04a79cbff0c6fdd377ba08c90a21b77382c36 bitcoin: move annex and code_separator_pos to the end (jrakibi)

Pull request description:

These arguments are uncommon, so we can put them at the end of the argument list. This will give existing callers clearer compiler error messages when upgrading.

Closes #7109


ACKs for top commit:
Kixunil:
ACK f7d04a79cbff0c6fdd377ba08c90a21b77382c36
Abeeujah:
ACK f7d04a79cbff0c6fdd377ba08c90a21b77382c36


Tree-SHA512: 79ccef326c5804cd6809df2e1ad278b8a33ce43dddf5c0bcf4b412e3260686f0d93152ce9293ef1bba8c984d9774e578b86a3305fb0777523ae3c0383b3b73c1

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
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This change simply reorders the arguments of two Bitcoin Taproot signature hash functions so that rarely-used optional parameters appear at the end. It is a developer-experience improvement and does not change any security behavior.

Security candidatebitcoin: move annex and code_separator_pos to the endby jrakibi · f7d04a79 · Oct 28, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · jrakibi

bitcoin: move annex and code_separator_pos to the end

These arguments are uncommon, so we can put them at the end of the
argument list. This will give existing callers clearer compiler error
messages when upgrading.

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

This commit simply reorders the arguments of two Bitcoin Taproot sighash functions so that less commonly used parameters (annex and code_separator_pos) appear at the end of the argument list. It is a developer-experience/API cleanup change, not a security fix. There is no change to the underlying cryptographic logic, transaction parsing, or signature validation.

Security candidateMerge rust-bitcoin/rust-bitcoin#7111: units: remove unused fee_rate serde OverflowErrorby Andrew Poelstra · 130ed631 · Oct 28, 2026 · 2 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7111: units: remove unused fee_rate serde OverflowError

bc0b5a3ec3a6c650864cfd6a345131b90f60c678 units: remove unused fee_rate serde OverflowError (satsfy (Renato Britto))

Pull request description:

`from_sat` constructors became infallible on [this commit](https://github.com/rust-bitcoin/rust-bitcoin/commit/0ff8d82193ef562c1aedabe98a6283d09f803c0c), and this is now useless. I just dropped and nothing broke, that error was never constructed.


ACKs for top commit:
apoelstra:
ACK bc0b5a3ec3a6c650864cfd6a345131b90f60c678; successfully ran local tests
Kixunil:
ACK bc0b5a3ec3a6c650864cfd6a345131b90f60c678
Abeeujah:
ACK bc0b5a3ec3a6c650864cfd6a345131b90f60c678


Tree-SHA512: c15ef6438b0192d68f3164a878f62b3f1917004976d2ced218f0b1e8c5ce4ef5c67cf81a581bb62864613a6a8d235e969fd1ec873ac6cf28f96ca77651130517

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
memory safetymerge-commit duplicate discount
AI analysis · Informational 19/100

This commit removes an unused error type called OverflowError from the fee_rate serde module. The error was no longer needed because the underlying constructor became unable to fail. It is a straightforward cleanup with no security impact.

AI review queuedunits: remove Amount::MAX_MONEYby satsfy (Renato Britto) · 71641e87 · Oct 27, 2026 · 6 filesMessage 70 · AdequateInformational 19Details
Commit message · satsfy (Renato Britto)

units: remove Amount::MAX_MONEY

We are hedging between looking like core and looking
rustonic on the Amount::MAX and Amount::MAX_MONEY. I think
we should just kill MAX_MONEY because:
1. DRY principle
2. Why are we afraid of looking different from core?
3. We can remove now and add later, but not easily later.
4. We have Weight::MAX, Sequence::MAX...
5. It just looks bad

This commit also makes `MAX_MONEY` only a doc alias to `MAX`

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This is a routine code cleanup in the rust-bitcoin library. It removes a duplicate constant named MAX_MONEY and replaces all uses with an existing identical constant named MAX. The actual numeric limit (21 million bitcoin) and all safety checks stay exactly the same. There is no security bug being fixed here.

Security candidateunits: remove unused fee_rate serde OverflowErrorby satsfy (Renato Britto) · bc0b5a3e · Oct 27, 2026 · 2 filesMessage 60 · AdequateInformational 18Details
Commit message · satsfy (Renato Britto)

units: remove unused fee_rate serde OverflowError

from_sat constructors became infallible and this is now
useless.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
memory safety
AI analysis · Informational 18/100

This commit simply deletes an unused error type called OverflowError from the fee rate serialization code. It is a cleanup change with no security impact. The type became unnecessary because the underlying constructors can no longer fail.