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 42 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 queuedp2p: remove HeaderExt dependencyby Nick Johnson · 6710addb · Dec 10, 2025 · 1 fileMessage 68 · AdequateLow 34Details
Commit message · Nick Johnson

p2p: remove HeaderExt dependency

This breaks another link between p2p and bitcoin. p2p is focused on
encoding and decoding the peer to peer messages, the POW verification
should probably be on the caller or perhaps added to the primitives
decoder.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationsecond-pass: broader security terminology
AI analysis · Low 34/100

This commit removes a helper function called all_targets_satisfied() from the peer-to-peer (p2p) message handling code. That function used to check whether every block header in a 'headers' message met its own proof-of-work target. The change is framed by the author as a design cleanup: p2p should only encode and decode network messages, while proof-of-work verification should be done by the caller or elsewhere. Removing the check does not by itself create a vulnerability, but any downstream code that relied on this function to validate headers before processing them will no longer get that protection automatically. Those callers must now add the check themselves or use a different validation path.

AI review queuedCreate empty `bip158` crateby rustaceanrob · 47fe9ceb · Dec 9, 2025 · 9 filesMessage 66 · AdequateInformational 15Details
Commit message · rustaceanrob

Create empty `bip158` crate

As part of discussion #5331, `bitcoin` and `p2p` should not depend on
each other and should instead mutually depend on `primitives`, `hashes`,
etc. BIP-158 is the last remaining dependency from `bitcoin` in `p2p`.
It is not a peer-to-peer specification, but it is not an essential
module of `bitcoin` either. IMO the best option for this module is to
release it as a crate.

Blaming the module shows it hasn't changed architecturally in many
years. A new crate would allow us to revisit some of the design choices.
Particularly the heavy use of generics, dependency on `io` that could be
replaced by `consensus_encoding`, and perhaps an opportunity to benchmark
and improve performance.

66/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit creates a brand-new, empty placeholder crate named `bitcoin-bip158` inside the rust-bitcoin workspace. It adds no executable code, no network functionality, no cryptographic operations, and no changes to existing crates. It is purely a project-structure refactor in preparation for later moving BIP-158 filter code out of the main `bitcoin` crate.

AI review queuedunits: Set TBD in deprecate attributeby Tobin C. Harding · d19605cb · Dec 7, 2025 · 7 filesMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

units: Set TBD in deprecate attribute

Set deprecation version. Note that this deprecated code is only going
to exist until the do the non-RC i.e., `v1.0.0`.

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

This commit only fills in placeholder version numbers in deprecation warnings. It does not change any program behavior, fix any bug, or introduce any security issue. It is a routine documentation/metadata cleanup.

AI review queuedinternals: Bump version to 0.4.2by Tobin C. Harding · fb65b565 · Dec 7, 2025 · 5 filesMessage 80 · StrongInformational 15Details
Commit message · Tobin C. Harding

internals: Bump version to 0.4.2

In preparation for releasing `bitcoin 0.33.0-rc.0` we need do a point
release of `internals` because we move a macro out of `bitcoin` and
over to `internals`. No other crate uses the macro so far so we only
update the `bitcoin` dependency on `internals` leaving the other
crates as they are.

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
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a routine version bump for an internal helper crate. It only changes version numbers in package files and a changelog entry. There is no code change, no bug fix, and no security issue visible in the diff.

AI review queuedp2p: remove io::Error from exposed APIby Nick Johnson · 213b85ba · Dec 6, 2025 · 1 fileMessage 60 · AdequateInformational 19Details
Commit message · Nick Johnson

p2p: remove io::Error from exposed API

Part of the process to break the p2p package's dependency on the old io
package.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This commit refactors how Bitcoin peer-to-peer address errors are reported. It replaces a generic input/output error type with a new, more specific error type for addresses that cannot be routed over normal internet connections (Tor, I2P, CJDNS). This is a routine API cleanup, not a fix for an active security vulnerability. The change is part of a larger effort to reduce internal package dependencies.

AI review queuedMove `bip152` to `p2p`by rustaceanrob · e242dd61 · Dec 6, 2025 · 6 filesMessage 59 · ThinInformational 15Details
Commit message · rustaceanrob

Move `bip152` to `p2p`

