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 22 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 queuedhashes: Introduce hex stable and remove unecessary uses of hex_unstableby Mitchell Bagot · ba7cab15 · Mar 11, 2026 · 11 filesMessage 73 · AdequateInformational 18Details
Commit message · Mitchell Bagot

hashes: Introduce hex stable and remove unecessary uses of hex_unstable

The hashes crate provides various cross-crate macros, which expose
unstable hash errors in the public API of the crates that use them. In
order to remove these unstable errors from the bitcoin API, the hashes
crate needs to use stable hex_conservative errors in these macros.

Introduce hex_conservative 1.0.0 as a dependency for hashes and replace
uses of FromHex with decode_to_vec and decode_to_array.

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

This commit is a routine dependency and API cleanup in the rust-bitcoin project's hashing crate. It swaps an unstable hex-parsing helper for a newly released stable version and updates the error types that downstream code sees. There is no direct evidence of a security vulnerability being fixed; it is best understood as a maintainability and API-stability improvement.

AI review queuedp2p: Introduce hex stable and remove unecessary uses of hex_unstableby Mitchell Bagot · 26ccfd92 · Mar 11, 2026 · 7 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

p2p: Introduce hex stable and remove unecessary uses of hex_unstable

While the p2p crate doesn't directly expose unstable hex errors, it has
various uses of the unstable hex crate where the stable hex crate would
be sufficient.

Introduce hex_conservative 1.0.0 as a dependency for p2p and replace
uses of FromHex with decode_to_vec and decode_to_array.

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

This commit is a routine internal cleanup in the rust-bitcoin project's peer-to-peer (p2p) crate. It swaps some test and internal code from using an unstable version of a hex-encoding helper library to a newly released stable version. There is no user-facing behavior change, no bug fix, and no security fix visible in the diff.

AI review queuedAdd missing license commentby Jamil Lambert, PhD · 3dff2d7c · Mar 11, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

Add missing license comment

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 a missing software license comment (CC0-1.0) to a test file. It does not change any code behavior, fix any bug, or alter any security-relevant logic.

AI review queuedAdd missing doc inlineby Jamil Lambert, PhD · 1df9d49e · Mar 11, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

Add missing doc inline

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

This commit adds a missing documentation attribute to a public type alias in the rust-bitcoin hashes library. It only affects how the SHA3-256 hash type appears in generated API documentation and has no security or runtime effect.

AI review queuedconsensus_encoding: Introduce decode_from_slice_unboundedby Mitchell Bagot · 7ee482c1 · Mar 11, 2026 · 7 filesMessage 63 · AdequateLow 34Details
Commit message · Mitchell Bagot

consensus_encoding: Introduce decode_from_slice_unbounded

The old consensus code deserialize function returned an error when
decoding failed to consume all bytes in the input slice. The new
nearest-equivalent function, decode_from_slice, does not error on
unconsumed bytes.

Introduce decode_from_slice_unbounded which errors on unconsumed bytes.
Adjust decode_from_slice to error on unconsumed bytes.
Introduce DecodeError type to specify decoder vs unconsumed bytes
errors for decode_from_slice.

63/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 34/100

This commit changes how a Bitcoin library decodes byte slices. Previously, a function called decode_from_slice silently accepted extra bytes after a valid object. Now it rejects leftover bytes, and a new function decode_from_slice_unbounded is provided for cases where callers intentionally want to read only part of the input. This is a defensive correctness fix that prevents accidental acceptance of malformed or padded data, but it also changes the public API behavior and error types, which could break downstream code.

AI review queuedp2p: add serde impls for FilterHash and FilterHeaderby busayo-OD · 5e968d57 · Mar 10, 2026 · 5 filesMessage 65 · AdequateInformational 19Details
Commit message · busayo-OD

p2p: add serde impls for FilterHash and FilterHeader

p2p: update lock files for serde dependency

65/100 · AdequateMessage clarity
✓ Specific, 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 adds optional serialization/deserialization support (via the serde library) for two data types, FilterHash and FilterHeader, used in Bitcoin peer-to-peer compact block filters. It is a routine feature addition, not a security fix or vulnerability patch. There is no indication of a security issue in the code changes themselves.

AI review queuedUpdate api filesby Jamil Lambert, PhD · 2e8bd11d · Mar 10, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

Update api files

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

This commit only updates a generated text file that lists the public API surface of the crate. It adds entries for new serde helper functions that support vectors of amounts and fee rates. There is no source code change, no bug fix, and no security relevance visible in the diff.

