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
140commits · 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 11 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.

Lower-priorityIntroduce Opcode::from_u8by Mitchell Bagot · 5cf9bc2f · Jun 15, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · Mitchell Bagot

Introduce Opcode::from_u8

While Opcode can be constructed from a u8 with the From impl, there
exists no way to do so in a const context outside of the opcodes
module. This will make moving the type to primitives impossible.

Introduce from_u8 const function on Opcode to construct an opcode from
a raw u8.

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

This is a routine internal code cleanup in the Rust Bitcoin library. It adds a new public constant function `Opcode::from_u8` so that Bitcoin script opcodes can be created from raw byte values inside constant contexts (for example, at compile time). The existing `From<u8>` conversion is rewritten to use this new function. There is no security-relevant change: the behavior is identical, no new data is accepted, and no existing checks are removed.

Lower-priorityRemove decoding functionality from HexPrimitiveby Mitchell Bagot · 36377768 · Jun 15, 2026 · 1 fileMessage 68 · AdequateInformational 12Details
Commit message · Mitchell Bagot

Remove decoding functionality from HexPrimitive

With all uses of HexPrimitive decoding removed, the ParsePrimitiveError
and decoding functionality on HexPrimitive can be removed.

Delete from_str, and IntoIterator from HexPrimitive and delete
ParsePrimitiveError.

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

This commit removes unused hex-decoding helper code from an internal module. It is a cleanup change: it deletes functions and an error type that are no longer used anywhere in the project. There is no indication this fixes a security bug or changes behavior visible to users.

AI review queuedUpdate API filesby Mitchell Bagot · 7fdbb879 · Jun 15, 2026 · 1 fileMessage 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 an automatically-generated text file that lists the project's public API surface. It removes entries for some error types that were renamed or replaced elsewhere, and updates type signatures to match. No actual source code, logic, or behavior changed in this commit, so it has no security relevance on its own.

AI review queuedReplace HexPrimitive decoding with consensus_encodingby Mitchell Bagot · f0a52a65 · Jun 15, 2026 · 5 filesMessage 73 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Replace HexPrimitive decoding with consensus_encoding

The HexPrimitive type in primitives provides an alloc-less hex str
decoding for types in primitives. Since consensus_encoding now has
the same functionality in decode_from_hex, the entire from_str on
HexPrimitive (and ParsePrimitiveError) can be completely eliminated.

Replace all decoding uses with decode_from_hex in consensus_encoding.
Remove Parse*Error wrappers around ParsePrimitiveError.

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

This commit is a routine internal cleanup in the rust-bitcoin library. It removes a duplicate way of turning hex strings into Bitcoin data structures (blocks, block headers, transactions) and replaces it with a single shared helper called decode_from_hex. The actual hex decoding logic stays functionally the same; only the error types and code paths are simplified. There is no indication this fixes a security bug.

Lower-priorityRemove HexPrimitive use in ScriptBuf::from_hex_prefixedby Mitchell Bagot · 1dcca97d · Jun 15, 2026 · 5 filesMessage 73 · AdequateInformational 17Details
Commit message · Mitchell Bagot

Remove HexPrimitive use in ScriptBuf::from_hex_prefixed

Recently, HexPrimitive was used to provide alloc-less decoding of
ScriptBuf in the from_hex_prefixed function on ScriptBuf. With the
stabilisation of consensus_encoding and the alloc-less hex decoding
there, the use of HexPrimitive can be eliminated in favor of a single
call to encoding::decode_from_hex. Further, this eliminates the
single-use error type FromHexError entirely.

Remove script::FromHexError and replace use of HexPrimitive with
consensus_encoding hex decoding for ScriptBuf::from_hex_prefixed.

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

This commit is a routine internal cleanup in the rust-bitcoin library. It removes a custom error type and switches one function to use a newer, shared hex-decoding path. There is no indication this fixes a security bug; it is a refactoring change.

Lower-priorityunits: Bump version to 0.5.0by Tobin C. Harding · fb0f425c · Jun 14, 2026 · 7 filesMessage 76 · AdequateInformational 15Details
Commit message · Tobin C. Harding

units: Bump version to 0.5.0

We just removed a set of public functions (parse an integer from hex
`_unchecked` version).

In preparation for release bump the version, upgrade local downstream
crates, add a changelog entry, and update the lock files.

Note on deprecated code:

In #6290 we did the 'final polish before 1.0' including removal of
deprecated code. Hoping that the next release was 1.0 and users could
use `0.4.0` as 1.0 + deprecated stuff.

Now we are going to do `0.5.0` and semver everything possible back
into `0.4.1` so this reasoning still stands. From the changelog it
should be clear also what is going on.

76/100 · AdequateMessage clarity
✓ 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 is a routine version bump for the bitcoin-units crate from 0.4.0 to 0.5.0. It updates dependency references and lock files, and records in the changelog that some deprecated and internal-only hex-parsing helper functions were removed. There is no security-relevant code change in the diff itself.

Lower-priorityUpdate the API text filesby Tobin C. Harding · 9ae5eca2 · Jun 14, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Tobin C. Harding

