rust-bitcoin

This commit adds a normal 'pop' method to a small internal vector-like data structure called ArrayVec. It is a routine API addition to make the type behave more like Rust's standard Vec. There is no indication of a security bug or fix.

This commit only adds text to a changelog file. It copies release notes for versions 0.32.6 and 0.32.7 from a maintenance branch into the master branch. No program code was changed, so this commit by itself cannot introduce a security vulnerability or fix one.

This commit is a routine packaging fix for the rust-bitcoin project's `io` subcrate. It adds missing version numbers to internal dependencies in the crate's manifest file (Cargo.toml) so the crate can be published to the Rust package registry. There is no code change, no security fix, and no vulnerability addressed.

This commit is a code reorganization, not a security fix. It moves block validation helpers (Merkle root checks, witness commitment checks, and the validate() method) from an extension trait in the higher-level bitcoin crate directly onto the Block<Unchecked> type in the lower-level primitives crate. The goal is to simplify the public API and remove a workaround trait that existed only because of crate-dependency ordering. The actual validation logic is preserved, with only minor implementation changes such as using a different helper to encode the witness root into the hash engine.

This commit adds standard Bitcoin consensus encoding and decoding support for WitnessMerkleNode, a data type used when computing witness commitments in SegWit blocks. It mirrors the existing support already present for TxMerkleNode. There is no indication this fixes a vulnerability; it appears to be a routine API completeness change.

This commit is a routine internal code reorganization. It moves a helper method, is_coinbase, from one module to another within the same project. The method's logic and behavior are unchanged, and there is no indication of a security fix or vulnerability.

This commit is a routine internal code reorganization. It moves the existing Merkle tree helper trait and transaction identifier abstraction from the main `bitcoin` crate into the lower-level `primitives` crate, and adds public wrapper functions and tests. The actual Merkle root calculation logic is copied verbatim, with no functional change.

This commit only adds a missing changelog entry for a previously released version (io 0.1.3). No code was changed, so it cannot introduce or fix any security issue.

This commit is a routine version bump for the bitcoin-io crate from 0.2.0 to 0.3.0. It updates version numbers in package manifests, lockfiles, a dependency reference, and fills in the release date and placeholder deprecation version strings. There are no code behavior changes and no security fixes or security-relevant changes in the diff itself.

This commit is a routine code reorganization. It moves a helper macro that generates standard methods for array-like types from the main `bitcoin` crate into the shared `internals` crate. The goal is to let other crates (specifically `p2p`) use the macro without depending directly on `bitcoin`. The generated behavior is essentially unchanged, though a couple of deprecated `to_bytes` methods are moved from the macro into individual type definitions.

This commit is a routine version bump for the bitcoin_hashes crate from 0.17.0 to 0.18.0. It updates version numbers in package manifests, lock files, and adds a changelog entry. There is no code change and no security relevance visible in the diff.

This commit removes an old, already-deprecated error type called FromSliceError from the rust-bitcoin hashes crate. The function that used to return this error was removed in an earlier version, so this change just cleans up leftover code. It is a routine API cleanup, not a security fix.

This commit is a small API cleanup, not a security fix. It changes a Bitcoin data-encoding helper so it accepts ordinary memory sizes (usize) instead of a special internal type. The only behavioral change is on hypothetical future 128-bit computers, where impossibly large values would be encoded as the maximum allowed u64 value. On all current systems the output is unchanged.

This commit only updates documentation comments and a test comment in the rust-bitcoin hashes crate. It replaces outdated references to a removed 'GeneralHash' trait with descriptions of the actual current requirements. There are no code behavior changes.

This commit is a routine code-quality improvement. It marks a number of simple constructor and getter functions as 'const', which lets the Rust compiler evaluate them at compile time. There is no change to what the functions do, no bug fix, and no security-relevant behavior change.

This commit is a routine code-quality improvement. It marks several simple constructor and getter functions as 'const', meaning they can be evaluated at compile time. There is no change to program logic, no bug fix, and no security relevance.

This commit only updates a Markdown documentation file listing the project's crates. It adds two new crate names (`consensus_encoding` and `crypto`) to a descriptive list. There are no code changes, no bug fixes, and no security-related content.

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.