AI review queuedAdd serde support for Vec<(Signed)Amount>by Jamil Lambert, PhD · c104a521 · Mar 10, 2026 · 2 filesMessage 78 · AdequateInformational 16Details
Commit message · Jamil Lambert, PhD

Add serde support for Vec<(Signed)Amount>

Expand the serde module to also support Vec<Amount> and
Vec<SignedAmount>.

Add tests of the Vec serialization and
deserialization.

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

This commit adds new Rust code that lets programs serialize and deserialize lists (vectors) of Bitcoin amounts when using the serde data-format library. It is a feature addition with matching tests. There is no indication it fixes a security bug or introduces a vulnerability.

AI review queuedAdd serde support for Vec<FeeRate>by Jamil Lambert, PhD · 1afe0abe · Mar 10, 2026 · 2 filesMessage 78 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Add serde support for Vec<FeeRate>

Serde support for Vec<FeeRate> is needed in corepc to update the bitcoin
dependence to 0.33.0.

Expand the serde support for FeeRate to also support Vec<FeeRate>.

Add tests of Vec<FeeRate> serialization and deserialization.

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

This commit adds new serialization/deserialization helpers so that a list of Bitcoin fee-rate values can be converted to and from JSON (or other serde formats). It is a straightforward feature addition with matching unit tests and contains no security fix or vulnerability.

AI review queuedconsensus_encoding: whitelist timeout mutantsby Nick Johnson · 8ab8c465 · Mar 10, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nick Johnson

consensus_encoding: whitelist timeout mutants

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 updates a test-tool configuration file. It tells an automated mutation-testing tool (cargo-mutants) to skip testing certain code patterns because they would cause the test suite to loop forever. It does not change any actual library code, fix a bug, or alter how the software behaves in production.

AI review queuedprimitives: Move TxMerkleNodeDecoder/Error to merkle_treeby Mitchell Bagot · 469a9cc7 · Mar 10, 2026 · 4 filesMessage 73 · AdequateInformational 20Details
Commit message · Mitchell Bagot

primitives: Move TxMerkleNodeDecoder/Error to merkle_tree

In primitives the TxMerkleNode and its encoder are exported from the
merkle_tree module. The decoder is exported from the transaction
module.

Move the TxMerkleNodeDecoder and TxMerkleNodeDecoderError re-exports
to the merkle_tree module from the transaction module.

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

This commit is a straightforward code organization change. It moves where two helper types (TxMerkleNodeDecoder and TxMerkleNodeDecoderError) are publicly exported so they sit alongside related types in the merkle_tree module instead of the transaction module. There is no change to how data is decoded, no bug fix, and no security impact.

AI review queuedprimitives: Use ArrayRefEncoderby Tobin C. Harding · 736adeb9 · Mar 9, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Tobin C. Harding

primitives: Use ArrayRefEncoder

No need to copy the hash type when encoding the `TxMerkleNode` or
the `WitnessMerkleNode`.

Use `ArrayRefEncoder` as we do for the other hash types. Props to
claude for noticing this while chugging through some other changes
for me. I did the changes manually though.

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

This is a small internal code cleanup in the rust-bitcoin library. It changes how two hash-like types (transaction merkle node and witness merkle node) are encoded so that they reference existing data instead of making a copy. There is no security issue here—it's a performance/maintainability improvement that makes the code consistent with how other hash types are already encoded.

AI review queuedconsensus_encoding: add common trait implementationsby Nick Johnson · a7519267 · Mar 9, 2026 · 4 filesMessage 85 · StrongInformational 19Details
Commit message · Nick Johnson

consensus_encoding: add common trait implementations

Following API guidelines C-COMMON-TRAITS, adding Debug and Clone
implementations where we can to encoders and decoders.

A lot of the common traits, including PartialEq, Hash, Ord, Display,
Default, and Copy don't have semantic value for the stateful encoders
and decoders. For example, comparing two encoders with PartialEq would
be comparing a buffer and a cursor, not a logical value.

The composite decoders do not implement Clone because it would require a
Clone bound on the intermediate A::Output types, which seems too
constraining.

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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit adds standard Rust helper traits (Debug for printing, Clone for copying) to the library's byte encoders and decoders. It also adds a few new unit tests. There is no security fix or vulnerability here; it is a routine API-quality improvement.

AI review queuedapi: update consensus_encoding traitsby Nick Johnson · 798195df · Mar 9, 2026 · 3 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nick Johnson

