RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

2570 commits in the local evidence base

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

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

Does the history explain itself?

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

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

Who is changing the project?

Public Git author strings; identities are not independently verified.

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

Published AI watches

Last scanned 43 minutes ago

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

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

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

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

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

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

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

key_expression: Forward serde feature to network

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

key_expression: Flatten BIP32 decode error construction

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

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

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

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

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

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

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

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

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

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

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

Explore captured commits

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

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

Ungate FromStr and Display for Xpriv and Xpub

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

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

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

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

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

Gate individual items in bip32 instead of whole module

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

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

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

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

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

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

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

Pull request description:

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

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

Assisted-by: Claude Opus 5.5


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


Tree-SHA512: 413f366296187df400d56d7b723df40f9d58776eac35b06cc157d70295b282155fa79a1a2ced4a9cfd4526b5592f2d5c98615dd814d04c1f5f99684f6cb41b92

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

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

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

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

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

Pull request description:

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

Closes #7109


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


Tree-SHA512: 79ccef326c5804cd6809df2e1ad278b8a33ce43dddf5c0bcf4b412e3260686f0d93152ce9293ef1bba8c984d9774e578b86a3305fb0777523ae3c0383b3b73c1

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 19/100

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

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

bitcoin: move annex and code_separator_pos to the end

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

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

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

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

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

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

Pull request description:

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


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


Tree-SHA512: c15ef6438b0192d68f3164a878f62b3f1917004976d2ced218f0b1e8c5ce4ef5c67cf81a581bb62864613a6a8d235e969fd1ec873ac6cf28f96ca77651130517

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

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

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

units: remove unused fee_rate serde OverflowError

from_sat constructors became infallible and this is now
useless.

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

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

Security candidateMerge rust-bitcoin/rust-bitcoin#7102: Flatten nested error constructorsby Andrew Poelstra · 965f7863 · Oct 27, 2026 · 5 filesMessage 81 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7102: Flatten nested error constructors

96dc7c3f70f053ce61b6f434c73553323aa43b3f key_expression: Flatten nested error constructors (Mitchell Bagot)
3ef33748bc9da500c39879990bc8b5d11e35f4dc base58: Flatten nested error constructors (Mitchell Bagot)
f09d1924a3da60e8ed16d1def9664328620ed094 primitives: Flatten nested error constructors (Mitchell Bagot)
18bde4fd1b38376ecf918cc924336bf952e54f7e units: Flatten nested error constructors (Mitchell Bagot)

Pull request description:

As has been an established pattern, error constructors should be flattened and use map_err to wrap successive error types. There remain places that need to follow this pattern.

Contributes to #6539


ACKs for top commit:
tcharding:
ACK 96dc7c3f70f053ce61b6f434c73553323aa43b3f
Abeeujah:
ACK 96dc7c3f70f053ce61b6f434c73553323aa43b3f


Tree-SHA512: 9a241830f4dd18517aeecb8123a706d6ba932c019954ae0af7fd5651e9fa16722be92088b1d9bf6673d5b796dc4fe987b6b3d9acb7f08f3778560c759ae234d5

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

This commit is a code-style cleanup in the rust-bitcoin library. It rewrites how some internal error types are constructed so that nested error wrappers are created in a flatter, more consistent way using a common Rust pattern (map_err). There is no functional change to how the library behaves, no bug fix, and no security improvement or vulnerability introduced.

Security candidateconsensus_encoding: Remove derive feature outside testsby Mitchell Bagot · 16bffa0c · Oct 27, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · Mitchell Bagot

consensus_encoding: Remove derive feature outside tests

In consensus_encoding, serde is only used for the serde_as_consensus.
In order to reduce compile time, the feature can be removed. When the
derives are removed from types in units and primitives, this also
ensures that the feature is not re-enabled.

Only enable derive feature in consensus_encoding for tests.

95/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
Why it was queued
consensus or confidential-proof validation
AI analysis · Informational 15/100

This commit is a routine build optimization. It removes the automatic 'derive' feature from the serde dependency in the consensus_encoding crate, keeping it only for test builds. This reduces compile time and prevents unused derive machinery from being pulled in. There is no security-relevant change.

