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 28 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 apiby Nick Johnson · c9cdde0b · Feb 21, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nick Johnson

Update api

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

This commit updates a generated API snapshot file to reflect a minor relaxation of trait bounds on an error type. It is a documentation/tracking file change, not a code change, and has no security relevance.

AI review queuedconsensus_encoding: remove redundant trait boundsby Nick Johnson · 3ea57579 · Feb 20, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Nick Johnson

consensus_encoding: remove redundant trait bounds

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

This is a minor code cleanup in a Rust Bitcoin library. It removes unnecessary requirements (trait bounds) from an error-handling implementation. The change does not affect security, runtime behavior, or how the library processes Bitcoin data.

AI review queuedUpdate the API filesby jrakibi · d65b496d · Feb 19, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · jrakibi

Update the 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 (text listings of public types and methods). It does not change any source code, behavior, or fix any bug. The added lines reflect new methods like non_secure_erase and Drop that already exist in the actual library code; the removed line shows Hkdf no longer implements Copy. These are documentation/snapshot updates, not a security patch.

AI review queuedp2p: implement decoding for Addressby yancy · ca7e9259 · Feb 19, 2026 · 1 fileMessage 86 · StrongInformational 16Details
Commit message · yancy

p2p: implement decoding for Address

Endian byte order for both IPv4 and the port number are interpreted as
big endian per the Addr section of:
https://developer.bitcoin.org/reference/p2p_networking.html

In the test cases, `deserialize` is swapped for
`encoding::decode_from_slice` since the addition of push bytes decoding
is planned to replace the existing `deserialize` implementation.

86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 16/100

This commit adds a new way to decode Bitcoin peer-to-peer network addresses in the rust-bitcoin library. It is a feature/refactoring change that introduces a new decoder implementation and swaps test cases to use it. There is no indication in the commit that it fixes a security bug, vulnerability, or crash.

AI review queuedconsensus: Add CompactSize range check to deserializationby Erick Cestari · 1dd1d92f · Feb 18, 2026 · 4 filesMessage 83 · StrongModerate 61Details
Commit message · Erick Cestari

consensus: Add CompactSize range check to deserialization

Reject CompactSize values exceeding MAX_COMPACT_SIZE (0x02000000) during
deserialization, matching Bitcoin Core's serialize.h limit.

Extract read_compact_size logic into a private free function to allow
tests to bypass the range check when validating non-minimal encoding.

Add test for the new SizeTooLargeCompactSize error at the boundary.

Update bip152 error test to expect failure at deserialization rather
than at index computation, since the range check now triggers earlier.

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

This commit adds a safety limit when reading Bitcoin's 'CompactSize' numbers from serialized data. Before, a malformed message could claim an absurdly large number of elements (for example, billions of items in a list), which could be used to exhaust memory or trigger a panic. Now values above Bitcoin Core's documented maximum are rejected early during parsing. The change also refactors the parsing code so tests can still check non-minimal encoding without the new limit.

AI review queuedhashes: simplify trait boundsby Conger Rassen · c423b93a · Feb 18, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Conger Rassen

hashes: simplify trait bounds

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 is a tiny code cleanup change in the rust-bitcoin hashes library. It replaces a more verbose way of referring to a constant (<H as HashEngine>::BLOCK_SIZE) with a simpler equivalent (H::BLOCK_SIZE). The behavior of the program is unchanged, and there is no security relevance.

AI review queuedunits: Add fmt traits for simple wrapper typesby Mitchell Bagot · 9c166f5e · Feb 17, 2026 · 11 filesMessage 60 · AdequateInformational 19Details
Commit message · Mitchell Bagot

units: Add fmt traits for simple wrapper types

Add Display, LowerHex, UpperHex, Octal and Binary implementations for
all integer wrapper types except FeeRate.

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

This commit adds new ways to print or display several simple numeric wrapper types in the rust-bitcoin library, such as block heights, amounts, and timestamps. It does not change any security-sensitive logic, parsing, arithmetic, or network behavior. It is a routine API enhancement with no apparent security relevance.

AI review queuedupdate renamed clippy lintsby Conger Rassen · be83540a · Feb 17, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Conger Rassen