api: update consensus_encoding traits

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

This commit only updates generated API text files that list which Rust traits (like Clone and Debug) are implemented by various types in the bitcoin_consensus_encoding crate. No actual source code, logic, or behavior changed. It is a documentation/maintenance update for the public API snapshot, not a security fix.

AI review queuedImprove From<Infallible> impls to the hex_codec errorsby Tobin C. Harding · 5508596d · Mar 9, 2026 · 3 filesMessage 73 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Improve From<Infallible> impls to the hex_codec errors

Policy is to implement `From<Infallible>` for all error types.

Add missing impls, move the existing one to the 'right' place (right
by codebase convention), and import `Infallible`.

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 is a routine code-quality change in a Rust Bitcoin library. It adds and reorganizes implementations of `From<Infallible>` for certain hex-decoding error types. `Infallible` is a Rust type that can never actually be produced, so these conversions are only useful for making the type system happy and have no security impact.

AI review queuedprimitives: Return reference to inner error in sourceby Tobin C. Harding · 73d30231 · Mar 9, 2026 · 2 filesMessage 73 · AdequateInformational 17Details
Commit message · Tobin C. Harding

primitives: Return reference to inner error in source

Each call to `source` for a stack of nested errors adds a layer. To
tie this all together `source` should return the layer below it i.e.,
the inner error not call through to `source` itself.

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

This commit fixes a small bug in how Rust error chains are reported for two Bitcoin parsing error types. Previously, when asking 'what caused this error?', the code accidentally skipped past the immediate cause and returned the next level up. Now it correctly returns the immediate inner error. This is a correctness fix for error reporting and does not directly create a security vulnerability or allow attacks.

AI review queuedconsensus_encoding: Add tests for CompactSizeDecoder limit handlingby Mitchell Bagot · c7592569 · Mar 7, 2026 · 1 fileMessage 83 · StrongInformational 14Details
Commit message · Mitchell Bagot

consensus_encoding: Add tests for CompactSizeDecoder limit handling

The CompactSizeDecoder can enforce a limit on the valid values to
decode through the new or new_with_limit constructors. At present,
there are no tests to validate this functionality at the boundary
values.

Introduce tests to check limit handling at the boundaries for both
the new and new_with_limit constructors.

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
defensive validationparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 14/100

This commit only adds new unit tests for an existing feature. It does not change any production code, fix a bug, or alter behavior. The tests verify that a decoder correctly accepts values at or below its configured limit and rejects values above it. There is no security issue here.

AI review queuedDo not call into_iterby Tobin C. Harding · fb006eb4 · Mar 3, 2026 · 1 fileMessage 51 · ThinInformational 15Details
Commit message · Tobin C. Harding

Do not call into_iter

