CommitWatch RSS
RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Source repository ↗
Repository coverage

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

461security candidates452second-pass queue2076AI analyses
183commits · 30 days
409commits · 60 days
1296commits · 180 days
2064commits · 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.

64/100 average clarity
318Strong · 80–100
1058Adequate · 60–79
557Thin · 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.
Mitchell Bagot643192641068
Tobin C. Harding41366410063
jrakibi944994068
Andrew Poelstra582155077
Nick Johnson18920189059
Jamil Lambert, PhD11418114061
Fmt Bot311431045
Trevor Arjeski111111069
Shing Him Ng31731056
Ismail Daif22622050
satsfy (Renato Britto)17617066
Martin Habovstiak27527069
Analysis record

Published AI watches

Last scanned 55 minutes ago

Informational 20 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6678: units: Add `Weight::to_vb_*` functions, deprecating `to_vbytes_*`

This is a routine API cleanup in a Rust Bitcoin library. It adds new method names (to_vb_floor, to_vb_ceil) for converting transaction 'weight' to 'virtual bytes' and marks the old names (to_vbytes_floor, to_vbytes_ceil) as deprecated. The…

7f614781by Andrew Poelstra+30−86 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6597: Release tracking PR: `crypto 0.3.0`

This commit is a routine release-tracking merge. It only bumps version numbers (bitcoin-crypto to 0.3.0 and bitcoin-primitives to 0.103.1), updates dependency version requirements, refreshes lock files, and adds changelog entries. There ar…

1fddd49eby Andrew Poelstra+34−1210 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update API files

This commit only updates generated API listing files (text snapshots of public functions) to reflect a newly added public function, `to_consensus_u32`, on the `CompactTarget` type. It does not change any source code, logic, or behavior, an…

a75c53c8by Mitchell Bagot+6−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6675: units: Remove unnecessary track_caller

This commit removes two Rust compiler hints (`#[track_caller]`) from helper functions that simply return a value or call a user-provided fallback. These functions never panic, so the hints were unnecessary and had no security effect. The c…

ce894f36by Andrew Poelstra+0−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6644: primitives: Add serde impls for `WitnessVersion`

This commit adds standard serialization/deserialization support for the WitnessVersion type when the optional serde feature is enabled. It is a routine feature addition with no security relevance visible in the code or commit message.

4981faa7by Andrew Poelstra+50−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktime

This commit only changes documentation comments and variable names in the rust-bitcoin library. It rewords references to 'block height' as 'block count' for relative locktime, because a relative locktime measures elapsed blocks since a coi…

6ea4ff92by Andrew Poelstra+20−172 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6670: ci: fix labeller permissions

This is a routine GitHub Actions workflow fix. The change gives the automated PR labeler workflow permission to download artifacts and explicitly tells the GitHub CLI which repository to act on. It does not change the Bitcoin library code,…

CI workflow permission fixNo source code changesNo cryptographic or consensus changes
276e0a61by Andrew Poelstra+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6657: Release tracking PR: `base58ck 0.5.0`

This commit is a routine version bump for the base58ck crate from 0.4.0 to 0.5.0. It only updates version numbers in package manifests, lock files, and adds a changelog entry. There are no code changes and no security relevance.

9deb5de1by Andrew Poelstra+22−168 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decoding

This commit is a routine feature addition to the rust-bitcoin base58 crate. It adds a new no-allocator function to decode short base58-check strings into fixed-size byte arrays, and renames the existing error type while keeping a deprecate…

No security-relevant bug fix is described in the commit message or diff.New decoding path uses a fixed 128-byte scratch buffer (`ArrayVec`) and rejects oversized inputs.Checksum verification and invalid-character handling are preserved from the existing alloc implementation.
c5fd1832by Andrew Poelstra+330−775 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0

This commit is a routine feature release for the bitcoin_hashes crate. It adds new public methods and a constant to the SHA-256 Midstate type so developers can compute SHA-256 midstates in const contexts. There is no indication of a securi…

0f68fcb3by Andrew Poelstra+157−4210 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: reword docs to block count in relative locktime

This commit only rewords documentation comments and variable names in the codebase. It changes references from 'block height' to 'block count' for relative lock times, which is a terminology correction with no functional code changes. Ther…

8867fe2eby satsfy (Renato Britto)+20−172 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` private

This commit makes a small internal helper type called WitnessesEncoder private. It was previously exported as public API but is only used inside the transaction encoder. The change removes it from the public API surface and moves the code …

07d91f7fby Andrew Poelstra+54−1324 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 75 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: fix labeller permissions

This commit adjusts a GitHub Actions workflow that automatically labels pull requests based on CI results. It adds a built-in repository token, tells the artifact download step to merge single-file artifacts, and explicitly sets the reposi…

Workflow-only change with no library code modificationsUses the default GITHUB_TOKEN rather than a custom secretRuns in workflow_run context, which already has elevated repository access by design
715f2bd6by Nick Johnson+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`

This is a routine API cleanup, not a security fix. The developers removed a shortcut that let programmers create a 'number of blocks' value directly from any u16 number, replacing it with an existing named constructor called from_height. T…

