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 queue1789AI analyses
183commits · 30 days
403commits · 60 days
1283commits · 180 days
2057commits · 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 Bagot640192624068
Tobin C. Harding40965313063
jrakibi944986068
Nick Johnson18920170059
Andrew Poelstra512036075
Jamil Lambert, PhD1141886061
Fmt Bot311428045
Trevor Arjeski111111069
Shing Him Ng31727056
Ismail Daif22622050
satsfy (Renato Britto)17617066
Martin Habovstiak27527069
Analysis record

Published AI watches

Last scanned 27 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
Open full analysis →Source 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
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 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
Open full analysis →Source 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
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 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`

This is a routine API cleanup, not a security fix. The developers removed a shortcut that let programmers create a 'number of blocks' value directly from any u16 number, replacing it with an existing named constructor called from_height. T…

ed5f1b68by Andrew Poelstra+18−358 files
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#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
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 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
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update the API text files

This commit only updates two generated API text files that list the public surface of the Rust crate. It removes entries for a `WitnessesEncoder` type, reflecting that the type is no longer part of the public API. There is no source code c…

9c391145by Tobin C. Harding+0−782 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 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

release bitcoin_hashes 1.2.0

This commit is a routine version bump for the bitcoin_hashes library from version 1.1.0 to 1.2.0. It only updates lock files, the package version number, and the changelog. There is no code change and no security relevance visible in the c…

8899dfd2by Andrew Poelstra+27−224 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 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
Open full analysis →Source 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
Open full analysis →Source 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
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 ↗
Repository ledger

Explore captured commits

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

Security candidateAdd panics section to docsby Jamil Lambert, PhD · 43dae788 · Apr 8, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Jamil Lambert, PhD

Add panics section to docs

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 adds documentation comments describing when three functions can panic. No code behavior was changed, so it cannot introduce or fix a security vulnerability on its own.

Security candidateDocs cleanupby Jamil Lambert, PhD · f68ae3cb · Apr 8, 2026 · 2 filesMessage 33 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

Docs cleanup

Add a couple of missing full stops and capital letters.

33/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body! Too few words to establish purpose! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only fixes punctuation and capitalization in code comments (documentation). No program logic, behavior, or security properties were changed.

Security candidatebitcoin: Move key module errors to error submoduleby Mitchell Bagot · bd8f15bc · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 18Details
Commit message · Mitchell Bagot

bitcoin: Move key module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from key module into error submodule and re-export.

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 code cleanup that moves error type definitions into a new 'error' submodule and re-exports them so existing code keeps working. It does not change how keys are parsed, validated, or used, and it does not fix or introduce any security vulnerability.

Security candidatebitcoin: Move sighash module errors to error submoduleby Mitchell Bagot · e2d65253 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move sighash module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from sighash module into error submodule and re-export.

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 commit is a pure internal code reorganization: it moves error type definitions from one place in the file to a new `error` submodule and re-exports them. There is no change to how the library behaves, no bug fix, and no security-relevant change.

AI review queuedbitcoin: Move transaction module errors to error submoduleby Mitchell Bagot · 5bd3c36a · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Mitchell Bagot

bitcoin: Move transaction module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from transaction module into error submodule and
re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a straightforward internal code reorganization. It moves several error type definitions from one place in the transaction module into a new 'error' submodule and re-exports them so existing code can still use them the same way. There is no functional change to how transactions are validated, parsed, or secured.

Security candidatebitcoin: Move ecdsa module errors to error submoduleby Mitchell Bagot · 630ca5ac · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move ecdsa module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from ecdsa module into error submodule and re-export.

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 commit is a simple internal code cleanup in the rust-bitcoin library. It moves two error types (DecodeError and ParseSignatureError) from the main ECDSA module into a new 'error' submodule and re-exports them so existing code keeps working. There is no change to behavior, no bug fix, and no security issue.

Lower-prioritybitcoin: Move bip158 module errors to error submoduleby Mitchell Bagot · 54a644cb · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move bip158 module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from bip158 module into error submodule and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a simple internal code reorganization. It moves the existing error type for BIP-158 block filters from the main bip158 module into a new error submodule and re-exports it. No behavior, logic, or public API changes are visible in the diff.

Lower-prioritybitcoin: Move witness_program module errors to error submoduleby Mitchell Bagot · 492f1c27 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move witness_program module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from witness_program module into error submodule
and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a simple internal code cleanup. It moves the definition of error types for witness programs into a new 'error' submodule and re-exports them at the original location. There is no change to how the code behaves, no bug fix, and no security improvement or regression.

Lower-prioritybitcoin: Move block module errors to error submoduleby Mitchell Bagot · d371956a · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move block module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from block module into error submodule and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a routine code cleanup: it moves error type definitions for Bitcoin blocks into a new 'error' submodule and re-exports them. There is no change to how the code behaves, no bug fix, and no security impact.

Lower-prioritybitcoin: Move script module errors to error submoduleby Mitchell Bagot · e98a0625 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Mitchell Bagot

bitcoin: Move script module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from script module into error submodule and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 19/100

This commit is a routine code cleanup: it moves error type definitions for Bitcoin scripts into a dedicated 'error' submodule and re-exports them so existing code keeps working. There is no change to how the library behaves, no bug fix, and no security-relevant change.

Lower-prioritybitcoin: Move witness_version module errors to error submoduleby Mitchell Bagot · 0f0f7d74 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move witness_version module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from witness_version module into error submodule
and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a straightforward internal code cleanup. It moves three error types (FromStrError, TryFromInstructionError, TryFromError) from the witness_version module into a new error submodule and re-exports them so existing code keeps working. There is no functional change to how witness versions are parsed, validated, or used.

Security candidatebitcoin: Move bip32 module errors to error submoduleby Mitchell Bagot · 9d80f54b · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 20Details
Commit message · Mitchell Bagot

bitcoin: Move bip32 module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from bip32 module into error submodule and re-export.

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

This commit is a pure code reorganization: it moves several BIP-32 error type definitions from the main bip32.rs file into a new error submodule and re-exports them so existing code keeps working. There are no functional changes to how keys are derived, parsed, or validated, and no security bug is fixed or introduced.

AI review queuedbitcoin: Move sign_message module errors to error submoduleby Mitchell Bagot · c4f8b1e6 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move sign_message module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from sign_message module into error submodule and
re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a simple internal code cleanup. It moves an error type (MessageSignatureError) from one place in the sign_message module into a new error submodule and re-exports it so users can still access it the same way. No behavior, logic, or security properties changed.

Lower-prioritybitcoin: Move network module errors to error submoduleby Mitchell Bagot · ad011920 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 20Details
Commit message · Mitchell Bagot

bitcoin: Move network module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from network module into error submodule and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 20/100

This commit is a straightforward internal code reorganization. It moves two error types related to Bitcoin network parsing into a new 'error' submodule and re-exports them so existing code keeps working. There is no functional change, no bug fix, and no security improvement or regression visible in the diff.

Lower-prioritybitcoin: Move consensus_validation module errors to error submoduleby Mitchell Bagot · eea7af8a · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move consensus_validation module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from consensus_validation module into error submodule
and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a routine code cleanup. It moves two error types (BitcoinconsensusError and TxVerifyError) from the main consensus_validation file into a new error submodule and re-exports them so existing code keeps working. There is no functional change to how transactions are validated or how errors behave.

Lower-priorityMake consensus errors pub and no_inlineby Mitchell Bagot · b6eb5ce7 · Apr 8, 2026 · 1 fileMessage 68 · AdequateInformational 16Details
Commit message · Mitchell Bagot

Make consensus errors pub and no_inline

As part of the process of moving errors to error submodules, all error
types at the top-level should be no_inline. Further, we want all errors
in top-level modules to be re-exported from a pub error submodule.

Make consensus::error pub and change error re-exports to be no_inline.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 16/100

This commit is a routine Rust code organization change. It makes an internal error module publicly visible and adjusts how error types are re-exported so they appear in documentation as coming from their submodule rather than being shown inline. There is no change to how errors are handled, no new functionality, and no security fix or vulnerability.

Lower-prioritybitcoin: Move taproot module errors to error submoduleby Mitchell Bagot · f014ab48 · Apr 8, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

bitcoin: Move taproot module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from taproot module into error submodule and re-export.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a routine code cleanup in the rust-bitcoin library. It moves error type definitions for the Taproot module into a new 'error' submodule and re-exports them so existing code keeps working. There are no functional changes to how the library behaves, and no security issue is present.

Lower-priorityMake address module errors no_inlineby Mitchell Bagot · 6687f835 · Apr 8, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Make address module errors no_inline

As part of the process of moving errors to error submodules, all error
types at the top-level should be no_inline.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit changes a single documentation attribute for re-exported error types in the address module. It tells Rust's documentation generator not to inline the descriptions of those errors on the parent module page. There is no runtime code change, no bug fix, and no security relevance.

Lower-priorityconsensus_encoding: Bump version to 0.2.0by Tobin C. Harding · e29fdc30 · Apr 7, 2026 · 10 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

consensus_encoding: Bump version to 0.2.0

This release is a release candidate for `consensus_encoding v1.0.0`.
And hopefully it is the last one. `v1.0.0` release imminent ...

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

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit is a routine version bump for a Rust library package called `bitcoin-consensus-encoding` from version 0.1.0 to 0.2.0. It updates version numbers in package manifests and lock files, and adds a changelog entry describing the new release. There is no code change in this commit, and nothing in the commit suggests a security fix or vulnerability.

Lower-prioritychacha20_poly1305: bump minor version and changelog for v0.2.0by Nick Johnson · 8f02fa6a · Apr 7, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · Nick Johnson

chacha20_poly1305: bump minor version and changelog for v0.2.0

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is purely a housekeeping release: it bumps the version number of the chacha20-poly1305 sub-crate from 0.1.2 to 0.2.0 and updates the changelog and lock files. No code behavior changes, no bug fixes, and no security-related content is present.

Security candidatefuzz: pin cargo-fuzz to 0.12.0by Ismail Daif · 40fa0cac · Apr 7, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Ismail Daif

fuzz: pin cargo-fuzz to 0.12.0

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
access controlfuzzing or regression evidence
AI analysis · Informational 15/100

This change pins the version of a fuzzing tool used only in internal testing. It does not alter any code that end users run, and there is no indication it fixes a security vulnerability.

Lower-priorityp2p: Fix types and wording for decoder errorsby Mitchell Bagot · c1c2fe9a · Apr 7, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

p2p: Fix types and wording for decoder errors

Some of the decoder errors in p2p include types in the doc comments.
For some of these, the choice of a/an is incorrect, and for others, the
decoder error type itself is mentioned, instead of the decoder result
type.

Adjust wording and types for AddressDecoderError,
V1MessageHeaderDecoderError, PingDecoderError, and PongDecoderError.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit fixes four doc comments in the P2P networking code. The comments previously referred to the wrong type names (the decoder error structs themselves) and used incorrect 'a/an' grammar. There is no code behavior change, only documentation wording corrections.

AI review queuedprimitives: Replace decoder definitions with decoder_newtype macroby Mitchell Bagot · ac2308b7 · Apr 7, 2026 · 6 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

primitives: Replace decoder definitions with decoder_newtype macro

Introduce decoder_newtype macro in primitives through the include!
macro.
Replace all newtype Decoder structs in primitives with decoder_newtype
calls.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine code cleanup in the rust-bitcoin library. It replaces several manually-written decoder helper structs with a new macro that generates the same code automatically. There is no change to how data is parsed, no new behavior, and no security fix or vulnerability introduced.

AI review queuedunits: Replace decoder definitions with decoder_newtype macroby Mitchell Bagot · 5c9efe7a · Apr 7, 2026 · 8 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

units: Replace decoder definitions with decoder_newtype macro

Throughout the crates, there exist various decoder types that are
newtype wrappers around existing encoders. Almost all of these use the
same boilerplate for most of their logic and can be replaced by a
macro that provides the same functionality.

Introduce private decoder_newtype macro in include file and introduce
to units crate through include! macro.
Replace all Decoder structs in units with decoder_newtype calls.

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

This commit is a routine code cleanup in the rust-bitcoin library. It replaces several nearly identical decoder definitions with a single macro, reducing boilerplate. There is no change to user-facing behavior, no bug fix, and no security relevance.

Lower-priorityUpdate API filesby Mitchell Bagot · ca68bb5c · Apr 7, 2026 · 4 filesMessage 51 · ThinInformational 15Details
Commit message · Mitchell Bagot

Update API files

As part of introducing explicit impls for std::error::Error, various
error types are now recorded as including a source() impl. To satisfy
the API checker, the files must be updated.

Update API files with just check-api

51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates generated API snapshot files (text listings of public functions/types) to reflect that several error types now expose a `source()` method as part of adding explicit `std::error::Error` implementations. No actual source code behavior changes, no bug fixes, and no security-sensitive modifications are present.