Found by clippy and the new nightly toolchain update in (#5743).

No need to explicitly call `into_iter`.

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

This is a minor code cleanup commit. It removes unnecessary `.into_iter()` calls in three places where Rust will automatically handle iteration. The behavior of the code is unchanged, and there is no security issue.

AI review queuedconsensus_encoding: move decoders inline tests to integrationby Nick Johnson · 976a2348 · Feb 26, 2026 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · Nick Johnson

consensus_encoding: move decoders inline tests to integration

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply moves existing unit tests from inside the source file to a separate integration test file. No production code behavior was changed, so there is no security impact.

AI review queuedconsensus_encoding: move decode inline tests to integrationby Nick Johnson · 9d1810d3 · Feb 26, 2026 · 2 filesMessage 83 · StrongInformational 15Details
Commit message · Nick Johnson

consensus_encoding: move decode inline tests to integration

Prefer integration test over inline since they hit the exposed API. A test
can live in integration as long as every name it touches is reachable
through lib.rs.

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

This commit simply moves existing unit tests from inside the source file to a separate integration test file. No production code behavior was changed, so there is no security risk or fix.

AI review queuedconsensus_encoding: beef up module docsby Nick Johnson · 3e765dba · Feb 24, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Nick Johnson

consensus_encoding: beef up module docs

More conventional C-CRATE-DOC and C-EXAMPLE. The crate doc is essentially
a stripped down version of the original ADR doc. C-EXAMPLE calls for an
example on every public item within reason. It would be very repetative
to apply examples on every item in this crate, a single encoder and
decoder example can probably be used by all items.

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 only adds documentation and code examples to a Rust Bitcoin encoding/decoding library. It does not change any actual program logic, fix bugs, or alter behavior. There is no security issue here.

AI review queuedRemove alloc requirement for HexPrimitiveby Mitchell Bagot · 032c5db4 · Feb 24, 2026 · 3 filesMessage 80 · StrongInformational 18Details
Commit message · Mitchell Bagot

Remove alloc requirement for HexPrimitive

The Display/Debug/UpperHex/LowerHex implementations on HexPrimitive
all relied on alloc due to the implementation of hex_write_with_case.
This locks LowerHex and UpperHex on Header behind alloc, and led to
an unnecessary custom implementation of Display.

Change hex_write_with_case to remove alloc requirement, and remove
corresponding feature gates. Move hex_write_with_case to inherent
function on HexPrimitive, and rename to fmt_hex. Replace Display impl
on Header with call through to HexPrimitive. Remove feature gates on
Header Upper/LowerHex.

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

This is a routine code cleanup in the rust-bitcoin library. It removes the need for the 'alloc' feature when formatting certain Bitcoin data types as hex, making the hex formatting work in more constrained environments. There is no indication this fixes a security vulnerability.

AI review queuedAdjust from_str in HexPrimitive to be no-allocby Mitchell Bagot · 8b4b80b3 · Feb 24, 2026 · 4 filesMessage 80 · StrongInformational 17Details
Commit message · Mitchell Bagot

Adjust from_str in HexPrimitive to be no-alloc

The from_str implementation for parsing types from hex strings currently
relies on alloc due to the use of hex::decode_to_vec. This locks Header
FromStr decoding behind alloc.

Implement from_str without alloc, and adjust feature gates on
HeaderDecoder to match new relaxed requirements.

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

This commit is a routine refactoring of how hex strings are parsed into Bitcoin data structures in the rust-bitcoin library. It replaces an allocation-based hex decoder with a streaming, no-allocation decoder so the code can run in environments without a heap allocator. There is no direct security bug being fixed; it is a feature-gate and performance/capability cleanup.

AI review queuedconsensus_encoding: add track_caller to panic-able sitesby Nick Johnson · 0276325e · Feb 23, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Nick Johnson

consensus_encoding: add track_caller to panic-able sites

Defensively added to the Decoder trait itself since the performance
impact is negligible.

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

This commit adds Rust's #[track_caller] attribute to two methods in a decoding trait. This is a diagnostic improvement: if the code ever panics, the error message will point to the caller's location instead of deep inside the library. It does not change what the code does, what data it accepts, or whether it panics. There is no security fix here.

AI review queuedRe-release without rc suffixby Tobin C. Harding · 418685a9 · Feb 23, 2026 · 20 filesMessage 90 · StrongInformational 20Details
Commit message · Tobin C. Harding

Re-release without rc suffix

Turns out that the `-rc.0` suffix causes way more problems than it
solves because of how `cargo` resolves the version numbers and what we
intended on using the RC releases for.

In brief

- We wanted to be able to do breaking changes if required
- We wanted to signal that these releases were almost there (TM)
- We wanted to be able to do downstream testing including releasing
downstream crates with the RC releases as part of their public API.

In hindsite we messed up and should have just kept iterating as normal
until we were ready.

Re-release the whole stack without any rc suffix's. However keep
`bitcoin 0.33.0-beta` because we want 0.32.0 to be the latest stable
release and its important that it shows as such on docs.rs

Also, for pre-1.0 crates that had an rc release just jump to the next
version i.e., `io 0.4.0-rc.0` goes to `io 0.5.0`. Just for good
measure.


crate | latest stable | latest RC | with this applied
-----------------------------------------------------------
consensus_encoding 0.0.0 1.0.0-rc.3 0.1.0
units 0.2.0 1.0.0-rc.4 0.3.0
primitives 0.101.0 1.0.0-rc.2 0.102.0
hashes 0.19.0 - 0.20.0
io 0.3.0 0.4.0-rc.0 0.5.0
base58ck 0.3.0 - 0.4.0


bitcoin - 0.33.0-beta.0 to be yanked. Release as 0.33.0-beta

p2p - updated deps, unrelased so no other changes.
internals - not touched (currently 0.5.0)
chacha20_poly1305 - not touched

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
second-pass: unusually broad change
AI analysis · Informational 20/100

This commit is a routine release-management change for the rust-bitcoin project. It re-releases several crates without the '-rc' (release candidate) suffix in their version numbers and updates internal dependency version requirements accordingly. There are no code logic changes, bug fixes, or security patches in the diff—only version numbers, lock files, changelogs, and README text.