RB
← All projectsRust Bitcoin

rust-bitcoin

Rust library for Bitcoin data structures, serialization, consensus encoding, and scripts.

BitcoinCryptographic librariesNormal
Repository coverage

2313 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.

532security candidates511second-pass queue2206AI analyses
130commits · 30 days
248commits · 60 days
1102commits · 180 days
2008commits · 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.

66/100 average clarity
510Strong · 80–100
1085Adequate · 60–79
567Thin · 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 Poelstra23179157290
Mitchell Bagot649193645068
Tobin C. Harding41566410063
jrakibi944994068
Nick Johnson19121190060
Jamil Lambert, PhD11919116061
satsfy (Renato Britto)381527066
Fmt Bot331431045
Trevor Arjeski111111069
Shing Him Ng31731056
Martin Habovstiak30628068
Ismail Daif22622050
Analysis record

Published AI watches

Last scanned 21 minutes ago

Moderate 62 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6954: units: serialize unsigned amounts as u64

This commit fixes a mismatch in how unsigned Bitcoin amounts were serialized versus deserialized when using certain compact binary formats. Previously, an unsigned amount (like 100 satoshis) was written as a signed number, which caused for…

Data integrity bug: serialized values decode to different numeric values in varint binary formatsRange-check failure: Amount::MAX and large values near the cap fail deserialization after round-tripSerde serialize/deserialize hint mismatch for unsigned amount types
295c9d8aby Andrew Poelstra+66−112 files
No security note in commit
Low 25 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6955: key_expression: preserve master-key invariants in Xpub Arbitrary

This change fixes a bug in test-only code that generates random fake Bitcoin extended public keys (xpubs). Previously, when generating a master xpub (depth 0), the code could pick random values for the parent fingerprint and child number, …

BIP32 master-key invariant violation in generated test dataEncode/decode round-trip failure for generated master xpubsFix aligns Xpub::arbitrary with existing Xpriv::arbitrary behavior
4116ecc6by Andrew Poelstra+35−31 file
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6947: build(deps): bump cargo-bins/cargo-binstall from 1.21.0 to 1.21.1

This commit updates the version of a helper tool (cargo-binstall) used only inside GitHub Actions automation. It is a routine dependency bump by Dependabot and does not change any code that ships to users. There is no indication of a secur…

c1be49cbby Andrew Poelstra+2−22 files
No security note in commit
High 70 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6919: Sanitize serde size hints before allocating

This commit fixes a denial-of-service weakness in how the library deserializes lists of Bitcoin data (witnesses, amounts, fee rates) from untrusted input. Before the fix, a few bytes of attacker-controlled data could claim a list would con…

Untrusted serde size hint fed directly into Vec::with_capacityPotential memory exhaustion / OOM kill from small malicious inputDenial-of-service vector in deserialization paths
55ddbc0cby Andrew Poelstra+88−105 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6945: bitcoin: handle OP_CODESEPARATOR in legacy

This commit fixes how the Rust Bitcoin library calculates old-style (legacy) transaction signatures when the spending script contains a special opcode called OP_CODESEPARATOR. Previously the library did not handle this opcode at all, which…

Protocol correctness fix for legacy sighash serializationOP_CODESEPARATOR handling added to match Bitcoin Core consensus behaviorPreviously omitted test vectors restored, indicating prior non-compliance
5b815281by Andrew Poelstra+600−3093 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6948: build(deps): bump taiki-e/install-action from 2.83.2 to 2.85.4

This is a routine update by Dependabot to the version of a third-party GitHub Action used in the project's automated testing workflows. The change only affects internal continuous integration (CI) scripts, not the actual Bitcoin library co…

d1431904by Andrew Poelstra+2−22 files
No security note in commit
Low 33 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6946: Fix integer overflow in `get_array`

This commit fixes a small but real bug in a Rust helper that reads fixed-size chunks from a data slice. The helper was supposed to safely return 'nothing' when asked to read past the end of the data, but it accidentally added two numbers t…

Integer overflow in bounds-checking helperContract violation: method documented to return None on out-of-bounds access could panic insteadDebug-build panic (denial of service) possible
c6e80843by Andrew Poelstra+2−11 file
Vendor flagged security relevance
Moderate 62 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Fix integer overflow in `get_array`

This commit fixes a bug in a Rust helper method called `get_array`, which is meant to safely read a fixed-size chunk from a slice and return nothing if the requested range is out of bounds. The bug was that the code added the caller's offs…

