RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

2086 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
389commits · 60 days
1289commits · 180 days
2052commits · 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
320Strong · 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 Poelstra602155078
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 44 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 queuedIntroduce dep treeby Tobin C. Harding · 03e63103 · Aug 15, 2025 · 3 filesMessage 51 · ThinInformational 15Details
Commit message · Tobin C. Harding

Introduce dep tree

Add a just command to generate a dependency tree and commit the
result. This gives us a starting point for design discussions while
crate smashing.

51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit adds documentation showing the project's internal crate dependency tree and a helper command to regenerate it. It does not change any executable code, cryptographic logic, or network handling, so it has no security impact on its own.

AI review queuedImprove import statementsby Tobin C. Harding · b5641a95 · Aug 15, 2025 · 7 filesMessage 58 · ThinInformational 15Details
Commit message · Tobin C. Harding

Improve import statements

In days gone past we decided try to minimize merge conflicts by
keeping use statements really separate, over time we moved more and
more towards combining them (ie., not reaching into modules all the
time but using re-exports).

Now, in a push to make our codebase's imports mirror downstream usage
while still keeping our aims don't reach into `units` or `primitives`,
just grab things by way of their re-export.

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

This commit is a routine code cleanup that changes how internal Rust import statements are written. It replaces direct imports from internal sub-crates (like `units::BlockTime` or `primitives::Sequence`) with imports through the crate's own public re-exports (like `crate::BlockTime` or `crate::Sequence`). There is no change to program logic, behavior, or security.

Lower-prioritydocs: fix inconsistent terminology in README.mdby James Niken · 1a2a4161 · Aug 14, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · James Niken

docs: fix inconsistent terminology in README.md

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit changes one word in the README.md file, replacing 'MR' (merge request) with 'PR' (pull request). It is a documentation-only terminology fix with no code changes and no security relevance.

Lower-priorityfix: IsSatisfiedByTimeError::Incompatible wording to lock-by-timeby yyhrnk · 1f5e6ed3 · Aug 14, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · yyhrnk

fix: IsSatisfiedByTimeError::Incompatible wording to lock-by-time

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit fixes a typo in an error message. The message previously said 'lock-by-height' when it should have said 'lock-by-time'. It does not change any program logic, calculations, or security behavior.

Lower-priorityfix: correct typos in commentsby kurahin · 6bddb33b · Aug 13, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · kurahin

fix: correct typos in comments

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit fixes two spelling mistakes in code comments: adding a missing space in a comment about Rust formatting and changing 'a authentication tag' to 'an authentication tag'. No program logic, cryptographic code, or behavior was changed.

Lower-priorityManual update to Github CI to rustc nightly-2025-08-08by Tobin C. Harding · 3a63b3a8 · Aug 13, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Manual update to Github CI to rustc nightly-2025-08-08

Update the nightly toolchain as done by the bot in #4826 now that we
have a couple of fixes in place.

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

This commit simply updates a single text file that records which nightly version of the Rust compiler the project's automated tests use. It changes one date to another newer date. There is no code change, no bug fix, and no security relevance visible in the commit itself.

Lower-priorityUse correct taproot iter type in rustdocby Tobin C. Harding · 6bff520c · Aug 13, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Use correct taproot iter type in rustdoc

This type was apparently changed at some stage and the rustdoc was not
update, new nightly toolchain catches it - WIN.

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

This is a one-word documentation fix in a code comment. The developer corrected the name of an iterator type in a rustdoc comment so it matches the actual returned type. No code behavior changed, and there is no security issue.

Security candidatepsbt: Remove noisy paths in error inner typesby Update Nightly Rustc Bot · 30c253e1 · Aug 13, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Update Nightly Rustc Bot

psbt: Remove noisy paths in error inner types

Add a bunch of imports and make usage more terse with no loss of
clarity.

Internal change only, no logic change.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit is a cosmetic code cleanup in the rust-bitcoin library. It replaces fully written-out module paths (like `crate::Txid`) with shorter imported names (like `Txid`) in the PSBT error definitions. The commit message and diff show no functional changes—only style improvements.

Lower-prioritydocs: fix typo "inefficientcies" -> "inefficiencies"by Bashmunta · b39d564d · Aug 13, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Bashmunta

docs: fix typo "inefficientcies" -> "inefficiencies"

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit fixes a single spelling mistake in a code comment, changing 'inefficientcies' to 'inefficiencies'. No program code, logic, or behavior was changed. It has no security relevance.

Lower-priorityunits: Add my name to authors listby Tobin C. Harding · 5acdb668 · Aug 13, 2025 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

units: Add my name to authors list

