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 52 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 candidateSplit encapsulate module to modules per typeby Mitchell Bagot · cd167603 · May 27, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Split encapsulate module to modules per type

The encapsulate module is a name copied from units, where module files
hold encapsulate modules with a single type and a limited API surface.
In crypto::key, the encapsulate module has grown to encompass all of
the key types, which makes it unwieldy. It should be broken into
modules per type, like the single-type encapsulate modules in units.

Split encapsulate module into individual modules per type and adjust
re-exports accordingly.

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

This commit is a straightforward internal code reorganization. It takes a single large module named 'encapsulate' in the cryptographic key code and splits it into several smaller modules, one for each key type. The public types and their behavior remain exactly the same; only the internal file/module structure and re-export paths changed. There is no security fix or vulnerability here.

Security candidateAdjust BIP340 in tapsighash docsby Mitchell Bagot · 43df739f · May 27, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Adjust BIP340 in tapsighash docs

It is policy in this repo to use 4-digit zero padded numbers for BIPs
in documentation. BIP-340 should thus be BIP-0340 in the tapsighash
signing function docs.

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

This commit only fixes the formatting of a documentation link. It changes 'BIP-340' to 'BIP-0340' and wraps the URL in angle brackets so it renders correctly in Rust's generated documentation. No code behavior was changed, and there is no security impact.

Security candidateReplace pk with key in sighash signby Mitchell Bagot · 1bc56e90 · May 27, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Replace pk with key in sighash sign

'pk' typically is shorthand for public key, not private key. Instead,
the generic term key would better suit.

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Informational 15/100

This commit is a simple variable rename from 'pk' to 'key' in two Rust functions because 'pk' is commonly understood to mean public key, while the parameter is actually a private key. There is no change to program logic, no security fix, and no behavior change.

Security candidatebip32: validate master key seed lengthby satsfy (Renato Britto) · 284ed9c8 · May 26, 2026 · 3 filesMessage 68 · AdequateLow 35Details
Commit message · satsfy (Renato Britto)

bip32: validate master key seed length

BIP-32 requires the master seed to be between 16 and 64 bytes, but
new_master accepted any length. bitcoinfuzz flagged this as a
inconsistency on seeds out of range.

Introduce a Bip32Seed type that validates on construction.
new_master now takes a ref to Bip32Seed (a transparent newtype of
&[u8]). Fixed-size arrays go through infallible From<[u8; N]>. Slices
go through TryFrom<&[u8]> returning InvalidSeedLengthError.
`Debug` shows first 4 bytes of seed's sha256. `PartialEq` fixed
time equality comparison based on hashes.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialdefensive validationfuzzing or regression evidencecryptography-sensitive path
AI analysis · Low 35/100

This commit tightens input checking for Bitcoin wallet master-key creation. Previously, the library would accept any seed length when creating a BIP-32 master key, even though the standard only allows seeds between 16 and 64 bytes. Now it validates the length and rejects out-of-range seeds. It also changes how seed bytes are printed in debug logs so the full secret is no longer exposed, and compares seeds in constant time to reduce timing side-channel risk.

Security candidatePromote BLOCK_SIZE assertion to hard assertby Jamil Lambert, PhD · 8f2ee2b8 · May 25, 2026 · 1 fileMessage 68 · AdequateModerate 60Details
Commit message · Jamil Lambert, PhD

Promote BLOCK_SIZE assertion to hard assert

The debug_assert only fires in debug builds; a downstream HashEngine
implementation with BLOCK_SIZE > 128 would silently produce wrong
outputs in release builds by indexing into fixed-size 128-byte ipad/opad
buffers beyond their length.

Change to assert! so the check is unconditional.

Assisted-by: claude-sonnet-4.6

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

This commit fixes a safety check in the HMAC code. Previously, the code only verified in debug builds that a hash engine's block size did not exceed 128 bytes. In release builds, an oversized block size would cause the code to write past the end of fixed 128-byte internal buffers, leading to incorrect HMAC results or memory corruption. The fix makes this check run unconditionally by changing a debug-only assertion into a regular assertion.

Security candidateIntroduce signing functions on sighash typesby Mitchell Bagot · 3edf875b · May 25, 2026 · 3 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Introduce signing functions on sighash types