Replaces #5333 and #5365 by manually implementing `hex` traits for the
`ShortId` type. `FromStr` is omitted as I can't think of a logical use
of that method in this context. To make any sense of a string short ID
one needs the nonce and siphash keys.

This module is only relevant between two peers relaying blocks over the
peer to peer network.

59/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine code reorganization: it moves the BIP-152 compact block module from the main `bitcoin` crate into the `p2p` crate, where it is more logically located. It also replaces an auto-derived hex formatting trait with a manual implementation for one small type. There is no security fix or behavior change visible in the diff.

AI review queuedRemove alloc feature gate for MerkleNodeby Mitchell Bagot · cc0da4ca · Dec 5, 2025 · 6 filesMessage 68 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Remove alloc feature gate for MerkleNode

With the introduction of pop() to ArrayVec, the
MerkleNode::calculate_root logic can be implemented using ArrayVec
instead of alloc::vec::Vec. This allows for use of the functionality
without the alloc feature, albeit with an upper iterator length bound
of 32768 (exclusive) items.

Introduce ArrayVec bounded variation to MerkleNode::calculate_root,
and remove alloc feature gate from MerkleNode.

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

This commit refactors how Bitcoin Merkle roots are calculated so the code works even when the optional 'alloc' memory allocator feature is disabled. It replaces a growable vector with a fixed-size 15-slot array, which limits the no-alloc path to at most 32,767 transaction IDs. The change is a feature-portability improvement, not a security fix, and it explicitly returns None when the no-alloc limit is exceeded rather than overflowing or corrupting state.

AI review queuedprimitives: Move is_coinbase into primitivesby Mitchell Bagot · d325c292 · Dec 3, 2025 · 4 filesMessage 80 · StrongInformational 15Details
Commit message · Mitchell Bagot

primitives: Move is_coinbase into primitives

In order to move various functionality from BlockUncheckedExt trait
into the main Block<Unchecked> implementation, various surrouning
functionality must also be moved into primitives to prevent an
inverted dependency of primitives on bitcoin.

Move is_coinbase implementation from the TransactionExt in bitcoin
directly to the Transaction implementation in primitives.

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

This commit is a routine internal code reorganization. It moves a helper method, is_coinbase, from one module to another within the same project. The method's logic and behavior are unchanged, and there is no indication of a security fix or vulnerability.

AI review queuedprimitives: Move MerkleNode and TxIdentifier into primitivesby Mitchell Bagot · a8741234 · Dec 1, 2025 · 10 filesMessage 83 · StrongInformational 15Details
Commit message · Mitchell Bagot

primitives: Move MerkleNode and TxIdentifier into primitives

The MerkleNode trait in bitcoin provides convenience functions for
the TxMerkleNode and WitnessMerkleNode hash types to work with the
nodes as a tree. Moving the functionality of this trait into primitives
acts as a precursor to allow other functionality to move also.

Move the MerkleNode trait to primitives, making it private. Provide the
same interface for users through pub functions that wrap the private
trait. Introduce tests to cover mutants. Introduce TxIdentifier in
primitives.

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

This commit is a routine internal code reorganization. It moves the existing Merkle tree helper trait and transaction identifier abstraction from the main `bitcoin` crate into the lower-level `primitives` crate, and adds public wrapper functions and tests. The actual Merkle root calculation logic is copied verbatim, with no functional change.

AI review queuedUse usize for CompactSizeEncoder::newby Mitchell Bagot · b486c836 · Nov 30, 2025 · 6 filesMessage 68 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Use usize for CompactSizeEncoder::new

The current CompactSizeEncoder::new() constructor uses an impl ToU64
for its first parameter. The ToU64 trait is part of internals, and
thus isn't permitted to be part of the public API of consensus_encoding.

Change the ToU64 parameter type to usize, encoding values outside of
the u64 range (such as on 128 bit system) as u64::MAX.

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

This commit is a small API cleanup, not a security fix. It changes a Bitcoin data-encoding helper so it accepts ordinary memory sizes (usize) instead of a special internal type. The only behavioral change is on hypothetical future 128-bit computers, where impossibly large values would be encoded as the maximum allowed u64 value. On all current systems the output is unchanged.

AI review queuedprimitives: Convert various functions to constby Mitchell Bagot · ec9ec525 · Nov 28, 2025 · 10 filesMessage 60 · AdequateInformational 15Details
Commit message · Mitchell Bagot

