rust-bitcoin

This commit is a routine version bump for a Rust package called `bitcoin-consensus-encoding`, moving it from one release candidate (1.0.0-rc.1) to the next (1.0.0-rc.2). It only updates version numbers in package manifests and lock files. There are no code changes, no bug fixes, and no security-related changes visible in the diff.

This commit only adds two new unit tests to verify that two decoder types allocate memory in correctly-sized batches. It does not change any production code, fix a bug, or alter behavior. There is no security-relevant change.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces hand-written ceiling-division logic with Rust's newer built-in `div_ceil` function. The math result is intended to be identical, and there is no indication of a security bug being fixed.

This commit adds a new automated testing step to the project's GitHub Actions CI pipeline. It runs a tool called cargo-mutants on the code changed in a pull request to help detect whether tests are thorough enough. There is no change to the actual Bitcoin library code, no new feature, and no security fix or vulnerability.

This commit fixes two typos in documentation comments. One incorrectly called a private key type an 'extended public key,' and another incorrectly referenced a different struct name in a conversion function's doc comment. These are purely cosmetic comment corrections and do not change any executable code.

This commit is a large but purely cosmetic code cleanup in the Rust Bitcoin library. It removes wildcard imports of error types (like `use Error::*`) and replaces them with explicit `Self::Variant` or fully-qualified names. The behavior of the code does not change; it only makes the source code easier to read and maintain.

This commit only reformats source code using the Rust formatter (cargo fmt). It changes whitespace, line breaks, and import grouping but does not alter program logic, behavior, or any security checks. There is no security issue.

This commit is a routine API cleanup for the rust-bitcoin library. It adds a few helper methods (to_signature, from_signature, len, iter) to the ECDSA serialized-signature type and reorders existing methods in the Taproot serialized-signature type so both types look the same. There is no security fix or behavior change that would affect users' funds or data.

This commit is a minor code cleanup. It imports two common Rust traits (`Borrow` and `Deref`) directly at the top of two source files, instead of referring to them with their full `core::...` module path inside the code. There is no functional change, no bug fix, and no security relevance.

This commit is a small internal code reorganization. It moves an existing conversion helper (so a serialized ECDSA signature can be viewed as a script 'push bytes' object) to a more central location, and adds an equivalent helper for Taproot signatures. There is no security fix or behavior change visible to users.

This commit fixes a bug in how serialized Bitcoin signatures expose their byte content. Previously, code asking for the signature bytes could receive the entire internal buffer, including leftover or uninitialized bytes beyond the actual signature length. Now only the valid, used portion is returned. This prevents accidental misuse where someone might hash, encode, or transmit extra garbage bytes as if they were part of the signature.

This commit removes the ability for outside code to directly modify the raw bytes of an ECDSA serialized signature object in the rust-bitcoin library. Previously, callers could obtain a mutable reference to the internal byte buffer and change it, which the developers consider meaningless because a signature is supposed to be a fixed cryptographic result. The change makes the type consistent with the taproot signature type, which already did not allow mutation. It is a hardening/correctness change rather than a fix for a known exploitable vulnerability.

This commit simply reorders existing code in a Rust source file. It moves two blocks of code (implementations of Deref and DerefMut for SerializedSignature) to a different location within the same file so the order matches another module. No code behavior is changed, no bugs are fixed, and no security issue is introduced.

This commit adds two new ways to display a taproot serialized signature as hexadecimal text (lowercase and uppercase). It is a pure API-consistency change to make taproot signatures match the existing ecdsa signature API. There is no security issue visible in the diff.

This commit adds standard Rust comparison traits (equality and ordering) to a type that wraps a raw ECDSA signature byte array. It simply lets programmers compare these signature objects more conveniently; it does not change signature validation or introduce a security vulnerability.

This commit is purely a code cleanup: it moves some trait implementation blocks for the ECDSA SerializedSignature type to a different location in the same file and reorders the Taproot Eq impl to sit next to PartialEq. No logic, behavior, or signatures changed.

This commit is a straightforward internal code reorganization. It moves the SerializedSignature type from one module to another within the same crate, without changing its behavior or public API. There is no security fix or vulnerability here.

This commit simply reorders two methods inside the same Rust source file so that the taproot signature code matches the layout of the ECDSA signature code. No code behavior, logic, or public API changed. It is a cosmetic cleanup only.

This commit only fixes a documentation comment in the source code. It changes the module description from incorrectly saying it contains Taproot keys to correctly saying it contains Taproot signatures. There is no code change and no security impact.

This commit adds new helper functions for decoding data from a reader in the rust-bitcoin `io` crate. It is a feature addition that copies existing decoding logic from another module and includes tests. There is no indication in the commit or supplied references that this fixes a security vulnerability.

This commit only adds formatting hints to test code so that a code formatter (rustfmt) leaves byte arrays arranged in tidy 8-byte columns. It does not change any behavior, logic, or security-sensitive code.

This commit only corrects two documentation comments that pointed to the wrong module name. It changes no executable code, so it cannot affect program behavior or security.

This commit simply bumps the version number of a CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.44.0 to 0.45.0. It does not change any library code, dependencies shipped to users, or runtime behavior of the rust-bitcoin crate. There is no security relevance visible in the commit.

This commit is a routine maintenance update to the project's fuzz-testing infrastructure. It adds newly-created fuzz test targets to a script that auto-generates configuration files, and refreshes the generated files to match. There is no change to the actual Bitcoin library code that users rely on, and no security fix or vulnerability is present.

This commit removes a redundant feature flag called 'rand-std' from the rust-bitcoin library and replaces its use with the combination of 'rand' and 'std'. It is a cleanup change to make feature selection clearer for users. There is no security vulnerability or bug fix in the code itself.