CommitWatch RSS
RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Source repository ↗
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 queue563AI analyses
190commits · 30 days
404commits · 60 days
1283commits · 180 days
2069commits · 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 Bagot640192232068
Tobin C. Harding4096580063
jrakibi944954068
Nick Johnson1892027059
Andrew Poelstra512020075
Jamil Lambert, PhD1141830061
Fmt Bot311416045
Trevor Arjeski111111069
Shing Him Ng31710056
Ismail Daif2267050
satsfy (Renato Britto)1768066
Martin Habovstiak2759069
Analysis record

Published AI watches

Last scanned 50 minutes ago

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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: add sha256::Midstate::SHA256_IV constant

This commit is a routine internal refactoring in the rust-bitcoin SHA-256 hashing code. It exposes the SHA-256 initial value (IV) as a public constant and renames an internal helper function so it can start from any midstate rather than al…

dc21841bby Andrew Poelstra+39−143 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: add several methods to sha256::Midstate for computing them in const contexts

This commit adds new helper methods to the SHA-256 'Midstate' type in the rust-bitcoin hashes library. These helpers let callers compute SHA-256 intermediate states inside 'const' contexts (compile-time constants). It is a routine feature …

7d8f06d2by Andrew Poelstra+80−72 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: make Sequence inner field private

This commit makes a single internal number field private in a Rust Bitcoin library type called Sequence. It is an API-cleanup change to follow Rust naming conventions (C-STRUCT-PRIVATE). It does not fix a memory corruption bug, a cryptogra…

No security signal: this is an API-encapsulation refactorNo validation or serialization logic changedNo unsafe code, no cryptographic operations modified
30f280daby satsfy (Renato Britto)+9−96 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

taproot-primitives: Implement encoding traits for TapLeafHash

This commit adds standard data-encoding support for a Bitcoin Taproot hash type (TapLeafHash) so it can be properly serialized and deserialized in PSBT data. There is no indication of a security bug being fixed; it appears to be a missing-…

No security-relevant signal in commit message or diffChange is a feature addition (encoding trait implementations)No bounds-checking, memory-safety, or cryptographic flaws evident in diff
b2ab0896by Mitchell Bagot+59−12 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Split Address into an extension trait

This commit is a routine code reorganization in the rust-bitcoin library. It moves the `Address::from_script` method out of the main `Address` type into a new 'extension trait' called `AddressExt`. The actual logic of the function is copie…

c900fa8cby Mitchell Bagot+35−263 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: update cargo-rbmt ever month instead of week

This commit simply renames a GitHub Actions workflow file and changes its schedule from weekly to monthly. It is a routine CI maintenance change with no security relevance.

778018e1by Nick Johnson+46−461 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Use generic arguments for functions

This commit is a routine API cleanup: it makes a few Bitcoin merkle-root functions accept a broader range of input types (generic iterators and borrowed transactions) instead of only slices or exact iterator types. There is no security bug…

e887140aby Mitchell Bagot+26−184 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: Flatten nested checked_ops methods

This commit is a straightforward code cleanup in the rust-bitcoin library. It replaces deeply nested match blocks with newer, cleaner Rust syntax (let-else statements) inside safe arithmetic helper functions. The actual behavior of the cod…

99f3721dby Abeeujah+53−1274 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 23 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

primitives: Remove todo

This commit only changes a code comment. It replaces a developer TODO note with a short explanation that the code is verbose because it implements a state machine. No code behavior, logic, or security properties changed.

e62e553dby Tobin C. Harding+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

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