primitives: Convert various functions to const

Convert constructors with zero arguments, getter and setter functions
to const in primitives.

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

This commit is a routine code-quality improvement. It marks a number of simple constructor and getter functions as 'const', which lets the Rust compiler evaluate them at compile time. There is no change to what the functions do, no bug fix, and no security-relevant behavior change.

AI review queuedunits: Convert various functions to constby Mitchell Bagot · 98b5777c · Nov 28, 2025 · 8 filesMessage 60 · AdequateInformational 15Details
Commit message · Mitchell Bagot

units: Convert various functions to const

Convert constructors with zero arguments, getter and setter functions
to const in units.

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

This commit is a routine code-quality improvement. It marks several simple constructor and getter functions as 'const', meaning they can be evaluated at compile time. There is no change to program logic, no bug fix, and no security relevance.

AI review queuedAdd decode test for reserve capacityby Jamil Lambert, PhD · 11d3f375 · Nov 26, 2025 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Add decode test for reserve capacity

There are new mutants in the reserve function for both VecDecoder and
ByteVecDecoder.

Add two new tests to check the functionality of reserve and kill the
mutants.

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

This commit only adds two new unit tests to verify that two decoder types allocate memory in correctly-sized batches. It does not change any production code, fix a bug, or alter behavior. There is no security-relevant change.

AI review queuedunits: Replace manual ceil division with div_ceilby Mitchell Bagot · a9f54c64 · Nov 26, 2025 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

units: Replace manual ceil division with div_ceil

Since the bump to MSRV 1.74, we now have access to div_ceil for ceiled
division of integer types. There are various places in units that we
manually implement ceiling division that can now be replaced by calls
to div_ceil.

Convert div_by_weight_ceil, div_by_fee_rate_ceil and mul_by_weight
to use div_ceil in place of manual ceiling division.

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

This commit is a routine code cleanup in the rust-bitcoin library. It replaces hand-written ceiling-division logic with Rust's newer built-in `div_ceil` function. The math result is intended to be identical, and there is no indication of a security bug being fixed.

AI review queuedSkip formatting byte arraysby Tobin C. Harding · 1f806395 · Nov 23, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

Skip formatting byte arrays

8 byte column are easier to read.

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

This commit only adds formatting hints to test code so that a code formatter (rustfmt) leaves byte arrays arranged in tidy 8-byte columns. It does not change any behavior, logic, or security-sensitive code.

AI review queuedfuzz: Update generate_files.sh for current targetsby Mitchell Bagot · b7c2e084 · Nov 21, 2025 · 3 filesMessage 83 · StrongInformational 15Details
Commit message · Mitchell Bagot

fuzz: Update generate_files.sh for current targets

In a2c809b, several new fuzz targets were introduced for
consensus_encoding. The fuzz crate's Cargo.toml was updated, but the
corresponding changes to generate-files.sh were not made. Since the
fuzz Cargo.toml is generated by generate-files.sh, it should be kept
up to date with any new changes.

Add consensus_encoding dependency and new Clippy lints to
generate-files.sh, and update the Cargo.toml and daily fuzz files
by running generate-files.sh.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidencesecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a routine maintenance update to the project's fuzz-testing infrastructure. It adds newly-created fuzz test targets to a script that auto-generates configuration files, and refreshes the generated files to match. There is no change to the actual Bitcoin library code that users rely on, and no security fix or vulnerability is present.

AI review queuedUpdate CHANGELOG.mdby maradini77 · 4eb16391 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · maradini77

Update CHANGELOG.md

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 is a one-character typo fix in the changelog, changing 'paramater' to 'parameter'. It does not modify any source code, build scripts, tests, or documentation that affects how the software behaves.

AI review queuedio: Make traits dyn compatibleby Tobin C. Harding · 45d3f188 · Nov 21, 2025 · 6 filesMessage 78 · AdequateInformational 18Details
Commit message · Tobin C. Harding

io: Make traits dyn compatible

Add an API test that shows dyn compatibility of std io traits and the
same for ours. Patch the crate to make the test pass.

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

This commit is a routine API cleanup: it changes custom I/O traits in the rust-bitcoin project so they can be used with Rust's dynamic-dispatch feature ('dyn'). The code changes are purely about making the traits more flexible for downstream users. There is no indication in the commit or title that this fixes a security vulnerability, and the diff does not change any security-critical behavior such as bounds checking, parsing limits, or cryptographic validation.

