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 10 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#7071: hashes: Allow deprecated_in_future in cpufeatures modulesby Andrew Poelstra · 2fe28fae · Oct 25, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7071: hashes: Allow deprecated_in_future in cpufeatures modules

f47d41e4fd86b8ff4f64a7e29045b75fcb970b61 hashes: Allow deprecated_in_future in cpufeatures modules (PeterXMR)

Pull request description:

Closes #6930.

The `cpufeatures::new!` macro expands to a call to `u8::max_value()`, which trips the crate-wide `deprecated_in_future` warning in `hashes`. The four cpuid modules already carried `#[allow(deprecated)]`, but that is a separate lint and never covered this warning. This adds `deprecated_in_future` to those four attributes, as suggested in the issue.

Bumping `cpufeatures` was not an option since `Cargo-minimal.lock` pins 0.2.5 and both 0.2.5 and 0.2.17 call `u8::max_value()`.

The second half of the issue, the removed clippy lint `from_iter_instead_of_collect`, was already fixed by #6963.

This patch was written with the assistance of an LLM (Claude Fable 5.1) and reviewed by me.


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


Tree-SHA512: 1e6067f4b742465c45c62f98a58794ccc8301731f22d984bf35138e41c43604a481daf2931ac06bf42cc8a6e904e79dfbd6eec3e26a0b5f79d4890d1d9374d8b

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 minor code-quality patch that adds a compiler warning suppression. It does not change any runtime behavior, cryptographic logic, or security boundary. The change simply tells Rust not to warn about a deprecated function used internally by a dependency (cpufeatures).

Lower-priorityhashes: Override write_all for std::io::Writeby PeterXMR · a8a612d6 · Oct 24, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · PeterXMR

hashes: Override write_all for std::io::Write

Hash engines consume the whole buffer on every `write`, so the default
`write_all` loop, with its `Interrupted` and zero-length handling, only
ever runs once. Override it to feed the buffer to `HashEngine::input`
directly.

Assisted-by: Claude Opus 5.5

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityio: Override write_all for hash enginesby PeterXMR · 60a7bfce · Oct 24, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · PeterXMR

io: Override write_all for hash engines

Hash engines consume the whole buffer on every `write`, so the default
`write_all` loop, with its `Interrupted` and zero-length handling, only
ever runs once. Override it to feed the buffer to `HashEngine::input`
directly.

Close #4034

Assisted-by: Claude Opus 5.5

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7066: docs(units): Correct Sequence seconds conversion limitsby Andrew Poelstra · d3505041 · Oct 22, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7066: docs(units): Correct Sequence seconds conversion limits

c9e70bbb347b4bc69e74bc60ff70a057b2029f40 docs(units): Correct Sequence seconds conversion limits (elonfliter)

Pull request description:

The documentation for `Sequence::from_seconds_floor` and `Sequence::from_seconds_ceil` incorrectly states that the input seconds must fit in 16 bits. The implementation limits the rounded number of 512-second intervals instead.

Correct both error descriptions and document the maximum accepted inputs: 33,554,431 seconds for floor conversion and 33,553,920 seconds for ceiling conversion.


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


Tree-SHA512: 1a1fe729e158d5a43d7b050e8136cab70a99439f4a386324a87879a1d5d07e9a7c51c051aa0d927ad96bad3859492968e56d3fcc1bd6f4fce44a8fabe021421a

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#7063: build(deps): bump taiki-e/install-action from 2.85.12 to 2.86.3by Andrew Poelstra · 53ee132c · Oct 19, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7063: build(deps): bump taiki-e/install-action from 2.85.12 to 2.86.3