ed5f1b68by Andrew Poelstra+18−358 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logic

This commit is a pure code reorganization (refactor) in the rust-bitcoin library. It moves transaction encoding and decoding definitions around within a single file so the code follows the project's preferred layout. No logic, behavior, or…

c5588ba5by Andrew Poelstra+57−571 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6662: build(deps): bump actions/checkout from 6.0.2 to 6.0.3

This commit is a routine update to the GitHub Actions checkout tool used by the project's automated workflows. It changes the pinned version from 6.0.2 to 6.0.3 across many workflow files. The newer version fixes minor bugs related to SHA-…

Dependency bump of actions/checkout to a patch releaseUpstream fixes for SHA-256 repository checkout and merge commit regexAll affected workflows already disable persisted credentials
f7d364cdby Andrew Poelstra+29−2915 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6663: build(deps): bump taiki-e/install-action from 2.79.12 to 2.81.4

This is a routine Dependabot update that bumps the version of a third-party GitHub Action used only in automated testing workflows. The change does not touch the project's actual Bitcoin library code, and there is no indication it fixes or…

5c92c0b0by Andrew Poelstra+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update the API text files

This commit only updates two generated API text files that list the public surface of the Rust crate. It removes entries for a `WitnessesEncoder` type, reflecting that the type is no longer part of the public API. There is no source code c…

9c391145by Tobin C. Harding+0−782 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Scrub the transaction encoding logic

This commit is a pure code reorganization: it moves existing transaction encoding and decoding definitions around within a single file so they follow the project's preferred layout. No logic was changed, no security bug was fixed, and no n…

80dcef15by Tobin C. Harding+57−571 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Make the WitnessesEncoder private

This commit simply hides an internal helper type called WitnessesEncoder from public view. It is a routine API-cleanup change with no security relevance visible in the code or commit message.

b37accc3by Tobin C. Harding+54−542 files
No security note in commit
Open full analysis →Source 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-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.

Lower-priorityFix header hex test case commentsby Mitchell Bagot · 65fb7690 · Jan 6, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Fix header hex test case comments

The comments say 'transaction', when the test case only relates to
functionality on the Header type.

Replace 'transaction' with 'header' in header hex round trip test
comments.

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

This commit only fixes three incorrect comments in a test function. The comments mistakenly referred to 'transaction' when the test actually exercises the block Header type. No code behavior changes.

Lower-priorityRemove HeaderIter wrapper typeby Mitchell Bagot · 76259478 · Jan 6, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · Mitchell Bagot

Remove HeaderIter wrapper type

After introducing the ExactSizeEncoder trait, EncodableByteIter now
provides a len() implementation for use with fmt_hex_exact on the
HeaderEncoder.

Remove HeaderIter wrapper type and directly pass the header encoder
in an EncodableByteIter to fmt_hex_exact.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This is a small internal code cleanup in the rust-bitcoin library. It removes a hand-written wrapper type called HeaderIter and instead uses a newer built-in trait (ExactSizeEncoder) to achieve the same result. There is no user-visible behavior change and no security relevance.

Security candidateAdd ExactSizeEncoder for known-length Encodersby Mitchell Bagot · 96b8902e · Jan 6, 2026 · 25 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Add ExactSizeEncoder for known-length Encoders

Current encoders have no way to distinguish between fixed and variable
sized encoders. Having a way to get the size of fixed-size encoders
in constant time allows for a trivial implementation of
ExactSizeIterator for EncodableByteIter.

Add ExactSizeEncoder trait, implement it on the consensus_encoding
encoders where applicable. Add encoder_newtype_exact macro for
newtype encoders that wrap ExactSizeEncoders and convert most
existing encoder_newtype calls to encoder_newtype_exact.

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

This commit is a routine feature addition to the Rust Bitcoin library. It introduces a new ExactSizeEncoder trait that lets callers ask fixed-size encoders how many bytes they will produce, and adds an ExactSizeIterator implementation for the byte iterator. There is no security fix or vulnerability here; it is purely an API enhancement with tests.

Security candidateprimitives: reject transaction with duplicate inputsby jrakibi · af7a11b9 · Jan 6, 2026 · 1 fileMessage 91 · StrongModerate 60Details
Commit message · jrakibi

primitives: reject transaction with duplicate inputs

As part of adding validation rules to transactions, this check rejects
transactions with duplicate inputs during the decoding stage

Also updated a test case in the encode/decode roundtrip, the test was
using duplicated inputs which causes it to fail with the current
implementation.

Addresses part of https://github.com/rust-bitcoin/rust-bitcoin/issues/5383

Related: CVE-2018-17144

91/100 · StrongMessage clarity
✓ Specific, 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
explicit security languagesigning or wallet path
AI analysis · Moderate 60/100

This commit adds a safety check in the rust-bitcoin library so that when a Bitcoin transaction is being decoded, it is rejected if it tries to spend the same coin twice within the same transaction. This prevents a known bug class (CVE-2018-17144) where duplicate inputs could cause nodes to crash or accept invalid transactions. The change also updates existing tests that accidentally used duplicate inputs.