Update the API text files

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 only updates generated API text files that list what functions are publicly available in the library. It removes lines that described four internal 'unchecked' hex-parsing helper functions from the public API snapshot. There is no actual code change, no bug fix, and no security-relevant behavior change visible in the diff.

Lower-priorityunits: Remove _unchecked parsing functionby Tobin C. Harding · 1586151d · Jun 14, 2026 · 1 fileMessage 68 · AdequateInformational 18Details
Commit message · Tobin C. Harding

units: Remove _unchecked parsing function

Remove from the public API the 'unchecked' hex parsing function. This
function is not useful, we proved a prefixed, a non-prefixed, and
'any' (with or without prefix). The 'unchecked' function fails if
there is a prefix so should only be called after first ensuring there
is no prefix. Hence it is a helper function and should not be part of
the public API.

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

This commit removes a helper function from the public API of a Rust Bitcoin library. The function was never intended for outside use and only parses hex numbers that have no '0x' prefix. Making it private reduces the library's exposed surface, which is a good defensive practice, but there is no evidence it fixed an active security bug.

Lower-priorityp2p: sequence assertsby yancy · 0b7893c4 · Jun 14, 2026 · 1 fileMessage 43 · ThinInformational 15Details
Commit message · yancy

p2p: sequence asserts

The assertion has a needless assignment before it. Move assignment to
be above where the assertion makes sense.

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
AI analysis · Informational 15/100

This is a tiny code cleanup inside test code. It moves a variable assignment to a slightly different spot so the test reads more logically. There is no change to how the program behaves, no security fix, and no user-facing effect.

Security candidate2026-06-14 automated rustfmt nightlyby Fmt Bot · 90c665e3 · Jun 14, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Fmt Bot

2026-06-14 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 pathparser or protocol path
AI analysis · Informational 15/100

This commit is an automated code-formatting run by rustfmt. It only reorders import/use statements in two files without changing any program logic, behavior, or security properties.

Security candidateAdd #[inline] to all trivial functions in cryptoby Mitchell Bagot · 2a1e1ffa · Jun 13, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Add #[inline] to all trivial functions in crypto

All functions that are relatively trivial should be annotated with the
inline attribute to hint to the compiler to optimise them by inlining.

Add #[inline] to all small/trivial functions in crypto.

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

