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 36 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 queuedAdd *_with_max difficulty functions to Targetby Mitchell Bagot · 2f842a42 · Jan 18, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · Mitchell Bagot

Add *_with_max difficulty functions to Target

In order to allow for Target to eventually be moved out from bitcoin,
it is necessary to decouple its dependency on Params. Since it is
necessary to maintain the difficulty calculations, a Params-less
variation is introduced that the original version can call through to.

Add difficulty_with_max and difficulty_float_with_max to Target.

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

This commit is a routine code refactoring in the rust-bitcoin library. It splits the existing difficulty calculation functions into two parts: new lower-level functions that take a maximum target directly, and the original functions that now simply call these new functions with the network's maximum target from the Params object. There is no change to the actual math or behavior, and no security issue is present.

AI review queued2026-01-18 automated rustfmt nightlyby Fmt Bot · 4d2fee84 · Jan 18, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-01-18 automated rustfmt nightly

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

This commit is purely a code-formatting cleanup performed by an automated rustfmt nightly run. It reorders imports, collapses or expands brace blocks, removes blank lines, and adjusts line wrapping in test code. No program logic, APIs, or security behavior was changed.

AI review queuedprimitives: test individual output value > MAX_MONEYby jrakibi · 75682547 · Jan 17, 2026 · 1 fileMessage 60 · AdequateInformational 12Details
Commit message · jrakibi

primitives: test individual output value > MAX_MONEY

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

This commit only adds a new unit test. It does not change any production code. The test checks that the library rejects Bitcoin transactions containing an output worth more than the maximum allowed money (MAX_MONEY + 1 satoshi) when decoding transaction bytes. It is a defensive test borrowed from Bitcoin Core's test data, confirming an existing safety check works.

AI review queuedFix typos highlighted in closed LLM PRsby Jamil Lambert, PhD · 8ff6130e · Jan 14, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Jamil Lambert, PhD

Fix typos highlighted in closed LLM PRs

Simple spelling mistakes etc. only.

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

This commit fixes only spelling mistakes in documentation and a test comment. There are no code behavior changes, no security fixes, and no functional changes to the library.

AI review queuedFix incorrect comments in unitsby Jamil Lambert, PhD · 4ff621d4 · Jan 14, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Fix incorrect comments in units

Correct incorrect calculation of U16::MAX * 512.

Correct copy paste error that reverenced wrong fn name.

Originally highlighted in an LLM PR that was closed without merging.

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 fixes two mistakes in code comments. One comment incorrectly named a previously called function, and another comment had a wrong arithmetic result for the maximum time value. No actual code behavior changes, so there is no security impact.

AI review queuedFix unreachable error bug during iteration of funding utxosby Shing Him Ng · a5bd5024 · Jan 7, 2026 · 1 fileMessage 50 · ThinLow 45Details
Commit message · Shing Him Ng

Fix unreachable error bug during iteration of funding utxos

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 45/100

This commit fixes a bug where a specific PSBT error—'PsbtUtxoOutOfbounds'—was not handled during transaction extraction, causing the program to panic (crash) instead of returning a proper error. The fix makes the code treat this error the same as a missing UTXO, returning a controlled error message instead of hitting an 'unreachable' panic path. It is a robustness fix that prevents crashes when processing malformed or inconsistent PSBT data.

AI review queuedRun the formatterby Jamil Lambert, PhD · d4e6ea90 · Jan 5, 2026 · 9 filesMessage 28 · OpaqueInformational 15Details
Commit message · Jamil Lambert, PhD

Run the formatter

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

This commit is purely a code-formatting run. It rewraps long lines, reorders imports, removes blank lines, and adjusts whitespace to match the project's style rules. No logic, behavior, or security checks were changed.

AI review queuedAdd hex codec traits for Transactionby Mitchell Bagot · 7c2ddb17 · Jan 2, 2026 · 4 filesMessage 68 · AdequateInformational 18Details
Commit message · Mitchell Bagot

Add hex codec traits for Transaction

Currently, the Transaction type can be easily encoded into bytes using
consensus_encoding, but there exists no way to encode it to hex without
using the bitcoin crate's serialize_hex or a manual implementation.
Neither such solution is elegant or discoverable.
In implementing traits to hex, FromStr should also be introduced to
decode from a hex string.