update renamed clippy lints

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 simply renames two Clippy lint settings in the project's configuration file to match updated Clippy lint names. It does not change any executable code, behavior, or security properties of the library.

AI review queuedrefactor(fuzz): remove custom fuzz_utils moduleby Erick Cestari · 4b4053c0 · Feb 14, 2026 · 3 filesMessage 90 · StrongInformational 15Details
Commit message · Erick Cestari

refactor(fuzz): remove custom fuzz_utils module

Remove the hand-rolled `consume_random_bytes`, `consume_u64`, and
`consume_u32` helpers and the `bitcoin_fuzz` lib crate.

- Use `<&[u8]>::arbitrary` to split fuzz input into borrowed slices
- Flatten nested match blocks into early returns for readability

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidencesigning or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine code cleanup in the project's fuzz-testing harness. It removes a small set of hand-written helper functions and replaces them with a standard library approach for splitting fuzz input into slices. There is no change to the actual Bitcoin library code that users rely on, and nothing in the commit suggests a security fix.

AI review queuedchacha20poly1305: migrate to workspace lintby Nick Johnson · 639212bb · Feb 13, 2026 · 5 filesMessage 68 · AdequateInformational 15Details
Commit message · Nick Johnson

chacha20poly1305: migrate to workspace lint

Some copy code for initializing poly1305 key was refactored to
semantically equivelent (produces same machine code), but doesn't
trigger the clippy panic docs requirement.

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 is a routine code cleanup in the ChaCha20-Poly1305 cryptography module. It moves linting rules from an individual crate to the shared workspace configuration, updates documentation formatting, and refactors how the Poly1305 key is copied from a keystream slice. The commit explicitly states the refactored code is semantically equivalent and produces the same machine code. There is no security-relevant behavior change.

AI review queuedprimitives: Add hash type name to Debug outputby Mitchell Bagot · b75a2633 · Feb 13, 2026 · 12 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

primitives: Add hash type name to Debug output

The hash types from primitives all debug using hexadecimal. Unlike
typical newtypes, they don't debug with the newtype name, making
the exact hash type unclear without contextual clues.

Introduce newtype name to debug output for hash types in primitives.

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

This commit only changes how hash values look when printed for debugging. It adds the type name (like 'Txid(...)') around the hexadecimal hash string so developers can more easily tell which kind of hash they are looking at. It does not change how hashes are compared, stored, serialized, or used in Bitcoin logic.

AI review queuedhashes: Add hash type name to Debug outputby Mitchell Bagot · 17322bff · Feb 13, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

hashes: Add hash type name to Debug output

For the sake of uniformity with the changes in primitives, change
the Debug format in the hashes implementations for hash wrapper
types.

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

This commit only changes how hash values look when printed in debugging output. Instead of showing just the raw hex string, the debug format now also includes the type name, like 'Txid(bitcoin_hashes::sha256d::Hash(...))'. It does not change any behavior that handles real bitcoin data, secrets, or network messages, and it introduces no security risk.

AI review queuedReplace DecoderNError implementations with macroby Mitchell Bagot · 6bec9c13 · Feb 9, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Replace DecoderNError implementations with macro

As with the EncoderN composite encoders, the DecoderNError types
can be trivially replaced with a macro to significantly reduce the
quantity of repeated boilerplate code for each of them.

Introduce define_decoder_n_error macro to define DecoderNError types
for any N.

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 code cleanup. It replaces several nearly identical error-type definitions with a single Rust macro, reducing duplicated boilerplate. There is no change to how the library behaves, what data it accepts, or how it handles errors.

AI review queueddev: implement standard traits for ChaCha20-Poly1305 data typesby Abeeujah · 0df18257 · Feb 5, 2026 · 3 filesMessage 90 · StrongInformational 17Details
Commit message · Abeeujah

dev: implement standard traits for ChaCha20-Poly1305 data types

Implement a comprehensive suite of common traits (Copy, Clone, Eq, Ord, Hash)
across chacha20_poly1305 cryptographic structures to improve API usability and integration with
standard library collections.

Changes
- Added Copy, Clone, PartialEq, Eq, PartialOrd, Ord, and Hash to:
- Poly1305
- Key
- Nonce
- U32x4
- State
- ChaCha20
- ChaCha20Poly1305
- Added Debug only to non-sensitive internal types (U32x4, State).

