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 queuedUpdate API filesby Abeeujah · 17204a8b · May 18, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Abeeujah

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 listing files (text snapshots of what functions and types are publicly exposed). It adds documentation of a new error type and a new 'try_push' method for an internal array vector, but it does not change any actual source code or behavior. There is no security issue here.

AI review queuedUpdate `ArrayVec` deserializationby Abeeujah · a375642a · May 18, 2026 · 1 fileMessage 58 · ThinLow 44Details
Commit message · Abeeujah

Update `ArrayVec` deserialization

Deserialization of ArrayVec now uses `ArrayVec::try_push` method
over the `ArrayVec::push` method, which would panic if the array
is full, causing us to manually check for capacity before pushing.

The `try_push` method returns a `Result` which is mapped to Serde's
`invalid_length` error.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Low 44/100

This commit fixes a deserialization bug in an internal array-like data structure. Previously, if untrusted serialized data claimed to contain more items than the structure could hold, the code would panic (crash) instead of returning a proper error. The fix makes deserialization gracefully reject oversized input.

AI review queuedp2p: Remove `bitcoin` dependencyby rustaceanrob · 3a46e0a6 · May 11, 2026 · 4 filesMessage 58 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Remove `bitcoin` dependency

`hex` is brought in from `primitives` as it is an unconditional
dependency. `arbitrary` is brought in from `primitives` as opposed to
`bitcoin`. `primitives` and `encoding` need `alloc`. One doc line is updated.

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

This is a routine internal refactoring commit in the rust-bitcoin project. It removes a direct dependency on the main 'bitcoin' crate from the smaller 'p2p' (peer-to-peer messages) crate and instead pulls in the needed features from more focused sub-crates. The only code change is updating a documentation example to use a different decoding function. There is no security-relevant change visible in the diff.

AI review queuedUse stacked attributes over #[cfg(all(...))]by Mitchell Bagot · f5c09645 · May 11, 2026 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · Mitchell Bagot

Use stacked attributes over #[cfg(all(...))]

Per our policy, feature gates should use stacked attributes instead
of #[cfg(all(...))]. Presumably due to changes at the same time as
this policy was introduced, there remain a few uses of the old style
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: security-sensitive path
AI analysis · Informational 15/100

This commit is a purely cosmetic code-style change. It rewrites some Rust feature-gate conditions from one allowed syntax to another preferred syntax, with no change to which features enable which code. There is no security relevance.

AI review queuedMove deserialize tests to primitivesby Mitchell Bagot · c26faf9c · May 11, 2026 · 5 filesMessage 90 · StrongInformational 15Details
Commit message · Mitchell Bagot

Move deserialize tests to primitives

In bitcoin, there are various tests that only have a dependency on
bitcoin due to the deserialize/serialize functions on the old encoding
traits. Changing these to use consensus_encoding allows them to be
trivially moved to primitives.

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

This commit simply moves existing unit tests from one internal crate to another and rewrites them to use a newer encoding API. No production code behavior changes, and no security bug is fixed or introduced.

AI review queuedMove tests to upstream cratesby Mitchell Bagot · 20825743 · May 11, 2026 · 7 filesMessage 78 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move tests to upstream crates

Test cases for Outpoint, Version, CompactTarget and Sequence have been
left in bitcoin even following their moves to primitives and units. In
order to keep tests close to the corresponding types, the tests should
be moved to the upstream leaf crates.

Move tests to units and primitives alongside their corresponding types.

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

This commit simply moves existing unit tests from one crate to another within the same project. No production code behavior is changed, so it has no security impact on users of the library.

AI review queuedp2p: Remove `io` dependencyby rustaceanrob · ee3e929b · May 9, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Remove `io` dependency

`io` is no longer required with the introduction of
`bitcoin-consensus-encoding`

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit simply removes an unused library dependency (bitcoin-io) from the p2p crate after a newer encoding library made it unnecessary. There is no code change, no bug fix, and no security issue visible in the diff.

AI review queuedImprove codec methods implementationby Abeeujah · 0a5f2762 · May 8, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Abeeujah

Improve codec methods implementation

Use Rust's Option methods and Pattern matching to collapse if_let_else
constructs in the `read_limit` method implementation, this maintains a
clearer and concise usage of the `Option<T>` API.