Security candidateMerge rust-bitcoin/rust-bitcoin#7096: Add x_only_serde module for `XOnlyPublicKey` serdeby Andrew Poelstra · 64780981 · Oct 26, 2026 · 6 filesMessage 91 · StrongLow 37Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7096: Add x_only_serde module for `XOnlyPublicKey` serde

50940cb20fad4839b00ba56e499df4ab75beb8f2 Remove default XOnlyPublicKey serde impl (Mitchell Bagot)
877faa8f4399a3e6fe20de29bd16f9470a1568a1 Remove uses of default XOnlyPublicKey serde (Mitchell Bagot)
65ea85ba008f8a2f1c3889f8e0bee0b35cb50066 Add x_only_serde module for XOnlyPublicKey serde encoding (Mitchell Bagot)

Pull request description:

Currently, the x-only public key serde encodes and decodes using the inner type, without any parity. Since the bitcoin-crypto type holds the parity, this makes the type unable to roundtrip odd parity keys. Instead, with or without parity encoding should be selectable by users.

Closes #5729


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


Tree-SHA512: 9de8f4794a8897c0956540b050e5d4a290516921cb7a2964739626652e2e09d8664c349714e188d9d24a053915422e9803228e3769a124df7618d1958a2884f4

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 · Low 37/100

This change fixes a data-integrity problem in how a special Bitcoin public key type (XOnlyPublicKey) was being saved and loaded through serde. Previously, the type silently dropped the 'parity' bit during serialization, so an odd-parity key could be serialized and then deserialized as a different, even-parity key. The patch removes the automatic serde implementation and instead offers two explicit modules: one that preserves parity by serializing the full public key, and one that intentionally drops parity. It also removes serde support from Taproot ControlBlock because that structure contained an XOnlyPublicKey and could no longer round-trip safely by default. This is a correctness and API-breaking change, not a remote code-execution vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7067: Add annex and codeseparator position to taproot sighash methodsby Andrew Poelstra · 62c7c658 · Oct 26, 2026 · 2 filesMessage 96 · StrongModerate 60Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7067: Add annex and codeseparator position to taproot sighash methods

897a4e32f3cce741955f3ec906e9013f36ffb2ac bitcoin: add codeseparator test vectors from Core (anshumancanrock)
65b7d7dfa9b07c9208f1a1502b469d6681a60161 bitcoin: test taproot sighash methods (anshumancanrock)
f8e2f4eea0e43d3da53c217d9870f039080a1f78 bitcoin: add annex and codeseparator position to taproot sighash methods (anshumancanrock)

Pull request description:

Fixes #7019

`taproot_key_spend_signature_hash` and `taproot_script_spend_signature_hash` have no way to pass an annex, so they return the wrong sighash for any input that has one. The script spend one also hardcodes the codeseparator position to `0xFFFFFFFF`, which is wrong once an `OP_CODESEPARATOR` has executed.

I Added `annex: Option<Annex>` to both, and `code_separator_pos: Option<u32>` to the script spend one (`None` = no `OP_CODESEPARATOR` was executed). Arg order matches `taproot_signature_hash`.

The existing taproot sighash tests, including the annex ones, now also go through these methods. There's also a small test for the codeseparator position.

The mainnet example from the issue is tx `f859a4e6692c3f15a279449eac191ecb9d17d2d6c003bbae9a55e5da07147eab`, in block 896088 (not 896078). Its signature verifies with the annex and fails without it.


ACKs for top commit:
jrakibi:
ACK 897a4e32f3cce741955f3ec906e9013f36ffb2ac
apoelstra:
ACK 897a4e32f3cce741955f3ec906e9013f36ffb2ac; successfully ran local tests


Tree-SHA512: 9465eb838a7b3454e4307341b725a0f49ce44bd3ee2764108e85f79bd8d796bfb2d04ddcae49e6c47f669a2bd28c025ec4013befc04af8ea93bd2c86541d8179

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
signing boundaryfuzzing or regression evidencecryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 60/100

