RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

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

459security candidates448second-pass queue969AI analyses
188commits · 30 days
404commits · 60 days
1283commits · 180 days
2064commits · 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.

64/100 average clarity
311Strong · 80–100
1054Adequate · 60–79
555Thin · 40–59
150Opaque · 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.
Mitchell Bagot640192332068
Tobin C. Harding40965152063
jrakibi944963068
Nick Johnson1892091059
Andrew Poelstra512033075
Jamil Lambert, PhD1141849061
Fmt Bot311420045
Trevor Arjeski111111069
Shing Him Ng31724056
Ismail Daif22612050
satsfy (Renato Britto)17611066
Martin Habovstiak27511069
Analysis record

Published AI watches

Last scanned 9 minutes ago

Informational 15 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktime

This commit only changes documentation comments and variable names in the rust-bitcoin library. It rewords references to 'block height' as 'block count' for relative locktime, because a relative locktime measures elapsed blocks since a coi…

6ea4ff92by Andrew Poelstra+20−172 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6670: ci: fix labeller permissions

This is a routine GitHub Actions workflow fix. The change gives the automated PR labeler workflow permission to download artifacts and explicitly tells the GitHub CLI which repository to act on. It does not change the Bitcoin library code,…

CI workflow permission fixNo source code changesNo cryptographic or consensus changes
276e0a61by Andrew Poelstra+5−01 file
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6657: Release tracking PR: `base58ck 0.5.0`

This commit is a routine version bump for the base58ck crate from 0.4.0 to 0.5.0. It only updates version numbers in package manifests, lock files, and adds a changelog entry. There are no code changes and no security relevance.

9deb5de1by Andrew Poelstra+22−168 files
No security note in commit
Informational 21 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decoding

This commit is a routine feature addition to the rust-bitcoin base58 crate. It adds a new no-allocator function to decode short base58-check strings into fixed-size byte arrays, and renames the existing error type while keeping a deprecate…

No security-relevant bug fix is described in the commit message or diff.New decoding path uses a fixed 128-byte scratch buffer (`ArrayVec`) and rejects oversized inputs.Checksum verification and invalid-character handling are preserved from the existing alloc implementation.
c5fd1832by Andrew Poelstra+330−775 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0

This commit is a routine feature release for the bitcoin_hashes crate. It adds new public methods and a constant to the SHA-256 Midstate type so developers can compute SHA-256 midstates in const contexts. There is no indication of a securi…

0f68fcb3by Andrew Poelstra+157−4210 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: reword docs to block count in relative locktime

This commit only rewords documentation comments and variable names in the codebase. It changes references from 'block height' to 'block count' for relative lock times, which is a terminology correction with no functional code changes. Ther…