Leverage `Option<T>::is_some_and` method for the `advance` method impl,
which proceeds to propagate to `Encoder::advance` if the encoder is
`Some(T)` and returns false if the encoder is `None`.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 code cleanup in the Rust Bitcoin library. It rewrites a few internal helper methods to use more idiomatic Rust syntax (Option methods and pattern matching) instead of longer if/else blocks. There is no change to what the code actually does, no security fix, and no bug being patched.

AI review queuedUpdate API filesby Nick Johnson · a517bf1f · May 3, 2026 · 7 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nick Johnson

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 files that record what public functions and traits the library exposes. The actual code changes happened in an earlier commit; this one just refreshes the snapshots. There is no security-relevant change here.

AI review queuedSimplify `Decodable` traitby Martin Habovstiak · 5d2eec3c · May 3, 2026 · 16 filesMessage 58 · ThinInformational 15Details
Commit message · Martin Habovstiak

Simplify `Decodable` trait

The `Decodable` trait already required that a decoder can be created
without providing any extra arguments and it required that the output of
the decoder is `Self`, implying that no decoder can be reused for
different types.

We observe that simply requiring that `Decoder` impls `Default` is
practically the same thing - requires constructibility without
arguments. By bounding `Decoder` on `Default` in addition to `Decoder`
and providing a default implementation of the method we simplify the
implementations: they now only need to impl `Default` which often can be
derived and specify the associated decoder type.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 internal code cleanup in the Rust Bitcoin library. It changes how decoders are created so that Rust's built-in Default mechanism is used instead of manually writing a decoder() function for every type. There is no change to how data is parsed, no bug fix, and no security relevance.

AI review queuedRemove now-useless overrides of `decoder`by Martin Habovstiak · f3c75710 · May 3, 2026 · 30 filesMessage 68 · AdequateInformational 15Details
Commit message · Martin Habovstiak

Remove now-useless overrides of `decoder`

The previous commit added a default impl for the `decoder` method which
renders the existing ones uselsess overrides. This commit simply removes
all of them.

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

This commit is a routine cleanup: it removes dozens of identical-looking helper functions that were made unnecessary by a previous change. There is no security issue here. The code still decodes data the same way; it just relies on a shared default implementation instead of repeating the same boilerplate in every file.

AI review queuedUpdate API filesby Abeeujah · 62895cdb · May 1, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Abeeujah

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 a generated text file listing the public API surface of the crate. It records that an internal ArrayVec type now implements standard serde serialization/deserialization traits. The diff itself contains no source code changes, no bug fixes, and no behavior changes.

AI review queuedp2p: add V1MessageHeader constructorby yancy · 5bb9e5db · May 1, 2026 · 1 fileMessage 58 · ThinInformational 12Details
Commit message · yancy

p2p: add V1MessageHeader constructor

Adds a constructor to `V1MessageHeader` which also computes the 4 byte
checksum as defined by protocol docs. This constructor is used to
compose a network header that can be transmitted over the network stream.

Any network message (payload) must be directly preceded in the network
stream by a header. In that way, the receiving client knows how many
bytes to read, and what message to interpret.

A working code example might be a Pong response:
```
let message = bitcoin_p2p_messages::message::Pong(nonce);
let msg_header = V1MessageHeader::new(magic, &message, "pong");

// write the header to stream
encoding::encode_to_writer(&msg_header, &stream);

// write message to stream
encoding::encode_to_writer(&message, &stream);
```

Note that Currently, CommandString wraps a Cow<'static, str>, so the
lifetime of `cmd` must match the static lifetime. However, the protocol
documents define this as a 12 byte field, so this can and should be
changed at some point.

The fields defined in `V1MessageHeader` is the first four fields of a
message structure. An example given in the docs of message header is
given as:

```
Message Header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 73 69 6F 6E 00 00 00 00 00 - "version" command
64 00 00 00 - Payload is 100 bytes long
35 8d 49 32 - payload checksum (byte order)
```

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

This commit adds a new helper function (constructor) to build a Bitcoin P2P network message header. It simply packages existing fields and computes the message checksum automatically. There is no indication it fixes a security bug or introduces a vulnerability; it appears to be a routine API improvement.