Implement FromStr, Display, LowerHex, UpperHex and DisplayHex for
Transactions.

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

This commit adds convenience features to the rust-bitcoin library so that Bitcoin transactions can be easily converted to and from hexadecimal strings. It does not fix a bug, change security behavior, or introduce any obvious vulnerability. It is a routine API enhancement.

AI review queuedprimitives: reject transactions with invalid coinbase scriptSig lengthby jrakibi · c621401a · Jan 1, 2026 · 2 filesMessage 65 · AdequateModerate 52Details
Commit message · jrakibi

primitives: reject transactions with invalid coinbase scriptSig length

Coinbase input scriptSig must be between 2 and 100 bytes in length.
Add this validation rule to transaction decoder

65/100 · AdequateMessage clarity
✓ Specific, 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 · Moderate 52/100

This commit adds a missing validation rule to the library's Bitcoin transaction decoder: a coinbase transaction (the special first transaction in a block that creates new coins) must have an input script between 2 and 100 bytes long. Before this change, the library would accept shorter or longer coinbase scripts, which violates Bitcoin consensus rules and could let malformed transactions slip through. The fix rejects them with clear errors and includes tests for the boundary cases.

AI review queuedUpdate the API filesby Tobin C. Harding · 7cef310d · Dec 30, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

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 an automatically-generated API listing file. It records that a new test-helper trait implementation (for generating random 'relative::LockTime' values) is now part of the crate's public API surface. There is no code change, no bug fix, and no security-sensitive behavior introduced.

AI review queuedprimitives: prevent null prevout in non-coinbase transactionsby jrakibi · c71db422 · Dec 28, 2025 · 1 fileMessage 73 · AdequateModerate 60Details
Commit message · jrakibi

primitives: prevent null prevout in non-coinbase transactions

Non-coinbase transactions must not contain a null prevout (coinbase prevout)
Add this validation to the transaction decoder to reject txs
that violate this rule.

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 · Moderate 60/100

This commit adds a safety check in the Rust Bitcoin library's transaction decoder. It ensures that any transaction with more than one input cannot contain a 'coinbase-style' empty previous transaction reference. Such a reference is only allowed in the special coinbase transaction that creates new coins. Without this check, a malformed or malicious transaction could slip through and potentially cause incorrect behavior in software using this library to parse Bitcoin transactions.

AI review queuedFix decoder bug when ending before decoding prefixby Shing Him Ng · 5d4f9cff · Dec 26, 2025 · 1 fileMessage 73 · AdequateModerate 50Details
Commit message · Shing Him Ng

Fix decoder bug when ending before decoding prefix

Before this fix, calling `ByteVecDecoder.end()` on a decoder that hadn't
finished reading in the full prefix would result in a valid result of an
empty vec. This should instead result in an error, since the decoder
shouldn't be able to decode something with an incomplete prefix.

73/100 · AdequateMessage clarity
✓ Specific, 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 · Moderate 50/100

This commit fixes a bug in a Bitcoin data decoder. Previously, if you stopped decoding early—before the full length prefix was read—the decoder would incorrectly report success with an empty result instead of reporting an error. The fix makes the decoder correctly return an 'unexpected end of data' error in those cases. This could matter for anyone parsing Bitcoin protocol data from partial or truncated inputs.

AI review queuedMove internals::compact_size encoding into CompactSizeEncoderby Mitchell Bagot · 46097693 · Dec 22, 2025 · 15 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move internals::compact_size encoding into CompactSizeEncoder

Currently, the CompactSizeEncoder calls into the internals::compact_size
module to perform the actual encoding process. This creates a strange
API where there are two ways to do the same thing, one of which differs
from how other encoders work.

Move encode and encoded_size from internals::compact_size to the
CompactSizeEncoder in consensus_encoding. Replace usage of
compact_size::encode with pub(crate) function in primitives and
direct usage of CompactSizeEncoder in bitcoin.

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

