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
975commits · 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 50 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 candidateReplace to_inner with as_inner on Keypairby Mitchell Bagot · bdb0bb74 · Mar 17, 2026 · 5 filesMessage 68 · AdequateLow 28Details
Commit message · Mitchell Bagot

Replace to_inner with as_inner on Keypair

When used on Copy types, to_inner produces a copy of the type. This is
undesirable for secret key types. For Keypair, access to the inner
type is necessary, so to_inner should be replaced by as_inner.

Replace to_inner (owned -> owned) with as_inner (ref -> ref) on
Keypair.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialcryptography-sensitive pathsigning or wallet path
AI analysis · Low 28/100

This commit changes how the library exposes a Bitcoin secret key pair internally. Previously, calling `to_inner()` made a full copy of the secret key data. The new `as_inner()` returns a reference instead, so the secret bytes are not duplicated in memory as often. This is a defensive hardening change: it reduces the number of copies of sensitive key material floating around in memory, which slightly lowers the chance that a secret key could leak through memory dumps, swap, or debugging. It is not a fix for an active bug or a directly exploitable vulnerability.

Security candidateMove script hex parsing to primitivesby Tobin C. Harding · cd735bf2 · Mar 16, 2026 · 10 filesMessage 68 · AdequateInformational 18Details
Commit message · Tobin C. Harding

Move script hex parsing to primitives

Now that we use stable error types we can move the hex parsing
functions from `bitcoin` to `primitives`.

Leave the deprecated method behind in `bitcoin`.

68/100 · AdequateMessage clarity
✓ 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 18/100

This commit is a routine code reorganization: it moves functions that parse Bitcoin script hex strings from the main `bitcoin` crate into the lower-level `primitives` crate. The old functions in `bitcoin` are kept as deprecated aliases so existing code keeps working. There is no security fix or vulnerability here.

Security candidatebitcoin: Stop using FromHexby Tobin C. Harding · 12782954 · Mar 16, 2026 · 1 fileMessage 75 · AdequateInformational 18Details
Commit message · Tobin C. Harding

bitcoin: Stop using FromHex

In the upcoming `hex v1.1.0` we remove the `FromHex` trait. In order
to use that release we need to remove its usage here. The single usage
was left in so as not to change the function signature on a deprecated
signature, just go ahead and do that now. It is still better to keep
the different signature because downstream will get the deprecation
notice and _hopefully_ not too many folk are matching on the return type.

75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 18/100

This is a routine code-maintenance change. The developers replaced one way of reading hexadecimal strings with another, because the old helper tool (the `FromHex` trait) is being removed in an upcoming version of a dependency. The function being changed is already marked as deprecated, so it is not the preferred way to do things. There is no indication this fixes a security bug or introduces a vulnerability.

Security candidateRemove outdated doc from `XOnlyPublicKey::from_secp`by Shing Him Ng · 277e0dce · Mar 16, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Shing Him Ng

Remove outdated doc from `XOnlyPublicKey::from_secp`

50/100 · ThinMessage clarity
✓ Specific, 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 simply removes two outdated lines from a code comment. The removed text incorrectly claimed that the function always sets an even parity, but the function actually accepts a parity argument supplied by the caller. There is no code change and no security issue.

Security candidateDrop the hex_lit dep in favor of built in hexby Nick Johnson · 470795a1 · Mar 16, 2026 · 26 filesMessage 45 · ThinInformational 15Details
Commit message · Nick Johnson

Drop the hex_lit dep in favor of built in hex

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

This commit is a routine dependency cleanup. It removes the external hex_lit crate and switches test/example code to use built-in hex macros from the project's own hex-conservative crate. There is no user-facing behavior change and no security fix or vulnerability introduced.

Security candidateAdd _secret_ to functions that take and return secret bytesby Mitchell Bagot · e3d39953 · Mar 16, 2026 · 1 fileMessage 85 · StrongInformational 20Details
Commit message · Mitchell Bagot

Add _secret_ to functions that take and return secret bytes

In order to make it immediately clear to users when they are working
with or needing secret bytes, all functions that take and return
secret bytes should include the word secret in the function name.

Add _secret_ to all functions in Keypair and PrivateKey that take and
return secret bytes.
Rename from_byte_array to from_secret_bytes.

85/100 · StrongMessage clarity
✓ Specific, 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 20/100

This commit is a routine API rename with no security bug. It renames functions in the Rust Bitcoin library that handle private key bytes so their names include the word 'secret' (for example, 'to_vec' becomes 'to_secret_vec' and 'from_byte_array' becomes 'from_secret_bytes'). The goal is to make it more obvious to developers when they are working with sensitive secret material. The actual behavior of the code is unchanged.

