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 50 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 queuedunits: add clippy::use_self lintby Jose Storopoli · 29f9b110 · Oct 31, 2025 · 20 filesMessage 45 · ThinInformational 15Details
Commit message · Jose Storopoli

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

This commit is a code-style cleanup in the rust-bitcoin library's units crate. It enables a Clippy lint called use_self and replaces explicit type names (like FeeRate, Weight, LockTime) with the shorthand Self inside impl blocks. These changes do not alter program behavior, fix no bugs, and have no security relevance.

AI review queuedprimitives: add clippy::use_self lintby Jose Storopoli · f4d7e05d · Oct 31, 2025 · 11 filesMessage 45 · ThinInformational 15Details
Commit message · Jose Storopoli

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

This commit only turns on a Rust style lint (clippy::use_self) and replaces explicit type names with `Self` in the source code. It does not change what the code does, only how it is written. There is no security impact.

AI review queuedConvert encoder/decoder constructors to constby Mitchell Bagot · db0de95e · Oct 31, 2025 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Convert encoder/decoder constructors to const

Using const functions allows the compiler to make certain optimisations
by precomputing some values during compilation, instead of at runtime.

Convert all constructors in the consensus_encoding crate to const, with
the following exceptions:
SliceEncoder::without_length_prefix - This needs to call T::encoder,
which would require making the Encodable trait use a const fn.
CompactSizeEncoder::new - Requires various ArrayVec functions to be
const, which requires a cascade of const functions elsewhere.

68/100 · AdequateMessage clarity
✓ 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 · Informational 15/100

This commit is a routine performance and ergonomics improvement. It changes several Rust constructor functions from regular functions to 'const' functions, which lets the compiler precompute some values at compile time rather than runtime. There is no change to security behavior, no bug fix, and no vulnerability patch.

AI review queuedprimitives: Use stable hex depenencyby Tobin C. Harding · f43b94ef · Oct 28, 2025 · 18 filesMessage 68 · AdequateInformational 19Details
Commit message · Tobin C. Harding

primitives: Use stable hex depenency

