RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

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

524security candidates506second-pass queue2193AI analyses
141commits · 30 days
284commits · 60 days
1150commits · 180 days
2046commits · 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
489Strong · 80–100
1083Adequate · 60–79
566Thin · 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 Bagot649193645068
Andrew Poelstra21072145089
Tobin C. Harding41566410063
jrakibi944994068
Nick Johnson19121190060
Jamil Lambert, PhD11919116061
satsfy (Renato Britto)381527066
Fmt Bot331431045
Trevor Arjeski111111069
Shing Him Ng31731056
Ismail Daif22622050
Martin Habovstiak28527069
Analysis record

Published AI watches

Last scanned 22 minutes ago

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
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump github/codeql-action/upload-sarif

This is a routine patch-version update of a GitHub-maintained action used only to upload static-analysis results (SARIF files) from a scheduled CI job. The change does not touch any project source code, cryptographic logic, or user-facing …

2cac6e38by dependabot[bot]+1−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump astral-sh/setup-uv from 8.3.2 to 9.0.0

This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install a Python tool called 'uv' in two workflow files. The new version is a major release of the setup-uv action itself, but the …

7d7e7269by dependabot[bot]+2−22 files
No security note in commit
Informational 21 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6894: Harden `Copy` policy and apply to all pre-1.0 crates

This commit removes the automatic `Copy` trait from several public error types in the rust-bitcoin library and updates the project's written policy to discourage `Copy` on error types. `Copy` is a Rust trait that lets values be duplicated …

API hardening: removes `Copy` from public error types to preserve future flexibilityPolicy update: docs/policy.md now explicitly discourages `Copy` on error typesNo vulnerability fix: change is defensive/preventive, not reactive to a disclosed issue
457cb9b5by Andrew Poelstra+14−146 files
No security note in commit
Informational 18 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6787: Move `from_script` to `Address` and drop `AddressExt`

This change is a routine code cleanup, not a security fix. It moves a method that converts Bitcoin output scripts into human-readable addresses from a temporary 'extension trait' directly onto the main Address type. The actual conversion l…

ed42dabdby Andrew Poelstra+38−414 files
No security note in commit
Low 35 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6061: Units improvements

This is a routine code-quality and API-expansion pull request for the rust-bitcoin library's 'units' crate. It widens some fee-rate constructors from 32-bit to 64-bit inputs, renames the old 32-bit versions, improves serde error messages, …

API surface change: new u64 fee-rate constructors return NumOpResult to prevent silent overflowRenaming of existing u32 constructors to *_u32 may break downstream callers at compile time (breaking API change)Removal of artificial restriction in from_per_vb allows larger valid inputs
f9460859by Andrew Poelstra+266−12211 files
No security note in commit
Low 49 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6862: units: Preserve error in NumOpResult add and sub

This commit fixes a bug in how the library handles math errors. Previously, if you added or subtracted two values and one of them already had an error (for example, dividing by zero), the library would silently replace that original error …

Error-state information loss in arithmetic wrapper typeIncorrect error propagation could mask prior failures such as division by zeroDefensive correctness fix in numeric operation result handling
5324e59aby Andrew Poelstra+26−41 file
No security note in commit
Low 37 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6896: Fix `cargo audit` findings

This is a routine dependency-maintenance merge that swaps out old, unmaintained helper libraries for newer, patched versions in the project's example embedded programs and benchmark harness. The changes are driven by automated security sca…

cargo audit advisory remediationdependency upgrade for known-vulnerable crate (rand 0.7 / jobserver)dependency upgrade for known-vulnerable crate (crossbeam-epoch)
5f5f666dby Andrew Poelstra+51−1849 files
Vendor flagged security relevance
Low 37 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6897: consensus_encoding: fix overcounting bug in the composite encoders exact size len calculation

This commit fixes a counting bug in a Rust Bitcoin library. The library has combined encoders that bundle multiple pieces of data together. A method called len() is supposed to report how many bytes are left to encode, but it was incorrect…

Violation of documented API contract (ExactSizeEncoder::len)Potential incorrect buffer-size or progress decisions by downstream callersComposite encoder state not fully isolated in size reporting before fix
22bbc326by Andrew Poelstra+19−13 files
No security note in commit
Low 37 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

consensus_encoding: fix bug in the composite encoder's exact size

This commit fixes a bookkeeping bug in a Rust Bitcoin library's composite encoder. The encoder is a tool that combines multiple pieces of data into a single byte stream, and it has a method that is supposed to report how many bytes are lef…