Security candidateRemove all crate-level alloc feature gatesby Mitchell Bagot · 99b7c289 · Mar 16, 2026 · 4 filesMessage 68 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Remove all crate-level alloc feature gates

In addresses, base58, crypto and key_expression, all functionality in
the crate is gated on the alloc feature through a crate-level alloc
feature gate. In some cases, the ordering of the #![no_std] and alloc
gate cause problems with linking against std for no-alloc builds. In
order to completely avoid the potential of that problem, and unify the
crates with the others, all crate-level feature gates should be removed
and replaced with alloc gates on all types and functionality.

Remove crate-level alloc feature gate from addresses, base58, crypto
and key_expression, replacing them with individual feature gates where
necessary.

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

This commit is a build-system cleanup, not a security fix. It removes crate-wide switches that made entire Rust sub-crates disappear when the 'alloc' feature was off, and instead marks individual functions and types as requiring 'alloc'. The stated reason is to fix linking problems in no-alloc builds, not to patch a vulnerability. There is no evidence in the commit of an exploitable bug.

Security candidatepsbt: Handle underflow on small key byte lengthby Mitchell Bagot · ef822345 · Mar 16, 2026 · 1 fileMessage 80 · StrongModerate 65Details
Commit message · Mitchell Bagot

psbt: Handle underflow on small key byte length

In PSBT keys, a change was recently introduced to allow for multi-byte
key type values. In this change, the key data length was changed to
calculate based on the total key length, subtracting the byte count of
the key type compact size value. For malformed PSBT inputs where the
total key length is insufficient to cover the type value compact size,
this causes an underflow in the subtraction, panicing on debug and
potentially causing incorrect behaviour for release.

Instead, this calculation should use a checked_sub, erroring gracefully
when this underflow would otherwise occur.

Change key data length calculation to use checked_sub and return an
InvalidKey error when the total key length value is invalid to parse
the key type correctly.

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
signing boundarysigning or wallet path
AI analysis · Moderate 65/100

This commit fixes a bug in how the library reads PSBT (Partially Signed Bitcoin Transaction) keys. A recent change accidentally made it possible for a malformed input to cause an arithmetic underflow when calculating how many bytes of key data remain. In debug builds that would panic (crash); in release builds it could wrap around and behave incorrectly. The fix uses a safe checked subtraction and returns a proper parsing error instead.

Security candidateMigrate from Honggfuzz to libfuzzerby Shing Him Ng · 35c0b9d3 · Mar 14, 2026 · 44 filesMessage 78 · AdequateInformational 15Details
Commit message · Shing Him Ng

Migrate from Honggfuzz to libfuzzer

This commit has a few main parts:

- Update CI to install required dependencies for libfuzzer
The default Cross s390x image uses an older version of GCC (Ubuntu
20.04), which lacks std::clamp needed by libfuzzer-sys. The s390x
Dockerfile provides Cross with a container with GCC 13, native build
tools, and QEMU for running s390x tests. Cross.toml configures Cross to
use this custom image instead of the default.

- Update the lock files
- Update the fuzz targets to use libfuzzer
- Update the fuzz helper scripts and documentation
- Update the duplicate dependency whitelist to include libc
- Move `fuzz` into a nested workspace

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidencecryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit is a maintenance change that switches the project's fuzz testing framework from Honggfuzz to libfuzzer (cargo-fuzz). It updates build files, CI configuration, documentation, and fuzz target source files to use the new framework. There is no change to the actual Bitcoin library code that end users or applications depend on, and no security vulnerability is introduced or fixed.

Security candidateRemove Display from PrivateKeyby Mitchell Bagot · c04f2dd2 · Mar 13, 2026 · 3 filesMessage 58 · ThinLow 38Details
Commit message · Mitchell Bagot

Remove Display from PrivateKey

As part of the work in hiding secret data in keys, we want to remove
the Display impl for PrivateKey. Users may still display the secret
data using to_wif, or by calling display_secret on the inner key.

Remove Display from PrivateKey.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Low 38/100

This change removes the ability to accidentally print a Bitcoin private key using Rust's standard '{}' formatting. Before, code like println!("{}", private_key) would expose the secret key. Now developers must explicitly call .to_wif() or similar methods, making secret leakage less likely through casual logging or error messages. It is a defensive hardening improvement, not a fix for an active exploit.

Security candidateRemove Index<RangeFull> from PrivateKeyby Mitchell Bagot · e4d46398 · Mar 13, 2026 · 1 fileMessage 68 · AdequateLow 29Details
Commit message · Mitchell Bagot

Remove Index<RangeFull> from PrivateKey

The Index trait allows for indexing on the PrivateKey type. Since we're
working towards hiding secret data in the PrivateKey, this trait should
not be included on the PrivateKey type.