We worked hard on this crate, its a team effort and at a minimum both
Andrew and I should be held accountable for any bugs or mistakes made.
I'm also proud of the code we produced.

Add my name to the authors list of the `units` crate.

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

This commit simply adds a second developer's name to the author list in a package metadata file. It changes no code, no functionality, and has no security relevance.

Lower-prioritychore: fix grammarby oooLowNeoNooo · 9775e7ac · Aug 12, 2025 · 2 filesMessage 40 · ThinInformational 15Details
Commit message · oooLowNeoNooo

chore: fix grammar

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only fixes grammar in comments and a shell script help message. No code behavior is changed, so it has no security relevance.

Security candidateFix overflow during *_ceil FeeRate conversionsby Shing Him Ng · dc2de6ad · Aug 12, 2025 · 1 fileMessage 85 · StrongLow 38Details
Commit message · Shing Him Ng

Fix overflow during *_ceil FeeRate conversions

This fixes an overflow bug which occured when these ceil functions were
called on `FeeRate::MAX`, which is u64::MAX under the hood. This
resulted in the function panicking due to an overflow since part of the
ceil operation involves adding to the FeeRate before dividing by the
appropriate unit. By calling `saturating_add` instead of using `+`, this
prevents the function from panicking while preserving the expected
behavior when converting `FeeRate`s that would have previously
overflowed

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Low 38/100

This commit fixes a bug in the rust-bitcoin library where three fee-rate conversion functions would crash when given the maximum possible fee rate. The functions round fee rates up to different units, and internally they added a small number before dividing. When the input was the maximum value (the largest 64-bit unsigned integer), that addition overflowed and caused a panic. The fix uses saturating addition, which caps the value instead of overflowing, so the functions now return a sensible result rather than crashing.

Lower-priorityp2p: Add `HeadersMessage` sanity check methodsby rustaceanrob · 7d813372 · Aug 12, 2025 · 1 fileMessage 80 · StrongInformational 18Details
Commit message · rustaceanrob

p2p: Add `HeadersMessage` sanity check methods

While this collection of crates does not try to implement the bitcoin
consensus logic, it can help prevent obvious spam or noise. Any list of
block headers must be connected in a linked list by their hashes, and
each header must pass its own work requirement, regardless of network.

Adding this here because I imagine anyone that uses these types would
want to know if they are receiving garbage.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI analysis · Informational 18/100

This commit adds two optional helper methods to check whether a list of Bitcoin block headers is correctly chained and whether each header meets its own proof-of-work target. It is a defensive, non-breaking feature addition for users of the library; it does not fix an existing vulnerability or change any default behavior.

Lower-priorityp2p: Expose `HeadersMessage` newtypeby rustaceanrob · 761576ae · Aug 12, 2025 · 1 fileMessage 58 · ThinInformational 19Details
Commit message · rustaceanrob

p2p: Expose `HeadersMessage` newtype

The `headers` message has a unique encoding that is represented by the
`Header(De)/SerializationWrapper` types. this exposes a publically
accessable type so users may properly encode a list of headers without
using `NetworkMessage`. The use of such a type is expressed in the
subsequent commit.

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

This commit is a straightforward code cleanup in the Bitcoin peer-to-peer networking code. It replaces two internal-only wrapper types with a single public type called `HeadersMessage` so that outside developers can directly serialize and deserialize lists of block headers. The actual encoding and decoding logic is unchanged; only the names and visibility are different.

AI review queuedfix: correct typos and clarify comments and testsby SashaMalysehko · e0982ae1 · Aug 12, 2025 · 3 filesMessage 67 · AdequateInformational 15Details
Commit message · SashaMalysehko

fix: correct typos and clarify comments and tests

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

This commit fixes three minor typos: one grammar correction in a code comment about SegWit transaction parsing, one grammar correction in a documentation comment about a feature flag, and one typo ('crate' to 'create') in an error message inside a test. There are no code behavior changes.

Security candidatehashes: Remove code deprecated in 0.15.0by Tobin C. Harding · d1595876 · Aug 11, 2025 · 7 filesMessage 80 · StrongInformational 19Details
Commit message · Tobin C. Harding

hashes: Remove code deprecated in 0.15.0

Policy is to keep deprecated stuff for two releases. We have released
0.16.0 already so we can remove stuff deprecated in 0.15.0 (assuming
0.17.0 is out next).

Furthermore this assists with the `primitives` stable release because
it removes `FromSliceError` from the API of crates that call public
macros across crate boundaries from `hashes`.

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
cryptography-sensitive path
AI analysis · Informational 19/100

This commit removes old, deprecated functions from the rust-bitcoin `hashes` crate that were marked for removal two releases ago. It is a routine cleanup change: it deletes functions like `from_slice`, `const_hash`, and `as_u64` that users were already warned not to use, and switches internal code to use the newer replacements. There is no bug fix or security patch here.