This commit fixes a bug in how Bitcoin transaction signatures are calculated for Taproot-style transactions. Previously, two helper methods could not accept an optional extra data chunk called an 'annex' and always assumed no special code-separator instruction had run. That meant any transaction using those features would compute an incorrect signature hash, causing a valid signature to be rejected. The change adds the missing parameters so the helpers match the more complete API. It is a correctness fix rather than a memory-safety or remote-exploitable vulnerability, but incorrect sighashes can break wallets, tests, or services that rely on these methods.

Security candidateMerge rust-bitcoin/rust-bitcoin#7085: build(deps): bump github/codeql-action/upload-sarif from 4.37.7 to 4.37.9by Andrew Poelstra · 8b246155 · Oct 26, 2026 · 1 fileMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

2875f67ab04a88ec088f95a681dc9abd113794b5 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.7 to 4.37.9.
<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.9</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>v4.37.8</h2>
<p>No user facing changes.</p>
</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.1 - 21 Oct 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.3">2.27.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4256">#4256</a></li>
</ul>
<h2>4.39.0 - 15 Oct 2026</h2>
<ul>
<li><em>Breaking change</em>: Bump the minimum required CodeQL bundle version to 2.20.7. <a href="https://redirect.github.com/github/codeql-action/pull/4205">#4205</a></li>
<li>The <code>codeql-action/analyze</code> step now validates that a correct argument for the <code>checkout_path</code> input has been provided. The <code>checkout_path</code> input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by <code>codeql-action/init</code>, then the CodeQL Action now produces a warning. <a href="https://redirect.github.com/github/codeql-action/pull/4148">#4148</a></li>
<li>Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. <a href="https://redirect.github.com/github/codeql-action/pull/4206">#4206</a></li>
<li>The <code>codeql-action/start-proxy</code> step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as <code>codeql-action/init</code>. This primarily benefits customers who are using GitHub instances other than <code>github.com</code> where the <code>codeql-action/start-proxy</code> step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. <a href="https://redirect.github.com/github/codeql-action/pull/4198">#4198</a></li>
</ul>
<h2>4.38.3 - 08 Oct 2026</h2>
<ul>
<li><em>Upcoming breaking change</em>: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. <a href="https://redirect.github.com/github/codeql-action/pull/4188">#4188</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.2">2.27.2</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4203">#4203</a></li>
<li>Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4184">#4184</a></li>
</ul>
<h2>4.38.2 - 24 Sept 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.1">2.27.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4160">#4160</a></li>
</ul>
<h2>4.38.1 - 18 Sept 2026</h2>
<ul>
<li>The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4146">#4146</a></li>
</ul>
<h2>4.38.0 - 09 Sept 2026</h2>
<ul>
<li>On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. <a href="https://redirect.github.com/github/codeql-action/pull/4124">#4124</a></li>
<li>The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native <code>linux-arm64</code> CodeQL bundle when available. <a href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.0">2.27.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4129">#4129</a></li>
</ul>
<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>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/github/codeql-action/commit/cdf488f595d80d6e07e03d4674febd5ab45fa938"><code>cdf488f</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4107">#4107</a> from github/update-v4.37.9-920ba7cd1</li>
<li><a href="https://github.com/github/codeql-action/commit/7243f38558d187dde99730d224bb47aa26a95306"><code>7243f38</code></a> Update changelog for v4.37.9</li>
<li><a href="https://github.com/github/codeql-action/commit/920ba7cd1596037e042122c00381eb16b397d68e"><code>920ba7c</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4106">#4106</a> from github/update-bundle/codeql-bundle-v2.26.4</li>
<li><a href="https://github.com/github/codeql-action/commit/ecfa6e16817b8f490bc9a59baa391baf4fa3e3c2"><code>ecfa6e1</code></a> Add changelog note</li>
<li><a href="https://github.com/github/codeql-action/commit/adcdf4a70d247343cf9c29e0f7a6658b51c3a2b1"><code>adcdf4a</code></a> Update default bundle to codeql-bundle-v2.26.4</li>
<li><a href="https://github.com/github/codeql-action/commit/486fec2a3ea2626afcd8c7e9208b4f515078dd7e"><code>486fec2</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4099">#4099</a> from github/update-supported-enterprise-server-versions</li>
<li><a href="https://github.com/github/codeql-action/commit/134624c67b20869c2aaa36dafa726375b78a5d76"><code>134624c</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4101">#4101</a> from github/dependabot/npm_and_yarn/npm-minor-457d82...</li>
<li><a href="https://github.com/github/codeql-action/commit/ff43db8f982a368288f117354fb8d046e937124c"><code>ff43db8</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4103">#4103</a> from github/mergeback/v4.37.8-to-main-db488dde</li>
<li><a href="https://github.com/github/codeql-action/commit/4605e03a74cf891614c4d76f82384a16c1c11816"><code>4605e03</code></a> Rebuild</li>
<li><a href="https://github.com/github/codeql-action/commit/099c869cad6bf3b88657154d4ae47ffed27e632d"><code>099c869</code></a> Update changelog and version after v4.37.8</li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd...cdf488f595d80d6e07e03d4674febd5ab45fa938">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.7&new-version=4.37.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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

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

