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.
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
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.…
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 …
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
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…
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…
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
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…
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 …
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 …
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
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…
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
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
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)
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
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
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
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`
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…
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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6446: base58: Add examples and adjust docsby Andrew Poelstra · d8b4c865 · Aug 8, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6446: base58: Add examples and adjust docs
703021ac862dec7587050b99574c6acb89702143 Add doctest examples for decoding (Mitchell Bagot) 7aa7d4c06bd28274424ff0a44fc86f9609a5866b base58: Update crate docs to suit new API (Mitchell Bagot) 9296dba011dd6916e7dc86c376aa3f6b54cee4c8 Add doctest examples for Base58CkString (Mitchell Bagot) 3c266fef445136506d8a2d5b987c273b0e9c2dd9 Adjust wording for error module docs (Mitchell Bagot)
Pull request description:
The base58 crate docs currently lack any examples. While the API is fairly self-explanatory, examples are typically recommended and can be useful to illustrate use and specifics of the functionality. Further, some other docs are sub-optimal for a 1.0 release.
- Patch 1 adjusts the wording for the error module docs. - Patch 2 adds examples to the Base58CkString encoding methods. - Patch 3 updates the crate-level docs. - Patch 4 adds examples to the decode_check* functions.
ACKs for top commit: apoelstra: ACK 703021ac862dec7587050b99574c6acb89702143; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityci: setup debug level based on runner debug settingby Nick Johnson · fb887b19 · Aug 7, 2026 · 2 filesMessage 100 · StrongTriage 0Details
Commit message · Nick Johnson
ci: setup debug level based on runner debug setting
Don't use the "progress" log level because the ascii end line symbols are leaking through.
Also removing the "test-ci/*" trigger. We have been testing workflow changes on fork'd remotes which is more flexible and doesn't clutter the config here.
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
documentation-only discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6683: units: Add `CompactTarget::to_consensus_u32`by Andrew Poelstra · f552ea88 · Aug 7, 2026 · 5 filesMessage 100 · StrongTriage 0Details
a75c53c86266e6c7f7f181d6e03896f7b7b9da91 Update API files (Mitchell Bagot) 270a2267af049d127719452fe814648db528493f Replace uses of deprecated CompactTarget::to_consensus (Mitchell Bagot) 446771dfb510080accd7da1c538f6b18e93619b6 Add CompactTarget::to_consensus_u32 (Mitchell Bagot)
Pull request description:
Currently, of all of the types that have from_consensus and to_consensus* functions, only CompactTarget excludes the _u32 suffix on the to_consensus function. In order to have LockTime, Sequence and CompactTarget all use a consistent naming scheme, a to_consensus_u32 function should be used for CompactTarget.
Add CompactTarget::to_consensus_u32 and deprecate CompactTarget::to_consensus.
ACKs for top commit: apoelstra: ACK a75c53c86266e6c7f7f181d6e03896f7b7b9da91; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedMerge rust-bitcoin/rust-bitcoin#6678: units: Add `Weight::to_vb_*` functions, deprecating `to_vbytes_*`by Andrew Poelstra · 7f614781 · Aug 7, 2026 · 6 filesMessage 91 · StrongInformational 20Details
c4a5a5e64de86f100008972389a76c3eae2faeae Update API files (Mitchell Bagot) 4af70a4eb6a18f4f6ca27c4ea0898f5c9e4bc363 Replace uses of deprecated methods with Weight::to_vb_* (Mitchell Bagot) 519ba8c8a113e679f00a9669ccec51e5c5ef7b54 units: Add Weight::to_vb_* functions, deprecating to_vbytes_* (Mitchell Bagot)
Pull request description:
The Weight type uses from_vb* as the pattern for constructors, but to_vbytes_* for conversion. FeeRate is consistent with to/from_vb*. Before we go to 1.0, Weight's conversion functions should be renamed to keep everything consistent.
Add Weight::to_vb_{floor,ceil} and deprecate Weight::to_vbytes_{floor,ceil}.
ACKs for top commit: apoelstra: ACK c4a5a5e64de86f100008972389a76c3eae2faeae; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This is a routine API cleanup in a Rust Bitcoin library. It adds new method names (to_vb_floor, to_vb_ceil) for converting transaction 'weight' to 'virtual bytes' and marks the old names (to_vbytes_floor, to_vbytes_ceil) as deprecated. The actual math is unchanged, and existing callers are updated to use the new names. There is no security bug or fix here.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6677: primitives: Add track_callerby Andrew Poelstra · 10c2e41e · Aug 6, 2026 · 1 fileMessage 91 · StrongTriage 0Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
1c118339ac3d0d4445d2062d9b54e3dbc482b9af crypto: Bump version to 0.3.0 (Tobin C. Harding) b6d44ee8af9f388fc25989c2e9da73bdcf66fd1d primitives: Bump version to 0.103.1 (Tobin C. Harding) 9516435c7371c22e7a6f02b93f65a7231f41e123 primitives: Depend on encoding 1.1.0 (Tobin C. Harding)
Pull request description:
In preparation for release add a changelog entry, bump the version number, and update the lock files.
ACKs for top commit: apoelstra: ACK 1c118339ac3d0d4445d2062d9b54e3dbc482b9af; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit is a routine release-tracking merge. It only bumps version numbers (bitcoin-crypto to 0.3.0 and bitcoin-primitives to 0.103.1), updates dependency version requirements, refreshes lock files, and adds changelog entries. There are no code changes that fix or introduce security behavior.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6669: units: Add `RemAssign` to `NumOpResult<Amount/SignedAmount>`by Andrew Poelstra · a150957b · Aug 6, 2026 · 5 filesMessage 100 · StrongTriage 0Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6669: units: Add `RemAssign` to `NumOpResult<Amount/SignedAmount>`
90d5f7448aa09a77f1795f0aca4d22a9e4c38d7e Update API files (Mitchell Bagot) 6b5902163e094b2dc59e1c43294207171785568e Add test case to cover RemAssign on NumOpResult (Mitchell Bagot) e772a74a57e55d18b394ca35098bd6ab88005af9 Add RemAssign to NumOpResult<Amount/SignedAmount> (Mitchell Bagot)
Pull request description:
Currently, the Amount and SignedAmount types implement Rem<i64/u64>. So that operations can be chained on the NumOpResult types, RemAssign should also be introduced on them with the same semantics, i.e. impl RemAssign<i64/u64> for NumOpResult<Amount/SignedAmount>.
Add RemAssign impls for NumOpResult<Amount/SignedAmount> by i64/u64.
Closes #4031
ACKs for top commit: apoelstra: ACK 90d5f7448aa09a77f1795f0aca4d22a9e4c38d7e; successfully ran local tests tcharding: ACK 90d5f7448aa09a77f1795f0aca4d22a9e4c38d7e
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedUpdate API filesby Mitchell Bagot · a75c53c8 · Aug 6, 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
This commit only updates generated API listing files (text snapshots of public functions) to reflect a newly added public function, `to_consensus_u32`, on the `CompactTarget` type. It does not change any source code, logic, or behavior, and therefore has no security relevance on its own.
Lower-priorityReplace uses of deprecated CompactTarget::to_consensusby Mitchell Bagot · 270a2267 · Aug 6, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Mitchell Bagot
Replace uses of deprecated CompactTarget::to_consensus
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Currently, of all of the types that have from_consensus and to_consensus* functions, only CompactTarget excludes the _u32 suffix on the to_consensus function. In order to have LockTime, Sequence and CompactTarget all use a consistent naming scheme, a to_consensus_u32 function should be used for CompactTarget.
Add CompactTarget::to_consensus_u32 and deprecate CompactTarget::to_consensus.
a1942b52f5efd29a7ed52fd2e77490c24c1809f2 units: Remove unnecessary track_caller (Tobin C. Harding)
Pull request description:
I audited `units` with Claude to check for missing usage of `track_caller`. None found but bot did uncover two usages that are unnecessary because the functions don't panic.
Remove unnecessary `track_caller` attributes on functions that do not panic.
Part of #5518
ACKs for top commit: apoelstra: ACK a1942b52f5efd29a7ed52fd2e77490c24c1809f2; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit removes two Rust compiler hints (`#[track_caller]`) from helper functions that simply return a value or call a user-provided fallback. These functions never panic, so the hints were unnecessary and had no security effect. The change is a minor code cleanup with no functional or security impact.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6644: primitives: Add serde impls for `WitnessVersion`by Andrew Poelstra · 4981faa7 · Aug 5, 2026 · 2 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6644: primitives: Add serde impls for `WitnessVersion`
3f4adcb9c64a0165b270d7636d9469c0894a6157 Update API files (Mitchell Bagot) 394a351c38dc0b05ad2cd3a8b23fa8f96a30e65f Add tests to cover new serde traits (Mitchell Bagot) ffbdf5729dc87587782883d1895cb5de4d292240 Add serde impls for WitnessVersion (Mitchell Bagot)
Pull request description:
The WitnessVersion type in primitives should have serde trait impls, per the C-SERDE guideline.
Add serde Serialize and Deserialize impls for WitnessVersion.
Contributes to #6630
ACKs for top commit: tcharding: ACK 3f4adcb9c64a0165b270d7636d9469c0894a6157 apoelstra: ACK 3f4adcb9c64a0165b270d7636d9469c0894a6157; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit adds standard serialization/deserialization support for the WitnessVersion type when the optional serde feature is enabled. It is a routine feature addition with no security relevance visible in the code or commit message.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktimeby Andrew Poelstra · 6ea4ff92 · Aug 5, 2026 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktime
8867fe2e37f3fcd9e60a763c5e6911445ccdd13e units: reword docs to block count in relative locktime (satsfy (Renato Britto))
Pull request description:
This is a philosophical PR based on [this comment](https://github.com/rust-bitcoin/rust-bitcoin/issues/3632#issuecomment-5160990873). It rewrites the remaining spots that mention relative locktime docs to say block count instead of block height, because a relative lock counts blocks elapsed since the UTXO was confirmed, it is not a chain height.
The goal is to make locktime usage crystal clear to the user. The wording choice regarding lock times is unfortunate.
ACKs for top commit: apoelstra: ACK 8867fe2e37f3fcd9e60a763c5e6911445ccdd13e; successfully ran local tests tcharding: ACK 8867fe2e37f3fcd9e60a763c5e6911445ccdd13e
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI analysis · Informational 15/100
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 coin was created, not an absolute position in the blockchain. No code behavior changed, so there is no security impact.
The labeller runs in a separate workflow for security reasons, but this forces the `download-artifact` action to need an explicit token.
Here is a test end to end run on my remote: https://github.com/nyonson/rust-bitcoin/pull/5
ACKs for top commit: apoelstra: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756; successfully ran local tests; sure, whatever satsfy: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756 tcharding: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege statedocumentation-only discountmerge-commit duplicate discount
AI analysis · Informational 15/100
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, user-facing behavior, or introduce a security vulnerability.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
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.
Lower-priorityprimitives: Add track_callerby Tobin C. Harding · 789315db · Aug 5, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Tobin C. Harding
primitives: Add track_caller
Audit `primitives` with Claude for missing instances of `track_caller`. Just one found.
Add `track_caller` to the macro defined `index` function.
Security candidateMerge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decodingby Andrew Poelstra · c5fd1832 · Aug 5, 2026 · 5 filesMessage 100 · StrongInformational 21Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decoding
b0eba4c097ca68da53abbbaf8603a5facd7c82bd Rename Error to DecodeCheckError (Mitchell Bagot) 7e6ab80baf795c9985d63c35d54b622ec59daa0a Add tests for decode_check_to_array (Mitchell Bagot) ae6ea3616fd6de3fb8cd976346d0b5d9a537abc7 base58: Add decode_check_to_array (Mitchell Bagot) 0a70c578514c3ecfedac508045397b627071e265 Split decode into build_base256 (Mitchell Bagot)
Pull request description:
At present, base58 has only encoding functionality in no-alloc builds. In order to allow decoding of known size data from base58 without an allocator, the base58 crate needs a decoder function like hex's decode_to_array. Such a function has more failure modes than the alloc decode_check function, so new error types are required also.
- Patch 1 splits the existing decode function into a private build_base256 function that writes to a provided scratch buffer. - Patch 1 introduces decode_check_to_array function for decoding short (<128 char) base58 strings to byte arrays, and associated error types. - Patch 2 adds tests to cover the new function. - Patch 3 renames Error to DecodeCheckError, retaining a deprecated type alias.
ACKs for top commit: tcharding: ACK b0eba4c097ca68da53abbbaf8603a5facd7c82bd apoelstra: ACK b0eba4c097ca68da53abbbaf8603a5facd7c82bd; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
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 deprecated alias for backward compatibility. The changes are mostly refactoring and API expansion; there is no direct evidence of a security vulnerability being fixed.
Security candidateMerge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0by Andrew Poelstra · 0f68fcb3 · Aug 4, 2026 · 10 filesMessage 93 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0
8899dfd242cf418ee6ce3f05e5828e8579af9f3c release bitcoin_hashes 1.2.0 (Andrew Poelstra) 44552e3ad3035e1001b665bfd4dd3511042cd1f2 hashes: update API files (Andrew Poelstra) 7d8f06d256152a3de1ec9b54e3dd643271983f0d hashes: add several methods to sha256::Midstate for computing them in const contexts (Andrew Poelstra) dc21841b46abc39c49ed7075131f1ac46416137f hashes: add sha256::Midstate::SHA256_IV constant (Andrew Poelstra)
Pull request description:
Adds a new `Midstate::SHA256_IV` constant which allows you to construct a midstate equivalent to a new empty sha256 engine. Then adds `update` methods to `Midstate` which allow you to "ratchet forward" arbitrary midstates, 64 bytes at a time, by hashing the data. There is one fast method and two slow constfn methods.
The motivation is that in Elements we have many Merkle roots which are computed using sha256 midstates, which is safe to do because we're using domain-separated hashes and because our internal nodes are always hashes of exactly 64 bytes of data, which do not not need any length-suffixing. In rust-simplicity we have several such Merkle root types, many of which have a huge pile of precomputed constants, but whose constructors are forced to be non-`const`, which limits their use in generic contexts.
It's maybe a bit uncouth for me to just add some methods I need and cut a new release in a 1.x crate, but
* we have taken great pains to keep `hashes` out of other crates' public APIs, so its stability is not as paramount as it would be for encoding or units, say * all the new methods (and one constant) are on the `Midstate` type, which is a "don't touch this unless you are a cryptographer" part of the API and already has some ugly methods * the additions seem pretty reasonable to me, assuming you accept that we have a `Midstate` type at all; essentially they generalize the already-existing `hash_tag` method * I am BDFL of this project
ACKs for top commit: tcharding: ACK 8899dfd242cf418ee6ce3f05e5828e8579af9f3c
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 security bug, fix, or vulnerability. The change expands the public API surface slightly, which is normal for a library release.
Lower-priorityunits: reword docs to block count in relative locktimeby satsfy (Renato Britto) · 8867fe2e · Aug 4, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · satsfy (Renato Britto)
units: reword docs to block count in relative locktime
This commit rewords the remaining spots that mention relative locktime docs to say block count instead of block height.
A relative lock counts blocks elapsed since the UTXO confirmed, it is not a chain height.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100
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. There is no security impact.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` privateby Andrew Poelstra · 07d91f7f · Aug 4, 2026 · 4 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` private
9c391145fa57dc54e6af1f18758db4e0ba2049de Update the API text files (Tobin C. Harding) b37accc3db1f164a5b3dee7ff6bbd7a2d0af5be4 Make the WitnessesEncoder private (Tobin C. Harding)
Pull request description:
The `WitnessesEncoder` is an auxilary encoder that is used internally within the transaction encoder. It does not need to be public.
Make it private and put the code right below where it is used.
ACKs for top commit: apoelstra: ACK 9c391145fa57dc54e6af1f18758db4e0ba2049de; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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 closer to where it is used. There is no security bug being fixed here.
Security candidateci: fix labeller permissionsby Nick Johnson · 715f2bd6 · Aug 4, 2026 · 1 fileMessage 75 · AdequateInformational 12Details
Commit message · Nick Johnson
ci: fix labeller permissions
The labeller runs in a separate workflow for security reasons, but this forces the download-artifact actoin to need an explicit token.
75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Informational 12/100
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 repository for command-line GitHub operations. There is no change to the Rust Bitcoin library code that end users or applications depend on.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`by Andrew Poelstra · ed5f1b68 · Aug 4, 2026 · 8 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`
6ea25bed2982858815abeb8788f12f342584108b Update API files (Mitchell Bagot) f9b08eb1fb1ec6871d144f16c6fdad3d13d9b552 Remove From<u16> from NumberOfBlocks (Mitchell Bagot)
Pull request description:
The NumberOfBlocks type has a From\<u16> impl on it, which is used to simplify construction of the type in various tests. However, the from_height constructor already takes a u16 and functions identically. Since the NumberOf512Seconds type has no such From impl, it should be removed from this to reduce the API surface and make the two consistent.
Remove From\<u16> impl from NumberOfBlocks.
ACKs for top commit: apoelstra: ACK 6ea25bed2982858815abeb8788f12f342584108b; successfully ran local tests tcharding: ACK 6ea25bed2982858815abeb8788f12f342584108b
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI analysis · Informational 19/100
This is a routine API cleanup, not a security fix. The developers removed a shortcut that let programmers create a 'number of blocks' value directly from any u16 number, replacing it with an existing named constructor called from_height. The behavior of the code is unchanged; only the way callers write it is slightly different. There is no vulnerability here.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logicby Andrew Poelstra · c5588ba5 · Aug 4, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logic
80dcef1527479e2e0790bf5995636b7640bb56f8 Scrub the transaction encoding logic (Tobin C. Harding)
Pull request description:
Third time lucky. Layout the encoding code in `transaction` as is now customary. (`Transaction` was done but I missed the others.)
Code move only.
ACKs for top commit: apoelstra: ACK 80dcef1527479e2e0790bf5995636b7640bb56f8; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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 security properties were changed.