AI review queuedbuild(deps): bump astral-sh/setup-uv from 7.1.2 to 8.1.0by dependabot[bot] · fab2fabb · Jul 6, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

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

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 7.1.2 to 8.1.0.
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](https://github.com/astral-sh/setup-uv/compare/85856786d1ce8acfbcc2f13a5f3fbd6b938f9f41...08807647e7069bb48b6ef5acd8ec9567f424441b)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
dependency-version: 8.1.0
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI review queuedbuild(deps): bump actions/cache from 5.0.0 to 5.0.5by dependabot[bot] · a22ae9a8 · Jul 6, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

build(deps): bump actions/cache from 5.0.0 to 5.0.5

Bumps [actions/cache](https://github.com/actions/cache) from 5.0.0 to 5.0.5.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/a7833574556fa59680c1b7cb190c1735db73ebf0...27d5ce7f107fe9357f9df03efb73ab90386fccae)

---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 5.0.5
dependency-type: direct:production
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI review queuedUpdate API filesby Mitchell Bagot · b32abd74 · Jul 6, 2026 · 3 filesMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
Security candidateconsensus_encoding: Rename _with decoder functionsby Mitchell Bagot · 12325a67 · Jul 6, 2026 · 4 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

consensus_encoding: Rename _with decoder functions

The _with decoder functions are generic on Decoder instead of Decode,
which allows them to decode ad-hoc decoder types, rather than requiring
a type with Decode. However, the _with suffix is already used for
decode_from_read_unbuffered_with, in which it has a different meaning.
For the sake of consistency, the _with function suffix should instead
be with_decoder.

Rename _with decoder functions to use _with_decoder suffix instead.

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

This commit is a simple renaming of internal Rust functions from names ending in '_with' to names ending in '_with_decoder'. It does not change what the code does, only what the functions are called, to avoid confusion with another function that already uses '_with' differently. There is no security issue here.

Lower-priorityci: only flag major semver breaksby jrakibi · 047761e5 · Jul 6, 2026 · 1 fileMessage 88 · StrongTriage 0Details
Commit message · jrakibi

ci: only flag major semver breaks

semver-check currently flags minor API changes as breaking (ref: #6465).
As a side effect, a minor change to a 1.0 crate (eg: bitcoin-consensus-encoding)
fails CI and blocks the merge.

Flag only major changes and ignore minor ones.

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMove address constants to addressesby Mitchell Bagot · 0e6b97c1 · Jul 6, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Move address constants to addresses

There are four constants in bitcoin that are only used for addresses
logic. Since these will be used in addresses, they should be moved
there and redefined in bitcoin's constants module as equal to the
upstream crate's values.

Move PUBKEY_ADDRESS_PREFIX_MAIN, SCRIPT_ADDRESS_PREFIX_MAIN,
PUBKEY_ADDRESS_PREFIX_TEST, and SCRIPT_ADDRESS_PREFIX_TEST to addresses.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityFix lint errors in addressesby Mitchell Bagot · 56ba9b8f · Jul 6, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Mitchell Bagot

Fix lint errors in addresses

After the move of WitnessProgram to addresses, various lint errors have
appeared due to stricter lint requirements. In order to simplify the
following steps, these should be fixed.

Fix lint errors in addresses after WitnessProgram move.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Security candidateMove ScriptPubKeyBufExt to addressesby Mitchell Bagot · ed00d91a · Jul 6, 2026 · 2 filesMessage 63 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Move ScriptPubKeyBufExt to addresses

The new_p2pkh function is necessary to implement the script_pubkey
function on Address. Since the function signature includes a hash type
from crypto, it can't be moved to primitives yet. Instead, we can move
the extension trait to addresses where it can be used, and re-export
the trait in bitcoin to retain the same API.

Move ScriptPubKeyBufExt to addresses, Adjust new_p2pk function impl to
remove use of Builder::push_key.

63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 17/100

This commit is a routine internal code reorganization in the rust-bitcoin library. It moves a helper trait (ScriptPubKeyBufExt) and its functions from one internal module to another, and re-exports it so existing users see no change. There is no indication this fixes a security bug or introduces a vulnerability.

Lower-priorityCopy new_witness_program_unchecked into addressesby Mitchell Bagot · 3ac9d3e7 · Jul 6, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Mitchell Bagot

Copy new_witness_program_unchecked into addresses

The new_witness_program_unchecked function is required for the
implementation of Address:script_pubkey and ScriptPubKeyBufExt.
However, since the function needs to remain private in any instance,
the only option to use it here is to duplicate the function.

Copy new_witness_program_unchecked as a private function into addresses.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Lower-priorityMove WitnessProgram to addressesby Mitchell Bagot · 3716268b · Jul 6, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Mitchell Bagot

Move WitnessProgram to addresses

As part of moving Address to addresses, WitnessProgram and
WitnessVersion will both also need to be moved.

Move WitnessProgram and associated error to addresses, re-exporting
from bitcoin.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
AI review queueddocs: Update dep-treeby Tobin C. Harding · 3ee5556f · Jul 6, 2026 · 1 fileMessage 63 · AdequateTriage 0Details
Commit message · Tobin C. Harding

docs: Update dep-tree

The workspace dependency trees have changed a bit:

- Added `internals` dep to `encoding`
- Added `crypto` crate

Run `cd docs; rm dep-tree; just gen-dep-tree > dep-tree`.

63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discountsecond-pass: broader security terminology
Lower-prioritybitcoin: Add PR links to 101 changelogby Tobin C. Harding · 2b815008 · Jul 6, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Tobin C. Harding

bitcoin: Add PR links to 101 changelog

Improve the changelog with links to other PRs merged in this release.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
Security candidatehashes: Deprecate sha256t_tag macroby jrakibi · ac921e97 · Jul 5, 2026 · 3 filesMessage 50 · ThinInformational 16Details
Commit message · jrakibi

hashes: Deprecate sha256t_tag macro

Deprecate the macro in favor of implementing sha256t::Tag by hand

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 16/100

This is a routine code-maintenance change: the developers are marking an old helper macro as deprecated and telling users how to write the same code by hand. There is no bug fix, no security patch, and no vulnerability being addressed in the commit itself.

Security candidate2026-07-05 automated rustfmt nightlyby Fmt Bot · 673e5ee4 · Jul 5, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

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

Lower-priorityhashes: update API text filesby jrakibi · 50654cc4 · Jul 4, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · jrakibi

hashes: update 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-priorityhashes: fix unusable HKDF aliasby jrakibi · 04ae6494 · Jul 4, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · jrakibi

hashes: fix unusable HKDF alias

In #4085 we reparameterized `Hkdf` to use `HashEngine` instead
of the old `GeneralHash`, but missed updating the `HkdfSha256` and
HkdfSha512 aliases

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Security candidatehashes: implement sha256t::Tag without the macroby jrakibi · 0131814d · Jul 4, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · jrakibi

hashes: implement sha256t::Tag without the macro

Midstate::hash_tag is a const fn, so a tag can be defined by hand with
a sha256t::Tag impl without using the macro. The macro dates to a time
before sha256 could be computed in a const context (constfns make it
unnecessary now)

Migrate the tag definitions off the macro:
- taproot-primitives: TapLeafTag, TapBranchTag, TapTweakTag
- bitcoin: TapSighashTag

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 cleanup in the rust-bitcoin library. It replaces a macro used to define SHA-256 tagged hash identifiers with direct Rust code that does the same thing. The actual hash values and behavior are unchanged; only the internal implementation style is different.

AI review queuedconsensus_encoding: Add decode_from_hex_withby Mitchell Bagot · b8c3387a · Jul 3, 2026 · 4 filesMessage 58 · ThinTriage 7Details
Commit message · Mitchell Bagot

consensus_encoding: Add decode_from_hex_with

Recently, decode_from_*_with functions have been added that take a
Decoder generic type instead of a Decode generic. The decode_from_hex
function does not currently have such a counterpart.

Introduce decode_from_hex_with counterpart to decode_from_hex.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
Lower-priorityci: adapt bench subcommand to cargo-rbmt 0.4.0by satsfy (Renato Britto) · 7ffed444 · Jul 3, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · satsfy (Renato Britto)

ci: adapt bench subcommand to cargo-rbmt 0.4.0

cargo-rbmt 0.4.0 drops the bench subcommand. This commit moves the bench run
into the new form from the documentation of rbmt. The old command set
RUSTFLAGS=--cfg=bench so the bench gated crates get compiled in.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Security candidateci: adapt default and no feature bip32 test for rbmt 0.4.0by satsfy (Renato Britto) · 5f933d5c · Jul 3, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · satsfy (Renato Britto)

ci: adapt default and no feature bip32 test for rbmt 0.4.0

Rbmt 0.4.0 changes how the example test matrix parses feature specs. The
sentinel for no default features was removed (bare name now means no default
features). The config relied on the old meaning that bip32 ran with default
features and 'bip32:-' ran with no features.

Translate both to the new syntax so the same two runs are preserved: 'bip32'
(no features) and 'bip32:std secp-recovery' (default feature set).

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
secret or key material
AI analysis · Informational 15/100

This is a routine update to the project's automated testing configuration. A tool used to run example tests changed its syntax, so the developer updated one line to keep the same tests running the same way. There is no user-facing change and no security relevance.

Lower-priorityci: regenerate api snapshotsby satsfy (Renato Britto) · edca8ec9 · Jul 3, 2026 · 18 filesMessage 70 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

ci: regenerate api snapshots

cargo-rbmt 0.4.0 changed the snapshot format so trait items carry an
`[impl: ...]` annotation naming the impl block they come from.

The nightly bump to nightly-2026-06-19 changed the rustdoc output for
derived `StructuralPartialEq` impls on generic types, which now print the
`PartialEq` bound.

This commit regenerates the api snapshots so the check passes.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Lower-priorityAutomated update to rustc nightly-2026-06-26by Update Nightly Rustc Bot · cfa24add · Jul 3, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Update Nightly Rustc Bot

Automated update to rustc nightly-2026-06-26

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAutomated update to cargo-rbmt-0.4.1by Update RBMT Bot · ae072165 · Jul 3, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Update RBMT Bot

Automated update to cargo-rbmt-0.4.1

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateReplace uses of encode_to_engine with encode_to_hashby Mitchell Bagot · f40e1879 · Jul 2, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Replace uses of encode_to_engine with encode_to_hash

There are a couple of uses of encode_to_engine that follow the trivial
pattern and can be replaced with encode_to_hash.

Replace appropriate uses of encode_to_engine in sighash and primitives
with encode_to_hash to simplify the code.

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

This is a small internal code cleanup in the rust-bitcoin library. It replaces a slightly longer two-step hashing pattern with a shorter helper function that does the same thing. The actual cryptographic results and behavior are unchanged.

AI review queuedUpdate API filesby Mitchell Bagot · 16ca3c27 · Jul 2, 2026 · 3 filesMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message