RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

2570 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

612security candidates555second-pass queue2330AI analyses
153commits · 30 days
279commits · 60 days
975commits · 180 days
2058commits · 365 days
Backfill bands
Aug 5 → Feb 6787 seen32 candidatesComplete
Feb 6 → Jun 6878 seen53 candidatesComplete
Jun 6 → Jul 6211 seen15 candidatesComplete
Jul 6 → Aug 5184 seen2 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
702Strong · 80–100
1135Adequate · 60–79
582Thin · 40–59
151Opaque · 0–39
20security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Andrew Poelstra407139251391
Mitchell Bagot659200654068
Tobin C. Harding42167411063
jrakibi1015096069
satsfy (Renato Britto)652235065
Nick Johnson19621190060
Jamil Lambert, PhD12619117062
Fmt Bot351532045
Trevor Arjeski111111069
Shing Him Ng31731056
Martin Habovstiak31629069
Ismail Daif22622050
Analysis record

Published AI watches

Last scanned 12 minutes ago

Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7220: refactor(bip32)!: replace KeySource with KeyOrigin

This is a routine code cleanup in a Bitcoin library. It renames a simple data container from KeySource to KeyOrigin and gives it named fields (fingerprint and path) instead of numbered tuple slots (.0 and .1). The serialized format is inte…

6bb507b2by Andrew Poelstra+84−33 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto dep

This change is a routine internal cleanup: the key_expression crate stops depending directly on the secp256k1 cryptography library and instead uses a re-export provided by another internal crate called crypto. No user-facing behavior, type…

d193efc5by Andrew Poelstra+7−107 files
No security note in commit
Informational 17 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Forward serde feature to network

This is a small Cargo.toml fix in a Rust Bitcoin subcrate. When the optional 'serde' feature was enabled on the key_expression crate alone, it did not also enable serde on the network crate. That meant a type called NetworkKind could not b…

806f1e1fby bytescape30+1−11 file
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7223: build(deps): bump taiki-e/install-action from 2.87.9 to 2.87.13

This is a routine update to a GitHub Actions helper used in automated testing workflows. It bumps the version of taiki-e/install-action, which downloads and installs Rust developer tools during CI runs. There is no change to the actual Bit…