We don't want `hex v0.3.0` to appear in the public API of `primitives
1.0.0`.

Add a dep on `hex v1.0.0` and use it for anything that appears in the
public API.

And it seems we do not need the `serde` feature of `hex-unstable` so
remove it.

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 commit swaps in a newer, stable version of a helper library (hex-conservative 1.0.0) for public-facing parts of the rust-bitcoin 'primitives' crate, while keeping the older version for internal-only uses. It is a dependency/API-stability cleanup, not a fix for a known security bug. There is no direct evidence in the commit that it addresses an exploit or vulnerability.

AI review queuedbuild(deps): bump actions/upload-artifact from 4 to 5by dependabot[bot] · ad4835ef · Oct 27, 2025 · 3 filesMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump actions/upload-artifact from 4 to 5

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 5.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v4...v5)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...

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

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine dependency update by Dependabot that bumps the GitHub Actions 'upload-artifact' action from version 4 to version 5 in three internal workflow files. There is no code change to the rust-bitcoin library itself, and nothing in the commit suggests a security problem or fix.

AI review queuedbuild(deps): bump actions/download-artifact from 5 to 6by dependabot[bot] · 42f01eab · Oct 27, 2025 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump actions/download-artifact from 5 to 6

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 5 to 6.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](https://github.com/actions/download-artifact/compare/v5...v6)

---
updated-dependencies:
- dependency-name: actions/download-artifact
dependency-version: '6'
dependency-type: direct:production
update-type: version-update:semver-major
...

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

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (used to download build artifacts) from version 5 to version 6 in a daily fuzzing workflow. There is no indication of a security vulnerability or malicious change in the commit itself.

AI review queuedChange extension trait function return types to Selfby Mitchell Bagot · faca7b36 · Oct 25, 2025 · 4 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Change extension trait function return types to Self

Within the extension traits in the bitcoin crate, some functions use
a Self return type, while others use the specific type name. Use of a
specific type name causes discontinuity in the codebase, is longer,
and is semantically less clear for distinguishing return of a trait
implementor's type vs an instance of a specific type.

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-style cleanup. It changes some function return type declarations from explicit type names (like `TxOut` or `CompactTarget`) to `Self` inside Rust extension traits. This has no effect on what the functions do or on security.

AI review queuedrefactor: remove redundant clones in bitcoin crateby Klaklax · 4649e5cf · Oct 24, 2025 · 3 filesMessage 62 · AdequateInformational 15Details
Commit message · Klaklax

refactor: remove redundant clones in bitcoin crate

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 minor code cleanup that removes unnecessary copy operations (clones) inside test code only. It does not change any production behavior and has no security relevance.

AI review queuedAdd decode segwit testby Jamil Lambert, PhD · 29cb875e · Oct 23, 2025 · 1 fileMessage 61 · AdequateInformational 12Details
Commit message · Jamil Lambert, PhD

Add decode segwit test

There is a mutant in <impl Decoder for TransactionDecoder>::push_bytes.

Add a test that decoding a transaction with 1 input but no witnesses
for any input errors.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds a new test case. It does not change any production code. The test checks that decoding a SegWit-formatted transaction with no witness data correctly produces an error. There is no fix or behavior change in the actual decoder.

AI review queuedAdd transaction decode round trip testby Jamil Lambert, PhD · 9f79146f · Oct 23, 2025 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Add transaction decode round trip test

There is a mutant in push_bytes.

Add a transaction encode/decode round trip test to kill it.

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

This commit only adds a new test that encodes a Bitcoin transaction and decodes it again to make sure the result matches the original. It does not change any production code, fix a bug, or introduce a security issue. The commit message mentions a 'mutant in push_bytes,' which is testing jargon for a surviving fake code change during mutation testing, not a real vulnerability.

AI review queuedRemove unused comments on TransactionExt trait implementationby Mitchell Bagot · 43ae5fa9 · Oct 23, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused comments on TransactionExt trait implementation

Comments applied to function implementations of traits do not render
in compiled Rust documentation. The TransactionExt trait implementation
for Transaction includes two such comments that duplicate similar
warnings present in the trait definition.

This patch removes the useless comments above the functions
total_size and base_size in the TransactionExt implementation of
Transaction.

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 only removes two short documentation comments from a Rust trait implementation. The actual code behavior is unchanged. There is no security relevance.

AI review queuedMove encode_to_hash_engine to hashes from consensus_encodingby Mitchell Bagot · 1a3dfbe5 · Oct 22, 2025 · 8 filesMessage 85 · StrongInformational 18Details
Commit message · Mitchell Bagot

Move encode_to_hash_engine to hashes from consensus_encoding

The encode_to_hash_engine function created a dependency on hashes from
consensus_encoding. Since consensus_encoding is moving to 1.0, it is
best to remove the dependency on the pre-1.0 hashes crate.

This patch moves the encode_to_hash_engine function to the hashes
crate, and reverses the dependency so that hashes now depends on
consensus_encoding instead of vice-versa.

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

This is a routine internal code reorganization. A helper function that feeds encoded data into a hash calculation was moved from one Rust crate to another, and the dependency direction between those two crates was reversed. The actual logic of the function did not change, and there is no indication this fixes or introduces a security bug.

AI review queued2025-10-19 automated rustfmt nightlyby Fmt Bot · 24e7124a · Oct 19, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2025-10-19 automated rustfmt nightly

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

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and brace style in two source files. No program logic, behavior, or security properties were changed.

AI review queuedconsensus_encoding: add more encode/decode testsby Nick Johnson · 6fadad68 · Oct 18, 2025 · 2 filesMessage 78 · AdequateInformational 15Details
Commit message · Nick Johnson

consensus_encoding: add more encode/decode tests

A bunch of corner cases and boundary condition tests. Some of these
boundary cases are not actually part of the explicit contract, but we
would want to know if the behavior changed since it is exposed to the
caller.

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 new unit tests for encoding and decoding routines in the rust-bitcoin consensus_encoding crate. It does not change any production code, fix bugs, or alter behavior. The tests cover corner cases such as zero-length arrays, empty slices, boundary values for compact-size integers, and state transitions in combined encoders/decoders.

AI review queuedRemove doc_auto_cfgby Tobin C. Harding · 3f332405 · Oct 17, 2025 · 11 filesMessage 33 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

Remove doc_auto_cfg

This was removed in recent nightly and is breaking all the docs builds
when we try and publish crates.

33/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body! Too few words to establish purpose
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit removes a Rust compiler feature flag called doc_auto_cfg from 11 library files. The feature was removed in recent nightly Rust compilers and was causing documentation builds to fail when publishing crates. It is purely a build/documentation compatibility fix with no effect on the actual Bitcoin code or its security.

AI review queuedAdd fuzz targets for consensus_encoding crateby Nick Johnson · ecadab6c · Oct 17, 2025 · 7 filesMessage 78 · AdequateInformational 15Details
Commit message · Nick Johnson

Add fuzz targets for consensus_encoding crate

The four new targets focus on the decoding half of the exposed API. This
is the half which deals with consuming bytes from unknown sources.
Encoding on the other hand probably wouldn't benefit much from fuzzing
since all bytes are known before the operation.

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

This commit only adds new fuzz testing targets for the consensus_encoding crate. Fuzz testing is an automated quality-assurance technique that feeds random or crafted inputs to code to find crashes or unexpected behavior. The commit does not change any production library code, so it cannot by itself introduce a security vulnerability or fix one.

AI review queuedunits: Bump version to 1.0.0-rc.1by Tobin C. Harding · cf10e50d · Oct 17, 2025 · 7 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

units: Bump version to 1.0.0-rc.1

In preparation for release bump the version, update the 1.0.0
changelog, and update the lock files.

While we are at it add an explicit version number to the dependency in
`p2p`, `bitcoin`, and `primitives`.

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

This commit is a routine release preparation: it bumps the version number of the `bitcoin-units` crate from 1.0.0-rc.0 to 1.0.0-rc.1, updates the two lock files, adds an explicit version requirement to the dependency declarations in three other crates, and moves a couple of changelog entries under the new release heading. There are no code changes, no bug fixes, and no security-relevant behavior changes in the diff.

AI review queuedchore: clarify TODO comment in Cargo.tomlby Ethfan · 33a3f957 · Oct 16, 2025 · 1 fileMessage 37 · OpaqueInformational 15Details
Commit message · Ethfan

chore: clarify TODO comment in Cargo.toml

37/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only rewords a code-comment in a configuration file. It changes 'TODO' to 'TODO: Consider enabling this lint.' There is no code change, no behavior change, and no security relevance.

AI review queuedUpdate transaction.rsby sashaodessa · 7890935d · Oct 16, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · sashaodessa

Update transaction.rs

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit fixes two spelling mistakes in code comments ('coversion' to 'conversion'). No program logic, behavior, or security properties were changed.

AI review queuedfix typoby Forostovec · 46506337 · Oct 15, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Forostovec

fix typo

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit corrects a single-word typo in a documentation comment. The comment for the Decodable trait incorrectly said 'encoded' and now correctly says 'decoded'. No code behavior changes.

AI review queuedUpdate API text filesby Tobin C. Harding · fcfaafcb · Oct 15, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

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 a generated text file that records the project's public API surface. It changes the documented return type of several encoder helper methods from 'optional byte slice' to 'byte slice'. No actual source code, logic, or behavior changed, so there is no security issue in this commit itself.

AI review queuedconsensus_encoding: composite error typesby Nick Johnson · 9f93c901 · Oct 14, 2025 · 6 filesMessage 58 · ThinInformational 17Details
Commit message · Nick Johnson

consensus_encoding: composite error types

Ditch the complexity of the From implementation mapping for decoder
errors and just have predefined composites for 2,3,4, and 6.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit is a routine internal refactoring of how composite decoders report errors in the rust-bitcoin library. It replaces a generic error-mapping scheme with fixed error types for decoders that combine 2, 3, 4, or 6 sub-decoders. There is no indication this fixes a security bug or changes how data is parsed; it only changes the shape of error values returned when parsing fails.

AI review queuedAdd documentation for panics during size calculationsby Shing Him Ng · c3e1bdc1 · Oct 14, 2025 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Shing Him Ng

Add documentation for panics during size calculations

50/100 · ThinMessage clarity
✓ Specific, 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 15/100

This commit only adds documentation comments explaining that certain size-calculation functions can panic if an arithmetic overflow occurs. It does not change any actual code behavior, fix a bug, or introduce new functionality. There is no security-relevant code change.

AI review queuedRemove stale comment in transaction decodingby Tobin C. Harding · fa480cbb · Oct 14, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Remove stale comment in transaction decoding

This comment is stale now that we remove the old transition stuff.

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 removes two lines of stale explanatory comment from transaction decoding code. No code behavior changes, no security relevance.

AI review queuedchore: fix typosby Galoretka · 94498e07 · Oct 14, 2025 · 3 filesMessage 40 · ThinInformational 15Details
Commit message · Galoretka

chore: fix typos

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 only fixes spelling mistakes in comments and documentation strings. No code behavior was changed, so it has no security impact.