eb884418350b27135bcc6cf94e5f0605edb623a1 build(deps): bump taiki-e/install-action from 2.85.12 to 2.86.3 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.85.12 to 2.86.3.
<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.86.3</h2>
<ul>
<li>
<p>Update <code>prek@latest</code> to 0.4.14.</p>
</li>
<li>
<p>Update <code>osv-scanner@latest</code> to 2.5.1.</p>
</li>
<li>
<p>Update <code>cargo-llvm-cov@latest</code> to 0.9.0.</p>
</li>
</ul>
<h2>2.86.2</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.5.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.6.</p>
</li>
<li>
<p>Update <code>cargo-tarpaulin@latest</code> to 0.37.2.</p>
</li>
</ul>
<h2>2.86.1</h2>
<ul>
<li>Fix an issue where <code>oxfmt</code> was accidentally installed as <code>oxfmt-{target}{exe}</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1969">#1969</a>)</li>
</ul>
<h2>2.86.0</h2>
<ul>
<li>Support <code>oxfmt</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1967">#1967</a>, thanks <a href="https://github.com/rami3l"><code>@​rami3l</code></a>)</li>
</ul>
<h2>2.85.14</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.4.</p>
</li>
<li>
<p>Update <code>trivy@latest</code> to 0.74.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.4.0.</p>
</li>
<li>
<p>Update <code>mdbook-mermaid@latest</code> to 0.17.1.</p>
</li>
<li>
<p>Update <code>cargo-xwin@latest</code> to 0.23.1.</p>
</li>
</ul>
<h2>2.85.13</h2>
<ul>
<li>
<p>Update <code>tombi@latest</code> to 1.3.3.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.5.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 1.113.0.</p>
</li>
<li>
<p>Update <code>cargo-shear@latest</code> to 1.13.4.</p>
</li>
<li>
<p>Update <code>bpf-linker@latest</code> to 0.11.0.</p>
</li>
</ul>
</blockquote>
</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.87.29] - 2026-10-16</h2>
<ul>
<li>
<p>Update <code>zizmor@latest</code> to 1.31.0.</p>
</li>
<li>
<p>Update <code>wasmtime@latest</code> to 49.0.3.</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.262.0.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.13.1.</p>
</li>
<li>
<p>Update <code>trivy@latest</code> to 0.76.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.8.4.</p>
</li>
<li>
<p>Update <code>release-plz@latest</code> to 0.3.172.</p>
</li>
<li>
<p>Update <code>osv-scanner@latest</code> to 2.7.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.11.</p>
</li>
<li>
<p>Update <code>mdbook-d2@latest</code> to 0.3.9.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.13.0.</p>
</li>
<li>
<p>Update <code>kache@latest</code> to 1.2.1.</p>
</li>
<li>
<p>Update <code>just@latest</code> to 1.59.0.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.63.0.</p>
</li>
<li>
<p>Update <code>cargo-crap@latest</code> to 0.8.0.</p>
</li>
<li>
<p>Update <code>bpf-linker@latest</code> to 0.12.0.</p>
</li>
</ul>
<h2>[2.87.28] - 2026-10-12</h2>
<ul>
<li>Update <code>dprint@latest</code> to 0.62.0.</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/5b4d68e2e660441203ab128a23676f1e4faf1532"><code>5b4d68e</code></a> Release 2.86.3</li>
<li><a href="https://github.com/taiki-e/install-action/commit/82754b800cccabcaf4235c23ec7928b52ecf3581"><code>82754b8</code></a> Update <code>prek@latest</code> to 0.4.14</li>
<li><a href="https://github.com/taiki-e/install-action/commit/e90445abe560105799df7c7d631cf8cd6b97c958"><code>e90445a</code></a> Update <code>osv-scanner@latest</code> to 2.5.1</li>
<li><a href="https://github.com/taiki-e/install-action/commit/a7016b999bbc1e1c1590e629abc56decf9014516"><code>a7016b9</code></a> Update mise manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/330a629dce907cc92a7d2f6c530ec3a1fc4372c2"><code>330a629</code></a> Update <code>cargo-llvm-cov@latest</code> to 0.9.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/5582db7a6a920e00c05bbdd554d533fdc6e592d5"><code>5582db7</code></a> Update biome manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b6b84cf49ebfe0176417bdce007c624f0db37f20"><code>b6b84cf</code></a> Release 2.86.2</li>
<li><a href="https://github.com/taiki-e/install-action/commit/822eb9a731103a6afbfa603ab7ff02185a124607"><code>822eb9a</code></a> Update <code>uv@latest</code> to 0.12.5</li>
<li><a href="https://github.com/taiki-e/install-action/commit/5c017c5438cad8fb6e9855caae3622dd889862ee"><code>5c017c5</code></a> Update prek manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/f3371b0ada03f6dd26a8a4d2572a504f06b34f82"><code>f3371b0</code></a> Update osv-scanner manifest</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/b20dedce73af6905cdc30d6611090c9b67557c8d...5b4d68e2e660441203ab128a23676f1e4faf1532">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.85.12&new-version=2.86.3)](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 eb884418350b27135bcc6cf94e5f0605edb623a1; successfully ran local tests


Tree-SHA512: 892b5cbae3cc851a0ead9ab1c4032305f9caadb44977e2b19c071de5866a3c8fac5259f9e4f8fe954de4d1d4f3a5c0e671174494290ec99929e560927965eb55

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 by Dependabot to the version of a third-party GitHub Action used in automated testing workflows. The change only affects internal CI tooling and does not alter the project's actual Bitcoin library code or any software shipped to users.

Security candidateMerge rust-bitcoin/rust-bitcoin#7064: build(deps): bump github/codeql-action/upload-sarif from 4.37.6 to 4.37.7by Andrew Poelstra · 9dedb03a · Oct 19, 2026 · 1 fileMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7064: build(deps): bump github/codeql-action/upload-sarif from 4.37.6 to 4.37.7

ce82988aa656dbe61c76c8c662b4f078d55cdbec 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.6 to 4.37.7.
<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.37.7</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</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.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>
<h2>4.37.9 - 26 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.4">2.26.4</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4106">#4106</a></li>
</ul>
<h2>4.37.8 - 21 Aug 2026</h2>
<p>No user facing changes.</p>
<h2>4.37.7 - 13 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</a></li>
</ul>
<h2>4.37.6 - 04 Aug 2026</h2>
<ul>
<li>Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to <code>.github/codeql-config.yml</code> to align it with the suggested path that is used elsewhere. <a href="https://redirect.github.com/github/codeql-action/pull/4070">#4070</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/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd"><code>ff2f1c6</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4093">#4093</a> from github/update-v4.37.7-be7a3dbb8</li>
<li><a href="https://github.com/github/codeql-action/commit/951a133f96aa2114dd747e9e437305335d0bde16"><code>951a133</code></a> Update changelog for v4.37.7</li>
<li><a href="https://github.com/github/codeql-action/commit/be7a3dbb8147b82cd6d27e0707105b36aa190fc1"><code>be7a3db</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4087">#4087</a> from github/dependabot/npm_and_yarn/npm-minor-0aa561...</li>
<li><a href="https://github.com/github/codeql-action/commit/9310334b11405b305d9444edfa56cd86e2f1e4fe"><code>9310334</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4086">#4086</a> from github/mbg/thread-action-state-to-codeql</li>
<li><a href="https://github.com/github/codeql-action/commit/b4d8a54218a8792de9af2f6f32e33af899ca5212"><code>b4d8a54</code></a> Rebuild</li>
<li><a href="https://github.com/github/codeql-action/commit/ab5db2519c3344f2fa61c711fa2d6ad135829200"><code>ab5db25</code></a> Bump the npm-minor group across 1 directory with 8 updates</li>
<li><a href="https://github.com/github/codeql-action/commit/38055a3c3cf3979323eaf70fc6c73a8690250bde"><code>38055a3</code></a> Drop <code>logger</code> from <code>databaseInitCluster</code> in interface</li>
<li><a href="https://github.com/github/codeql-action/commit/1f87aed5e66849f0c43ae147377cc77f2d98ac99"><code>1f87aed</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4085">#4085</a> from github/update-bundle/codeql-bundle-v2.26.3</li>
<li><a href="https://github.com/github/codeql-action/commit/dc1b98ad1c2f13ccf9fc33fb82f32fc76f944253"><code>dc1b98a</code></a> Make <code>logger</code> available to <code>getCodeQLForCmd</code></li>
<li><a href="https://github.com/github/codeql-action/commit/6f0220ee37121218af472efbde25f06907a4da4f"><code>6f0220e</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4084">#4084</a> from github/navntoft/bump-undici</li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/5595ccaf912efad79be6eef63a5619ff05969be3...ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd">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.6&new-version=4.37.7)](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 ce82988aa656dbe61c76c8c662b4f078d55cdbec; successfully ran local tests


Tree-SHA512: 0779bfbca8d412befec1a2c87280d5bdced0f88faaf9001133e41253367304642d9fc1b2d738ccdc2d0c3c3d241251cc4d496fda92b5f7e10fdac4bacbe96b05

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 of the GitHub CodeQL action used inside a CI workflow. It changes only the pinned version of the upload-sarif action from 4.37.6 to 4.37.7. The new version simply updates the default CodeQL bundle. There is no change to the rust-bitcoin library code, no user-facing behavior change, and no security fix in the project itself.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7065: build(deps): bump dtolnay/rust-toolchain from e2a55d2ffb04f378e9626c28d38b36d230d1e12f to 683b588c487a69d01f6c6ddf40f036ff682cc2c8by Andrew Poelstra · cf039d0f · Oct 19, 2026 · 4 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7065: build(deps): bump dtolnay/rust-toolchain from e2a55d2ffb04f378e9626c28d38b36d230d1e12f to 683b588c487a69d01f6c6ddf40f036ff682cc2c8

e9418abc210a7b37d0cc0d986323554793399796 build(deps): bump dtolnay/rust-toolchain (dependabot[bot])

Pull request description:

Bumps [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain) from e2a55d2ffb04f378e9626c28d38b36d230d1e12f to 683b588c487a69d01f6c6ddf40f036ff682cc2c8.
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/dtolnay/rust-toolchain/commit/683b588c487a69d01f6c6ddf40f036ff682cc2c8"><code>683b588</code></a> Add 1.99.1 patch release</li>
<li>See full diff in <a href="https://github.com/dtolnay/rust-toolchain/compare/e2a55d2ffb04f378e9626c28d38b36d230d1e12f...683b588c487a69d01f6c6ddf40f036ff682cc2c8">compare view</a></li>
</ul>
</details>
<br />


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 e9418abc210a7b37d0cc0d986323554793399796; successfully ran local tests


Tree-SHA512: 93074db34a54a0e0d96c363ef26ee533dd404d1715f54d9277a3103e08c7547c7feb63185b76b1895d0cf754d3beec8714dd0cddd92fc5f8988f504547db5fdf

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

This commit is a routine update by Dependabot that changes the pinned version of a GitHub Action used to install Rust in the project's automated CI workflows. The action was bumped to a newer commit that adds support for a Rust patch release. There is no change to the actual rust-bitcoin library code, no security fix, and no vulnerability introduced.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7062: build(deps): bump astral-sh/setup-uv from 10.0.0 to 10.0.1by Andrew Poelstra · 60ac62c0 · Oct 19, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

7555780d7be2a8cfe0069068712230b5a23df1b0 build(deps): bump astral-sh/setup-uv from 10.0.0 to 10.0.1 (dependabot[bot])

Pull request description:

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.0.0 to 10.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p>
<blockquote>
<h2>v10.0.1 🌈 Tolerate transient manifest timeouts</h2>
<h2>Changes</h2>
<p>Thank you <a href="https://github.com/arguile"><code>@​arguile</code></a>- for making this action more resilient.</p>
<h2>🐛 Bug fixes</h2>
<ul>
<li>Tolerate transient manifest timeouts <a href="https://github.com/arguile"><code>@​arguile</code></a>- (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1016">#1016</a>)</li>
</ul>
<h2>🧰 Maintenance</h2>
<ul>
<li>chore: update known checksums for 0.12.4 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1017">#1017</a>)</li>
</ul>
<h2>📚 Documentation</h2>
<ul>
<li>docs: update version references to v10.0.0 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1014">#1014</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/astral-sh/setup-uv/commit/20cfd1bf945f4377ade1205e4dbc17946fc9a30d"><code>20cfd1b</code></a> chore: update known checksums for 0.12.4 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1017">#1017</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/d73a0cab66a532d7afa440d9df4a67ea9fe65a30"><code>d73a0ca</code></a> Tolerate transient manifest timeouts (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1016">#1016</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/ae3b92d1bdb308a10adfe7b8f408e5cc8c30f3f6"><code>ae3b92d</code></a> docs: update version references to v10.0.0 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1014">#1014</a>)</li>
<li>See full diff in <a href="https://github.com/astral-sh/setup-uv/compare/ae62891fec2bb8e7d6c99fc78c9fec3a63790f8d...20cfd1bf945f4377ade1205e4dbc17946fc9a30d">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=astral-sh/setup-uv&package-manager=github_actions&previous-version=10.0.0&new-version=10.0.1)](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 7555780d7be2a8cfe0069068712230b5a23df1b0; successfully ran local tests


Tree-SHA512: 18c36eb5cb58af9befe7a6c30e35336459c054c06996fca4bb623f36c31be355dd248e88965545f17c889654c3c9c7cc720f1d303b938f8c3362d9e006f205ee

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 only in the project's own security-scanning workflows. The change bumps the pinned version of 'setup-uv' from 10.0.0 to 10.0.1, which fixes a transient network-timeout bug during installation. It does not touch the Rust Bitcoin library code, does not change how user funds or data are handled, and is not described by the project as a security fix.

Security candidateMerge rust-bitcoin/rust-bitcoin#7059: Automated nightly rustfmt (2026-10-18)by Andrew Poelstra · c8ed0815 · Oct 18, 2026 · 12 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7059: Automated nightly rustfmt (2026-10-18)

d55b676d15b7036ecda9c80957b175cc17013cbc 2026-10-18 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 d55b676d15b7036ecda9c80957b175cc17013cbc; successfully ran local tests
tcharding:
ACK d55b676d15b7036ecda9c80957b175cc17013cbc


Tree-SHA512: b18b70ee1c5aa3ef90ea6e4503aa48060541c8ffe49e3ae28e9c15704ed0a96ffe64fcfd58cce137755e02c314e150a6c0732e34c560da3ccc637b9dca0a15f9

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 is an automated code-formatting run by the project's nightly rustfmt bot. It only reorders imports, rewraps lines, and adjusts brace style for cosmetic consistency. No program logic, cryptographic calculations, parsing rules, or API behavior was changed.

Security candidateMerge rust-bitcoin/rust-bitcoin#7058: consensus_encoding: fix wrong default limit in CompactSizeDecoder docsby Andrew Poelstra · 39ed4490 · Oct 18, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7058: consensus_encoding: fix wrong default limit in CompactSizeDecoder docs

20c2dc05939132e1747dd023196224c950a70239 consensus_encoding: fix wrong default limit in CompactSizeDecoder docs (kleonyuan)

Pull request description:

The `CompactSizeDecoder` documentation stated that the decoded value is bounded
by a default limit of 4,000,000. This is incorrect: the default limit is
`MAX_COMPACT_SIZE = 0x0200_0000`, i.e. 33,554,432 bytes (32 MiB), which is the
value used by `CompactSizeDecoder::new()` and is already stated elsewhere in the
same doc block (`new`, `new_with_limit`).

The 4,000,000 figure is the limit used by the vec decoders (`MAX_VEC_SIZE`), not
by compact-size decoding, so it looks like a copy-paste error.


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


Tree-SHA512: 51bf13b507e4b99d0bc8e2da9f0abaa6c312909ef1f8a87951ddbd97896d5257c795fa010a7d212640297fa9e8c2ae7990348c6750cbb0027c597eb11eeb4aea

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 change only corrects a mistake in a code comment. The documentation for CompactSizeDecoder wrongly said the default size limit was 4,000,000, when the actual default is about 33.5 million (32 MB). No program behavior was changed; only the explanatory text was fixed.

Security candidateMerge rust-bitcoin/rust-bitcoin#7061: hashes: disable SHA256 ARM SIMD on big-endian targetsby Andrew Poelstra · be5fba02 · Oct 18, 2026 · 2 filesMessage 100 · StrongModerate 59Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7061: hashes: disable SHA256 ARM SIMD on big-endian targets

cad9a03cfc9d6c1eb41d3edd5520db7b33d844de hashes: disable SHA256 ARM SIMD on big-endian targets (russeree)

Pull request description:

The AArch64 SHA2 backend loads message words as native-endian `u32` and then unconditionally applies `vrev32q_u8` for little-endian memory order. On `aarch64_be` the `vld1q_u32` load already yields the correct big-endian words, so the extra reversal corrupts every message word. All SHA256, SHA256d, and SHA256t digests are silently wrong on big-endian AArch64 when SHA2 is detected.

This gates the ARM SIMD backend on `target_endian = "little"` (module declaration, cpuid module, and both the one-block SHA256 and two-way SHA256d dispatch sites). Big-endian targets use the endian-correct software fallback, which decodes words with `u32::from_be_bytes`.

Reproduced with QEMU user-mode (`qemu-aarch64_be-static`) and a static `no_std` AArch64 BE binary running the exact ARM SHA2 block routine over the padded `"abc"` block:

```
current (vrev on BE): 312892d3e4bda55775e12e46320ed33a329b15d73167b830ec07ba0845c7b4cf
without vrev (fixed): ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
expected : ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
```

Testing done locally:

- `cargo check` on `x86_64-unknown-linux-gnu`
- `cargo check --target aarch64-unknown-linux-gnu`
- `cargo check -Zbuild-std=std,panic_abort --target aarch64_be-unknown-linux-gnu`
- known-answer SHA256("abc") on x86_64

I did not add an in-tree BE test because `aarch64_be` has no prebuilt Rust std; a QEMU-based `contrib/` repro can be added if maintainers want one.


ACKs for top commit:
apoelstra:
ACK cad9a03cfc9d6c1eb41d3edd5520db7b33d844de; successfully ran local tests; sure, disabling ASM on an obscure arch is fine.


Tree-SHA512: f072189bd6b83584a9941d3c0329e15b9a9475a4a16681209d04a8a6712594d36ceaa4826a559a2cf675f3301c1b63ea1322195ca7a46db0fda64028d75d752f

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 · Moderate 59/100

This commit fixes a bug in the SHA-256 hashing code used on 64-bit ARM processors. On rare big-endian ARM systems, the code was accidentally reversing the byte order of data before hashing, producing completely wrong SHA-256 results. The fix disables the fast ARM-specific hashing path on big-endian ARM and falls back to the normal, correct software implementation. Wrong SHA-256 hashes could break digital signatures, transaction IDs, or any security check that relies on correct hashing.

Security candidatehashes: disable SHA256 ARM SIMD on big-endian targetsby russeree · cad9a03c · Oct 18, 2026 · 2 filesMessage 73 · AdequateModerate 59Details
Commit message · russeree

hashes: disable SHA256 ARM SIMD on big-endian targets

The AArch64 SHA2 backend loads message words as native-endian u32 and then
unconditionally byte-reverses them for little-endian memory order. On
aarch64_be the load already yields big-endian words, so the extra reverse
corrupts every message word and produces wrong digests for SHA256, SHA256d
and SHA256t.

Gate the ARM SIMD backend on target_endian = "little" for both the
one-block SHA256 path and the two-way SHA256d path; big-endian targets use
the endian-correct software fallback.

Assisted-by: deepseek-v4.1-flash-1017

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

This commit fixes a bug in the SHA-256 hashing code used by the rust-bitcoin library on big-endian ARM (AArch64) systems. The optimized ARM code always swapped bytes assuming the computer stores data in little-endian order. On a big-endian ARM system, that extra swap scrambled the input and produced completely wrong hash outputs. The fix disables the ARM-specific fast path on big-endian targets and falls back to the slower but correct generic code. Wrong SHA-256 hashes could break Bitcoin address generation, transaction validation, or any security check that depends on a correct hash.

Security candidate2026-10-18 automated rustfmt nightlyby Fmt Bot · d55b676d · Oct 18, 2026 · 12 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-10-18 automated rustfmt nightly

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, import order, line breaks, and similar stylistic details across 12 files. There are no functional changes, bug fixes, or security-related alterations.

Security candidateconsensus_encoding: fix wrong default limit in CompactSizeDecoder docsby kleonyuan · 20c2dc05 · Oct 18, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · kleonyuan

consensus_encoding: fix wrong default limit in CompactSizeDecoder docs

The decoded-value limit documented for CompactSizeDecoder said 4,000,000,
but the default is MAX_COMPACT_SIZE = 0x0200_0000 = 33,554,432 bytes (32 MiB),
as used by CompactSizeDecoder::new() and stated elsewhere in the same doc block.
The 4,000,000 figure belongs to the vec decoders (MAX_VEC_SIZE), not to
compact-size decoding.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
consensus or confidential-proof validation
AI analysis · Informational 15/100

This commit only corrects a comment in the source code. The documentation for CompactSizeDecoder incorrectly stated that the default decoded-value limit was 4,000,000, when the actual default is 33,554,432 bytes (32 MB). No program logic, limits, or behavior were changed.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7056: primitives: Test cast_to_usize_if_valid boundaryby Andrew Poelstra · 2df62093 · Oct 17, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7056: primitives: Test cast_to_usize_if_valid boundary

63733cc10e513fe7966438834c894cf883beee99 primitives: Test cast_to_usize_if_valid boundary (Chibey-max)

Pull request description:

The mutation test reported that replacing `>` with `>=` in
`cast_to_usize_if_valid` was not caught.

I added a boundary test confirming that `4_000_000` is accepted while
`4_000_001` is rejected.

Closes #7030


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


Tree-SHA512: a378cf5601529348b96c2a851bfa18089fb8b00640fd00407c54d47f8381cf97566576df7cc09733a11fc2023f335f49d4754ece693a0408f94a2679cb839655

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#7051: pow: Fix overflow in min difficulty time checkby Andrew Poelstra · 529394c2 · Oct 17, 2026 · 1 fileMessage 96 · StrongLow 45Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7051: pow: Fix overflow in min difficulty time check

7559880f2c3f98c9ebc4ab2e065fdd598300b4ad pow: Add test for min difficulty time near u32::MAX (Nuem.dev)
b2547a3221d39d9ab33660d630db7e556765f43f pow: Fix overflow in min difficulty time check (Nuem.dev)

Pull request description:

In `next_target_after` the testnet min difficulty check adds twice the target spacing to the current header's time using `u32`. If the time is within 1200 seconds of `u32::MAX` this panics in debug builds and wraps in release builds, returning the wrong target.

Bitcoin Core does this comparison using `int64_t`. Do the same by converting to `i64` first, and add a regression test.


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


Tree-SHA512: 049772504cbb9866ced028ccdd5aa7db3a2c22c422787f6c008441a5537aaeb37f46c2462f53498c738a16f4ca276fe72de45e261aef82b99427ba86b75d7b43

96/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetyfuzzing or regression evidencemerge-commit duplicate discount
AI analysis · Low 45/100

This commit fixes an arithmetic overflow bug in the code that calculates the next mining difficulty target for Bitcoin's testnet. When a block's timestamp was very close to the maximum value a 32-bit unsigned integer can hold, adding 20 minutes to it would either crash the program in debug builds or silently wrap around to a small number in release builds, causing the wrong difficulty target to be returned. The fix converts the values to 64-bit integers before adding them, matching how Bitcoin Core handles the same calculation.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#6716: Release tracking PR: `units 0.6.0`by Andrew Poelstra · 45ced7e3 · Oct 17, 2026 · 11 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6716: Release tracking PR: `units 0.6.0`

a14aada7f21c432f19ac219325c5145e37d40a78 units: Bump version to 0.6.0 (Tobin C. Harding)

Pull request description:

Another go at a last release candidate. A fair bit of stuff in this release. Well done team.

The plan is to let this sit for a bit then pull the trigger on `1.0.0`.


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


Tree-SHA512: 7b3c230e95d43ba24840b94f8074819db802a240f41c3e51b19064e6a5e3fea5fb8a990fe6ae58085fb45880f10ab19e8196b1bb26e6aafff3575a26981ef768

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#6974: Reject plus sign in U256 and hex integer stringsby Andrew Poelstra · 868f6d0a · Oct 17, 2026 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6974: Reject plus sign in U256 and hex integer strings

095c237863b578ed18218eb114016011eb559c17 units: test U256 hex rejects inner sign (satsfy (Renato Britto))
c18fb7e51e8a312511737ec1205871f0d31476e2 units: reject inner sign in U256 hex (satsfy (Renato Britto))
70412cf3f6158e7be1117a17011795cbe2e9b8c6 internals: test U256 decimal string rejects sign (satsfy (Renato Britto))
26bba608ac1ad1c14676b2ca1071815e3f025587 internals: reject sign inside U256 decimal string (satsfy (Renato Britto))

Pull request description:

`u128::from_str` accepts an optional leading `+`, as does `from_str_radix`. The code gave chunks of the input to them, so a `+` at the start of a chunk could be accepted and ignored. `U256::from_str` split decimal input into 38 digit chunks, so `"1+" + 37 zeros` string parsed as 10^38. Every `parse_int::hex_*` function accepted `0x+ff`. Also `hex_u256_unchecked` splits at 32 digits from the right, so `Target::from_unprefixed_hex` could accept `+`.

Compliments to my infinite llm+fuzzing loop.


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


Tree-SHA512: a7923b6304b9dc6f16230bdab554e963464bfa1480f84315cf5ad7a0f75e54ab3209f0f5368e086c690b3d06d55f1ebf30de475b3507221ebb99e38cbcb1b491

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
fuzzing or regression evidencemerge-commit duplicate discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7047: Automated weekly update to rustc stable (to 1.99.1) on masterby Andrew Poelstra · 225428b6 · Oct 17, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7047: Automated weekly update to rustc stable (to 1.99.1) on master

e7321ef876ed7e95e7f79156da40bc02ebfdc6f0 Automated update to rustc stable-1.99.1 (Update Stable 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:
satsfy:
ACK e7321ef876ed7e95e7f79156da40bc02ebfdc6f0
tcharding:
ACK e7321ef876ed7e95e7f79156da40bc02ebfdc6f0


Tree-SHA512: a32213c8da7bebca8d850237733a703bced88be9708b13cf7f90d38d29525ca39af7b6c9c03249dfdc795307ea2bb0f4bed8607025f9cfc6b7ab13533dbfb99c

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#6872: units: make zero target convert to zero workby Andrew Poelstra · 6a18eba4 · Oct 17, 2026 · 6 filesMessage 100 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6872: units: make zero target convert to zero work

d46a8a04e245b8d68acff152cfeee65017c6726c bitcoin: test invalid bits header has zero work (satsfy (Renato Britto))
276ec6c179698f11d4cb49590cc260f5d0238e85 units: make work and target conversion fallible (satsfy (Renato Britto))
2a0623727e5cb231cfc74717cb4d9a9a75317257 units: test invalid compact target errors (satsfy (Renato Britto))
0b9f060ba2e96fabab30d21ebf7f7066b20d274b units: make compact target conversion fallible (satsfy (Renato Britto))

Pull request description:

Closes https://github.com/project-loupe/audit-rust-bitcoin/issues/84

`Target::to_work` means `work = 2^256 / (target + 1)`, except that degenerate inputs result in zero. Rust-bitcoin does not cover the case when max target is set, because that result should be zero work.

Bitcoin core [does exactly that](https://github.com/bitcoin/bitcoin/blob/fc6923cec5b440b611700f6629d8c6a61c6f11bd/src/chain.cpp#L126).


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


Tree-SHA512: ef62b06370a5bf0397e74898321e76a6c89dd9bcd401207e8855e473fb2e6e8a5c63a8efbb0d4c5dedd58559f540760f4c07d819f7f067c9ba9b7372dbd66e01

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7046: params: Use 90% activation threshold for mainnet and signetby Andrew Poelstra · 431d6fc8 · Oct 16, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7046: params: Use 90% activation threshold for mainnet and signet

9a245e2a4c5c75094b5d22ebcd8a99c6ff7a3e8a params: Use 90% activation threshold for mainnet and signet (Nuem.dev)

Pull request description:

Bitcoin Core uses a version bits threshold of 1815 out of 2016 blocks (90%) on mainnet and signet. We still had the old 95% value (1916).


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


Tree-SHA512: 474fde4eb324fb479dbdf5092d3bc44cf9367123ae361aec3ab150389692db1885440f5f2aaf9b93a0c53a35a6d29d0a1ed21afb7b85caee0f9e8eba2d856e74

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#7045: p2p: Clarify transaction indexes returned by Merkle proofsby Andrew Poelstra · 6f81d399 · Oct 16, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7045: p2p: Clarify transaction indexes returned by Merkle proofs

b1e53cf7e8bf74ca1c8bb0da2450602f6293ab40 p2p: Clarify transaction indexes returned by Merkle proofs (luangucun)

Pull request description:

The two `extract_matches` methods describe their returned indexes as positions within the partial Merkle tree. They are positions in the original block transaction list: traversal records the leaf's transaction position.

Update both API comments to state what the indexes represent and clarify each method's return behavior.


ACKs for top commit:
vicjuma:
Such an interesting change. ACK b1e53cf7e8bf74ca1c8bb0da2450602f6293ab40
apoelstra:
ACK b1e53cf7e8bf74ca1c8bb0da2450602f6293ab40; successfully ran local tests


Tree-SHA512: 2bfee249b5d61eb78385c65bf36f52f9956aeba6105f3d46b1632fb2299b438d2d109d06bc86d4b65d580eae0669846f0968e135efd932292bce951f9b0f2338

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#7044: docs: Follow up on #6956by Andrew Poelstra · f7de3f7e · Oct 16, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7044: docs: Follow up on #6956

610cb95c41b9e800cc1a10fac036e5171c88e391 docs: Follow up on #6956 (jrakibi)

Pull request description:

Reword the `AsRef<ScriptCode>` docs to say that the conversions borrow the entire script.

Also fix the "modifyign" typo.

Follow up to review feedback on https://github.com/rust-bitcoin/rust-bitcoin/pull/6956#discussion_r4279308614.


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


Tree-SHA512: 2b66f7da398c725e40106a459a008bc0927c745f5d4c74a120ead0ef8a9048b0adadb600d1d50b473c8b3868066ee9861dc9deb487d95abf676c58ab8b708c98

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#6996: p2p: preserve non-mapped IPv6 addresses in Address::socket_addrby Andrew Poelstra · bddda292 · Oct 16, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6996: p2p: preserve non-mapped IPv6 addresses in Address::socket_addr

e92af6cb76f7726fcd826a6e45ab0eb3bb2c1ca6 p2p: preserve non-mapped IPv6 addresses in Address::socket_addr (fmtappendf)

Pull request description:

`Address::socket_addr()` currently round-trips IPv6 addresses incorrectly. It uses `Ipv6Addr::to_ipv4()` to detect IPv4, but `to_ipv4()` also maps IPv4-compatible addresses (`::1` -> `0.0.0.1`), so a legitimate IPv6 address such as `[::1]:8333` is silently turned into `0.0.0.1:8333`.

The Bitcoin wire format stores IPv4 as IPv4-*mapped* IPv6 (`::ffff:a.b.c.d`), identified by the `IPV4_EMBEDDED_IPV6` prefix. This PR restricts the IPv4 interpretation to exactly that prefix and keeps every other address as IPv6. The `Debug` impl had the identical bug and is fixed the same way.


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


Tree-SHA512: ce0f4fe089d9acb7a781edbc36a3828c5efc8ceabb72e804fa32e786f25d97e83910e6501d2408549aaf620acc8a8cc9ed6e3ff9cd4cf8432a23d44ec3af932b

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#7050: bitcoin: Correct script integer decoding documentationby Andrew Poelstra · 97d2d7de · Oct 16, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7050: bitcoin: Correct script integer decoding documentation

e4b1cff94ff3dda0fcec49720e597b7678cb4c54 bitcoin: Correct script integer decoding documentation (zoupingcenter)

Pull request description:

The script integer decoding docs conflate two different limits: read_scriptint accepts at most four bytes, while read_cltv_scriptint accepts at most five bytes.

Correct the documented ranges and replace the contradictory four-byte explanation for CLTV decoding. Also clarify that NumericOverflow reports an encoding exceeding the decoding method's byte-length limit.


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


Tree-SHA512: a02e7149b7b07a9cf0467898975a78ddee4be64f0deb83ad307a6f7cb77bea7f216901b263fb41a7335b136c2d7273bc4ba821d918e5779c63324d7853b4666e

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

This commit only fixes incorrect documentation comments for two functions that decode script integers. The actual code behavior did not change; only the explanatory text was corrected to match what the code already does.