Security Note
The Debug trait was intentionally omitted for types holding sensitive data
(Key, Nonce, ChaCha20, etc.) to prevent accidental leakage of secret
keying values or internal cipher states through logging or unwraps.

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

This commit adds common Rust traits like Copy, Clone, Eq, Ord, and Hash to ChaCha20-Poly1305 cryptographic types. It is a routine developer-facing API improvement. The commit deliberately avoids adding Debug to types that hold secret keys or nonces to prevent accidental leakage in logs. There is no direct security vulnerability in the diff itself.

AI review queuedrefactor: remove From<UnexpectedEof> impls for decoder errorsby Abeeujah · 73ee530d · Feb 3, 2026 · 9 filesMessage 93 · StrongInformational 17Details
Commit message · Abeeujah

refactor: remove From<UnexpectedEof> impls for decoder errors

Replace From UnexpectedEOF implementations with .map_err() calls
across various primitive decoder types.

Modified types:
- VersionDecoderError
- BlockHashDecoderError
- TxMerkleNodeDecoderError
- WitnessMerkleNodeDecoderError
- CompactTargetDecoderError

Fixes: #5562

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

This is a code cleanup change in the rust-bitcoin library. It removes automatic error conversions (From trait implementations) for certain decoder errors and replaces them with explicit .map_err() calls. The behavior of the code appears functionally identical—errors are still propagated the same way. There is no indication this fixes a security vulnerability.

AI review queuedEnforce lifetime in encoder_newtypeby Mitchell Bagot · d49f587c · Feb 2, 2026 · 23 filesMessage 58 · ThinInformational 17Details
Commit message · Mitchell Bagot

Enforce lifetime in encoder_newtype

Since we want all encoder types to include a lifetime, encoder_newtype
must be changed to introduce a lifetime to be passed to inner encoder
types.

Require lifetime specifier for encoder_newtype macro and introduce
lifetime for all affected call sites.

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

This commit is a Rust type-system cleanup. It changes a macro that creates encoder wrapper types so that every wrapper must carry a lifetime parameter, and updates all uses across the codebase. There is no change to runtime behavior, wire format, or cryptographic logic. It prevents future misuse of the macro but does not fix a known exploitable bug.

AI review queuedMove Transaction encoder inner type to aliasby Mitchell Bagot · 46d514de · Feb 2, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move Transaction encoder inner type to alias

With the introduction of lifetimes, the inner encoder type for the
Transaction encoder will become sufficiently complex to trigger lints.

Introduce a type alias TransactionEncoderInner.

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

This commit is a minor internal code cleanup in the Rust Bitcoin library. It replaces a long, complex type definition inside a macro with a shorter type alias name. There is no change to how transactions are encoded, no change to public behavior, and no security relevance.

AI review queuedprimitives: Add fmt traits for simple wrapper typesby Mitchell Bagot · 6b534904 · Feb 2, 2026 · 6 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

primitives: Add fmt traits for simple wrapper types

The integer wrapper types have inconsistent display trait
implementations. For 1.0, these should be unified to make working
with numeric types simple for users.

Introduce all fmt traits as passthroughs for CompactTarget and
both Version types.

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 adds extra text formatting abilities (like showing numbers in hexadecimal, binary, or octal) to three simple numeric wrapper types in the rust-bitcoin library: block version, transaction version, and compact target. It is a routine usability improvement with no security relevance.

AI review queuedtest(p2p): Update deserialize for `AddrV2`by rustaceanrob · 1d587674 · Jan 31, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · rustaceanrob

test(p2p): Update deserialize for `AddrV2`

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit only changes test code. It expands existing unit tests for the AddrV2 network address type so that deserialization is checked with both the old `deserialize` helper and a newer `encoding::decode_from_slice` function. No production code was modified, so it cannot directly introduce a runtime security vulnerability.

AI review queuedprimitives: reject transactions with 0 outputsby jrakibi · 15a947be · Jan 25, 2026 · 2 filesMessage 86 · StrongLow 47Details
Commit message · jrakibi

primitives: reject transactions with 0 outputs