Although the private key types have raw signing functions on them that
allow users to bypass secp, they still present a rough interface for
signing compared to directly signing on the sighash types that result
from the SighashCache.

Introduce signing functions on LegacySighash, SegwitV0Sighash and
TapSighash.

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
secret or key materialsigning boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit adds convenience helper methods that let developers sign Bitcoin transaction hash values more directly. It does not change any security-critical behavior; the same cryptographic signing operations were already available through other functions. The change is purely an API usability improvement.

Security candidateChange TapTweak to take self by refby Mitchell Bagot · 0e0146be · May 25, 2026 · 1 fileMessage 68 · AdequateInformational 19Details
Commit message · Mitchell Bagot

Change TapTweak to take self by ref

The TapTweak trait in bitcoin::key currently consumes the untweaked
key to construct the tweaked key. While this is mostly fine for users
who manually call into it, it prevents clean usage in functions that
take Keypair refs.

Change TapTweak::tap_tweak to take self by ref instead of by value.

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 is a small API ergonomics change in a Rust Bitcoin library. A function called tap_tweak is changed so callers pass a reference to the key instead of giving up ownership of the key. It does not fix a bug or vulnerability; it makes the library easier to use in code that holds key references.

Security candidatehashes: Bump version to 0.21.0by Tobin C. Harding · 411e4473 · May 25, 2026 · 12 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

hashes: Bump version to 0.21.0

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

One last release before we 1.0 this crate team.

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

This commit is a routine release-preparation change. It bumps the version number of the `bitcoin_hashes` crate from 0.20.0 to 0.21.0, updates the project's lock files, and adds a changelog entry summarizing prior changes. There is no code change that fixes or introduces a security issue in this commit itself.

Security candidate2026-05-24 automated rustfmt nightlyby Fmt Bot · acaec902 · May 24, 2026 · 10 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-05-24 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 pathsigning or wallet path
AI analysis · Informational 15/100

This is a purely cosmetic code-formatting commit. It only reorders imports, rewraps long lines, and collapses or expands function bodies to match the latest rustfmt nightly style. No program logic, behavior, or security properties were changed.

Security candidatehashes: Remove Bytes and LEN from HashEngineby jrakibi · caf9e7b4 · May 21, 2026 · 14 filesMessage 68 · AdequateInformational 18Details
Commit message · jrakibi

hashes: Remove Bytes and LEN from HashEngine

Simplify the API by removing Bytes and LEN from HashEngine.
Callers can still use HashEngine::Hash::LEN and
HashEngine::Hash::Bytes to access those values.

This will automatically solve the inconsistency between
HashEngine and Hash we found for sha512_256 output size.

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 is a routine code cleanup in the rust-bitcoin hashes library. It removes duplicate ways of asking a hash engine for the output length and byte type, directing callers to use the associated Hash type instead. The commit message explicitly says this fixes an inconsistency discovered for the sha512_256 output size, but the change itself is an API simplification, not a security patch. There is no evidence of a vulnerability being fixed.

Security candidateMove PushBytes and co to primitivesby Mitchell Bagot · 58965872 · May 20, 2026 · 12 filesMessage 68 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Move PushBytes and co to primitives

To simplify the move of Address to the new addresses crate, the
PushBytes type can be moved to primitives first.

Move PushBytes, PushBytesBuf, PushBytesError and PushBytesErrorReport
to primitives.

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 is a routine internal code reorganization. It moves the PushBytes family of types and helpers from the main bitcoin crate into a lower-level primitives crate, and adjusts re-exports and trait implementations accordingly. There is no indication of a security bug being fixed or introduced.

Security candidateFix lint errors in primitives and cryptoby Mitchell Bagot · dd3aaf61 · May 20, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Fix lint errors in primitives and crypto

With the move of PushBytes and co to primitives, a handful of lint
errors are now thrown in both crypto and primitives.

Fix lint errors in primitives and crypto.

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

This is a routine code cleanup commit that fixes compiler lint warnings. It removes an unused import, simplifies how a borrowed reference is obtained, makes a large numeric constant more readable with underscores, and adds a missing semicolon. None of these changes affect program behavior or fix any security issue.

Security candidateMove impl_asref_push_bytes macro to includeby Mitchell Bagot · ff4362be · May 20, 2026 · 6 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move impl_asref_push_bytes macro to include