AI review queuedprimitives: handle zero-input transactionsby Nick Johnson · 1f7969f4 · Nov 14, 2025 · 1 fileMessage 68 · AdequateLow 34Details
Commit message · Nick Johnson

primitives: handle zero-input transactions

rust-bitcoin always uses the Segwit witness encoding for zero input
transactions, described in detail in the Serialization notes of the
transaction docs. When decoding such case, there are no witnesses
so the decoder should skip to decoding the locktime.

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 · Low 34/100

This commit fixes a bug in how the rust-bitcoin library decodes Bitcoin transactions that have no inputs. Normally, the library uses a special encoding for zero-input transactions. The decoder was incorrectly trying to read witness data even when there were no inputs, which would cause decoding to fail. The fix skips witness decoding when there are no inputs, and a new test verifies that an empty transaction can be encoded and decoded correctly.

AI review queuedRemove redundant array allocation and copy in OutPointDecoderby Mitchell Bagot · 0e5f901f · Nov 13, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove redundant array allocation and copy in OutPointDecoder

OutPointDecoder::end() currently decodes data into a 36-byte array,
before copying subslices to pass through to constructors for the inner
fields. This is needlessly wasteful.

Remove the array allocations and byte array copies in
OutPointDecoder::end() and construct inner OutPoint fields directly
from the decoded array.

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 straightforward internal code cleanup. It removes a temporary 36-byte buffer and manual byte copying when decoding an OutPoint (a Bitcoin transaction reference), replacing it with a direct split of the already-decoded byte array. There is no security-relevant change.

AI review queueddoc: Add version documentby Tobin C. Harding · 7888b60a · Nov 11, 2025 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · Tobin C. Harding

doc: Add version document

Add a document that explicitly states which versions of `bitcoin` are
long term support (LTS).

Include a list that maps `bitcoin` version to its dependency versions
for crates in this repo.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit only adds a new documentation file describing which versions of the rust-bitcoin library are considered long-term support (LTS) and which dependency versions correspond to each release. No code was changed, and there is no security fix or vulnerability present.

AI review queuedrefactor: enable redundant_clone lint and fix warningsby Klaklax · 5ecef4b3 · Nov 5, 2025 · 19 filesMessage 62 · AdequateInformational 15Details
Commit message · Klaklax

refactor: enable redundant_clone lint and fix warnings

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine code cleanup: it turns on a Rust linter warning for unnecessary .clone() calls and removes those unnecessary clones. There is no security-relevant behavior change.

AI review queuedAdd test to kill mutant in decode_from_readby Jamil Lambert, PhD · d391298b · Nov 4, 2025 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Add test to kill mutant in decode_from_read

Mutation testing found a mutant in decode_from_read.

Add a decode_from_read test the same as `decode_from_slice_extra_data`
and `decode_from_read_unbuffered_extra_data`.

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

This commit only adds a new unit test to the codebase. It does not change any production code, fix a bug, or alter behavior. The test verifies that a decoding function correctly ignores extra bytes after the expected data when reading from a stream. There is no security issue present in the commit itself.

AI review queuedAdd test to kill mutant in push_bytesby Jamil Lambert, PhD · 20ebf277 · Nov 4, 2025 · 1 fileMessage 78 · AdequateInformational 12Details
Commit message · Jamil Lambert, PhD

Add test to kill mutant in push_bytes

Mutation testing found a mutant in calculating the remaining bytes to
decode in `<impl Decoder for ByteVecDecoder>::push_bytes`.

Add tests for both single and multi-chunk consumption.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new unit tests for a decoder that reads length-prefixed byte vectors. It does not change any production code, so it cannot introduce or fix a runtime security vulnerability by itself. The tests verify that the decoder stops exactly at the declared payload length and does not accidentally consume extra trailing bytes.

AI review queuedconsensus_encoding: add clippy::use_self lintby Jose Storopoli · 7a970b1f · Oct 31, 2025 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Jose Storopoli

consensus_encoding: add clippy::use_self lint

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

This commit is a routine code-quality cleanup. It turns on a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating a type's name inside its own implementation blocks, and updates the affected code to satisfy the new rule. There is no functional change, no bug fix, and no security relevance.