Transactions must have at least one output.

This is another syntactic check that doesn't depend on any context,
and the last one on this list https://github.com/rust-bitcoin/rust-bitcoin/issues/5383#issuecomment-3646014920.
We add validation to reject transactions with empty outputs during decoding.

Two existing tests that created transactions with no outputs are ignored
and will be fixed in the next commit.

86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 47/100

This commit adds a rule to reject Bitcoin transactions that have no outputs when they are decoded. In Bitcoin, every valid transaction must send bitcoin somewhere, so a transaction with zero outputs is invalid. The change prevents the library from accepting or processing such malformed transactions, which could otherwise lead to inconsistent behavior compared to Bitcoin Core and other nodes.

AI review queuedprimitives: fix tests that created txs with no outputsby jrakibi · 32fefd70 · Jan 25, 2026 · 2 filesMessage 83 · StrongInformational 15Details
Commit message · jrakibi

primitives: fix tests that created txs with no outputs

Update `decode_zero_inputs` and `block_decode` tests to include a
valid output, as transactions with no outputs are now rejected

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

This commit only updates two internal unit tests so they create transactions that have at least one output. The change is a test-only follow-up after the library started rejecting transactions with no outputs. There is no change to production code, no security fix, and no vulnerability being patched.

AI review queuedp2p: Allow too many argsby Tobin C. Harding · b997f142 · Jan 23, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

p2p: Allow too many args

For now just shoosh the linter.

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

This commit adds a single Rust lint suppression comment to silence a Clippy warning about a function having too many arguments. It does not change any executable code, behavior, or data flow. There is no security relevance.

AI review queuedImprove test coverage for TxMerkleNodeby Jamil Lambert, PhD · 5fb07d04 · Jan 22, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Improve test coverage for TxMerkleNode

Add two tests to increase the test coverage to 100% for
transaction_merkle_node.

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 two new unit tests for the TxMerkleNode type. It does not change any production code, fix a bug, or alter behavior. There is no security relevance.

AI review queuedbip152: Add an `Offset` wrapper typeby rustaceanrob · 940602f0 · Jan 22, 2026 · 2 filesMessage 90 · StrongLow 36Details
Commit message · rustaceanrob

bip152: Add an `Offset` wrapper type

When implementing `encoding` with a list of items it's nice to have
`Encodable` implemented for the item that will go into the
`SliceEncoder` to avoid prep steps. I also think this type should be
revamped.

For one, having struct initialization available for this type allows for
creating completely invalid states that result in panics. This is shown
by a test that literally asserts creating the struct results in a panic
when trying to serialize it later. A simple case that is not currently
tested is when the user passes an unsorted vector in the initialization
and later tries to encode this type. I introduce two constructors here
that make it clear the client should sort the list themselves, or allow
the sort to happen on construction. The encoding functions here were
doing an immense amount of logic, which I think should be pushed out to
a designated method call.

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: broader security terminology
AI analysis · Low 36/100

This commit refactors how Bitcoin compact-block transaction indexes are stored and encoded. It replaces a public Vec<u64> field with a private Vec<Offset> field and adds constructors that require callers to provide sorted indices. The change removes a documented panic during serialization when u64::MAX was used, and moves overflow detection from encoding time to a new indices() accessor. It is a defensive hardening patch rather than a clear-cut vulnerability fix, because the previous panic required a caller to deliberately construct an invalid object and then serialize it.

AI review queuedAdjust error re-export doc inliningby Mitchell Bagot · 9209abdf · Jan 21, 2026 · 3 filesMessage 80 · StrongInformational 15Details
Commit message · Mitchell Bagot

Adjust error re-export doc inlining

Error re-exports in bitcoin and primitives should use #[doc(no_inline)]
to ensure that pure re-export types are rendered as re-exports and not
defined types of the module in docs.

Use #[doc(no_inline)] for BlockHashDecoderError in primitives and
PushBytesError, ParseTransactionError, and ParseOutPointError in
bitcoin.

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 only changes how Rust documentation is generated for certain error types. It switches some re-exports from being shown as if they were defined in the current module to being shown as re-exports from another module. There is no change to actual code behavior, no security fix, and no vulnerability.