This macro will be used in multiple crates following the move of
PushBytes to primitives. To reduce code duplication, it should be
moved to the include directory and introduced into each crate as
needed using include!.

Move impl_asref_push_bytes to include/asref_pushbytes.rs and include!
in bitcoin.

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

This commit is a routine code reorganization. It moves a small helper macro that implements conversions for script push bytes from one internal file to a shared include directory, then pulls it back in with no functional changes. There is no security issue here.

Security candidatecrypto: Add primitives depby Mitchell Bagot · 327313f2 · May 20, 2026 · 3 filesMessage 70 · AdequateInformational 15Details
Commit message · Mitchell Bagot

crypto: Add primitives dep

In order to stabilise PushBytes now, the impls of AsRef/Borrow, etc
between PushBytes and the crypto types need to be in a non-stable
crate until the crypto types are stable. While we want primitives to
depend on crypto eventually, for now, the only way to stabilise
PushBytes in primitives is to invert the dependency and put the impls
in crypto.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only changes build configuration files (Cargo.toml and lock files) to add a new internal crate dependency. It does not modify any executable code, fix a bug, or address a security issue. It is a routine refactoring step to resolve a dependency direction problem during library development.

Security candidaterefactor(bip32): make child number a newtype ChildNumber(u32)by Trevor Arjeski · a4e61e3a · May 19, 2026 · 2 filesMessage 85 · StrongLow 32Details
Commit message · Trevor Arjeski

refactor(bip32): make child number a newtype ChildNumber(u32)

Convert from an enum into a private newtype `ChildNumber(u32)` that stores the
raw u32 value. This resolves the FIXME that describes an invariant where someone
could create a child number that is out of range for the given variant. Now we
have constructors that check the range.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Low 32/100

This commit refactors how BIP-32 child key indexes are represented in the rust-bitcoin library. Previously, the index was a public enum with separate fields for normal and hardened variants, and the commit message notes a FIXME: because those fields were public, callers could directly create an out-of-range index (for example, a 'normal' index with the high bit set). The change turns the type into a private newtype around a raw u32 and forces construction through checked constructors that validate the range. It is a defensive hardening change that closes a potential invariant violation, but it does not by itself fix a demonstrated exploit.

Security candidateAdd weekly cron job to update cargo rbmt to latest releaseby Benalleng · 2eaaa2ec · May 18, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Benalleng

Add weekly cron job to update cargo rbmt to latest release

This cron job runs every week but will only add a PR to update the
`rbmt-version` file if there is a new published release tag.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update pathdocumentation-only discount
AI analysis · Informational 15/100

This commit adds a scheduled GitHub Actions workflow that runs once a week to check for new releases of an internal maintainer tool (cargo-rbmt). If a newer release exists, it automatically opens a pull request updating a version-tracking file. There is no user-facing code change, no bug fix, and no security-sensitive behavior introduced.

Security candidate2026-05-17 automated rustfmt nightlyby Fmt Bot · f0178809 · May 17, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-05-17 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 a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and brace style in five files. There are no functional code changes, no bug fixes, and no security-related alterations.

Security candidatecrypto: Remove alloc feature gate from taproot moduleby Mitchell Bagot · b91a6600 · May 16, 2026 · 2 filesMessage 73 · AdequateInformational 18Details
Commit message · Mitchell Bagot

crypto: Remove alloc feature gate from taproot module

During the move of the taproot module into crypto, the alloc feature
was used to gate the entire module for simplicity. However, to match
the ecdsa module, gating should only be used on the types and
functionality necessary within the module.

Remove feature gate from taproot module and individually gate
functionality in the taproot module.

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

This change is a routine code cleanup, not a security fix. It removes an overly broad feature gate so that parts of the Taproot cryptographic module are available even when the optional 'alloc' feature is disabled, while keeping functions that actually need memory allocation behind the gate. There is no indication it fixes a vulnerability.

Security candidatecrypto: Change taproot::Signature FromStr to array hex decodeby Mitchell Bagot · 7422a744 · May 16, 2026 · 1 fileMessage 78 · AdequateInformational 17Details
Commit message · Mitchell Bagot

crypto: Change taproot::Signature FromStr to array hex decode