Remove Index<RangeFull> impl on PrivateKey.

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

This commit removes the ability to use square-bracket slicing (like `private_key[..]`) on a Bitcoin private key. The change is part of a longer-term effort to prevent secret key material from being accidentally exposed through Rust's indexing features. It is a hardening cleanup rather than a fix for an active security flaw.

Security candidateAdd hex Display formatting for taproot::Signatureby Mitchell Bagot · bf3d769c · Mar 13, 2026 · 1 fileMessage 83 · StrongInformational 19Details
Commit message · Mitchell Bagot

Add hex Display formatting for taproot::Signature

The ecdsa signature has display formatting which roundtrips with the
corresponding FromStr impl. The taproot signature has no such display
capabilities.

Introduce Display impl on taproot::Signature.
Add test for hex roundtrip with Display + FromStr and FromStr error.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarycryptography-sensitive path
AI analysis · Informational 19/100

This commit adds a human-readable hex display format for Taproot signatures in the rust-bitcoin library, matching a similar feature already available for ECDSA signatures. It is a straightforward feature addition with tests and does not fix any security bug.

Security candidateAdd hex string parsing for taproot::Signatureby Mitchell Bagot · e31b80ee · Mar 13, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Mitchell Bagot

Add hex string parsing for taproot::Signature

The ecdsa::Signature can roundtrip to hex, but taproot::Signature
cannot.

Add FromStr for taproot::Signature and ParseSignatureError as an error
type.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarycryptography-sensitive path
AI analysis · Informational 19/100

This commit adds a new feature: the ability to parse a Taproot cryptographic signature from a hexadecimal text string. Previously only ECDSA signatures could be parsed this way. The change is purely additive and does not fix any known bug or vulnerability. It simply exposes a new parsing function to users of the library.

Security candidatehashes: conservative upgrade to workspace lintsby Nick Johnson · 28ad2d31 · Mar 13, 2026 · 22 filesMessage 45 · ThinInformational 15Details
Commit message · Nick Johnson

hashes: conservative upgrade to workspace lints

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 a code-quality and linting cleanup for the `hashes` crate in rust-bitcoin. It moves the crate to use shared workspace lint rules, adds clippy allow attributes, fixes minor style issues (semicolons, doc formatting, import lists), and adds documentation comments. There are no functional changes to hash algorithms or public APIs, and no security bug is introduced or fixed.

Security candidateMove impl_array_newtype_stringify to includeby Mitchell Bagot · 6df5edae · Mar 12, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Mitchell Bagot

Move impl_array_newtype_stringify to include

The impl_array_newtype_stringify macro is an internal macro in bitcoin
that is used in bip32 and other logic. As part of the separation of
bip32 functionality into a new crate, this macro will be needed.

Split impl_array_newtype_stringify into a module in include/ directory
and include! in existing location in bitcoin.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
secret or key material
AI analysis · Informational 15/100

This commit simply moves an existing internal Rust macro from one file to another shared location. The code itself is unchanged; it is a pure refactoring to prepare for splitting a crate. There is no security-relevant change.

Security candidateMake crate headers uniformby Tobin C. Harding · 36db3222 · Mar 12, 2026 · 7 filesMessage 66 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Make crate headers uniform

I incorrectly churned this in #4667 which was pointed out in #5720 but
only fixed in the stabalizing crates. Now its been done in `hashes`
and again confused me so just do the whole repo already.

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

This commit only changes the wording and formatting of documentation comments at the top of seven source files. It makes crate header titles uniform by adding '#' markers and adjusting capitalization. There are no code changes, no security fixes, and no behavior changes.

Security candidatedocs: Favour Constructs over Createsby Tobin C. Harding · bab4f99c · Mar 12, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Tobin C. Harding

docs: Favour Constructs over Creates

We decided a while back to favour `/// Constructs ...` but some
`/// Creates ...` have snuck in again.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only changes two words in code comments, replacing 'Creates' with 'Constructs' in documentation. There is no change to actual program logic, no security fix, and no behavior change.

Security candidateexamples: Use NetworkKind in call to PrivateKey::from_secby Tobin C. Harding · 6012d8a4 · Mar 11, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Tobin C. Harding

examples: Use NetworkKind in call to PrivateKey::from_sec

Guide users to the `NetworkKind` by calling `PrivateKey::from_secp`
with it. Done because I was confused the other day why private key
needed the network and I've been hacking on this library for 5 years
now ...

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
secret or key material
AI analysis · Informational 15/100

This is a tiny documentation-style change to an example file. It swaps one way of saying 'use the Bitcoin main network' for another equivalent way, with no effect on actual code behavior or security.