---

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

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


</details>


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


Tree-SHA512: d60a4aca92fb7a38f71d00431a3fe3327677fc580c73133aa7a4879ff93d00444cdfbbfa5d42e3052f90e8931963143fe1b4c1eda12358e106df66374a895780

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

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security-scanning workflow. It changes only the pinned commit hash of a third-party GitHub Action from version 4.37.7 to 4.37.9. There is no change to the project's Rust code, no disclosed security vulnerability, and no indication this update fixes an active security problem in rust-bitcoin itself.

Security candidateMerge rust-bitcoin/rust-bitcoin#7086: build(deps): bump taiki-e/install-action from 2.86.3 to 2.86.8by Andrew Poelstra · 1e886979 · Oct 26, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

2968f432865f6fa2cada9c8b7900438989ab5c91 build(deps): bump taiki-e/install-action from 2.86.3 to 2.86.8 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.86.3 to 2.86.8.
<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.8</h2>
<ul>
<li>
<p>Update <code>wasmtime@latest</code> to 48.0.1.</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.258.0.</p>
</li>
<li>
<p>Update <code>oxfmt@latest</code> to 1.80.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.12.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.0.0.</p>
</li>
<li>
<p>Update <code>cargo-zigbuild@latest</code> to 0.23.2.</p>
</li>
</ul>
<h2>2.86.7</h2>
<ul>
<li>
<p>Update <code>tombi@latest</code> to 1.4.1.</p>
</li>
<li>
<p>Update <code>rafn@latest</code> to 0.1.5.</p>
</li>
<li>
<p>Update <code>cargo-binstall@latest</code> to 1.22.0.</p>
</li>
</ul>
<h2>2.86.6</h2>
<ul>
<li>
<p>Update <code>dprint@latest</code> to 0.56.1.</p>
</li>
<li>
<p>Update <code>cargo-lambda@latest</code> to 1.9.2.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.5.10.</p>
</li>
</ul>
<h2>2.86.5</h2>
<ul>
<li>
<p>Update <code>zola@latest</code> to 0.23.4.</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.257.1.</p>
</li>
<li>
<p>Update <code>protoc@latest</code> to 3.36.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.10.</p>
</li>
<li>
<p>Update <code>cargo-dinghy@latest</code> to 0.8.6.</p>
</li>
<li>
<p>Update <code>wasmtime@latest</code> to 48.0.0.</p>
</li>
</ul>
<h2>2.86.4</h2>
<ul>
<li>
<p>Update <code>oxfmt@latest</code> to 1.79.0.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.8.</p>
</li>
<li>
<p>Update <code>martin@latest</code> to 1.14.0.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.56.0.</p>
</li>
<li>
<p>Update <code>cargo-about@latest</code> to 0.9.2.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this file.</p>
<p>This project adheres to <a href="https://semver.org">Semantic Versioning</a>.</p>
<!-- raw HTML omitted -->
<h2>[Unreleased]</h2>
<h2>[2.87.31] - 2026-10-23</h2>
<ul>
<li>
<p>Downgrade <code>cargo-sort@latest</code> to 2.1.3.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.35.0.</p>
</li>
<li>
<p>Update <code>xh@latest</code> to 0.26.3.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.13.5.</p>
</li>
<li>
<p>Update <code>ubi@latest</code> to 0.13.0.</p>
</li>
<li>
<p>Update <code>trivy@latest</code> to 0.76.1.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.9.0.</p>
</li>
<li>
<p>Update <code>release-plz@latest</code> to 0.3.174.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.7.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.17.</p>
</li>
<li>
<p>Update <code>jaq@latest</code> to 3.1.2.</p>
</li>
<li>
<p>Update <code>espup@latest</code> to 0.17.1.</p>
</li>
<li>
<p>Update <code>cargo-zigbuild@latest</code> to 0.24.0.</p>
</li>
<li>
<p>Update <code>cargo-nextest@latest</code> to 0.9.149.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.6.2.</p>
</li>
</ul>
<h2>[2.87.30] - 2026-10-21</h2>
<ul>
<li>
<p>Update <code>zizmor@latest</code> to 1.31.1.</p>
</li>
<li>
<p>Update <code>wasmtime@latest</code> to 50.0.0.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taiki-e/install-action/commit/fcf5432d9f50d67e37ee6e29bdb7a224ff67b4a7"><code>fcf5432</code></a> Release 2.86.8</li>
<li><a href="https://github.com/taiki-e/install-action/commit/f62d9e4aee39b59d225de036323247d9aa3bcd5c"><code>f62d9e4</code></a> Update <code>wasmtime@latest</code> to 48.0.1</li>
<li><a href="https://github.com/taiki-e/install-action/commit/f8e3d097225a92555fe656cd8c5ce7aebf885b60"><code>f8e3d09</code></a> Update <code>wasm-tools@latest</code> to 1.258.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/484825a046ee4cf51ff46e4525d0af31412a277b"><code>484825a</code></a> Update vacuum manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/6d0ad88d70ae4ea951105b5f44ac67d1b739df47"><code>6d0ad88</code></a> Update uv manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/36fe62475978dfc558afa1765e51c6d9975236e9"><code>36fe624</code></a> Update <code>oxfmt@latest</code> to 1.80.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/fbcb11bef5d276954dce6be82dd36d31890620a1"><code>fbcb11b</code></a> Update <code>mise@latest</code> to 2026.8.12</li>
<li><a href="https://github.com/taiki-e/install-action/commit/6558a76193bdebc0fcf58fa1120f1c3976bb52b9"><code>6558a76</code></a> Update <code>kingfisher@latest</code> to 2.0.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/7d183c86d7fdea20b30442a1b39048f143f4dd65"><code>7d183c8</code></a> Update editorconfig-checker manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/12f8c84b95b5c8de1be2833276eeae67714b14da"><code>12f8c84</code></a> Update <code>cargo-zigbuild@latest</code> to 0.23.2</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/5b4d68e2e660441203ab128a23676f1e4faf1532...fcf5432d9f50d67e37ee6e29bdb7a224ff67b4a7">compare view</a></li>
</ul>
</details>
<br />


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