This commit only adds compiler hints (#[inline]) to small functions in the crypto module. It does not change any behavior, logic, or data handling. There is no security issue here.

Lower-priorityRemove From<Infallible> on inner error typesby Mitchell Bagot · 58a1c0c3 · Jun 12, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove From<Infallible> on inner error types

Inner error types do not appear in the public API, nor does a
From<Infallible> provide any internal purpose.

Remove From<Infallible> from private inner error types in base58 and
units.

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

This commit removes unused helper code that converted the impossible-to-create Infallible error type into several private inner error types. These inner types are not exposed to users of the library, and the removed conversions served no internal purpose. There is no security-relevant change.

Lower-priorityprimitives: avoid extra reallocation when decoding witnessby jrakibi · 17be36b6 · Jun 10, 2026 · 1 fileMessage 83 · StrongInformational 20Details
Commit message · jrakibi

primitives: avoid extra reallocation when decoding witness

Decoding a single element larger than ~128 bytes results in 3 allocations.
Instead of reserving the index space in end() we can reserve it at the moement
the last element's data is copied. This reduces the regression we have for the
case of one_element/256 from 42% to 10%.

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

This is a small performance optimization in how Bitcoin witness data is decoded. It changes when memory is reserved during decoding to avoid one extra memory reallocation for large witness elements. There is no security bug being fixed and no indication this change is security-relevant.

Lower-priorityIgnore reserve() capacity mutant in WitnessDecoderby jrakibi · f6160368 · Jun 10, 2026 · 1 fileMessage 75 · AdequateInformational 15Details
Commit message · jrakibi

Ignore reserve() capacity mutant in WitnessDecoder

Only reserves capacity, so no test can catch it

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only updates a mutation-testing configuration file. It tells the mutation-testing tool to skip certain artificial code changes in a WitnessDecoder because those changes only affect memory capacity reservations and cannot be detected by tests. There is no change to actual library code, no bug fix, and no security relevance.

Lower-prioritybenches: Add witness decode benchmarksby jrakibi · c7952378 · Jun 10, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · jrakibi

benches: Add witness decode benchmarks

benchmark results compared to master:

- many witness elements: ~45% faster
- one element of diff sizes: 14–27% faster
- chunked input: 6–84% faste

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

This commit only adds new performance benchmarks for decoding Bitcoin transaction witness data. It does not change any production code, fix any bug, or alter program behavior. There is no security relevance.

Security candidateprimitives: Simplify and optimize witness decoderby jrakibi · 4e780508 · Jun 10, 2026 · 1 fileMessage 68 · AdequateModerate 68Details
Commit message · jrakibi

primitives: Simplify and optimize witness decoder

The current logic for the index space in witness decoder lets an
attacker allocate a claimed size without giving any input, which opens
the door to many DoS attacks, some of which we already handle.

But the current code still lets an attacker force a 16 MB allocation
with ~10 bytes of input.

The new logic pushes bytes blindly into `content` without building the
index space in `push_bytes()`, then in `end()` walks through `content`
to build the index space.

This simplifies the code, gives an important speedup, and avoids:

- the 16 MB up-front allocation we currently have for the index space
- `reserve_batch()` is no longer needed, along with the
`MIN_` and `MAX_VECTOR_ALLOCATE` constants

- we can drop the `cursor` field from the decoder
- the DoS vector where an attacker sends a few bytes to force a large
allocation, since the buffer only grows by the bytes actually received

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
explicit security language
AI analysis · Moderate 68/100

This commit fixes a denial-of-service (DoS) weakness in how the rust-bitcoin library decodes Bitcoin transaction witness data. Previously, an attacker could send only about 10 bytes of data and trick the decoder into reserving 16 MB of memory up front. The new code only allocates memory for bytes that have actually arrived, making memory-exhaustion attacks much harder. The commit also simplifies the code and removes several helper functions and constants.

Security candidatenetwork: Bump version to 1.0.0by Tobin C. Harding · 4d4a8d28 · Jun 9, 2026 · 8 filesMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

network: Bump version to 1.0.0

In preparation for release add a changelog entry, bump the version
number, update local downstream crates, and update the lock files.

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

This commit is a routine version bump for the bitcoin-network-kind crate from version 0.1.0 to 1.0.0. It updates version numbers in package manifests, lock files, and a changelog, but does not change any source code or behavior. There is no security relevance.

Lower-priorityUpdate the API text filesby Tobin C. Harding · 4d35ff28 · Jun 9, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Tobin C. Harding

Update the API text files

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 only updates generated text files that list the public API surface of the crate. The change records that a new standard Rust conversion trait (`From<Infallible>`) is now implemented for an existing error type. No source code, logic, or behavior was changed, so there is no security issue here.

Lower-prioritynetwork: Implement From<Infallible> for error typeby Tobin C. Harding · ed405f6d · Jun 9, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Tobin C. Harding

network: Implement From<Infallible> for error type

As is customary add the impl.

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

This is a routine Rust language addition: it lets the library's network-parsing error type be created from Rust's 'Infallible' type, which can never actually occur. It has no security relevance on its own.

Lower-prioritynetwork: Move serde code down the fileby Tobin C. Harding · c5cf458f · Jun 9, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding

network: Move serde code down the file

This one is a bit subjective; following the idea that the least
important stuff goes further down the file move `serde` down.

This code move also leaves the `Display` and `FromStr` impls next to
each other, which is nice.

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

This commit simply rearranges code within a single file. It moves the Display, FromStr, and AsRef implementations for the Network type to appear earlier in the file, and moves the serde-related code lower down. No logic, behavior, or security properties of the code were changed.

Lower-prioritynetwork: Put impl block directly under typeby Tobin C. Harding · 21e5c690 · Jun 9, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Tobin C. Harding

network: Put impl block directly under type

As is customary put the impl block for `Network` directly under the
type definition.

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

This commit simply moves existing code around in the same file. It places the main implementation block for the Network type directly underneath the type definition, which is a common Rust style preference. No behavior, logic, or security properties changed.

AI review queuedUpdate API filesby Mitchell Bagot · 2ccf8548 · Jun 9, 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 three text files that list the project's public API surface. It removes entries for modules, macros, and types that are no longer part of the public API. There is no actual source code change, no bug fix, and no security-related content.

Lower-priorityRemove unused modules from internalsby Mitchell Bagot · b2607fd5 · Jun 9, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused modules from internals

There are two modules, parse and const_tools, that are completely
unused in internals. That is, their defined macros and types are
only ever used within themselves, not even elsewhere within internals.
These modules can be trivially dropped.

Drop parse and const_tools modules from internals.

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 two internal helper code modules that were not being used anywhere in the project. It is a cleanup change with no security relevance.

Lower-priorityRemove unused types and macros from internals::serdeby Mitchell Bagot · 0b2cb459 · Jun 9, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused types and macros from internals::serde

The IntoDeError and serde_struct_human_string_impl macro in
internals::serde are both entirely unused. These two are neither used
privately within internals, nor publicly by other crates.

Drop IntoDeError and serde_struct_human_string_impl from
internals::serde.

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

This commit simply deletes unused code—an internal trait and a macro for serde serialization helpers. There is no bug fix, behavior change, or security patch here. It is a routine cleanup that removes dead code.

Lower-priorityMove SerializeBytesAsHex to primitivesby Mitchell Bagot · 966d9295 · Jun 9, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Mitchell Bagot

Move SerializeBytesAsHex to primitives

The SerializeBytesAsHex type in internals is only ever used in Witness
in primitives. Rather than provide the type from internals, the type
can instead be pasted in-line in the primitives witness module (as a
private type) and used there.

Move SerializeBytesAsHex type as private type to primitives::witness.

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

This commit simply moves an existing helper type used for serializing bytes as hexadecimal from one internal module to another. The code is copied verbatim and made private to the module that uses it. There is no functional change, no bug fix, and no security relevance.