Integer overflow in bounds calculationPotential panic due to violated internal length expectationCaller-controlled arithmetic used for memory access bounds
56fb1287by Martin Habovstiak+2−11 file
Vendor flagged security relevance
High 71 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6915: primitives: Fix `Witness` handling of oversized items

This commit fixes a bug in how the Rust Bitcoin library counts and compares transaction witness data when a witness contains an oversized item. Previously, several functions relied on an iterator that silently skips oversized items, causin…

Inconsistent serialization/iterator behavior for oversized witness itemswtxid collision risk between transactions differing only in oversized witness bytesIncorrect witness equality for oversized single-item stacks
e1ed5884by Andrew Poelstra+106−273 files
Vendor flagged security relevance
Informational 19 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6922: Use `try_fold` instead of `fold` in `Sum` impl

This is a code-quality and performance improvement, not a security fix. It changes how the library adds up lists of Bitcoin amounts so that it stops early once an overflow is detected, rather than continuing to process the rest of the list…

No security-relevant signal in commit message or diffRefactor preserves overflow-checking behavior (short-circuits instead of continuing)New API method `NumOpResult::from_result` is a pure inverse of existing `into_result`
86e4d5daby Andrew Poelstra+60−562 files
No security note in commit
Moderate 52 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6893: units: Reject malformed amount strings

This update fixes a bug in how the library reads Bitcoin amount strings like '1.5 BTC'. Previously, certain malformed inputs such as '.', '._', '1_', '1_.0', and '1._0' were incorrectly accepted and treated as valid amounts (often zero), i…

Input validation bypass in amount parserMalformed strings silently parsed as zero or ordinary amountsUnderscore separator placement not enforced
fcb14622by Andrew Poelstra+88−343 files
Vendor flagged security relevance
Low 48 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6921: units: fix div_by_fee_rate_ceil precision

This commit fixes a rounding bug in how the rust-bitcoin library calculates the minimum transaction weight needed to pay a given fee at a given fee rate. The old code rounded the fee rate up too early, which could produce a weight slightly…

Incorrect fee-weight calculation due to premature integer roundingPotential transaction fee shortfall when using div_by_fee_rate_ceilOverflow protection added for Amount::MAX * 4_000_000 intermediate value
b31212e0by Andrew Poelstra+38−82 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6898: Release tracking PR: `consensus-encoding 1.3.0`

This is a routine release-management commit that bumps the version number of the `bitcoin-consensus-encoding` crate from 1.2.0 to 1.3.0 and updates lock files accordingly. It contains no code changes that fix or introduce a security issue.…

0cfc7908by Andrew Poelstra+37−349 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6909: build(deps): bump actions/labeler from 6.2.0 to 7.0.0

This commit updates a GitHub Actions automation tool (actions/labeler) used to automatically tag pull requests with labels. It is a routine dependency version bump from 6.2.0 to 7.0.0, with no indication of a security fix or vulnerability.…

4ed7c068by Andrew Poelstra+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#6910: build(deps): bump actions/checkout from 7.0.0 to 7.0.1

This commit is a routine update to the GitHub Actions checkout tool used by the project's automated workflows. It only changes version numbers in configuration files and does not alter the actual Bitcoin library code that users run. There …

328c4ae9by Andrew Poelstra+37−3717 files
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6911: build(deps): bump astral-sh/setup-uv from 8.3.2 to 9.0.0

This commit updates a GitHub Actions helper used to install a Python tool called uv, which runs the zizmor security scanner. The change only bumps the pinned version of the helper from 8.3.2 to 9.0.0. The new version's release notes mentio…

No security-relevant signals in commit or upstream release notesDependency bump in CI only, not in library codeNo CVE or advisory referenced
67600795by 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#6912: build(deps): bump github/codeql-action/upload-sarif from 4.37.0 to 4.37.3

This is a routine Dependabot update that changes the pinned version of GitHub's official CodeQL upload-sarif action from 4.37.0 to 4.37.3 in a single CI workflow. The action only uploads static analysis results to GitHub; it does not touch…

b51cec63by Andrew Poelstra+1−11 file
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6913: build(deps): bump dtolnay/rust-toolchain from 6c977a6ca4077a0ceb28ffbe03f59d46e9ac8772 to 02cb101ec7c40f2c49e1d9714d64511d8e1b74de