8867fe2eby satsfy (Renato Britto)+20−172 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` private

This commit makes a small internal helper type called WitnessesEncoder private. It was previously exported as public API but is only used inside the transaction encoder. The change removes it from the public API surface and moves the code …

07d91f7fby Andrew Poelstra+54−1324 files
No security note in commit
Informational 12 AI analysisMessage 75 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: fix labeller permissions

This commit adjusts a GitHub Actions workflow that automatically labels pull requests based on CI results. It adds a built-in repository token, tells the artifact download step to merge single-file artifacts, and explicitly sets the reposi…

Workflow-only change with no library code modificationsUses the default GITHUB_TOKEN rather than a custom secretRuns in workflow_run context, which already has elevated repository access by design
715f2bd6by Nick Johnson+5−01 file
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logic

This commit is a pure code reorganization (refactor) in the rust-bitcoin library. It moves transaction encoding and decoding definitions around within a single file so the code follows the project's preferred layout. No logic, behavior, or…

c5588ba5by Andrew Poelstra+57−571 file
No security note in commit
Informational 18 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6662: build(deps): bump actions/checkout from 6.0.2 to 6.0.3

This commit is a routine update to the GitHub Actions checkout tool used by the project's automated workflows. It changes the pinned version from 6.0.2 to 6.0.3 across many workflow files. The newer version fixes minor bugs related to SHA-…

Dependency bump of actions/checkout to a patch releaseUpstream fixes for SHA-256 repository checkout and merge commit regexAll affected workflows already disable persisted credentials
f7d364cdby Andrew Poelstra+29−2915 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6663: build(deps): bump taiki-e/install-action from 2.79.12 to 2.81.4

This is a routine Dependabot update that bumps the version of a third-party GitHub Action used only in automated testing workflows. The change does not touch the project's actual Bitcoin library code, and there is no indication it fixes or…

5c92c0b0by Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Scrub the transaction encoding logic

This commit is a pure code reorganization: it moves existing transaction encoding and decoding definitions around within a single file so they follow the project's preferred layout. No logic was changed, no security bug was fixed, and no n…

80dcef15by Tobin C. Harding+57−571 file
No security note in commit
Informational 15 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Make the WitnessesEncoder private

This commit simply hides an internal helper type called WitnessesEncoder from public view. It is a routine API-cleanup change with no security relevance visible in the code or commit message.

b37accc3by Tobin C. Harding+54−542 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump astral-sh/setup-uv from 8.1.0 to 8.2.0

This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install the 'uv' Python tool in two workflow files. The new commit hash corresponds to the legitimate 8.2.0 release of astral-sh/se…

1c438632by dependabot[bot]+2−22 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 automated update by Dependabot that changes the pinned version of a GitHub-provided security scanning helper used in a workflow. It does not modify the project's actual Bitcoin library code, its cryptographic logic, or an…

5293bee4by 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 taiki-e/install-action from 2.79.12 to 2.81.4

This is a routine Dependabot update that bumps a GitHub Actions helper used in automated testing workflows from version 2.79.12 to 2.81.4. It only changes which version of the action is invoked during CI runs; it does not modify the Rust B…

eb9544f9by dependabot[bot]+2−22 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump actions/checkout from 6.0.2 to 6.0.3

This is a routine automated update by Dependabot that bumps the GitHub Actions 'actions/checkout' dependency from version 6.0.2 to 6.0.3 across all project workflow files. It only changes pinned commit hashes and version comments for the a…

Routine patch-level dependency bumpNo changes to permissions, inputs, or workflow logicpersist-credentials: false already present on all checkout steps
ae935fadby dependabot[bot]+29−2915 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update API files

This commit only updates generated API snapshot text files to remove two lines that documented a `From<u16>` conversion for a locktime type. No actual Rust source code was changed, so there is no runtime behavior change or security fix in …

6ea25bedby Mitchell Bagot+0−123 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

base58ck: Bump version to 0.5.0

This commit is a routine version bump for the base58ck crate from 0.4.0 to 0.5.0. It only updates version numbers in package manifests, lock files, and adds a changelog entry describing unrelated feature changes. There are no code changes,…

8479b56eby Tobin C. Harding+22−168 files
No security note in commit
Informational 20 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Rename Error to DecodeCheckError

This commit is a routine code cleanup: it renames the `Error` type in the base58 module to the more descriptive `DecodeCheckError`, and adds a deprecated type alias so existing code using `base58::Error` continues to work. There is no chan…

b0eba4c0by Mitchell Bagot+45−395 files
No security note in commit
Repository ledger

Explore captured commits

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

Lower-priorityRemove unused types and macros from internals::serdeby Mitchell Bagot · 0b2cb459 · Jun 9, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Remove unused types and macros from internals::serde

The IntoDeError and serde_struct_human_string_impl macro in
internals::serde are both entirely unused. These two are neither used
privately within internals, nor publicly by other crates.

Drop IntoDeError and serde_struct_human_string_impl from
internals::serde.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMove SerializeBytesAsHex to primitivesby Mitchell Bagot · 966d9295 · Jun 9, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Mitchell Bagot

Move SerializeBytesAsHex to primitives

The SerializeBytesAsHex type in internals is only ever used in Witness
in primitives. Rather than provide the type from internals, the type
can instead be pasted in-line in the primitives witness module (as a
private type) and used there.

Move SerializeBytesAsHex type as private type to primitives::witness.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Lower-priorityDrop wrap_debug module from internalsby Mitchell Bagot · a6683bc2 · Jun 9, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Drop wrap_debug module from internals

The wrap_debug module in internals is only ever used in Witness in
primitives. Rather than provide the module from internals, the type
can instead be pasted in-line in the primitives witness module (as a
private type) and used there.

Copy WrapDebug type as private type to primitives::witness and drop
wrap_debug module from internals.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidateMove serde_round_trip macro to bip32by Mitchell Bagot · 3cf7554a · Jun 9, 2026 · 5 filesMessage 78 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move serde_round_trip macro to bip32

The serde_round_trip macro from internals is only used in the bip32
module for testing. Rather than pulling it in from internals, it should
instead be defined in-line in the tests module.

Move serde_round_trip macro to bip32. Add bincode dev dependency to
key_expression.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Informational 15/100

This commit is a routine code cleanup: it moves a small test-only helper macro from a shared internal utility crate into the one place it is actually used. There is no change to user-facing behavior, no bug fix, and no security relevance.

AI review queuedprimitives: Re-order transaction codeby Tobin C. Harding · 6e2bb39a · Jun 9, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · Tobin C. Harding

primitives: Re-order transaction code

Put the encoding stuff in the conventional order and put other trait
impls all together.

Do `transaction` separately because its a bit more involved.

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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a pure code reorganization: it moves existing implementations of string formatting, hex display, encoding, and decoding for Bitcoin transactions into a different order within the same file. No logic was changed, no bugs were fixed, and no security behavior was altered.

Lower-priorityprimitives: Re-order encoding codeby Tobin C. Harding · 031392c3 · Jun 9, 2026 · 4 filesMessage 80 · StrongTriage 0Details
Commit message · Tobin C. Harding

primitives: Re-order encoding code

I thought we scrubbed this code but the code layout is not correct
here.

We are trying to make all the encoding code be **exactly** the same
because it is boilerplate and is going to live on various branches.

Re-order the code to match our convention.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Security candidateRemove Verification re-exportsby Mitchell Bagot · 31c3e51b · Jun 9, 2026 · 2 filesMessage 68 · AdequateInformational 20Details
Commit message · Mitchell Bagot

Remove Verification re-exports

These re-exports exist from the days when secp required an explicit
context for cryptographic operations. With the introduction of the
global context in recent secp versions, they are no longer needed.

Remove Verification re-exports from key modules.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Informational 20/100

This commit simply stops publicly re-exporting a secp256k1 type called `Verification` from two Rust Bitcoin key modules. It is a routine API cleanup: the type is still available directly from the underlying secp256k1 library, so no cryptographic capability is removed, only a convenience shortcut. There is no security bug or vulnerability here.

Lower-prioritypolicy: update docs on ordering derivesby Nick Johnson · ee1b1416 · Jun 8, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Nick Johnson

policy: update docs on ordering derives

`rust-ordering` is no longer recommended and was removed from the
workspace in #4065 (38c8c9).

There are types like `NetworkKind` which derive order and it is used
downstream in other workspace packages to also derive order (e.g. Xpub).
I believe this derive actually caused issues before in v0.32.4,
discussed in issue #4116. But it probably low risk going forward since
the enum is exhaustive and I don't think someone would change the
variant order just for fun.

This more general policy is discussed in #3865.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Lower-priorityunits: Add mention of wu to hex parsing functionsby Tobin C. Harding · db49559d · Jun 8, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Tobin C. Harding

units: Add mention of wu to hex parsing functions

The `Weight` type has a bunch of constructors each of which mentions
the unit used. However the hex parsing constructors do not mention the
weight unit, add it.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityunits: Use uniform docs style for 1000by Tobin C. Harding · 35303ad9 · Jun 8, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Tobin C. Harding

units: Use uniform docs style for 1000

We have '1000' and also '1,000' - pick one and be uniform.

Favour using the comma because we already have other usages eg
1,000,000

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityunits: Fix typoby Tobin C. Harding · c91ce9ef · Jun 8, 2026 · 1 fileMessage 43 · ThinTriage 0Details
Commit message · Tobin C. Harding

units: Fix typo

Should be 'from amount' like the other constructors that take an
`Amount` type.

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Lower-priorityunits: Use little t in docsby Tobin C. Harding · 4b4341b9 · Jun 8, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Tobin C. Harding

units: Use little t in docs

We use locktime 'n' (lowercase) but time 'T' (uppercase) in docs.
There does not seem to be a reason, I think lowercase reads better.
This may be subjective.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI review queuedunits: Use uniform whitespace in constsby Tobin C. Harding · cc9441fb · Jun 8, 2026 · 4 filesMessage 80 · StrongInformational 15Details
Commit message · Tobin C. Harding

units: Use uniform whitespace in consts

In some places we have no newlines between associated consts and in
others we have newlines. Lets pick one and be uniform.

Elect to use whitespace.

\me ducks to avoid flaming.

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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds or removes blank lines between constant definitions in four source files to make the code style consistent. It does not change any program logic, values, or behavior, so it has no security relevance.

Lower-priorityunits: Group private and public modules separatelyby Tobin C. Harding · a4b8391d · Jun 8, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Tobin C. Harding

units: Group private and public modules separately

As is customary group the private modules above the public ones.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityunits: no_inline errorby Tobin C. Harding · 322e49da · Jun 8, 2026 · 1 fileMessage 43 · ThinTriage 0Details
Commit message · Tobin C. Harding

units: no_inline error

As is customary here, use `no_inline` on error re-export.

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Lower-priorityunits: Fix fee_rate docsby Tobin C. Harding · e0cbd282 · Jun 8, 2026 · 1 fileMessage 43 · ThinTriage 0Details
Commit message · Tobin C. Harding

units: Fix fee_rate docs

Users get unit using the `to_sat_per` family of functions not
`from_sat`.

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Lower-priorityunits: Remove unnecessary unit testsby Tobin C. Harding · 46abb61b · Jun 8, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Tobin C. Harding

units: Remove unnecessary unit tests

We have two unit tests that test that we call through from a
deprecated function to its replacement. Remove them.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
AI review queuedunits: Remove all deprecated codeby Tobin C. Harding · f2618b6c · Jun 8, 2026 · 9 filesMessage 60 · AdequateInformational 19Details
Commit message · Tobin C. Harding

units: Remove all deprecated code

In preparation for releasing `v1.0.0` remove all deprecated code.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit removes old, deprecated function names and type aliases from the rust-bitcoin `units` crate in preparation for a 1.0.0 release. It is a routine API cleanup: no security bug is fixed and no new unsafe code is added. Downstream projects that still use the removed names will get compile-time errors and must switch to the replacement APIs.

Lower-priorityUpdate the API text filesby Tobin C. Harding · 05855fee · Jun 8, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Tobin C. Harding

Update the API text files

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityunits: Remove usage of deprecated to_hexby Tobin C. Harding · 34aa4463 · Jun 8, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Tobin C. Harding

units: Remove usage of deprecated to_hex

This function is deprecated, no need to use it in test code.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Security candidateReplace usage of secp256k1::Error with new errors in keyby Mitchell Bagot · 4eefd023 · Jun 8, 2026 · 1 fileMessage 83 · StrongInformational 17Details
Commit message · Mitchell Bagot

Replace usage of secp256k1::Error with new errors in key

As part of the goal of providing more precise error types, the new
error types should be used for the from_bytes, from_secret_bytes and
verify functions on the key types. This also requires replacement of
the various Secp256k1 variants in enum error types.

Replace Secp256k1 error variants with specific error types and
replace error return types with specific types for from_bytes,
from_secret_bytes and verify functions.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This commit is a routine code cleanup in the rust-bitcoin library. It replaces generic error types from the underlying secp256k1 cryptographic library with more specific, library-defined error types for key parsing and signature verification functions. There is no indication this fixes a security vulnerability; it is an API-quality improvement.

Security candidateReplace usage of secp256k1::Error with new error in ecdsaby Mitchell Bagot · f0a0f330 · Jun 8, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · Mitchell Bagot

Replace usage of secp256k1::Error with new error in ecdsa

The ecdsa::InvalidDerError can be used both in the key verify
functions but also to replace the Secp256k1 variant in DecodeError.

Replace DecodeError::Secp256k1 variant with InvalidDer.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is a straightforward internal cleanup in the rust-bitcoin library. It swaps one error type for another when an ECDSA signature fails to decode from DER format. The behavior of signature parsing does not change; only the name and contents of the error value reported to callers are different. There is no indication this fixes a security bug or introduces a vulnerability.

Security candidatecrypto: Remove all From impls for error typesby Mitchell Bagot · 33765355 · Jun 8, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

crypto: Remove all From impls for error types

Aside from From<Infallible>, error types should not have any From
impls but should instead make use of map_err. This ensures greater
future flexibility for changes to the error types moving forward.

Remove From<InvalidSighashTypeError> for SigFromSliceError from
taproot.

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 internal code cleanup in the rust-bitcoin library. It removes a convenience conversion (a 'From' implementation) between two error types and replaces it with an explicit error mapping. The actual behavior of signature parsing does not change; it is purely about how errors are wired through the code. There is no indication this fixes a security bug.

Security candidateRemove Secp256k1 variant from taproot SigFromSliceErrorby Mitchell Bagot · f3920e7b · Jun 8, 2026 · 1 fileMessage 78 · AdequateInformational 19Details
Commit message · Mitchell Bagot

Remove Secp256k1 variant from taproot SigFromSliceError

The Secp256k1 variant of the SigFromSliceError is no longer needed.
The secp parsing of the signature is now infallible, meaning there
cannot be a secp error during parsing of a signature from a slice.

Remove Secp256k1 error variant from taproot::SigFromSliceError.

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

This commit removes an unused error category from a Bitcoin cryptography library. It is a cleanup change because the underlying signature-parsing code can no longer fail in the way that error category described. There is no direct evidence this fixes an active security bug, but it does slightly reduce the library's public error surface, which can help downstream code handle errors more reliably.

Security candidateIntroduce errors for byte parsing and verificationby Mitchell Bagot · 1a337804 · Jun 8, 2026 · 2 filesMessage 83 · StrongInformational 18Details
Commit message · Mitchell Bagot

Introduce errors for byte parsing and verification

At present, the from_bytes, from_secret_bytes and verify methods on
the key types all return secp256k1::Error. In all of these methods,
only a single variant of that error type is returned. To both hide
the secp type, and to provide the possibility for more meaningful
error values, new error types should be introduced.

Add FromSecretBytesError, InvalidPublicKeyError and VerifyError to
key errors.
Add InvalidDerError error type to ecdsa error submodule.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Informational 18/100

This commit is a routine code-quality refactor. It introduces new, more specific Rust error types for parsing keys and signatures, replacing a generic underlying library error type. There is no change to cryptographic behavior, validation logic, or security boundaries. It only changes what kind of error message callers receive when parsing fails.