AI review queuedbitcoin: cut down on exact_features test matrixesby Nick Johnson · 0435a98d · Apr 28, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · Nick Johnson

bitcoin: cut down on exact_features test matrixes

The Github CI runner is timing out when running all the feature sets
on the older MSRV compiler. The current list of exact_features in the
bitcoin crate was a conserative "include everything" when we switched
over to cargo-rbmt. This cuts it down ~50% and focuses on core
interactions we want to always cover. This puts more responsibilites on
cargo-rbmt's random feature subsets it runs on every commit.

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

This commit only changes the list of feature combinations that are tested automatically in CI. It removes most of a large, exhaustive test matrix and keeps just two core combinations to avoid timeouts on older Rust compilers. There is no change to the actual library code, dependencies, or user-facing behavior.

AI review queuedRe-name consensus_encoding main traitsby Tobin C. Harding · ae1346f4 · Apr 27, 2026 · 46 filesMessage 80 · StrongInformational 15Details
Commit message · Tobin C. Harding

Re-name consensus_encoding main traits

When we did the first implementation of the `consensus_encoding` crate
we used the same names for the public traits as the old encoding code.

In hindsight we should have used the more Rusty terms `Encode` and
`Decode` instead of `Encodable` and `Decodable`.

Bonus points the new names are easier to spell.

Do trivial-ish rename. Leave the `EncodableBytesIter` as is because
the fix to it is non-trivial. Leave the old encoding traits as they
are because they are destined for the grave very soon anyways.

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

This commit is a simple, large-scale rename inside the Rust Bitcoin project. It changes the names of two public traits from Encodable/Decodable to Encode/Decode across many files, but does not alter any behavior, logic, or security properties. It is a routine code-quality refactor with no security impact.

AI review queuedfuzz: Migrate p2p fuzz targets to new encodingby rustaceanrob · 012ea1e6 · Apr 26, 2026 · 3 filesMessage 55 · ThinInformational 15Details
Commit message · rustaceanrob

fuzz: Migrate p2p fuzz targets to new encoding

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidencesigning or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates internal fuzz testing code to use a newer encoding/decoding helper crate. It does not change any production code that real users or network peers would run, and it does not fix or introduce any security vulnerability.

AI review queuedp2p: remove deprecated encoders in V1NetworkMessage constructorby yancy · adcee7cd · Apr 26, 2026 · 1 fileMessage 73 · AdequateInformational 12Details
Commit message · yancy

p2p: remove deprecated encoders in V1NetworkMessage constructor

`payload.consensus_encode()` is deprecated. Replace with
newer sans/IO `hashes::encode_to_engine()`.

Also, updated the doc comment now that encode no longer has a panic
path.

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

This is a small internal cleanup in the rust-bitcoin library's peer-to-peer message code. It swaps an older, deprecated way of computing a SHA256 double checksum for a newer helper function. The behavior should be equivalent, and the change removes a deprecated API call rather than fixing a security bug.

AI review queuedMove importby Tobin C. Harding · a9cf222d · Apr 23, 2026 · 1 fileMessage 13 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

Move import

There is an unrelated lint warning, no clue how it started showing up
but its a trivial fix. Move import from one feature gated scope to
another.

13/100 · OpaqueMessage clarity
✓ Provides detailed explanatory context! Very short subject! Too few words to establish purpose
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a minor code cleanup: it moves a Rust import statement (`use core::fmt;`) from one feature-gated code block to another. The change fixes a compiler lint warning and does not alter any program behavior or security logic.

AI review queuedImplement Consensus Encoding for V2NetworkMessageby Abeeujah · 9b6a6402 · Apr 21, 2026 · 1 fileMessage 68 · AdequateLow 29Details
Commit message · Abeeujah

Implement Consensus Encoding for V2NetworkMessage

Implement new consensus encoding traits for the V2NetworkMessage
struct, to be sent as a message across the Bitcoin Network P2P.

This is part of the ongoing attempt to drop bitcoin as a dependency
from `bitcoin-p2p-messages` crate.

Constructs the Encoder and Decoder types for the encoding and
deserialization of the V2NetworkMessage, introduces the
`V2NetworkMessageDecoderError` to report errors encountered while
enc/decoding the message.

