RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

2570 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

612security candidates555second-pass queue2330AI analyses
153commits · 30 days
280commits · 60 days
977commits · 180 days
2058commits · 365 days
Backfill bands
Aug 5 → Feb 6787 seen32 candidatesComplete
Feb 6 → Jun 6878 seen53 candidatesComplete
Jun 6 → Jul 6211 seen15 candidatesComplete
Jul 6 → Aug 5184 seen2 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
702Strong · 80–100
1135Adequate · 60–79
582Thin · 40–59
151Opaque · 0–39
20security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Andrew Poelstra407139251391
Mitchell Bagot659200654068
Tobin C. Harding42167411063
jrakibi1015096069
satsfy (Renato Britto)652235065
Nick Johnson19621190060
Jamil Lambert, PhD12619117062
Fmt Bot351532045
Trevor Arjeski111111069
Shing Him Ng31731056
Martin Habovstiak31629069
Ismail Daif22622050
Analysis record

Published AI watches

Last scanned 35 minutes ago

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

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

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

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

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

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

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

key_expression: Forward serde feature to network

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

key_expression: Flatten BIP32 decode error construction

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

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

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

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

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

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

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

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

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

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

2ccb0029by dependabot[bot]+2−22 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7212: AGENTS.md: add some more textby Andrew Poelstra · dc20ce97 · Nov 19, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7212: AGENTS.md: add some more text

753161e672e55588eb06a2a86258ed2f6f39ada1 AGENTS.md: add some more text (Andrew Poelstra)

Pull request description:

There has been an overall trend toward better LLM contributions. But they're still often pretty bad. I'd like to at least know what models people are using. Elaborate AGENTS.md to try to get this information.


ACKs for top commit:
Kixunil:
ACK 753161e672e55588eb06a2a86258ed2f6f39ada1
tcharding:
ACK 753161e672e55588eb06a2a86258ed2f6f39ada1
jamillambert:
ACK 753161e672e55588eb06a2a86258ed2f6f39ada1


Tree-SHA512: 1b13d3b2f9170735c59d214568c3dcefc5679b24b554e688d680aca0fe29d721c16eab86ab5156e41a0b82e679f7f4641a4d94c5436028d7fbea34896c93c394

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7235: units: narrow mutation testing excludesby Andrew Poelstra · 9584f04a · Nov 19, 2026 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7235: units: narrow mutation testing excludes

f62c8e2d72903c219d9fda01a75986e0fe6809f7 units: narrow `.*Error` mutant exclude (satsfy (Renato Britto))
e504e7405acc8f9824b4d6a04b28bee9247c2b37 units: narrow `parse_signed_to_satoshi` exclude (satsfy (Renato Britto))
1139b4f5ec91eaff746b4ae33f2e39430d3d9e78 units: narrow `fmt_satoshi_in` mutant exclude (satsfy (Renato Britto))
355c380f93eed9c5da663b835e3e9008eb4ffbb4 units: narrow `dec_width` mutant exclude (satsfy (Renato Britto))
850a3ba9d6b01b9796de5b81a294aa370436aeb2 units: narrow `| with ^` mutant excludes (satsfy (Renato Britto))
3364461af0923d23dd4f479121039534505d594b units: drop stale deprecated mutant excludes (satsfy (Renato Britto))
fc910cc0ccd4a6e2a1203dc55e4a7f940c79f304 units: drop `decode_compact` mutant exclusion (satsfy (Renato Britto))

Pull request description:

I'm trying to find any remaining place units errors could be uncovered. Looking at mutants I see several excludes in `.cargo/mutants.toml` match more than necessary. For example, `.*Error` excluded every function returning `Result<_, SomeError>`, in all applicable crates. This PR narrows them.

We went from 697 to 921 of the 1338 units mutants checked. For the whole workspace that is a 17% increase in mutants checked.


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


Tree-SHA512: 5c361531118dd13101d7adf0e0430f0191003435c0abfffc52b8a44048d39c20f8ad4b0194574d3657dfe6226fa701e6101a29cd6741dc334e61e3b7ad117ef0

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#7220: refactor(bip32)!: replace KeySource with KeyOriginby Andrew Poelstra · 6bb507b2 · Nov 19, 2026 · 3 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

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