Security candidatebitcoin: Remove uses of HexToBytesErrorby Mitchell Bagot · 22140d7a · Mar 11, 2026 · 10 filesMessage 80 · StrongInformational 19Details
Commit message · Mitchell Bagot

bitcoin: Remove uses of HexToBytesError

The HexToBytesError in hex_conservative comes from the unstable version
of the crate. Since we want to avoid unstable hex conservative in the
public API, we should remove all uses of this error.

Remove all direct uses of HexToBytesError in bitcoin and remaining
uses of unstable FromHex trait.

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 pathsigning or wallet path
AI analysis · Informational 19/100

This commit swaps out an unstable, experimental hex-decoding helper for a stable, project-owned one. It is a cleanup/refactoring change to keep the public API from depending on a crate version that is not yet finalized. There is no direct security bug being fixed; the main risk is that if done incorrectly, error handling could change slightly for users parsing hex strings.

Security candidatebitcoin: Remove uses of HexToArrayErrorby Mitchell Bagot · 9f3eca94 · Mar 11, 2026 · 3 filesMessage 80 · StrongInformational 17Details
Commit message · Mitchell Bagot

bitcoin: Remove uses of HexToArrayError

The HexToArrayError in hex_conservative comes from the unstable version
of the crate. Since we want to avoid unstable hex conservative in the
public API, we should remove all uses of this error.

Remove all direct uses of HexToArrayError in bitcoin.

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

This commit is a routine internal cleanup in the rust-bitcoin library. It swaps one hex-decoding helper for another equivalent one so the library no longer depends on an 'unstable' public API from a dependency. There is no indication this fixes a security bug or changes behavior visible to users in a dangerous way.

Security candidateMove impl blocks to below struct definitionby Jamil Lambert, PhD · 690da807 · Mar 10, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · Jamil Lambert, PhD

Move impl blocks to below struct definition

Some of the Hmac impl blocks were seperate from the others.

Move them so that they are all together directly below the struct
definition.

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

This commit only moves existing code around in the same file. It takes several implementation blocks for the Hmac type and places them directly below the Hmac struct definition instead of further down after another struct. No code behavior, logic, or public interface was changed.

Security candidateMove hash implementations to the topby Jamil Lambert, PhD · d6a6e0ef · Mar 10, 2026 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Move hash implementations to the top

To make all the modules consistent move the hash impl to the top.

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

This commit simply moves existing code around in two files. It relocates the implementation blocks for SHA256 and SipHash24 hash types to appear earlier in their respective files, right after the hash type is declared. No code behavior was changed, no bugs were fixed, and no security issues were introduced.

Security candidatekeys: Remove rng argument from Keypair::generateby Mitchell Bagot · 37c7a197 · Mar 9, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Mitchell Bagot

keys: Remove rng argument from Keypair::generate

The Keypair::generate function follows the signature of the underlying
secp library, in that it takes a rand generator. The existing
PrivateKey generate instead constructs the rand generator internally,
hiding the extra complexity from the user to provide a cleaner
interface.

Remove rng argument from Keypair::generate and adjust call sites
accordingly.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnesssigning boundarycryptography-sensitive path
AI analysis · Informational 19/100

This is a routine API cleanup, not a security fix. The change removes the requirement for callers to supply their own random number generator when creating a new keypair. Instead, the function now creates the generator internally, matching how the related PrivateKey API already works. There is no vulnerability here; it is a convenience and consistency change.

Security candidateCreate an empty key-expression crateby Mitchell Bagot · a44409cb · Mar 7, 2026 · 8 filesMessage 60 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Create an empty key-expression crate

In preparation for crate smashing the bip32 module and associated
functionality, create an empty crate.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
secret or key material
AI analysis · Informational 15/100

This commit creates a brand-new, empty placeholder crate named 'bitcoin-key-expression' inside the rust-bitcoin workspace. It contains no code, no logic, and no changes to existing behavior. It is purely a structural preparation step for future development.

Security candidateAdd parity argument to XOnlyPublicKey::from_secpby Mitchell Bagot · c74bf550 · Mar 7, 2026 · 1 fileMessage 68 · AdequateInformational 19Details
Commit message · Mitchell Bagot

Add parity argument to XOnlyPublicKey::from_secp

The XOnlyPublicKey from_secp constructor is the main method of creating
XOnlyPublicKey objects. At the moment, many places where it is used are
followed by a subsequent with_parity() call.

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

This commit is a small API cleanup in a Rust Bitcoin library. It changes one constructor so callers must provide a 'parity' value directly instead of setting it afterward. Existing callers are updated to preserve the same behavior as before. There is no indication this fixes a security bug or changes any security-relevant behavior.