AI review queuedUse CompactSize instead of VarIntby Tobin C. Harding · 8a243bf1 · Aug 11, 2025 · 5 filesMessage 76 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Use CompactSize instead of VarInt

The term for a variable size encoded integer should be compact size.
We recently removed the `VarInt` type but a few identifiers and docs
still mention it.

ref: https://bitcoin.stackexchange.com/questions/114584/what-is-the-different-between-compactsize-and-varint-encoding

Fix: #4784

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

This commit is a simple renaming cleanup. It replaces the old term 'VarInt' with 'CompactSize' in comments, variable names, error variants, and test strings. No behavior of the code changes, and no security issue is introduced or fixed.

AI review queueddocs: Remove varint from rustdocby Tobin C. Harding · fb5ec3a4 · Aug 11, 2025 · 3 filesMessage 80 · StrongInformational 15Details
Commit message · Tobin C. Harding

docs: Remove varint from rustdoc

Remove mention of `varint` from public rustdoc since we are using
compact size now. However plain old 'length prefix' is fine in most
cases.


Leaves one difficult to patch instance still, will be done separately.

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

This commit only changes documentation comments in three source files. It replaces the word 'varint' with 'CompactSize' or 'length prefix' to match the project's current terminology. No code logic, serialization, or API behavior was altered.

Lower-priorityImprove ControlBlock serialize rustdocby Tobin C. Harding · e8658cee · Aug 11, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Tobin C. Harding

Improve ControlBlock serialize rustdoc

Remove the mention of `varint` and attempt to improve the wording on
the rustdocs of `serialize`.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit only changes documentation comments (rustdoc) for a serialization function in the Taproot control block code. It rewords the explanation to remove the term 'varint' and clarify that the length prefix is added later when encoding as a witness element. No code logic was modified.

AI review queuedbuild(deps): bump actions/download-artifact from 4 to 5by dependabot[bot] · 489118f0 · Aug 11, 2025 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump actions/download-artifact from 4 to 5

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4 to 5.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](https://github.com/actions/download-artifact/compare/v4...v5)

---
updated-dependencies:
- dependency-name: actions/download-artifact
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (used to download build artifacts) from version 4 to version 5 in a daily fuzzing workflow. There is no indication of a security problem or malicious change in the commit itself.

Security candidateUpdate psbt.mdby hoffman · 78f63bee · Aug 11, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · hoffman

Update psbt.md

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing boundarysigning or wallet pathdocumentation-only discount
AI analysis · Informational 15/100

This commit fixes a single spelling mistake ('spilt' to 'split') in a project planning document. It does not change any code, configuration, or security behavior.

Lower-priorityAdd rustfmt skip to macro callby Tobin C. Harding · fb83fc25 · Aug 11, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Add rustfmt skip to macro call

The multi-line foramt is not clearer and takes up a bunch of lines,
just go over the usual column with on this one.

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

This commit is purely a code-style change. It tells the automatic formatter (rustfmt) to leave a macro call on one long line instead of spreading it across multiple lines. There is no functional change to the Bitcoin library and no security relevance.

Lower-prioritybitcoin: Use ptr::cast function intstead of manually castingby Tobin C. Harding · bfcc10e8 · Aug 10, 2025 · 1 fileMessage 73 · AdequateInformational 12Details
Commit message · Tobin C. Harding

bitcoin: Use ptr::cast function intstead of manually casting

There is only a single instance of `*const` casting in `bitcoin`. Use
`ptr::cast` since its in Rust 1.38

Note that this replaces _multiple_ casts in a single line with a call
to `from_raw_parts`.

FTR I'm not 100% groking what is going on but the compiler is happy.

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

This is a small code cleanup in the rust-bitcoin library. It replaces one style of low-level pointer casting with a more modern, equivalent Rust function. The change does not alter the actual behavior of the code; it is purely a stylistic/refactoring improvement.

Security candidate2025-08-10 automated rustfmt nightlyby Fmt Bot · 81f3d858 · Aug 10, 2025 · 12 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2025-08-10 automated rustfmt nightly

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

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, line breaks, and brace placement. There are no functional changes, bug fixes, or security-related alterations.

Lower-prioritydocs: Add missing closed parenthesisby Tobin C. Harding · 1a22ec39 · Aug 9, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Tobin C. Harding

docs: Add missing closed parenthesis

Recent roadmap doc has a typo in it.

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit fixes a single missing closing parenthesis in a Markdown documentation file (docs/roadmap.md). It is a typo correction with no code changes and no security relevance.