This commit is a routine internal code cleanup. It moves the logic for encoding Bitcoin 'compact size' numbers from one internal helper module into a dedicated encoder type, then updates call sites to use the new location. There is no security fix or behavior change intended.

AI review queued2025-12-21 automated rustfmt nightlyby Fmt Bot · 1da9343f · Dec 21, 2025 · 8 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2025-12-21 automated rustfmt nightly

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

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, line breaks, and the order of import statements. There are no functional changes, no bug fixes, and no security-related alterations.

AI review queuedMove `TxIdentifier` into `bip152`by rustaceanrob · b7f035be · Dec 17, 2025 · 2 filesMessage 58 · ThinInformational 18Details
Commit message · rustaceanrob

Move `TxIdentifier` into `bip152`

This trait was used in `bitcoin/blockdata/transaction` only to be used
in `p2p`. Move it to `p2p` and drop it in `bitcoin`. I opted to include
it directly in BIP-152, unless another context arises where these IDs
are interchangable.

Credit @mpbagot for the find

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

This commit is a simple code reorganization: a small trait called TxIdentifier that was defined in the main bitcoin crate is moved into the p2p crate's BIP-152 module because that was its only real user. There is no security fix, behavior change, or vulnerability being patched. It is purely a refactoring/cleanup change.

AI review queuedUse usize for CompactSizeDecoder and add new_with_limitby Mitchell Bagot · 4f80f6d0 · Dec 16, 2025 · 8 filesMessage 73 · AdequateLow 33Details
Commit message · Mitchell Bagot

Use usize for CompactSizeDecoder and add new_with_limit

Following the change to CompactSizeEncoder::new to take a usize, the
return types and ranges of the CompactSizeEncoder and CompactSizeDecoder
now differ. Since a device's memory addressing is limited to usize,
returning values beyond that size is largely useless. Converting the
CompactSizeDecoder to return a usize also allows the
cast_to_usize_if_valid function to be merged into the decoder itself.

Convert the CompactSizeDecoder to return a usize. Remove
cast_to_usize_if_valid and introduce its functionality into
CompactSizeDecoder.

73/100 · AdequateMessage clarity
✓ Specific, 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 · Low 33/100

This commit tightens how the library decodes Bitcoin 'compact size' length fields. Previously the decoder could return a 64-bit value, which callers then had to convert to a machine-usable size. Now the decoder itself returns a usize and enforces a configurable upper limit. This is a defensive hardening change: it reduces the chance that a maliciously large length value causes memory problems or integer-conversion bugs later on. It is not a fix for a known active exploit.

AI review queuedbip158: Remove doc_auto_cfgby Tobin C. Harding · 829c94aa · Dec 16, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

bip158: Remove doc_auto_cfg

Quick before someone has a seizure.

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 removes a documentation-only Rust compiler feature flag (`doc_auto_cfg`) from the BIP-158 crate. It does not change any executable code, runtime behavior, or security-sensitive logic. The change only affects how documentation is generated on docs.rs and appears to be a cleanup because the feature was unstable or causing issues.

AI review queuedDepend on primitives instead of bitcoin where type definitions overlapby yancy · f81e8d27 · Dec 15, 2025 · 6 filesMessage 73 · AdequateInformational 18Details
Commit message · yancy

Depend on primitives instead of bitcoin where type definitions overlap

Consolidate dependency tree for downstream crates that depend on
`bitcoin-p2p-messages` and `bitcoin-primitives` by reducing overlapping
dependencies. For example, consider crate A which depends on
`bitcoin-primitives` and `bitcoin-p2p-messages`. For types defined by
both `bitcoin-primitives` and `bitcoin`, Crate A may still need to
depend on `bitcoin` if a type of `bitcoin-p2p-messages` depends on
`bitcoin` instead of `bitcoin-primitives`.

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 change is a routine internal dependency cleanup. The developers moved some shared type definitions (like block and transaction identifiers) from a large crate called `bitcoin` into a smaller, more focused crate called `bitcoin-primitives`. This reduces duplicate dependencies for downstream projects but does not change what the code does or fix any security problem.

AI review queuedFix push_slice() testsby Nadav Ivgi · 0b9094c6 · Dec 14, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nadav Ivgi