1d564630a788847276c825c76d38631e61570ea8 refactor(bip32)!: replace KeySource with KeyOrigin (Trevor Arjeski)

Pull request description:

- Replace `KeySource` tuple with `KeyOrigin { fingerprint, path }` struct for readability and better alignment with BIP-0380 naming convention (preparing for BIP-0380 implementation).


ACKs for top commit:
tcharding:
ACK 1d564630a788847276c825c76d38631e61570ea8
apoelstra:
ACK 1d564630a788847276c825c76d38631e61570ea8; successfully ran local tests; GLM-5.3 read the BIP and was happy with the language


Tree-SHA512: c04628115a855493c8cbe9a8b1e50cead0af3a87255c9cf2cea085660535c4a515826f914ee0b73fd452012151894946083b82785c0fb2fd824531c8024c005e

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

This 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 intentionally kept identical, so existing saved data should still load. There is no security bug being fixed here.

Security candidateMerge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto depby Andrew Poelstra · d193efc5 · Nov 18, 2026 · 7 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

806f1e1f8de143911cc878c6319f16c80006a586 key_expression: Forward serde feature to network (bytescape30)
eeb5b20f516d977de45ae47c6e15642e21123483 key_expression: Drop direct secp256k1 dependency (bytescape30)
4ad585f69792de0bf7c7fb36af7b7964fca90da4 key_expression: Forward serde feature to crypto (bytescape30)

Pull request description:

Nothing about behavior, public types, or error variants changes. Only
the route changes, and one less dependency to manage.

crypto already re-exports secp256k1, so key_expression does not need
its own copy of the dependency. Depending on it in two places only
adds a second version requirement to keep in sync.

Use the re-export in bip32.rs and drop the secp256k1 entries from the
std, alloc, serde and arbitrary features. The matching crypto features
already forward to secp256k1, so the enabled feature set is unchanged.

secp256k1 now routes access through crypto.

Closes #7121


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


Tree-SHA512: 4e3e5f90de6619328a1f58dda42b5ee5e4da5940c7f674d1c03e356e6a393533bb787b3973a22bddade17640a6b6212dfb06b5a479a1531383fed3697979f7e5

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

This 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, types, or error messages change. It is not a security fix and does not introduce any obvious vulnerability.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7160: Support Testnet5 (BIP95) networkby Andrew Poelstra · af60aa3e · Nov 18, 2026 · 9 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7160: Support Testnet5 (BIP95) network

0b6d7bc4cf174dbbf26174040dbd53c6b141e42a Test Testnet5 network parameters and genesis handling (Pol Espinasa)
2679fa3a2673d08accbb80f41cb0075dd770a3e9 Add native Testnet5 network support (Pol Espinasa)

Pull request description:

Adds support for the new [Testnet5 (BIP95)](https://github.com/bitcoin/bips/blob/master/bip-0095.md).

All constants can be checked agains this Bitcoin Core's commit: https://github.com/bitcoin/bitcoin/pull/35861/changes/ef12208cc0304f57a8f3d8171ee321defa500675#diff-e20339c384d6f19b519ea2de7f4ba4fed92a36d66a80f0339b09927c3fa38d6d


**Disclaimer:** *I am not a rust-bitcoin contributor, or even a rust developer. The PR was assisted by an AI (I reviewed the code before opening the PR). I might be missing some things as I don't know the rust-bitcoin project code structure well. I will happily close it if someone wants to open a fresh one implementing this from scratch* :)


ACKs for top commit:
apoelstra:
ACK 0b6d7bc4cf174dbbf26174040dbd53c6b141e42a; successfully ran local tests; used kimi-k3.1-pro to check all the constants etc


Tree-SHA512: f31b0e8c55f296d58c286135f14f1403885c24139be3cc549694e21333d79c282ac90a5b4fa58d1bfc904d12abea7b617ca9e3954086012cc63c563f66b9b0b3

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#7225: units: derive `Ord` for `Denomination`by Andrew Poelstra · 233b4b0d · Nov 18, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7225: units: derive `Ord` for `Denomination`

c8a609d4debc55da2e7378c803ef622e2f355a82 units: derive `Ord` for `Denomination` (satsfy (Renato Britto))

Pull request description:

Closes #6353.

Now that `MicroBitcoin` was removed in PR https://github.com/rust-bitcoin/rust-bitcoin/pull/7167, there is exactly one `Demonimation` variant per magnitude. We can now derive `Ord` and `PartialOrd`, reordering the demoniations from smallest to largest which removed a quiky aspect about units crate's API.


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


Tree-SHA512: f1890a47d11e6b8cabe590741cf25331c438f7fdcf69391c5659ffab4d8f8e7e57f0d046c0829493d01719edd1871ccdf1c5e94c36ed91facbc49573f8c93c82

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-priorityunits: narrow `fmt_satoshi_in` mutant excludeby satsfy (Renato Britto) · 1139b4f5 · Nov 18, 2026 · 2 filesMessage 78 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: narrow `fmt_satoshi_in` mutant exclude

fmt_satoshi_in is not a trivial fn, so increasing mutants
coverage there is not a bad idea, and only 5 of its 70
mutants cannot be caught.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityunits: narrow `parse_signed_to_satoshi` excludeby satsfy (Renato Britto) · e504e740 · Nov 18, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · satsfy (Renato Britto)

units: narrow `parse_signed_to_satoshi` exclude

Only 4 of its 48 mutants cannot be caught.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityunits: narrow `.*Error` mutant excludeby satsfy (Renato Britto) · f62c8e2d · Nov 18, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: narrow `.*Error` mutant exclude

The pattern matched every mutant with "Error" in its name,
so any function returning `Result<_, SomeError>` was
excluded, `Target::from_compact` included. It now matches
only trait impls and methods of error types.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityunits: drop `decode_compact` mutant exclusionby satsfy (Renato Britto) · fc910cc0 · Nov 18, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: drop `decode_compact` mutant exclusion

The exclude said `<` and `<=` behave the same there but they
do not. On a 256 bit shift the error returns zero and with
`<=` it returns mantissa.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityunits: narrow `dec_width` mutant excludeby satsfy (Renato Britto) · 355c380f · Nov 18, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: narrow `dec_width` mutant exclude

2 of its 7 mutants cause an infinite loop. Tests already
catch the other 5.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Lower-priorityunits: drop stale deprecated mutant excludesby satsfy (Renato Britto) · 3364461a · Nov 18, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · satsfy (Renato Britto)

units: drop stale deprecated mutant excludes

These patterns match nothing.

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityunits: narrow `| with ^` mutant excludesby satsfy (Renato Britto) · 850a3ba9 · Nov 18, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: narrow `| with ^` mutant excludes

Both excludes matched a whole function, but the reason
given is about one particular mutant, `|` replaced with `^`.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI review queuedkey_expression: Forward serde feature to networkby bytescape30 · 806f1e1f · Nov 17, 2026 · 1 fileMessage 68 · AdequateInformational 17Details
Commit message · bytescape30

key_expression: Forward serde feature to network

Turning on serde for key_expression did not turn it on for network,
which left NetworkKind without Serialize and Deserialize. NetworkKind
has no Display or FromStr impl to fall back on the way Xpriv and Xpub
do, so the derive behind network's serde feature is its only route.

Workspace builds never showed the gap: bitcoin's serde feature turns
on network/serde, and Cargo builds network once with the features of
every crate that depends on it. The gap only shows up when
key_expression is built on its own with --features serde.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 17/100

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 be serialized or deserialized in that configuration. The patch adds 'network/serde' to the feature forwarding list so the dependency's serde support is turned on too. It is a build/feature correctness bug, not a security vulnerability.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7217: bip158: 6680 Follow-upby Andrew Poelstra · dbf03a89 · Nov 17, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7217: bip158: 6680 Follow-up

ce3c778efe9d4895c2a50d7e1c4d1f171faccac8 bip158: Drop TryFrom<Vec<u8>> impl for BasicFilter (Abeeujah)
66da02ea4f088979e247877c499330f84594c0c3 bip158: Use Cow in BasicFilter instantiation (Abeeujah)

Pull request description:

This PR addresses the review comments by Kixunil in #6680
- [#6680 comment](https://github.com/rust-bitcoin/rust-bitcoin/pull/6680#discussion_r4574018829) - Patch 1 addresses this by using `Cow<'_, [u8]>` instead of `Vec<u8>` when instantiating `BasicFilter` elements set.
- [#6680 comment](https://github.com/rust-bitcoin/rust-bitcoin/pull/6680#discussion_r4574143184) - Patch 2 - addresses this by dropping the `TryFrom<Vec<u8>>` impl for `BasicFilter`.

close #7213
close #7214


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


Tree-SHA512: e7da61a12c6ad25d54a4c45e5453c4e94a2f7530dc61fdf96ec2ddc023089d8b1e1bf064611fa0d1d3920d2064209db38186da5e366f41012a4117abd0d0618b

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#7223: build(deps): bump taiki-e/install-action from 2.87.9 to 2.87.13by Andrew Poelstra · c8ee144a · Nov 16, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

fe86b6f3d6e78398621688ffa6e7178368bf86aa build(deps): bump taiki-e/install-action from 2.87.9 to 2.87.13 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.9 to 2.87.13.
<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.13</h2>
<ul>
<li>
<p>Update <code>zola@latest</code> to 0.23.6.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.30.5.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.5.5.</p>
</li>
<li>
<p>Update <code>release-plz@latest</code> to 0.3.167.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.2.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.3.</p>
</li>
<li>
<p>Update <code>osv-scanner@latest</code> to 2.6.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.9.7.</p>
</li>
<li>
<p>Update <code>kache@latest</code> to 0.21.0.</p>
</li>
<li>
<p>Update <code>cargo-leptos@latest</code> to 0.3.8.</p>
</li>
<li>
<p>Update <code>cargo-auditable@latest</code> to 0.7.6.</p>
</li>
</ul>
<h2>2.87.12</h2>
<ul>
<li>
<p>Update <code>wasmtime@latest</code> to 48.0.2.</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.259.0.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.13.</p>
</li>
<li>
<p>Update <code>release-plz@latest</code> to 0.3.165.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.1.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.9.5.</p>
</li>
<li>
<p>Update <code>cargo-nextest@latest</code> to 0.9.144.</p>
</li>
</ul>
<h2>2.87.11</h2>
<ul>
<li>
<p>Update <code>biome@latest</code> to 2.5.13.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.12.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.9.4.</p>
</li>
<li>
<p>Update <code>kache@latest</code> to 0.19.0.</p>
</li>
</ul>
<h2>2.87.10</h2>
<ul>
<li>Update <code>zizmor@latest</code> to 1.30.1.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this file.</p>
<p>This project adheres to <a href="https://semver.org">Semantic Versioning</a>.</p>
<!-- raw HTML omitted -->
<h2>[Unreleased]</h2>
<h2>[2.90.5] - 2026-11-15</h2>
<ul>
<li>
<p>Update <code>mise@latest</code> to 2026.11.8.</p>
</li>
<li>
<p>Update <code>cargo-nextest@latest</code> to 0.9.152.</p>
</li>
</ul>
<h2>[2.90.4] - 2026-11-14</h2>
<ul>
<li>
<p>Update <code>yq@latest</code> to 4.54.3.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.40.1.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.13.8.</p>
</li>
<li>
<p>Update <code>typos@latest</code> to 1.52.2.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.11.2.</p>
</li>
<li>
<p>Update <code>syft@latest</code> to 1.57.1.</p>
</li>
<li>
<p>Update <code>rafn@latest</code> to 0.1.7.</p>
</li>
<li>
<p>Update <code>osv-scanner@latest</code> to 2.7.1.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.11.7.</p>
</li>
<li>
<p>Update <code>knope@latest</code> to 0.24.0.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.18.1.</p>
</li>
<li>
<p>Update <code>kache@latest</code> to 2.1.1.</p>
</li>
<li>
<p>Update <code>grcov@latest</code> to 0.10.8.</p>
</li>
<li>
<p>Update <code>cargo-shear@latest</code> to 1.14.1.</p>
</li>
<li>
<p>Update <code>cargo-cyclonedx@latest</code> to 0.5.10.</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/26e9283f268b880168bdbd2c545dfcd60ec2c6ab"><code>26e9283</code></a> Release 2.87.13</li>
<li><a href="https://github.com/taiki-e/install-action/commit/04a4a8246c7a2f2eaf87e42293bca7269081db97"><code>04a4a82</code></a> Update <code>zola@latest</code> to 0.23.6</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b9c60f15f4eb442f41065a510b0f59af400f446f"><code>b9c60f1</code></a> Update <code>vacuum@latest</code> to 0.30.5</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b31d41ab50dced8ea9cf3c57e9d5cc72056195b8"><code>b31d41a</code></a> Update uv manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/1b200db2bbc6f05645c43889fb464ddf599f8342"><code>1b200db</code></a> Update <code>tombi@latest</code> to 1.5.5</li>
<li><a href="https://github.com/taiki-e/install-action/commit/d3a7a77950c0ece9292ebee57d72a8b83d4d352c"><code>d3a7a77</code></a> Update sccache manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/3e3c2df701b5f6f49f22ed085cd483c3a315a5ad"><code>3e3c2df</code></a> Update <code>release-plz@latest</code> to 0.3.167</li>
<li><a href="https://github.com/taiki-e/install-action/commit/d4446731e441b4b4ec4f412c6f953fd4accd114b"><code>d444673</code></a> Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.2</li>
<li><a href="https://github.com/taiki-e/install-action/commit/e75a66b87d55a9adef6d69af04b0f69631daf082"><code>e75a66b</code></a> Update <code>prek@latest</code> to 0.5.3</li>
<li><a href="https://github.com/taiki-e/install-action/commit/034ed194fcb80aefbc57346f8e914946d777dee6"><code>034ed19</code></a> Update oxfmt manifest</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/c3ec0de9ae7f1019cea21aa96aa0a895b9552063...26e9283f268b880168bdbd2c545dfcd60ec2c6ab">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=taiki-e/install-action&package-manager=github_actions&previous-version=2.87.9&new-version=2.87.13)](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:
satsfy:
ACK fe86b6f3d6e78398621688ffa6e7178368bf86aa
apoelstra:
ACK fe86b6f3d6e78398621688ffa6e7178368bf86aa; successfully ran local tests


Tree-SHA512: 91ca327d76af4971e910f6f2ccdd22674fea7d57a2bce788ab94dcb3d751aa739342ea80f6fe6b3af8334526675594b0e1872e9e36d2e0b309a440ac8a5851bc

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

This is a routine update to a GitHub Actions helper used in automated testing workflows. It 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 Bitcoin library code, no disclosed security issue, and no indication this update fixes or introduces a vulnerability.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7224: build(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0by Andrew Poelstra · 7bc9d696 · Nov 16, 2026 · 2 filesMessage 100 · StrongInformational 20Details
Commit message · Andrew Poelstra

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

42b0bcbbcf0d3d4c4e8394dc3bd4fd804d455598 build(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0 (dependabot[bot])

Pull request description:

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.0.1 to 10.1.0.
<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.1.0 🌈 New output <code>python-runtime-id</code>and respect NO_PROXY</h2>
<h2>Changes</h2>
<p>This release adds more bheind the scene security improvements and also 2 small improvements.</p>
<h3>NO_PROXY</h3>
<p>This action now respects <code>no_proxy/NO_PROXY</code> environment variables which were previously ignored.</p>
<h3>New output <code>python-runtime-id</code></h3>
<p>The new output <code>python-runtime-id</code> can be used to know which python version exactly was installed if you use <code>activate-environment</code>. See <a href="https://redirect.github.com/pyca/cryptography/pull/15572#discussion_r3913508686">pyca/cryptography#15572</a> for details on why this can be useful.</p>
<h2>🐛 Bug fixes</h2>
<ul>
<li>fix: respect no proxy directive <a href="https://github.com/mj0nez"><code>@​mj0nez</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1037">#1037</a>)</li>
<li>Use JSON + a typed wrapper instead of TS codegen <a href="https://github.com/woodruffw"><code>@​woodruffw</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1025">#1025</a>)</li>
</ul>
<h2>🚀 Enhancements</h2>
<ul>
<li>Expose a Python &quot;identity&quot; output <a href="https://github.com/woodruffw"><code>@​woodruffw</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1036">#1036</a>)</li>
<li>Verify downloads with astral-sh/versions checksums <a href="https://github.com/zaniebot"><code>@​zaniebot</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1033">#1033</a>)</li>
</ul>
<h2>🧰 Maintenance</h2>
<ul>
<li>chore: update known checksums for 0.12.12 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1041">#1041</a>)</li>
<li>chore: update known checksums for 0.12.10/0.12.11 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1038">#1038</a>)</li>
<li>chore: update known checksums for 0.12.9 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1035">#1035</a>)</li>
<li>chore: update known checksums for 0.12.7/0.12.8 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1031">#1031</a>)</li>
<li>chore: update known checksums for 0.12.6 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1030">#1030</a>)</li>
<li>chore: update known checksums for 0.12.5 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1020">#1020</a>)</li>
<li>Use self-repo syntax for all in-repo actions/reusable workflows <a href="https://github.com/woodruffw"><code>@​woodruffw</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1024">#1024</a>)</li>
<li>Pin one-shot tools <a href="https://github.com/woodruffw"><code>@​woodruffw</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1022">#1022</a>)</li>
<li>ci: remove obsolete direct push attempts <a href="https://github.com/eifinger"><code>@​eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1019">#1019</a>)</li>
</ul>
<h2>📚 Documentation</h2>
<ul>
<li>docs: update version references to v10.0.1 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1018">#1018</a>)</li>
</ul>
<h2>⬆️ Dependency updates</h2>
<ul>
<li>chore(deps-dev): roll up Dependabot updates <a href="https://github.com/eifinger"><code>@​eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1043">#1043</a>)</li>
<li>Harden npm install defaults <a href="https://github.com/zaniebot"><code>@​zaniebot</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1026">#1026</a>)</li>
<li>Add dependency cooldowns <a href="https://github.com/woodruffw"><code>@​woodruffw</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1021">#1021</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/astral-sh/setup-uv/commit/bec219d24cd3e171d82865faccec33120bb574f4"><code>bec219d</code></a> chore(deps-dev): roll up Dependabot updates (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1043">#1043</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/b90ec40d15bfa44c33c6700196eb6efcdddb4373"><code>b90ec40</code></a> fix: respect no proxy directive (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1037">#1037</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/421feb646df5262e7dd93bc54161edfa30372417"><code>421feb6</code></a> chore: update known checksums for 0.12.12 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1041">#1041</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/f634bf473ad85bf3e23a613f52c5fa9f363874fc"><code>f634bf4</code></a> Expose a Python &quot;identity&quot; output (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1036">#1036</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/a6772c8f0a09dc9e3582c70a994b0c55af921803"><code>a6772c8</code></a> chore: update known checksums for 0.12.10/0.12.11 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1038">#1038</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/e105c8fb1d7b13074b851babdaef4185243c6a07"><code>e105c8f</code></a> chore: update known checksums for 0.12.9 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1035">#1035</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/cd13f9217092d43a771cf9ba7b09bdd3da8d7c4d"><code>cd13f92</code></a> Verify downloads with astral-sh/versions checksums (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1033">#1033</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/3aef7b92c52cec135792ea1e95f4c77683d39e61"><code>3aef7b9</code></a> chore: update known checksums for 0.12.7/0.12.8 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1031">#1031</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/d08d816a1ea176d61a318eff45abd3dffef415b1"><code>d08d816</code></a> chore: update known checksums for 0.12.6 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1030">#1030</a>)</li>
<li><a href="https://github.com/astral-sh/setup-uv/commit/19b4d1e990bec64818914c40230bde93a0de300b"><code>19b4d1e</code></a> Harden npm install defaults (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1026">#1026</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/astral-sh/setup-uv/compare/20cfd1bf945f4377ade1205e4dbc17946fc9a30d...bec219d24cd3e171d82865faccec33120bb574f4">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.1&new-version=10.1.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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

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

---

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

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


</details>


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


Tree-SHA512: e9c66b3eee7156bcc0c3a46660432a0a4799a474f44f5b7d9acec83ae2eed7d34dca9604643e08991c8f29bbbb7431dfdb274d003af103b48da12f20b5e72100

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
defensive validationdocumentation-only discountautomated dependency-update discountmerge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 20/100

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 fix any reported vulnerability in the rust-bitcoin library itself, nor does it change any code that end users run.

Security candidateMerge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising cratesby Andrew Poelstra · 9eeb7774 · Nov 16, 2026 · 10 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

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

98d482b05589eb6a07268da594d751e538c525c9 primitives: Remove serde derives from all types (Mitchell Bagot)
904eedc38427c12ad4339edf7633700f2d0af2b1 units: Remove serde derives from all types (Mitchell Bagot)
16bffa0cb3e31da963b2288a955404f509d22ea5 consensus_encoding: Remove derive feature outside tests (Mitchell Bagot)

Pull request description:

The serde derive feature introduces various additional dependencies to the dependency graph. Since derives are harder to reason about, and slow down the compilation with extra deps, it's better to simply provide explicit serde impls for all types and drop the feature.

Remove serde derive feature from consensus_encoding, units and primitives. Replace all serde derives with explicit impls for all remaining types in units and primitives.

Contributes to #4823


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


Tree-SHA512: 7dc603f26f25b38adcb92062f90c16f87fcf5599555f3d547a1526a85c8621d929dd1563ecd217bee849b41ce821789fdbd188976c9b0e005b5f551ee7fc878b

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

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 easier to reason about. The change is a refactoring/cleanup; it does not fix a known security bug, but any mistake in the new hand-written serde code could subtly change how data is serialized or parsed.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7211: script: tie Instruction::push_bytes return to script lifetimeby Andrew Poelstra · 0c150c93 · Nov 14, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7211: script: tie Instruction::push_bytes return to script lifetime

150650f02684db5954e814f86dd4297389f3b90a script: tie Instruction::push_bytes return to script lifetime (Yudis-bit)

Pull request description:

In `Instruction::push_bytes`, the return type `Option<&PushBytes>` elides to the lifetime of `&self` instead of `'a`.

Returning `Option<&'a PushBytes>` preserves the lifetime of the underlying script slice, allowing callers to retain the pushed data across instruction drops.

Closes #7202


ACKs for top commit:
Kixunil:
ACK 150650f02684db5954e814f86dd4297389f3b90a
apoelstra:
ACK 150650f02684db5954e814f86dd4297389f3b90a; successfully ran local tests


Tree-SHA512: b26b2e4a5d8ea9824683f607af3ce70be4d1c01440d2478243aeccea3c3b9a2ccff3a846c65fe97bfcd990713bea1aebacd482b0715d8d821fbd69d812dd05a4

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#7206: io: add `Unsupported` and `OutOfMemory` kindsby Andrew Poelstra · 3859fa3d · Nov 14, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7206: io: add `Unsupported` and `OutOfMemory` kinds

595b20567474e9a393805529a84038d788942f7c io: add `Unsupported` and `OutOfMemory` kinds (satsfy (Renato Britto))

Pull request description:

Closes #3870

Both are stable in std since before our MSRV and were missing from `ErrorKind`, so they converted to `Other`. With these, `ErrorKind` matches every stable std kind at MSRV 1.74.

Methodology: diffed every line that is not a comment in rust enum `ErrorKind` against ours in `define_errorkind`, only those 2 showed up in diff, this PR kills diff.

I pretty much stumbled in this PR reading rust changelogs.


ACKs for top commit:
tcharding:
ACK 595b20567474e9a393805529a84038d788942f7c
apoelstra:
ACK 595b20567474e9a393805529a84038d788942f7c; successfully ran local tests
Kixunil:
ACK 595b20567474e9a393805529a84038d788942f7c


Tree-SHA512: e2b4324a6a435163f72d57aa228ffb13cd42f316ac51e5f8b7a7b55df436459a4996a444832c6673c1f29fc270773a0431f025a60b47448c2510a70e4c9c4f23

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#7205: Manual update to rustc stable (to 1.100.0)by Andrew Poelstra · 44e6f0ca · Nov 14, 2026 · 2 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

2f1e93c438ba871805e6a4d509dcb6292e6938d5 ci: prune test cache on cargo 1.100 layout (satsfy (Renato Britto))
62e72d6e076465840093ccbd74a54313eb5e4bbc Automated update to rustc stable-1.100.0 (Update Stable Rustc Bot)

Pull request description:

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

Cargo 1.100 [uses a new directory layout for intermediate build artifacts](https://github.com/rust-lang/rust/blob/1.100.0/RELEASES.md?plain=1#L108). It writes a new directory every build on `build/<package>/<id>` and no longer has `.fingerprint` or `deps` in the profile directory for our jobs to quickly match. In fact, [`Prune workspace artifacts` step](https://github.com/rust-bitcoin/rust-bitcoin/blob/271f662a6890db459e5ab9088f2b09a3598a43ec/.github/workflows/rust.yml#L47-L72) of the `Test` job matches on `.fingerprint`, which would make it fail prune anything and our cache would be saved with workspace artifacts in it.

Measured locally on a whole workspace test build with 1.100.0, the target directory is 1551 MB unpruned and 491 MB after the new loop (376 MB against 119 MB compressed). The repo is at [6.1 GB of the 10 GB cache limit](https://github.com/rust-bitcoin/rust-bitcoin/actions/caches), so unpruned stable caches would pushing other caches to eviction fasting making our CI performance lower.


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


Tree-SHA512: 5d10db56c822fa16e9a5e2fcdcad24bc34ddc0534ec8cdedb0cc395541114e820a98d47190852051e9aca77530912c51930b4550f1b3787795161dfa0311d33a

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

This commit 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 automated tests and build caches working efficiently. There is no change to the actual Bitcoin library code, no bug fix, and no security-related content.

Lower-priorityscript: tie Instruction::push_bytes return to script lifetimeby Yudis-bit · 150650f0 · Nov 14, 2026 · 2 filesMessage 81 · StrongTriage 0Details
Commit message · Yudis-bit

script: tie Instruction::push_bytes return to script lifetime

In Instruction::push_bytes, the return type Option<&PushBytes> elides
to the lifetime of &self instead of 'a.

Explicitly return Option<&'a PushBytes> so callers can retain the pushed
data across instruction drops.

Closes #7202

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Security candidateMerge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leakby Andrew Poelstra · be14c72e · Nov 14, 2026 · 2 filesMessage 91 · StrongInformational 18Details
Commit message · Andrew Poelstra

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

40ac950acb35ca14e72f45afc3fd2746ed6f95c9 ci: fail API job on private dependency leak (satsfy (Renato Britto))
892bc18ca783fc084f22eb0dfeafb22e65fd2fd8 ci: bump cargo-rbmt to 0.5.5 (satsfy (Renato Britto))

Pull request description:

Closes #3849.

The issue asks for a CI job that greps the API text files to prove nothing from `internals` is in the public API of a stable crate. `cargo rbmt api` now does that check with no effort on our part, through `private = ["bitcoin_internals"]` in each stable crate, so the grep is not needed.

By bumping to rbmt to 0.5.5, we also catch re-exports (new feature). However, it has various exit codes: exit code 1 is a literal error with rbmt binary, 2 is API diff, and 3 is a private dependency leak. An exit code 2 is an API diff, so it should not fail the job, but 1 and 3 should cause the job to fail, which the rust.yml change does here.


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


Tree-SHA512: 8f28a32f1d3d11a65665cf0fbc0ee6ccd78c8aa9d43e41b436ab6c56a025c6c8783da4f0efa9e22fadb07ddf77d2c3662152c30c6174ef9a1cf7b0e937976371

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

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 internal implementation details but does not fix any currently exploitable bug.

Lower-priorityio: add `Unsupported` and `OutOfMemory` kindsby satsfy (Renato Britto) · 595b2056 · Nov 13, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

io: add `Unsupported` and `OutOfMemory` kinds

std has had both since before our MSRV but they were not in
`ErrorKind` and a std error of either kind converted to
`Other`.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityci: prune test cache on cargo 1.100 layoutby satsfy (Renato Britto) · 2f1e93c4 · Nov 13, 2026 · 1 fileMessage 90 · StrongTriage 0Details
Commit message · satsfy (Renato Britto)

ci: prune test cache on cargo 1.100 layout

Cargo 1.100 now writes build artifacts to only one
directory. Our cache pruning jobs depended on that path, so
the prune would not do be doing anything without this fix.

The cache would be saved with workspace artifacts in it,
which may add 1~3GB (We use 6.1/10GB), store and dowload
more and potentially make github start evicting important
recent caches.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
documentation-only discount