c8ee144aby Andrew Poelstra+2−22 files
No security note in commit
Informational 20 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7224: build(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0

This is a routine update to a GitHub Actions helper used only in automated security-scanning workflows. The new version adds minor improvements, including respecting proxy settings and verifying downloaded files with checksums. It does not…

Dependency bump of a third-party GitHub Action used in CI onlyUpstream release notes mention generic security improvements (checksum verification, npm install defaults, NO_PROXY)No CVE, advisory, or vendor security disclosure is present in the commit or supplied references
7bc9d696by Andrew Poelstra+2−22 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising crates

This commit removes automatic serde (serialization/deserialization) code generation from several Rust Bitcoin library crates and replaces it with hand-written implementations. The stated goal is to reduce dependencies and make the code eas…

Manual serde implementations replace derived ones, increasing the surface area for serialization-format bugsNo validation logic changes are visible in the diffNo mention of security fixes, CVEs, or vulnerability reports in commit message or PR description
9eeb7774by Andrew Poelstra+219−4110 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7205: Manual update to rustc stable (to 1.100.0)

This commit updates the project's automated Rust compiler version from 1.99.1 to 1.100.0 and adjusts a CI cache cleanup script to match a new directory layout used by Cargo 1.100. It is purely an infrastructure/maintenance change to keep a…

44e6f0caby Andrew Poelstra+8−22 files
No security note in commit
Informational 18 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leak

This is a build-system improvement, not a code change. It updates a CI helper tool and makes the automated API-checking job fail if a private internal crate accidentally becomes part of the public API. That prevents future leaks of interna…

CI guardrail added to prevent private dependency leaks into stable crate public APIsTool bump enables detection of re-exported private dependenciesNo source-code vulnerability is patched
be14c72eby Andrew Poelstra+7−12 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructors

This is a minor internal code cleanup in the Rust Bitcoin library. It changes how two functions (Xpriv::decode and Xpub::decode) build their error messages when an input is the wrong length. The behavior is the same before and after; only …

271f662aby Andrew Poelstra+8−61 file
No security note in commit
Informational 24 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`

This is a routine API cleanup, not a security fix. The change removes one way of naming a Bitcoin unit ('MicroBitcoin' / 'uBTC') and keeps the equivalent 'bits' form. Any code that previously used the old name will fail to compile or fail …

No security signal: public API deprecation and enum variant removalNo memory safety, cryptographic, or consensus code modifiedError message change is informational only
d0602195by Andrew Poelstra+53−403 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal types

This commit is a code cleanup and feature-gating refactor for the rust-bitcoin library's key_expression crate. It makes more BIP32 (Bitcoin wallet key derivation) types available when the 'alloc' memory allocator feature is disabled, and s…

Refactor of error types and parsing paths for Xpriv/Xpub base58 decodingSwitch from unbounded base58 decode to fixed-size array decode (78 bytes)Removal of explicit length-check error path in favor of decoder-reported length error
c3d27d5dby Andrew Poelstra+60−823 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7039: primitives: Fix daily Miri cron failures with measured test gating

This change only adds `#[cfg_attr(miri, ignore)]` annotations to a handful of slow unit tests so they are skipped when run under Miri, a Rust interpreter used for detecting undefined behavior. It does not change any production code, consen…

1dc09077by Andrew Poelstra+6−03 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7182: Update local dependencies

This commit only updates version numbers in package configuration files (Cargo.toml) for internal dependencies so that all crates in the project require the same minimum versions of shared libraries. There are no code changes, no bug fixes…

06f41225by Andrew Poelstra+7−75 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7179: build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9

This is a routine update to a GitHub Actions helper used in automated testing workflows. It changes which version of a third-party tool-installer action is used, but only for installing the cargo-mutants testing tool. There is no indicatio…

4fda66b5by Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This commit updates the version of a helper tool called cargo-binstall used in two automated GitHub workflows. The change only affects internal build/CI tooling and does not alter the rust-bitcoin library code that users install or run. Th…

53eae24dby Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security scanning workflow. It changes one pinned commit hash to a newer version of the same action. There is no indication this introduces…

4bb555f0by Andrew Poelstra+1−11 file
No security note in commit
Informational 15 AI analysisMessage 81 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Flatten BIP32 decode error construction

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how an error message is built when decoding BIP32 extended keys, switching from one nested construction style to two chained calls. The actual behavior and returne…

c31c11e0by Adewale Ijalana+8−61 file
No security note in commit
Low 36 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7168: units: add `visit_units` in optional serde visitors

This commit fixes a bug in how optional Bitcoin amount and fee-rate values are read from JSON when those fields are inside a flattened struct and the value is null. Previously, the code would error out because it did not handle a special s…

Deserialization failure in optional numeric types under serde flattenMissing serde visitor method (visit_unit) causing runtime errorsRegression test added for null handling in flattened structs
47340d2fby Andrew Poelstra+79−03 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump github/codeql-action/upload-sarif

This is a routine dependency update by Dependabot, bumping the version of a GitHub-provided action used to upload security scan results. There is no indication of a security vulnerability in the project itself or in this change.

fe755619by dependabot[bot]+1−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This is a routine automated update by Dependabot that changes the version of a GitHub Action used to install Rust tools in two CI workflows. There is no indication of a security issue in the commit itself, and no verified security referenc…

2ccb0029by dependabot[bot]+2−22 files
No security note in commit
Repository ledger

Explore captured commits

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

AI review queuedUpdate api filesby Jamil Lambert, PhD · c3e89fb7 · Mar 25, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

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
AI analysis · Informational 15/100

This commit only updates generated API snapshot text files to include a newly added public function, `Midstate::to_engine`. It does not change any source code, fix a bug, or alter program behavior. There is no security relevance visible in the commit itself.

AI review queuedprimitives: Update API filesby Mitchell Bagot · 78443e30 · Mar 25, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

primitives: Update API files

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates generated API snapshot files that list what types and functions are publicly available in the library. It adds entries for a new Signet-related script type that was already introduced elsewhere in the codebase. There is no actual code change, no bug fix, and no security relevance visible in the diff.

AI review queuedUpdate API text filesby Bortlesboat · 12627ed3 · Mar 25, 2026 · 9 filesMessage 28 · OpaqueInformational 15Details
Commit message · Bortlesboat

Update API text files

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

This commit only updates generated API text files that list the public interface of the Rust Bitcoin crates. The changes reflect newly added standard Rust trait implementations (From<Infallible>) for various error types. These are not code changes and do not alter runtime behavior, so there is no security impact.

AI review queuedImplement From<Infallible> for all public error typesby Andrew Barnes · c425a0cf · Mar 25, 2026 · 10 filesMessage 81 · StrongInformational 19Details
Commit message · Andrew Barnes

Implement From<Infallible> for all public error types

Add From<Infallible> implementations for 31 public error types
across the consensus_encoding, primitives, and units crates. Each
impl is placed directly below its type declaration. For hidden
error types, the impl is placed below the inner type declaration.

Closes: #5767

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit adds standard Rust trait implementations that let the library's error types be automatically converted from an 'impossible' error type (Infallible). It is a routine API-ergonomics improvement with no security relevance: Infallible can never actually be produced at runtime, so these conversions can never be triggered by an attacker.

AI review queuedRun the formatterby Mitchell Bagot · bf983044 · Mar 25, 2026 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Run the formatter

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is purely a code-formatting cleanup. It removes blank lines, collapses a struct literal onto one line, reorders re-exports and module declarations, and adds a blank line between imports. There is no functional change and no security relevance.

AI review queuedRun the formatterby Tobin C. Harding · 88fdfcef · Mar 25, 2026 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

Run the formatter

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only runs an automated code formatter. It reorders imports, removes blank lines, and collapses some struct literals onto single lines. There are no functional code changes and no security relevance.

AI review queuedUpdate API filesby busayo-OD · 5976a31e · Mar 24, 2026 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · busayo-OD

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
AI analysis · Informational 15/100

This commit only updates generated API snapshot text files. It removes lines that list certain error-conversion functions from the public API surface, but it does not change any actual Rust source code, logic, or behavior. There is no security-relevant change visible in the diff.

AI review queuedRemove From<SubError> for Error implsby busayo-OD · 39c6e225 · Mar 24, 2026 · 7 filesMessage 45 · ThinInformational 17Details
Commit message · busayo-OD

Remove From<SubError> for Error impls

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit removes automatic conversion traits (From implementations) that let sub-errors be silently turned into parent errors. It replaces them with explicit error wrapping at each call site. This is a code-quality and API-clarity change, not a security fix. There is no evidence in the commit message or diff that it addresses a vulnerability, exploit, or bug that could affect users.

AI review queuedRun the formatterby Mitchell Bagot · 1b962b50 · Mar 24, 2026 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Run the formatter

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is purely a code-formatting cleanup. It removes blank lines, reorders imports, and lets an automated formatter rewrap a few lines. There are no functional changes to how the software behaves, and nothing in the diff suggests a security fix or vulnerability.

AI review queuedconsensus_encoding: Error on byte-less end for VecDecoderby Mitchell Bagot · 4d6e7554 · Mar 23, 2026 · 1 fileMessage 73 · AdequateModerate 51Details
Commit message · Mitchell Bagot

consensus_encoding: Error on byte-less end for VecDecoder

In the existing encoding, Vec<T> would error when attempting to decode
an empty byte slice (i.e. one without a length prefix). In the new
consensus_encoding crate, a VecDecoder successfully decodes a
completely empty byte slice as 0 length Vec<T>. This difference in
behaviour manifests in various decoders throughout the stack and thus
results in differences in decoding behaviour.

Throw Eof error in VecDecoder::end() if no length prefix has been
provided to the decoder.

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

This commit fixes a behavioral mismatch in a new Bitcoin data-decoding library. Previously, the new decoder would silently accept an empty byte slice as an empty list, while the older code rejected it because it lacked a length prefix. The change makes the new decoder reject empty inputs too, preventing subtle parsing differences that could affect how transactions or network messages are interpreted across versions.

AI review queuedprimitives: Update API filesby Mitchell Bagot · da3f0930 · Mar 23, 2026 · 3 filesMessage 35 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

primitives: Update API files

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates generated API snapshot files that list what public types and functions exist in the rust-bitcoin 'primitives' crate. No actual source code was changed, and nothing in the commit message or diff suggests a security fix or vulnerability. It is a routine housekeeping change.

AI review queuedprimitives: Add Default and new to all decodersby Mitchell Bagot · 9804591b · Mar 23, 2026 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · Mitchell Bagot

primitives: Add Default and new to all decoders

In order to simplify composition of decoder types, the Default trait
and new() function should be provided for all decoder types.

Add Default and new to BlockDecoder, HeaderDecoder, TxInDecoder and
TxOutDecoder.

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 adds convenient ways to create certain Bitcoin data decoders (Default and new()) in the rust-bitcoin library. It does not change how data is parsed or validated, and there is no indication it fixes or introduces a security problem.

AI review queuedprimitives: Convert encoders to ExactSizeEncoderby Mitchell Bagot · 35c6e004 · Mar 21, 2026 · 3 filesMessage 68 · AdequateInformational 19Details
Commit message · Mitchell Bagot

primitives: Convert encoders to ExactSizeEncoder

For encoders, the use of the encoder_newtype_exact macro allows for the
implementation of the ExactSizeEncoder trait. This provides users with
the ability to determine the encoding length of types without needing
to perform the entire encoding process. The TxIn and TxOut encoders in
primitives can be made ExactSizeEncoders but are currently not.

Replace uses of encoder_newtype with encoder_newtype_exact for TxIn and
TxOut encoder types.

68/100 · AdequateMessage clarity
✓ 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 is a routine library improvement that lets users ask 'how many bytes will this transaction input/output take up when encoded?' without actually encoding it. It adds a length method to two encoder types by switching to a macro that supports exact-size encoders. There is no security bug being fixed and no indication this change addresses any vulnerability.

AI review queuedinternals, hashes, primivties: clean up optional depsby Nick Johnson · cecf021c · Mar 20, 2026 · 3 filesMessage 85 · StrongInformational 15Details
Commit message · Nick Johnson

internals, hashes, primivties: clean up optional deps

If you use the `dep:OPTIONAL_DEP` syntax in a package's feature, then
the implicit feature flag for the optional dependency is disabled. No need
to tell end users to avoid it.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a routine cleanup of how optional dependencies are declared in three Rust package configuration files. It changes feature flags to use the modern `dep:` syntax and updates comments to be clearer. There is no change to actual program logic, no security fix, and no vulnerability.

AI review queuedRe-export serde and arbitrary when they appear in public APIby Mitchell Bagot · e59a0040 · Mar 19, 2026 · 7 filesMessage 85 · StrongInformational 19Details
Commit message · Mitchell Bagot

Re-export serde and arbitrary when they appear in public API

In various crates, we have types from external crates in the public
APIs, such as serde's Serialize or arbitrary's Arbitrary. In order to
simplify dependency handling, we should re-export these crates which
have types appearing in the public API.

Add pub extern crate for serde and arbitrary in bitcoin, network, p2p,
units and primitives as needed.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This change makes two helper libraries (serde and arbitrary) publicly visible from several rust-bitcoin crates. It is a dependency-management convenience for downstream developers and does not fix or introduce any security vulnerability.

AI review queuedapi: update for CompactSizeU64Decoderby Nick Johnson · 85a6da3a · Mar 18, 2026 · 5 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nick Johnson

api: update for CompactSizeU64Decoder

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates generated API snapshot files (text listings of public types and functions) to reflect a new CompactSizeU64Decoder type and a moved CompactSizeEncoder module path. No actual source code, logic, or behavior changes are present in the diff, so it has no security relevance on its own.

AI review queuedconsensus_encoding: move compact size into its own moduleby Nick Johnson · a06bf033 · Mar 18, 2026 · 4 filesMessage 65 · AdequateInformational 15Details
Commit message · Nick Johnson

consensus_encoding: move compact size into its own module

Public API is unchanged; lib.rs re-exports all the same types.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a pure code reorganization: it moves the compact-size integer encoder and decoder into a new dedicated file/module. The public API is unchanged, the logic is unchanged, and no security-relevant behavior is modified.

AI review queuedunits: Add hex parsing for Amount and SignedAmountby Mitchell Bagot · 7abbd16f · Mar 18, 2026 · 3 filesMessage 73 · AdequateInformational 12Details
Commit message · Mitchell Bagot

units: Add hex parsing for Amount and SignedAmount

The Amount and SignedAmount types are numeric wrapper types that should
include functionality for parsing from hex. Since the types can error
during construction for non-hex reasons, the existing ParseAmountError
needs to be extended

Add additional variants to ParseAmountErrorInner to handle hex parsing.
Introduce from_hex and from_hex_unprefixed to Amount and SignedAmount.

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

This commit adds new public functions that let users create Bitcoin amount values from hexadecimal strings. It is a feature addition, not a fix for a known bug or vulnerability. There is no evidence in the commit or supplied references that this change addresses a security issue.

AI review queuedp2p: add version message encoder/decoderby yancy · 0a183542 · Mar 17, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · yancy

p2p: add version message encoder/decoder

* `VersionMessage` is a composition of 9 decoders, however, there is no
such `Decoder9`. Instead of creating a `Decoder9`, combine the first 3
decoders using a `Decoder3` and then the last 6 using a `Decoder6`.

* Replace `deserialize` in test with `decode_from_slice` since push based
encoding is planned to replace the current serialization provided by
`bitcoin::consensus::encode`.

* In the test cases, replace `serialize` with `encoding::encode_to_vec`
since the push encoding here is planned to replace the existing
`serialize` implementation.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit adds a new way to encode and decode Bitcoin peer-to-peer 'version' messages in the rust-bitcoin library. It is a routine refactoring and feature addition: it introduces a new encoder/decoder implementation and updates one test to use the new code. There is no indication of a security bug being fixed.

AI review queuedUpdate the API filesby Tobin C. Harding · 3388e573 · Mar 16, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

Update the API files

Run `just check-api`.

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

This commit only updates a generated text file listing the public API surface of the crate. It adds four new public methods for converting Bitcoin scripts to/from hex strings. There is no code change, no bug fix, and no security relevance visible in the diff.

AI review queuedMove script hexification functions to primitivesby Tobin C. Harding · 829a4ff7 · Mar 16, 2026 · 5 filesMessage 78 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Move script hexification functions to primitives

The functions for converting scripts to hex have clean API's, we
iterated on them a ton already. Currently the implementation uses the
old consensus code but we have all this available in `primitives` now
as well as an optional dependency on `hex_unstable`.

Lets move them to primitives.

Note that this patch adds a seemingly unnecessary allocation, maybe we
have an API that needs improving or maybe I'm being brain dead ATM.

Intentionally leave the unit test where it is for now to prove nothing
in `bitcoin` breaks.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine internal code reorganization. It moves two helper functions that convert Bitcoin scripts to hexadecimal strings from the main `bitcoin` crate into the lower-level `primitives` crate. The functions still behave the same way; they are just located in a different module. There is no security fix or vulnerability here.

AI review queuedbitcoin: Replace script hex decoding with new consensus crateby Tobin C. Harding · 545f73eb · Mar 16, 2026 · 1 fileMessage 73 · AdequateLow 27Details
Commit message · Tobin C. Harding

bitcoin: Replace script hex decoding with new consensus crate

Currently we are using the old consensus deserialization code to
decode scripts as well as the unstable hex crate.

Now that we have both a stable `hex` parsing crate and a
soon-to-be-stable consensus encoding crate we can use them to shore up
the script hex parsing functions.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Low 27/100

This commit swaps out the old way of turning hex strings into Bitcoin scripts for a newer, more stable set of libraries. It also introduces a clearer error type so callers can tell whether something went wrong with the hex string itself or with decoding the script. The change is described by the project as a hardening/cleanup move, not a fix for a known vulnerability.

AI review queuedRemove honggfuzz inputsby Shing Him Ng · 9a1149fd · Mar 16, 2026 · 438 filesMessage 43 · ThinInformational 15Details
Commit message · Shing Him Ng

Remove honggfuzz inputs

We have switched over to libfuzzer, so these honggfuzz inputs are no
longer needed

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
fuzzing or regression evidencesigning or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply deletes old fuzzing test input files that were used with the honggfuzz tool. The project has switched to a different fuzzer (libfuzzer), so these files are no longer needed. No code changes were made, and there is no security fix or vulnerability introduced.

AI review queuedFix decoder and encoder re-exportsby Mitchell Bagot · d427a7ff · Mar 16, 2026 · 6 filesMessage 90 · StrongInformational 18Details
Commit message · Mitchell Bagot

Fix decoder and encoder re-exports

The bitcoin crate should always be a superset of primitives, and
primitives a superset of units. Due to a filter check in
generate-bitcoin-re-export-test.sh, encoder and decoder types and their
associated errors are not being caught missing from bitcoin.

Remove the encoder/decoder type filter and add pub use (re-exports) to
generate-bitcoin-re-export-test.sh and correctly re-export all required
types.
Add pub use check to primitives re-export script.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes missing public re-exports of encoder/decoder types and their error types in the rust-bitcoin crate. It is a packaging/API consistency fix: the bitcoin crate is meant to expose everything primitives exposes, and primitives everything units exposes. The change adds those missing re-exports and updates the test scripts that check this property. There is no indication of a runtime vulnerability, memory corruption, or exploit path.

AI review queuedFix decoder error Display and source implsby busayo-OD · 7bfeae68 · Mar 13, 2026 · 6 filesMessage 45 · ThinInformational 18Details
Commit message · busayo-OD

Fix decoder error Display and source impls

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes how several Bitcoin data-decoding error types print messages and report their underlying cause. The changes are cosmetic/correctness improvements to error formatting and the `source()` chain used by Rust's standard error handling. There is no evidence of a security vulnerability, remote exploit, or memory-safety bug in the diff.