This is a routine update to a GitHub Actions helper used to install Rust during automated testing. It only changes the pinned version of the dtolnay/rust-toolchain action in workflow files. There is no change to the actual rust-bitcoin lib…

90330d15by Andrew Poelstra+8−84 files
No security note in commit
Informational 20 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6906: consensus_encoding, primitives: expose exact encoding size for block and transaction

This commit adds a way to ask, in advance, exactly how many bytes a Bitcoin block or transaction will take when serialized. It is a feature addition for the library's encoding system, not a fix for a vulnerability. There is no indication i…

No security-relevant signals in commit message or diffFeature addition: expose exact encoded sizeNo mention of vulnerability, CVE, bug bounty, or security report
1a365d53by Andrew Poelstra+129−1068 files
No security note in commit
Informational 15 AI analysisMessage 88 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump dtolnay/rust-toolchain

This is a routine update by Dependabot that changes which version of a popular GitHub Action (dtolnay/rust-toolchain) is used to install Rust in automated CI workflows. The commit only updates pinned commit hashes in workflow files; it doe…

a31e0b0eby dependabot[bot]+8−84 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.

Lower-priorityReplace match statements with matches! macrosby Jamil Lambert, PhD · 46dc828a · Jan 14, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jamil Lambert, PhD

Replace match statements with matches! macros

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a minor code cleanup in test code only. It replaces verbose match statements with the shorter matches! macro in two unit tests. The change does not affect production code, behavior, or security.

Lower-priorityImprove witness commitment validation testby Jamil Lambert, PhD · 64030388 · Jan 14, 2026 · 1 fileMessage 70 · AdequateInformational 12Details
Commit message · Jamil Lambert, PhD

Improve witness commitment validation test

Add check that block.validate() returns InvalidWitnessCommitment

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
defensive validation
AI analysis · Informational 12/100

This commit only adds an extra test case to an existing unit test. It does not change any production code, so it cannot introduce or fix a security vulnerability by itself. The new assertion checks that a block with an invalid witness commitment is rejected by the validation function, which is a normal correctness test rather than a security patch.

Security candidatehashes: remove unused bench filesby jrakibi · 7b41fabe · Jan 14, 2026 · 5 filesMessage 76 · AdequateInformational 15Details
Commit message · jrakibi

hashes: remove unused bench files

These `benches.rs` files were left behind when benchmarks were migrated
to Criterion in #5012. they are not run and duplicate the Criterion benchmarks in
`benches`

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit simply deletes five old benchmark test files that were accidentally left behind after benchmarks were moved to a newer testing framework. It removes unused code and has no effect on the actual Bitcoin hashing library or its users.

Lower-priorityp2p: Implement `encoding` traits for `CFHeaders`by rustaceanrob · a329c2ac · Jan 14, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `CFHeaders`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds standard encoding and decoding support for a Bitcoin peer-to-peer network message called CFHeaders (compact filter headers). It is a routine implementation of serialization traits and does not appear to fix or introduce any security issue.

Lower-priorityp2p: Implement `encoding` traits for `CFCheckpt`by rustaceanrob · 8d298c47 · Jan 14, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `CFCheckpt`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds missing data-encoding (serialization/deserialization) support for a Bitcoin peer-to-peer message type called CFCheckpt. It is a routine feature implementation, not a security fix. There is no indication in the commit or supplied references that this addresses a vulnerability, a bug, or a security-relevant issue.

Lower-priorityp2p: Implement `encoding` traits for `FilterHash/Header`by rustaceanrob · 5f179426 · Jan 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `FilterHash/Header`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds standard encoding and decoding support for two existing hash-like types (FilterHash and FilterHeader) used in Bitcoin peer-to-peer messages. It is a routine feature addition that wires up serialization traits; there is no indication it fixes a vulnerability or introduces unsafe behavior.

Lower-priorityp2p: Implement `encoding` traits for `CFilter`by rustaceanrob · d9cb8871 · Jan 14, 2026 · 1 fileMessage 45 · ThinInformational 12Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `CFilter`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 12/100

This commit adds standard encoding and decoding support for a Bitcoin peer-to-peer message called CFilter. It is a routine feature addition that lets the library serialize and deserialize compact-filter messages. There is no indication in the commit that this fixes a security bug or introduces a vulnerability.

Lower-priorityp2p: Implement `encoding` traits for `GetCFCheckpt`by rustaceanrob · 50dcce3c · Jan 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `GetCFCheckpt`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds standard encoding and decoding support for a Bitcoin peer-to-peer message type called GetCFCheckpt. It is a routine feature addition with no visible security bug or fix.