Incorrect implementation of a documented size/length contractPotential for callers to over-allocate buffers or miscompute transaction/witness sizesComposite encoder used in consensus-critical serialization paths
914365b4by Nick Johnson+19−13 files
No security note in commit
Informational 18 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6809: addresses: Add `AddressParams` type and remove most uses of network types

This is a routine API refactoring in the rust-bitcoin library. It introduces a new AddressParams type and replaces most public uses of the older Network/NetworkKind types when creating or validating Bitcoin addresses. There is no security …

No memory-safety issues, cryptographic errors, or input-validation changes observedNo new unsafe blocks, no new dependencies, no new parsing of untrusted dataAPI surface change only: parameter types replaced with semantically equivalent AddressParams
81032b1aby Andrew Poelstra+208−16414 files
No security note in commit
Low 38 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6886: units: preserve original err summing `NumOpResult`

This patch fixes a bug in how rust-bitcoin adds up a list of numeric operation results. Previously, if any item in the list already carried an error (for example, dividing by zero), the summing code would overwrite that error and falsely r…

Error-type confusion / misattribution in arithmetic result aggregationLoss of original failure context across iterator foldPotential for downstream logic to act on wrong `MathOp`/`MathErrorKind`
4af1ee1dby Andrew Poelstra+23−191 file
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6618: ci: disable fail-fast in weekly rustc update crons

This commit changes two GitHub Actions workflow files used for weekly automated Rust toolchain updates. It adds `fail-fast: false` so that if one branch's update job fails, the other branch jobs continue running instead of all being cancel…

c0a70548by Andrew Poelstra+2−02 files
No security note in commit
Moderate 62 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6884: units: Fix div_by_fee_rate_floor precision

This commit fixes a precision bug in a Rust Bitcoin library function that calculates how much transaction weight a given amount of money can afford at a given fee rate. The old code rounded the fee rate up to a coarser unit (satoshis per k…

Incorrect fee-rate-to-weight conversion leading to understated affordable weightInteger rounding direction (ceil) used as divisor in floor division causing off-by-one or larger precision lossAddition of overflow handling for Weight::MAX
9caad2c1by Andrew Poelstra+23−52 files
Vendor flagged security relevance
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 queuedbuild(deps): bump actions/upload-artifact from 6.0.0 to 7.0.1by dependabot[bot] · 9f63707f · Jul 13, 2026 · 3 filesMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump actions/upload-artifact from 6.0.0 to 7.0.1

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6.0.0 to 7.0.1.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/b7c566a772e6b6bfb58ed0dc250532a479d7789f...043fb46d1a93c77aae656e7c1c64a875d1fc6a0a)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-version: 7.0.1
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 the version of a GitHub Actions helper used to save build artifacts in three CI workflow files. There is no indication of a security issue in the project code itself, and the change does not alter how the project handles Bitcoin data, keys, or network messages.

AI review queuedbuild(deps): bump actions/labeler from 6.0.1 to 6.1.0by dependabot[bot] · d858acd1 · Jul 13, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump actions/labeler from 6.0.1 to 6.1.0

