rust-bitcoin

base58: Add decode_check_to_array

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.

Introduce decode_check_to_array function for decoding short (<128 char)
base58 strings to byte arrays.
Introduce DecodeCheckArrayError.
Adjust error gating such that only errors in the public API appear in
the error module.

Rename Error to DecodeCheckError

The Error type in base58 represents an error that can occur when
decoding a base58check string. Since there now exists the
DecodeCheckArrayError for errors that can occur when decoding in
allocless builds, the main error type should also be renamed to clarify
its exact use.

Rename Error to DecodeCheckError. Add deprecated type alias Error for
DecodeCheckError.

ci: actually capture exit code to pass on to label artifact

ci: fix check semver trap

Use double quotes to capture the local baseline variable in the trap,
even though this is against shellcheck's rules. Also move the trap from
RETURN to EXIT so it only fires once.

ci: migrate semver check labeller to ci labeller

ci: add toggle to api break label

2026-08-02 automated rustfmt nightly

fuzz: fix ci job, install cargo-fuzz first

Add explict bash shell for set -e fail fast default.

Use ${RUSTFLAGS:-} in fuzz.sh so an unset value expands to nothing and
any value the caller did set still gets through.

Co-authored-by: satsfy (Renato Britto) <renatobritto@protonmail.com>

Update API files

Add test to guarantee algebraic transform of Weight

When implementing div and rem, a user should always be able to
reconstruct their original value knowing the divisor, remainder and
division result. That is, if a / b = d, a % b = r, then d * b + r must
equal a.

Add test that checks the inverse of a division and remainder on Weight.

Make Weight % Weight return Weight

The Rem<Weight> for Weight op currently returns a u64. A remainder type
should always match the type itself, as the leftover after a division
is logically a sub-portion of the original quantity, and thus its type.

Adjust Rem<Weight> for Weight impl to return Weight instead of u64.

consensus_encoding: decoder docs which are consensus specific

The decode module has 6 driver functions bound to `Decode`, and thus
are consensus-encoding specific.

- `decode_from_slice<T: Decode>`
- `decode_from_slice_unbounded<T: Decode>`
- `decode_from_hex<T: Decode>`
- `decode_from_read<T: Decode>`
- `decode_from_read_unbuffered<T: Decode>`
- `decode_from_read_unbuffered_with<T: Decode>`
- `check_decode<T: Decode>`

One type is bound to `Decode`.

- `VecDecoder<T: Decode>`

consensus_encoding: update package docs for consensus encoding clarity

consensus_encoding: encoder docs which are consensus specific

The `encode` trait, and things which bound on it, are tied to consensus
encodings. Everything else is agnostic.

There are 4 driver functions tied specifically to `Encode`, and these
are simpler wrappers over the drains bound to the agnostic `Encoder`.

- `encode_to_vec<T: Encode>`
- `encode_to_writer<T: Encode>`
- `encode_to_hex<T: Encode>`
- `check_encode<T: Encode>`

There are two types bound to `Encode`.

- `SliceEncoder<'e, T: Encode>`
- `PrefixedSliceEncoder<'e, T: Encode>`

hashes: add sha256::Midstate::SHA256_IV constant

Add a unit test for the new constant. Rename the internal-only function
compute_midstate_unoptimized to update_midstate_unoptimized, and change
call sites to call it with the new SHA256_IV constant.

This lets us "ratchet forward" arbitrary midstates in const contexts. The
next commit will expose this general functionality in a correct way (by
enforcing lengths). I would like this in rust-simplicity, so I can compute
various Merkle roots in const contexts.

hashes: add several methods to sha256::Midstate for computing them in const contexts

hashes: update API files

Update API files

Add to_target conversion to CompactTarget

According to C-CONV-SPECIFIC, conversion methods should prefer
to/as/into over from, as it allows chaining. Due to CompactTarget being
stabilised before Target, Target currently has methods for converting
both to and from CompactTarget. Instead, a method for converting a
CompactTarget to a Target should exist on the CompactTarget.

Add to_target conversion method to CompactTarget and adjust test cases
to use it to kill mutants.

Update API files

Add tests for NumOpResult sum

To guarantee that the previous change to the sum permits summing over
Amount/SignedAmount, the test cases can be adjusted to also check
the new types.

Add tests to confirm Sum<Amount> and Sum<SignedAmount> to NumOpResult.

Make Sum generic for Signed/Amount -> NumOpResult

The current Sum implementations relating to Amount/SignedAmount only
permit users to sum NumOpResults into a NumOpResult. Since users are
far more likely to begin with an Amount/SignedAmount iterator, the Sum
impl should instead be generic over the source of NumOpResult<Amount>
allowing both summing NumOpResult<Amount> and Amount into a
NumOpResult.

Make Sum on NumOpResult<Amount/SignedAmount> generic to permit summing
over Amount and SignedAmount also.

units: Implement serde traits for relative lock times

To satisfy the API guideline
[C-SERDE](https://rust-lang.github.io/api-guidelines/interoperability.html#data-structures-implement-serdes-serialize-deserialize-c-serde),
data types in a crate must implement serde's `Serialize` and
`Deserialize` traits.

Add custom impls for the relative lock time subtypes. Note we use 512
second intervals for the `NumberOf512Seconds` type and not seconds so
that there is no error path.

Update the API text files

Implement serde traits for absolute locktime types

To satisfy the API guideline
[C-SERDE](https://rust-lang.github.io/api-guidelines/interoperability.html#data-structures-implement-serdes-serialize-deserialize-c-serde),
data types in a crate must implement serde's `Serialize` and
`Deserialize` traits.

Add custom impls for the absolute lock time sub types.