The taproot::Signature FromStr impl currently uses hex::decode_to_vec
to parse the hex into a byte vector which is then decoded with
from_slice. Since a valid signature can only be 64 or 65 bytes long,
the alloc dependency can be entirely removed by instead using
decode_to_array with a preceeding string length check.

78/100 · AdequateMessage clarity
✓ Specific, 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 17/100

This commit is a small internal cleanup in the rust-bitcoin library. It changes how a Taproot signature is parsed from a hexadecimal string so that it no longer needs to allocate a temporary byte vector. The change removes an unnecessary memory allocation but does not alter the allowed signature formats or fix any vulnerability. It is a performance and dependency-reduction refactor, not a security fix.

Security candidateRemove the unstable hex-conservative dependencyby Tobin C. Harding · a7787c1c · May 16, 2026 · 57 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Remove the unstable hex-conservative dependency

BOOM! Now that `hex 1.1.0` is out we can remove the unstable dep. This
is a breaking change all the way down the stack and will require
re-releases.

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

This commit is a routine dependency cleanup. The project previously had to use two different versions of the same hex-encoding helper library (one stable, one unstable preview) because a needed feature was only available in the unstable version. Now that the stable library released version 1.1.0 with that feature, the commit removes the unstable dependency and switches everything to the single stable version. It is not a security fix and does not change how the software behaves to users.

Security candidatehashes: Add `Arbitrary` impl for `Hmac`by Ismail Daif · 3715b605 · May 15, 2026 · 2 filesMessage 45 · ThinInformational 16Details
Commit message · Ismail Daif

hashes: Add `Arbitrary` impl for `Hmac`

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

This commit adds a standard trait implementation that lets the Hmac type be used with property-testing tools. It is a routine feature addition, not a security fix or vulnerability.

Security candidateReplace as_inner accessor on XOnlyPublicKey with to_innerby Mitchell Bagot · 0cb19c0c · May 13, 2026 · 1 fileMessage 73 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Replace as_inner accessor on XOnlyPublicKey with to_inner

Access to the inner types for the key wrappers should be uniform.
Specifically, for the public Copy types, inner access should be by
value. To achieve this XOnlyPublicKey::as_inner must be removed.

Remove XOnlyPublicKey::as_inner.

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

This commit is a routine API cleanup in the rust-bitcoin crypto library. It removes a method called as_inner that returned a reference to the underlying key data, and replaces internal uses with to_inner, which returns the key by value. The underlying key type is small and cheap to copy, so this is a consistency improvement, not a security fix. There is no indication this change addresses a vulnerability.

Security candidateMake to_inner on public key types pub(super)by Mitchell Bagot · 1d95006d · May 13, 2026 · 2 filesMessage 68 · AdequateInformational 23Details
Commit message · Mitchell Bagot

Make to_inner on public key types pub(super)

The to_inner function was introduced as a stop-gap to eliminate the
public access to inner secp types on the public key types. Now that
the key types have been adjusted such that inner access is no longer
needed outside of crypto, these conversion methods can be made private.

Make to_inner on all public key types pub(super).

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

This commit narrows the visibility of internal helper methods named to_inner on Bitcoin public-key types. Previously any outside code could call these methods to extract the raw underlying secp256k1 key objects; now only code inside the same module can do so. This is a defensive encapsulation change that reduces the public API surface and makes future misuse or accidental exposure of internal cryptographic details less likely. It is not a fix for an active vulnerability.

Security candidatehashes: capitalize hash algorithm namesby jrakibi · 3263f1ec · May 12, 2026 · 14 filesMessage 45 · ThinInformational 15Details
Commit message · jrakibi

hashes: capitalize hash algorithm names

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 only changes the capitalization of hash algorithm names in comments and documentation strings (for example, 'sha256' becomes 'SHA256' and 'sha256d' becomes 'SHA256d'). No program logic, code behavior, or security properties were modified.

Security candidatehashes: Fix doc typosby jrakibi · d25913a5 · May 12, 2026 · 7 filesMessage 43 · ThinInformational 15Details
Commit message · jrakibi

hashes: Fix doc typos

- Add missing full stop
- Capitalize first words in doc comments

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only fixes typos and formatting in documentation comments and test file comments. No code behavior changes.