Bumps [actions/labeler](https://github.com/actions/labeler) from 6.0.1 to 6.1.0.
- [Release notes](https://github.com/actions/labeler/releases)
- [Commits](https://github.com/actions/labeler/compare/634933edcd8ababfe52f92936142cc22ac488b1b...f27b608878404679385c85cfa523b85ccb86e213)

---
updated-dependencies:
- dependency-name: actions/labeler
dependency-version: 6.1.0
dependency-type: direct:production
update-type: version-update:semver-minor
...

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 the version of a GitHub Actions workflow helper (actions/labeler) used to automatically label pull requests. There is no indication of a security issue in the change itself, and no evidence of malicious code in the referenced version.

Security candidatebuild(deps): bump peter-evans/create-pull-request from 7.0.8 to 8.1.1by dependabot[bot] · 21337179 · Jul 13, 2026 · 5 filesMessage 93 · StrongInformational 19Details
Commit message · dependabot[bot]

build(deps): bump peter-evans/create-pull-request from 7.0.8 to 8.1.1

Bumps [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) from 7.0.8 to 8.1.1.
- [Release notes](https://github.com/peter-evans/create-pull-request/releases)
- [Commits](https://github.com/peter-evans/create-pull-request/compare/271a8d0340265f705b14b6d32b9829c1cb33d45e...5f6978faf089d4d20b00c7766989d076bb2fc7f1)

---
updated-dependencies:
- dependency-name: peter-evans/create-pull-request
dependency-version: 8.1.1
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
boot or update pathdocumentation-only discountautomated dependency-update discount
AI analysis · Informational 19/100

This is a routine Dependabot update that bumps a GitHub Actions helper used by automated weekly maintenance workflows to create pull requests. The change only affects internal tooling, not the Rust Bitcoin library code that users rely on. There is no direct evidence of a security vulnerability being fixed or introduced, but any third-party action update carries a small supply-chain risk if the new version were malicious or buggy.

Lower-priorityReplace use of as_str().len() with .len()by Mitchell Bagot · 3952e574 · Jul 13, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Replace use of as_str().len() with .len()

With the new .len() function, the previous .as_str().len() use in the
address tests can now be shortened to a single .len() call instead.

Replace encoded.as_str().len() with encoded.len() in
base58_invalid_payload_length_reports_decoded_size test in address
module.

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 is a trivial code cleanup inside a test file. It replaces a slightly longer way of getting a string's length with a shorter, equivalent way. There is no security relevance.

Lower-priorityAdd len and is_empty to Base58CkStringby Mitchell Bagot · dcb7558b · Jul 13, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Add len and is_empty to Base58CkString

The Base58CkString type is essentially treated like a string in some
cases. While users can cast to a &str with as_str, it is convenient to
instead provide len and is_empty functions for the user.

Add len and is_empty methods to the Base58CkString type.

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

This commit adds two simple helper methods, len() and is_empty(), to a Rust type that holds a base58check-encoded string. It is a routine convenience/API improvement with no security relevance visible in the code or commit message.

Security candidateinternals: Bump version to 0.6.0by Tobin C. Harding · aed7a9ce · Jul 13, 2026 · 16 filesMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

internals: Bump version to 0.6.0

In preparation for release add a changelog, bump the version, and
update the lock files.

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

This commit is a routine version bump for the internal 'bitcoin-internals' crate from 0.5.0 to 0.6.0. It updates version numbers across package manifests and lock files, and adds a changelog describing API cleanups and small improvements. There is no code change that fixes a security bug or introduces a vulnerability.

Lower-priority2026-07-12 automated rustfmt nightlyby Fmt Bot · 20300fc7 · Jul 12, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-07-12 automated rustfmt nightly

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

This is a routine automated code-formatting commit. It only reorders imports, removes blank lines, and collapses multi-line formatting to single-line formatting as directed by the rustfmt tool. There are no functional code changes, no bug fixes, and no security-related alterations.

Security candidateci: update LTS branches for toolchain and kani cronsby Nick Johnson · 183197ab · Jul 10, 2026 · 3 filesMessage 62 · AdequateInformational 15Details
Commit message · Nick Johnson

ci: update LTS branches for toolchain and kani crons

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update pathdocumentation-only discount
AI analysis · Informational 15/100

This commit only changes three GitHub Actions workflow files that control scheduled CI jobs. It updates the list of long-term support (LTS) branches used by automated cron jobs, replacing one branch name with two placeholder-looking names ('0.32.xxx' and '0.32.xx'). There are no changes to the Rust Bitcoin library code, no bug fixes, and no security-related modifications.

AI review queuedUpdate API filesby Mitchell Bagot · dc2418b3 · Jul 10, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates generated API snapshot files to reflect that two existing types now expose a new public helper method called builder(). No actual source code changes are included, and there is no indication of a security fix or vulnerability.

Lower-priorityMove builder script functions to primitivesby Mitchell Bagot · 16e93cac · Jul 10, 2026 · 4 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Move builder script functions to primitives

The builder function on ScriptExt and ScriptBufExt provides a shorthand
way to get a builder for a script type. With the Builder type moved to
primitives, this function can now also be moved.

Move builder functions from ScriptExt and ScriptBufExt to Script<T> and
ScriptBuf<T> respectively.

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

This commit is a routine internal code reorganization. It moves two helper functions that create a 'script builder' from one module to another within the same project. The functions themselves are unchanged, and there is no indication this affects security.

AI review queuedReplace uses of Encoder2 with prefixed encodersby Mitchell Bagot · b6c5adb3 · Jul 10, 2026 · 11 filesMessage 68 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Replace uses of Encoder2 with prefixed encoders

Throughout the code, there are myriad instances of
Encoder2<CompactSizeEncoder, Bytes/SliceEncoder> used to encode a length
prefixed element vector or byte slice. With the new prefixed encoders
these can all be replaced with the PrefixedBytes/SliceEncoder types.

Replace uses of Encoder2<CompactSizeEncoder, Bytes/SliceEncoder> with
the corresponding PrefixedBytes/SliceEncoder type.

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

This commit is a straightforward internal cleanup in the rust-bitcoin library. It replaces verbose pairs of encoders (a length counter plus a raw slice/bytes encoder) with new combined 'prefixed' encoder types that do the same job. There is no change to the actual bytes produced on the wire, no new behavior exposed to users, and no indication of a security bug being fixed.

AI review queuedUpdate API filesby Mitchell Bagot · 7119794f · Jul 10, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates generated API snapshot files (text listings of public types and methods). It does not change any source code, behavior, or fix any bug. There is no security relevance.

Lower-priorityAdd tests to cover the new length prefixed encodersby Mitchell Bagot · 68702c8d · Jul 10, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · Mitchell Bagot

Add tests to cover the new length prefixed encoders

In order to cover mutants in the new PrefixedBytesEncoder and
PrefixedSliceEncoders, new tests will be needed. These also
help to prevent regressions if changes are made later.

Introduce tests to cover the new Prefixed encoder functionality.

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

This commit only adds new unit tests for recently introduced encoder code. It does not change any production logic, fix bugs, or alter behavior. There is no security issue in the commit itself.

Lower-priorityAdd new prefixed encoders for BytesEncoder and SliceEncoderby Mitchell Bagot · 8cf6b291 · Jul 10, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Add new prefixed encoders for BytesEncoder and SliceEncoder

The SliceEncoder and BytesEncoder types both encode variable length
slices of data without a length prefix. Currently, the code suggests
using Encoder2 for length prefixes, but this bloats types and encoder
initialisation for a common use-case. Instead, we should provide
encoders that automatically calculate and encode the length prefix as
a compact size.

Introduce PrefixedBytesEncoder and PrefixedSliceEncoder types that
mirror BytesEncoder and SliceEncoder but include length prefixes.

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 two new helper types, PrefixedBytesEncoder and PrefixedSliceEncoder, to make it easier to encode byte slices and lists of items with a length prefix. It is a straightforward feature/refactoring change with no security relevance visible in the code or commit message.

Lower-priorityunits: Remove incorrect code commentby Tobin C. Harding · 980ccfd5 · Jul 10, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · Tobin C. Harding

units: Remove incorrect code comment

In #6384 we change `<=` to `<`. While reviewing I thought this change
was incorrect at the time. After deeper consideration I see my confusion.

However the code comment added in the linked PR is definitely
incorrect and contradicts the rustdoc comments on the function.

`time` is the MTP of the chain tip. This is what the rustdocs say and
it is also what is stated in `validation.cpp` in Core:

// BIP113 requires that time-locked transactions have nLockTime set to
// less than the median time of the previous block they're contained in.
// When the next block is created its previous block will be the current
// chain tip, so we use that to calculate the median time passed to
// IsFinalTx().
const int64_t nBlockTime{active_chain_tip.GetMedianTimePast()};

return IsFinalTx(tx, nBlockHeight, nBlockTime);

`IsFinalTx` contains the equivalent lock time check that
`is_satisfied_by` calculates. This is exactly why we changed to use
`<` to match that function:

```
bool IsFinalTx(const CTransaction &tx, int nBlockHeight, int64_t nBlockTime)
{
if (tx.nLockTime == 0)
return true;
if ((int64_t)tx.nLockTime < ((int64_t)tx.nLockTime < LOCKTIME_THRESHOLD ? (int64_t)nBlockHeight : nBlockTime))
return true;
```

Remove the code comment.

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit only deletes an incorrect explanatory comment. The actual code behavior does not change at all. It is a documentation cleanup, not a security fix.

Lower-priorityunits: Fix changelog 0.5.0 linkby Tobin C. Harding · da7ae89d · Jul 9, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Tobin C. Harding

units: Fix changelog 0.5.0 link

Fix typo in link.

45/100 · ThinMessage clarity
✓ 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 commit fixes a typo in a changelog hyperlink. It changes one version number in a Markdown reference link so the comparison URL points to the correct previous release. There is no code change and no security relevance.

Security candidateRemove hex dep from internalsby Tobin C. Harding · bd0d4bc0 · Jul 9, 2026 · 8 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

Remove hex dep from internals

The `hex` dep is no longer used in `internals` (since #6339).

Remove it.

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

This commit simply removes an unused software dependency (the hex-conservative crate) from the internals sub-package and updates related package configuration files. It is a routine cleanup change with no security relevance.

Security candidatedocs: root readme cleanupby Nick Johnson · efeab943 · Jul 8, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Nick Johnson

docs: root readme cleanup

* PSBT has moved to the rust-psbt crate.
* The CI badges are not helpful when viewed from things like crates.io,
we have detection jobs now for maintainers for stuff like kani.
* Update deprecated library json rpc library.
* Update changelog links to work from anywhere. Also add missing crates.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 15/100

This commit only edits the project's README.md file. It removes outdated CI badges, updates the recommended JSON-RPC client library, fixes changelog links, and adds missing crates to the changelog list. No code, build scripts, or cryptographic logic was changed, so it has no direct security impact on users of the library.

Lower-prioritydocs: update LTS versions and expand on policyby Nick Johnson · d704b494 · Jul 8, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Nick Johnson

docs: update LTS versions and expand on policy

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 only edits a documentation file describing which versions of the rust-bitcoin project are supported long-term. It removes detailed dependency tables and updates the list of maintained LTS branches. There is no code change and no security fix or vulnerability introduced.

Security candidateReplace external uses of base58 encoding with Base58CkStringby Mitchell Bagot · 7f5fbd13 · Jul 8, 2026 · 3 filesMessage 73 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Replace external uses of base58 encoding with Base58CkString

Before the old encoding functions can be removed, all uses from outside
the crate need to be replaced with the equivalent calls from the new
Base58CkString type.

Replace all uses of encode_check and encode_check_to_fmt with equivalent
Base58CkString uses.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This commit is a routine internal code cleanup in the rust-bitcoin project. It swaps old base58 encoding helper functions for a new equivalent type, Base58CkString, in three source files. There is no indication from the commit itself that this fixes a security bug; it appears to be part of a refactoring to remove deprecated functions.

Lower-priorityRemove unused old encoding functionsby Mitchell Bagot · de3554c5 · Jul 8, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused old encoding functions

With the introduction of the Base58CkString type, the old encoding
functions can now be completely removed.

Remove encode, encode_check and encode_check_to_fmt, alongside the
accompanying private functions.

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

This commit simply deletes unused base58 encoding helper functions from the rust-bitcoin library. There is no security issue: the removed code is not called anywhere, and the public API is being cleaned up after a newer replacement type was introduced.

AI review queuedAdjust crate level docsby Mitchell Bagot · 30a6f1c5 · Jul 8, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot

Adjust crate level docs

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

This commit changes a single sentence in the crate's documentation. It clarifies that the base58 crate requires an allocator specifically for decoding, not for all operations. There is no code change and no security impact.

Lower-priorityReplace encode with checksum encoding in testsby Mitchell Bagot · 903b5bef · Jul 8, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Mitchell Bagot

Replace encode with checksum encoding in tests

The new Base58CkString type only performs base58check encoding, not the
non-checksum type encoding. As such, it has no replacement for the old
encode function. In order to confirm the same functionality (leading
zeros, >128 chars, etc), the uses of encode can be replaced by
equivalent base58check strings in the tests.

Replace encode usage in test cases with equivalent base58check encoded
strings and encoding calls.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only changes test code in the rust-bitcoin base58 module. It replaces calls to an old plain base58 encoder with equivalent base58check-encoded strings and a new checksum-based encoder. There is no change to production code, no security fix, and no vulnerability.

Lower-priorityGate alloc-only decoding errorsby Mitchell Bagot · 67925869 · Jul 8, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Gate alloc-only decoding errors

The errors used for decoding are currently alloc-only, but are exported
even for no-alloc builds. These should be gated the same as the
functionality that uses them.

Gate Error, IncorrectChecksumError, TooShortError and
InvalidCharacterError behind alloc.

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

This commit is a build-system cleanup, not a security fix. It hides certain error types from builds that do not enable the 'alloc' feature, because those error types are only used by decoding functions that already require 'alloc'. There is no change to how data is decoded, checked, or handled at runtime.

Lower-priorityReplace encode_check with Base58CkString in tests and benchmarksby Mitchell Bagot · 44fe1c1c · Jul 8, 2026 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · Mitchell Bagot

Replace encode_check with Base58CkString in tests and benchmarks

The encode_check function is used for base58check encoding under the
old function API. With the introduction of the Base58CkString type,
base58check encoding is now done through Base58CkString::encode or
encode_unbounded.

Replace encode_check uses in tests and benchmarks with
Base58CkString::encode_unbounded.

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 updates internal tests and benchmarks to use a newer API for base58check encoding. It does not change any production code or fix a security problem.