Fix push_slice() tests

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

This commit only updates test code. It removes an 'ignore' marker from a test and corrects the expected byte output for pushing a single zero byte onto a Bitcoin script. There is no change to production code and no security issue.

AI review queuedExtend test coverage for BlockTimeby Mitchell Bagot · 781586d2 · Dec 14, 2025 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Extend test coverage for BlockTime

The encoding/decoding and serde functionality of BlockTime is not
covered in existing tests.

Add tests to cover BlockTimeEncoder, BlockTimeDecoder and the
Serialize + Deserialize traits on BlockTime.

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 only adds new automated tests for an existing data type called BlockTime. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

AI review queuedp2p: Remove `OutPointExt` from `p2p` testsby rustaceanrob · 54fd0c72 · Dec 13, 2025 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · rustaceanrob

p2p: Remove `OutPointExt` from `p2p` tests

Remove a pointless dependency on `bitcoin` WRT #5331

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

This is a tiny test-only cleanup commit. It removes an unused trait import and replaces a helper constructor with direct struct field assignment in a unit test. There is no security relevance.

AI review queuedprimitives: Remove arrayvec dependencyby Mitchell Bagot · 9a11819a · Dec 13, 2025 · 4 filesMessage 70 · AdequateInformational 15Details
Commit message · Mitchell Bagot

primitives: Remove arrayvec dependency

The primitives crate only uses the arrayvec crate to provide Display
trait for Header. In order to minimise the use of external
dependencies, it should be removed.

Convert Header Display impl to use fmt_hex_exact! and remove the
arrayvec dependency from primitives.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit removes a third-party dependency called `arrayvec` from the `bitcoin-primitives` crate and rewrites how a Bitcoin block header is printed as text. The old code built the text in a small fixed-size buffer from `arrayvec`; the new code streams the bytes directly through an internal formatting helper. There is no security fix here—this is a routine dependency-reduction refactor.

AI review queuedImplement Decodable for Witness using encoding crateby Tobin C. Harding · f9a6b37e · Dec 13, 2025 · 7 filesMessage 85 · StrongLow 34Details
Commit message · Tobin C. Harding

Implement Decodable for Witness using encoding crate

Use the new `consensus_encoding` crate (by way of the `io` crate
decoding function) to implement `consensus_decode` for `Witness`.

This is ugly a bit ugly because we remove equality derives from
`ParseError` so that we can jam the witness decoding error into it.
Cleanly it should not go there but in order to keep
`encode::deserialize_partial` working we have to be able to return
a `ParseError` and we have to be able to include the witness decoding
error if there was one.

Each subsequent time we try to do this in other decoding impls we will
add a new error variant each time also. This encoding code is on its
way out and will hopefully be deprecated soon so I believe this is ok.

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

This commit replaces the custom code that reads Bitcoin transaction witness data with a shared decoding library. The change is described by the author as a temporary, slightly messy refactor to keep an older decoding helper working while a newer encoding crate takes over. There is no claim in the commit that this fixes a security bug, and the diff itself is mostly code removal and plumbing a new error variant. It could affect how malformed witness data is rejected, but no vulnerability is disclosed or demonstrated.

AI review queuedPut feature gate below test attributeby Tobin C. Harding · a7aa12be · Dec 11, 2025 · 5 filesMessage 78 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Put feature gate below test attribute

For the stabilising crates we would like test code to be treated as a
first class citizen. In my book that means clean AF.

Audit all three crates and put the feature gate attributes below the
`#[test]` attribute, based on two things:

- Uniformity (we could arbitrarily pick either)
- Puts the more important thing closer to the code (subjective)

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

This commit only reorders two Rust attribute lines on test functions so that #[test] appears above #[cfg(...)]. It is a cosmetic/style change with no effect on what code runs or how it behaves. There is no security relevance.

AI review queuedbitcoin: Update changelogby Tobin C. Harding · 2714cded · Dec 11, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Tobin C. Harding

bitcoin: Update changelog

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 edits the project's changelog file. It documents an upcoming beta release and lists previously merged changes, but it does not modify any source code, build scripts, tests, or configuration. There is no security-relevant code change to review.