RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Repository coverage

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

459security candidates448second-pass queue969AI analyses
188commits · 30 days
404commits · 60 days
1283commits · 180 days
2064commits · 365 days
Backfill bands
Aug 5 → Feb 6787 seen32 candidatesComplete
Feb 6 → Jun 6878 seen53 candidatesComplete
Jun 6 → Jul 6211 seen15 candidatesComplete
Jul 6 → Aug 5184 seen2 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

64/100 average clarity
311Strong · 80–100
1054Adequate · 60–79
555Thin · 40–59
150Opaque · 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 Bagot640192332068
Tobin C. Harding40965152063
jrakibi944963068
Nick Johnson1892091059
Andrew Poelstra512033075
Jamil Lambert, PhD1141849061
Fmt Bot311420045
Trevor Arjeski111111069
Shing Him Ng31724056
Ismail Daif22612050
satsfy (Renato Britto)17611066
Martin Habovstiak27511069
Analysis record

Published AI watches

Last scanned 22 minutes ago

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

build(deps): bump astral-sh/setup-uv from 8.1.0 to 8.2.0

This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install the 'uv' Python tool in two workflow files. The new commit hash corresponds to the legitimate 8.2.0 release of astral-sh/se…

1c438632by dependabot[bot]+2−22 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 automated update by Dependabot that changes the pinned version of a GitHub-provided security scanning helper used in a workflow. It does not modify the project's actual Bitcoin library code, its cryptographic logic, or an…

5293bee4by 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 taiki-e/install-action from 2.79.12 to 2.81.4

This is a routine Dependabot update that bumps a GitHub Actions helper used in automated testing workflows from version 2.79.12 to 2.81.4. It only changes which version of the action is invoked during CI runs; it does not modify the Rust B…

eb9544f9by dependabot[bot]+2−22 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump actions/checkout from 6.0.2 to 6.0.3

This is a routine automated update by Dependabot that bumps the GitHub Actions 'actions/checkout' dependency from version 6.0.2 to 6.0.3 across all project workflow files. It only changes pinned commit hashes and version comments for the a…

Routine patch-level dependency bumpNo changes to permissions, inputs, or workflow logicpersist-credentials: false already present on all checkout steps
ae935fadby dependabot[bot]+29−2915 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 snapshot text files to remove two lines that documented a `From<u16>` conversion for a locktime type. No actual Rust source code was changed, so there is no runtime behavior change or security fix in …

6ea25bedby Mitchell Bagot+0−123 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

base58ck: Bump version to 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 describing unrelated feature changes. There are no code changes,…

8479b56eby Tobin C. Harding+22−168 files
No security note in commit
Informational 20 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Rename Error to DecodeCheckError

This commit is a routine code cleanup: it renames the `Error` type in the base58 module to the more descriptive `DecodeCheckError`, and adds a deprecated type alias so existing code using `base58::Error` continues to work. There is no chan…

b0eba4c0by Mitchell Bagot+45−395 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityMake primitives::opcodes pub with pub(crate) contentby Mitchell Bagot · 8063b435 · Jun 15, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Make primitives::opcodes pub with pub(crate) content

In preparation for the move of Opcode to primitives, the opcodes module
in primitives will need to be public. Since the existing content is not
supposed to be public, it should all be changed individually to
pub(crate) and gated appropriately.

Make primitives::opcode pub. Make all content of the module pub(crate)
and gate on alloc as needed.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMove as_str outside of all moduleby Mitchell Bagot · 6636c843 · Jun 15, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Move as_str outside of all module

The as_str function on Opcode will not be able to be moved to
primitives. As such, it must be modified ahead of time such that it
can be moved to an extension trait.

Introduce pub(super) opcode_to_str in all and move pub as_str
function outside of all module.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityReplace all Opcode.code access with to_u8()by Mitchell Bagot · 6ef52fd4 · Jun 15, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Replace all Opcode.code access with to_u8()

The Opcode code field is a private field which holds the u8 value of
the opcode. Since this should not be made public, the functionality
in the OpcodeExt extension trait will need to rely instead on the
public to_u8 function.

Replace all Opcode.code access in OpcodeExt and tests with to_u8().

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityRemove decoding functionality from HexPrimitiveby Mitchell Bagot · 36377768 · Jun 15, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
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 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 · AdequateTriage 0Details
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
Lower-priorityunits: Remove _unchecked parsing functionby Tobin C. Harding · 1586151d · Jun 14, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
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
Lower-priorityUpdate the API text filesby Tobin C. Harding · 9ae5eca2 · Jun 14, 2026 · 3 filesMessage 45 · ThinTriage 0Details
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
Lower-priorityunits: Bump version to 0.5.0by Tobin C. Harding · fb0f425c · Jun 14, 2026 · 7 filesMessage 76 · AdequateTriage 0Details
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
Lower-priorityp2p: sequence assertsby yancy · 0b7893c4 · Jun 14, 2026 · 1 fileMessage 43 · ThinTriage 0Details
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
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 · AdequateTriage 0Details
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
Lower-priorityprimitives: avoid extra reallocation when decoding witnessby jrakibi · 17be36b6 · Jun 10, 2026 · 1 fileMessage 83 · StrongTriage 0Details
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
Lower-priorityIgnore reserve() capacity mutant in WitnessDecoderby jrakibi · f6160368 · Jun 10, 2026 · 1 fileMessage 75 · AdequateTriage 0Details
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
Lower-prioritybenches: Add witness decode benchmarksby jrakibi · c7952378 · Jun 10, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
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
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 · ThinTriage 0Details
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
Lower-prioritynetwork: Move serde code down the fileby Tobin C. Harding · c5cf458f · Jun 9, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
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
Lower-prioritynetwork: Implement From<Infallible> for error typeby Tobin C. Harding · ed405f6d · Jun 9, 2026 · 1 fileMessage 50 · ThinTriage 0Details
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
Lower-prioritynetwork: Put impl block directly under typeby Tobin C. Harding · 21e5c690 · Jun 9, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
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 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 · AdequateTriage 0Details
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