Lower-priorityp2p: Implement `encoding` traits for `GetCFHeaders`by rustaceanrob · ede1b5da · Jan 14, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `GetCFHeaders`

These could have shared an encoder with the last commit, `GetCFilters`,
but we only gain a few lines back from overlap so I implement the
encoder seperately.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit adds standard encoding and decoding support for a Bitcoin peer-to-peer message called GetCFHeaders. It is a routine feature addition with no visible security bug, missing check, or unsafe code. The change simply lets the library serialize and deserialize this message type in the same way it already handles related messages.

Lower-priorityp2p: Implement `encoding` traits for `GetCFilters`by rustaceanrob · 50e2f9cb · Jan 14, 2026 · 1 fileMessage 50 · ThinInformational 12Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `GetCFilters`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 12/100

This commit adds new Rust code to encode and decode a Bitcoin peer-to-peer message called GetCFilters. It is a routine feature implementation with no visible security bug. The change does not fix a vulnerability, alter existing security behavior, or introduce suspicious logic such as unchecked lengths or unsafe code.

Security candidateFix rustdoc typos and grammar with three LLMsby Jamil Lambert, PhD · 3d80a99f · Jan 14, 2026 · 20 filesMessage 68 · AdequateInformational 15Details
Commit message · Jamil Lambert, PhD

Fix rustdoc typos and grammar with three LLMs

Run GPT-5.2, Claude Sonnet 4.5 and Gemini 3 Pro over the rustdocs of the
entire repo.

Review what they changed and remove any incorrect or unnecessary
changes.

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

This commit is a documentation-only cleanup. It fixes spelling mistakes, grammar, and typos in code comments, README files, and rustdoc strings. No executable code, logic, or security behavior was changed.

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.

Lower-priorityp2p: Implement `encoding` traits for `Alert`by rustaceanrob · 046f7b14 · Jan 14, 2026 · 1 fileMessage 45 · ThinInformational 17Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `Alert`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 17/100

This commit adds standard encoding and decoding traits for the legacy Bitcoin P2P `Alert` message type in the rust-bitcoin library. It is a routine feature implementation that lets `Alert` be serialized and deserialized like other network messages. There is no indication in the commit or supplied references that this fixes a security bug or introduces a vulnerability.

Lower-priorityp2p: Implement `encoding` traits for `Inventory`by rustaceanrob · a014046c · Jan 14, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `Inventory`

Part of the move from `bitcoin::consensus::encode` to `encoding`.

I gave a shot at a not-so-straightforward type to get a grip on the
encoding crate. I believe the right approach here is to use `Encodable2`
but let me know if I am missing something.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit adds a new way to serialize and deserialize the Inventory message type used in Bitcoin peer-to-peer networking. It is a straightforward refactoring that mirrors the existing consensus encoding logic, moving it to a new internal encoding crate. There is no indication of a security bug being fixed or introduced.

Security candidatepow: Fix U256::overflowing_mulby Mitchell Bagot · 0942a57a · Jan 10, 2026 · 1 fileMessage 73 · AdequateModerate 56Details
Commit message · Mitchell Bagot

pow: Fix U256::overflowing_mul

The overflowing_mul function in U256 doesn't compute correct values.
This can be obviously seen by the current single test case that
exists, which checks against an incorrect value and asserts an
incorrect overflow state.

Fix the implementation of overflowing_mul and add tests to check
edge cases.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Moderate 56/100

This commit fixes a bug in a 256-bit unsigned integer multiplication routine used by the Rust Bitcoin library. The old code produced wrong multiplication results and failed to detect when the result exceeded 256 bits. Because this arithmetic is used in Bitcoin's difficulty retargeting calculations, incorrect results could theoretically lead to wrong difficulty estimates, though the practical attack path is limited.

Lower-priorityAdd #[track_caller] to `FutureLeafVersion::from_consensus`by Shing Him Ng · 285c8421 · Jan 9, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Shing Him Ng

Add #[track_caller] to `FutureLeafVersion::from_consensus`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds a Rust compiler hint called #[track_caller] to an internal helper function. It does not change program behavior, fix a bug, or alter any security boundary. It only improves the quality of panic/error location reporting if the code ever panics.

Lower-priorityFilter diff to include only rust files in diff cargo mutants CIby user · be4bfe86 · Jan 8, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · user