Co-authored-by: rustaceanrob <rob.netzke@gmail.com>

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

This commit adds new encoding and decoding logic for Bitcoin P2P v2 network messages in the rust-bitcoin library. It is a feature/refactoring change that introduces a new way to serialize and deserialize v2 protocol messages. There is no direct evidence in the commit that this fixes a known security vulnerability, but any new parser for network-facing data is a potential source of bugs such as crashes, denial of service, or memory issues if it mishandles malformed input.

AI review queuedunits: scrub encoder/decoder layoutby Renato Britto · d06af66f · Apr 21, 2026 · 6 filesMessage 45 · ThinInformational 15Details
Commit message · Renato Britto

units: scrub encoder/decoder layout

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 is a pure code cleanup in the rust-bitcoin library's 'units' module. It reorders where encoder and decoder definitions appear in six source files so that the Encodable and Decodable trait implementations come before the macro-generated encoder/decoder structs. No behavior, logic, or security properties change; it only makes the layout consistent.

AI review queuedImprove hex codec test coverageby Jamil Lambert, PhD · c51ee8db · Apr 21, 2026 · 3 filesMessage 55 · ThinInformational 15Details
Commit message · Jamil Lambert, PhD

Improve hex codec test coverage

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! 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 new unit tests for the existing hexadecimal encoding/decoding code. It does not change any production logic, so it cannot introduce or fix a security vulnerability on its own.

AI review queuedUpdate API filesby Mitchell Bagot · 8d1dd754 · Apr 20, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Update API files

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

This commit only updates automatically-generated API snapshot files. It shows a public type being renamed from EncodableByteIter to EncoderByteIter and changing from borrowing an encodable value to owning an encoder. There is no source code change in the diff, no bug fix, and no security-relevant behavior shown.

AI review queuedMove transaction encoding tests to primitives/tests/encoding.rsby busayo-OD · 3951134d · Apr 19, 2026 · 2 filesMessage 95 · StrongInformational 15Details
Commit message · busayo-OD

Move transaction encoding tests to primitives/tests/encoding.rs

This change moves transaction consensus encoding and decoding tests,
along with shared helpers and constants, into a dedicated test file.
Removes the FIXME comment that requested this change.

The assert_eq! on the no-witnesses error is replaced with matches!
on the outer error type due to visibility constraints.

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

This commit simply moves existing transaction encoding and decoding tests from one file to another. It does not change any production code, only reorganizes test code. The only functional tweak is replacing one detailed error comparison with a broader pattern match, because the moved test can no longer see a private inner error type. There is no security issue here.

AI review queuedDrop use of deprecated methodsby Abeeujah · a18f6a78 · Apr 17, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Abeeujah

Drop use of deprecated methods

In sign-tx-segwit example, the deprecated `public_key` method was
still being used, not reflecting the now recommended `to_public_key`
method.

This patch drops the use of the deprecated method for the now recommended
method by the API.

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 is a routine code cleanup in an example file. It replaces an old, deprecated method name (`public_key`) with the newer recommended name (`to_public_key`). There is no security issue here; the change only affects example documentation code and does not alter how the library works.

AI review queuedRemove useless `Option`s in encodersby Martin Habovstiak · 06623b81 · Apr 16, 2026 · 6 filesMessage 78 · AdequateInformational 19Details
Commit message · Martin Habovstiak

Remove useless `Option`s in encoders

The `Encoder` contract states that implementors are not obligated to
make the state after `false` was returned defined, however they so far
did so anyway and this was even tested. This was a waste of performance
and complication of the code that would get amplified with multiple such
encoders chained as each would have to track the final state.

This change removes all those `Option`s, associated tests and in
addition replaces `&[]` return with panic in invalid state of a
composite encoder.

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

This commit is a routine internal cleanup in the rust-bitcoin library's data-encoding machinery. It removes unnecessary 'Option' wrappers from several encoder types and stops guaranteeing that encoders return an empty slice after they are exhausted. Instead, calling 'current_chunk()' on an exhausted encoder may now panic in some composite cases. The change is framed by the author as a performance and code-simplification improvement, not as a security fix. There is no evidence in the commit or supplied references of an exploitable vulnerability.