Tree-SHA512: 3905b49f736e7577b70244dd1ebcb31a45c39af718544c311a48470d58b5c3d77b1a9b73acf1fb4313a9a3e4d5840e23d42da6eaab6f3e26f8559eb2528da225

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

This is a routine Dependabot update that changes the version of a third-party GitHub Action used in automated testing workflows. The action installs developer tools like cargo-mutants. There is no indication this change fixes or introduces a security vulnerability in the rust-bitcoin library itself.

Security candidateMerge rust-bitcoin/rust-bitcoin#7083: key_expression: Add Xpriv::from_byte_array and Xpub::from_byte_arrayby Andrew Poelstra · 1c363f4f · Oct 26, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7083: key_expression: Add Xpriv::from_byte_array and Xpub::from_byte_array

245733dab9ad8b4917ccc754361e291ceab9440a key_expression: Add Xpriv::from_byte_array and Xpub::from_byte_array (PeterXMR)

Pull request description:

An encoded extended key is always 78 bytes and `encode` already returns `[u8; 78]`, so add `Xpriv::from_byte_array` and `Xpub::from_byte_array` taking `&[u8; 78]`, and make the internal `Common::decode` take the array too.

`decode(&[u8])` is kept unchanged so callers holding a slice, `Vec` or boxed slice keep working via deref coercion without a conversion. It now checks the length, still returning `XkeyDecodeError::WrongExtendedKeyLength` on a mismatch, and delegates to `from_byte_array`. `FromStr` behaves as before.