Filter diff to include only rust files in diff cargo mutants CI

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This is a minor change to a GitHub Actions CI workflow. It narrows the set of files included in a diff used by an automated mutation-testing tool (cargo-mutants) so that only Rust source files (*.rs) are considered. It does not change any production code, cryptographic logic, network handling, or user-facing behavior.

Lower-priorityp2p: Implement `encoding` traits for `UserAgent`by rustaceanrob · e9e16543 · Jan 8, 2026 · 1 fileMessage 60 · AdequateInformational 18Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `UserAgent`

One step before the `VersionMessage` mammoth.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 18/100

This commit adds new serialization/deserialization code for the Bitcoin P2P `UserAgent` field. It is a routine refactor that introduces a new internal encoding trait implementation alongside the existing one. There is no indication of a security bug in the change itself.

Security candidatehashes: add SHA256 ARM hardware accelerationby jrakibi · 22993503 · Jan 8, 2026 · 1 fileMessage 76 · AdequateInformational 16Details
Commit message · jrakibi

hashes: add SHA256 ARM hardware acceleration

rust-bitcoin/rust-bitcoin#1962 added SIMD SHA256 intrinsics for x86 machines. However, for
ARM machines we're still falling back to software_process_block(),
which is ~4x slower.

This adds support for ARM SHA2 crypto extensions. The code is
inspired by https://github.com/noloader/SHA-Intrinsics/blob/4e754bec921a9f281b69bd681ca0065763aa911c/sha256-arm.c.
variable names are kept the same for easier review and comparison.

I did benchmarks on an AWS EC2 (t4g.small, Neoverse-N1):

for 65kb:
- without ARM: 266.71 µs
- with ARM: 55.956 µs

That's almost ~5x faster for larger blocks.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 16/100

This commit adds a faster way to calculate SHA-256 hashes on modern 64-bit ARM processors (like Apple's M chips, AWS Graviton, and recent smartphones) by using built-in CPU instructions called ARM SHA2 crypto extensions. It mirrors an earlier change that did the same thing for x86 processors. There is no indication in the commit that this fixes a security bug; it is a performance improvement.

Lower-priorityp2p: Implement `encoding` traits for `ProtocolVersion`by rustaceanrob · 5d0ae392 · Jan 7, 2026 · 1 fileMessage 81 · StrongInformational 15Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `ProtocolVersion`

Per #5452 it doesn't look like the `encoding` traits will be macro-ized
anytime soon, so we might as well chip away with the types that comprise
`NetworkMessage`

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit adds new serialization/deserialization code for the `ProtocolVersion` type in the peer-to-peer networking module. It is a routine feature addition that mirrors existing patterns and does not fix any known bug or security issue.

Lower-priorityp2p: Implement `encoding` traits for `ServiceFlags`by rustaceanrob · 21cf74ba · Jan 7, 2026 · 1 fileMessage 73 · AdequateInformational 18Details
Commit message · rustaceanrob

p2p: Implement `encoding` traits for `ServiceFlags`

Another one of the many types required for #5411

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 18/100

This commit adds standard encoding and decoding support for ServiceFlags, a data type used in Bitcoin peer-to-peer messages. It is a routine feature addition with no visible security bug. The change simply lets the library serialize and deserialize ServiceFlags using a new internal encoding framework.

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.

Lower-priorityUse as_parts to encode Block<Unchecked> without cloningby Alkamal01 · f26ddba1 · Jan 6, 2026 · 4 filesMessage 85 · StrongInformational 15Details
Commit message · Alkamal01

Use as_parts to encode Block<Unchecked> without cloning

Add an as_parts method to Block<Unchecked> that returns references to
the header and transactions. Use it in the Encodable impl to avoid
the clone we were doing previously.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI analysis · Informational 15/100

This is a routine performance improvement: it removes an unnecessary data copy when encoding an unchecked Bitcoin block. There is no security issue visible in the change.

Lower-priorityRemove std requirement for bitcoin merkle_tree testsby Mitchell Bagot · 032f4732 · Jan 6, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · Mitchell Bagot

Remove std requirement for bitcoin merkle_tree tests

The std feature in the bitcoin merkle_tree block tests is now only
used for format!() macro calls, and can thus be safely removed.

Remove all std feature gates in bitcoin merkle_tree tests.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only changes test code in the rust-bitcoin project. It removes feature gates so that some merkle tree tests can run without the 'std' (standard library) feature. There is no change to production code, no security fix, and no vulnerability introduced.