This is purely additive, there is no API break.

Tests cover `decode` and `from_byte_array` agreeing on valid keys, `decode` rejecting 0, 77 and 79 byte inputs, and `FromStr` returning `InvalidBase58PayloadLength` for payloads of those lengths.

Closes #4196

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


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


Tree-SHA512: 2652c590d8e707a33d33cc0c70ccfe9f6dca24f56f7ce83b5bb757e7b4aa35392e8408919b78cd50e8a274d9e3f9aa8a7e398c51d298e8021b63e2c32a752705

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

This commit adds two new helper functions, Xpriv::from_byte_array and Xpub::from_byte_array, for decoding Bitcoin extended keys from a fixed 78-byte array. It also moves the length check out of an internal helper so the new functions can rely on Rust's type system for length safety. The existing decode(slice) API is preserved and still validates length. There is no security bug or vulnerability here—this is a routine, purely additive API improvement with added tests.

Security candidateRemove default XOnlyPublicKey serde implby Mitchell Bagot · 50940cb2 · Oct 26, 2026 · 1 fileMessage 68 · AdequateInformational 20Details
Commit message · Mitchell Bagot

Remove default XOnlyPublicKey serde impl

With the new x_only_serde module, the default XOnlyPublicKey serde impl
can be entirely dropped.

Remove the default XOnlyPublicKey serde impl.

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

This commit removes the automatic serialization/deserialization support for the XOnlyPublicKey type in the rust-bitcoin library. Previously, serializing this type would silently drop the 'parity' bit (a small piece of metadata indicating whether the full public key was even or odd). Now users must explicitly choose a serialization format from a new module. This is a design cleanup that prevents accidental data loss when the type is serialized, but it is not a fix for an active security vulnerability.

Security candidateRemove uses of default XOnlyPublicKey serdeby Mitchell Bagot · 877faa8f · Oct 26, 2026 · 5 filesMessage 68 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Remove uses of default XOnlyPublicKey serde

Before removing the current default XOnlyPublicKey serde impl, the
existing uses of it should be removed or replaced by the equivalent
format from the new x_only_serde module.

Replace all uses of the old XOnlyPublicKey serde with the new
x_only_serde.
Remove derived serde impl on ControlBlock and TweakedPublicKey.

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

This commit removes and replaces default serialization/deserialization handling for a special Bitcoin public key type (XOnlyPublicKey) in the rust-bitcoin library. It is a cleanup/refactoring change to prepare for a future removal of the old default serde implementation. It also removes derived serde support from two related types (ControlBlock and TweakedPublicKey). There is no direct security fix here; it is an internal API and test-data cleanup.

Security candidateAdd x_only_serde module for XOnlyPublicKey serde encodingby Mitchell Bagot · 65ea85ba · Oct 26, 2026 · 2 filesMessage 73 · AdequateInformational 12Details
Commit message · Mitchell Bagot

Add x_only_serde module for XOnlyPublicKey serde encoding

Currently, the x-only public key serde encodes and decodes using the
inner type, without any parity. Since the bitcoin-crypto type holds the
parity, this makes the type unable to roundtrip odd parity keys.
Instead, with or without parity encoding should be selectable by users.

Add x_only_serde module that provides with_parity and without_parity
serde encoding for the XOnlyPublicKey type.

Assisted by: Claude Opus 5.5

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 · Informational 12/100

This commit adds a new optional serde (serialization) helper module for x-only public keys. It does not change existing behavior or fix a vulnerability; it gives library users an explicit choice between round-tripping parity information or discarding it. There is no security bug visible in the diff.

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

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.

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.