rust-bitcoin

This commit is a routine version bump for an internal Rust library called `bitcoin-crypto` from version 0.1.0 to 0.2.0. It updates version numbers in package files, lock files, and a changelog. There are no code changes that fix or introduce security behavior.

This commit removes the entire PSBT (Partially Signed Bitcoin Transaction) module from the rust-bitcoin library on the master branch. It is a planned code cleanup, not a security fix. The PSBT functionality has been moved to a separate crate called psbt-v2, and the old module was already deprecated in a previous release. Users who relied on the built-in PSBT support will need to migrate to the new crate when upgrading.

This commit only updates internal fuzz testing code to use a newer encoding/decoding helper crate. It does not change any production code that real users or network peers would run, and it does not fix or introduce any security vulnerability.

This commit adds a new performance optimization for SHA-256 hashing on modern x86 processors that support AVX2 instructions. It enables the library to process up to 8 hash calculations at once when the CPU supports it. There is no indication in the commit that this fixes a security bug; it appears to be a routine performance improvement.

This commit is a code cleanup in the SHA-256 hashing implementation. It replaces roughly 1,000 lines of manually repeated hashing steps with a few short macros that generate the same instructions. The author explicitly states there is no behavior change, and the diff only restructures existing operations without altering constants, math, or control flow.

This commit adds a new, highly optimized implementation of the SHA256d hashing algorithm for 64-byte inputs, using Intel AVX2 processor instructions. It is a pure performance optimization that computes eight hashes at once. There is no indication in the commit that it fixes a security bug; it simply adds a faster code path.

This commit is purely a code-formatting cleanup. It only changes whitespace, line breaks, and import order to match the project's style rules. No program logic, behavior, or security properties were changed.

This commit is a simple rename of internal functions from 'flush_to_writer' and 'flush_to_vec' to 'drain_to_writer' and 'drain_to_vec'. The word 'flush' was confusing because it normally means something specific in I/O code, so the team chose 'drain' instead. No behavior changed, and there is no security issue.

This commit is a minor code cleanup: it moves a Rust import statement (`use core::fmt;`) from one feature-gated code block to another. The change fixes a compiler lint warning and does not alter any program behavior or security logic.

This commit is a routine cleanup that removes an unused dependency called bitcoin-io from the crypto crate. It only touches package metadata and lock files, not any code that handles keys, signatures, or user data. There is no security issue visible in this change.

This commit removes convenience methods for reading and writing public keys from/to byte streams in the rust-bitcoin crypto crate. It is a routine API cleanup to reduce dependency on the bitcoin-io crate, not a security fix. There is no evidence in the commit or supplied references that this change addresses a vulnerability.

This is a routine internal API cleanup in the rust-bitcoin hashing library. A helper function that feeds data into a hash calculator is changed so callers pass in the calculator by mutable reference instead of handing it over and getting it back. No security vulnerability is present in the diff; it is a usability and ownership-style refactor.

This commit adds a new performance optimization for SHA-256 hashing on modern x86 processors. It introduces a code path that processes four blocks at once using SSE4.1 instructions when available. There is no indication in the commit that this fixes a security vulnerability; it appears to be a routine performance improvement.

This commit is a code cleanup in the Bitcoin library's SHA-256 hashing code. It replaces roughly 1,000 lines of manually repeated calculation steps with a few short macros that generate the same steps automatically. The author explicitly calls it a refactor with no behavior change, and the constants and arithmetic operations appear unchanged.

This commit adds a new, faster way to calculate SHA256d hashes for 64-byte inputs on modern Intel/AMD processors using SSE4.1 CPU instructions. It is a pure performance optimization and does not appear to fix or introduce a security vulnerability based on the code shown. However, because it is new cryptographic code, any bug in it could in principle produce wrong hash results, which would be a correctness issue rather than a direct security flaw.

This commit only changes documentation wording for a Rust Bitcoin data type. It adds a note that the serialized legacy public key type avoids heap allocation and has a maximum size of 65 bytes. No code behavior was altered.

This commit removes two helper methods that wrote ECDSA signatures to a custom I/O writer. It is a straightforward API cleanup to drop a dependency, not a security fix. There is no evidence of a vulnerability being patched.

This commit is a small internal cleanup in the rust-bitcoin library. It stops using a PSBT-specific deserialization helper to build test-only 'Arbitrary' instances of TapTree, and instead builds the tree directly from its internal NodeInfo. It also switches serde derives to use the proper serde::Deserialize trait. There is no direct evidence this fixes an exploitable security bug, but it removes a confusing and potentially incorrect reuse of PSBT serialization logic outside the PSBT module.

This commit is a pure code cleanup in the rust-bitcoin library's 'units' module. It reorders where encoder and decoder definitions appear in six source files so that the Encodable and Decodable trait implementations come before the macro-generated encoder/decoder structs. No behavior, logic, or security properties change; it only makes the layout consistent.

This commit only adds new unit tests for the existing hexadecimal encoding/decoding code. It does not change any production logic, so it cannot introduce or fix a security vulnerability on its own.

This commit is a simple internal code reorganization. It moves the SerializedLegacyPublicKey type from the main bitcoin crate into the lower-level crypto crate and re-exports it so existing code keeps working. No behavior changes, no bug fixes, and no security implications are visible in the diff.

This is a small internal code cleanup in the rust-bitcoin library. It changes how one public-key wrapper type exposes its underlying byte slice, removing a dependency on another type (PushBytes) so the code can be moved between crates more easily. There is no user-visible behavior change and no security fix.

This commit removes automatic error-conversion shortcuts in the crypto module of the rust-bitcoin library. It does not fix a bug or vulnerability; it is a deliberate API cleanup to avoid promising too much to future users. Existing code that relied on the removed conversions will need minor updates, but runtime behavior is unchanged.

This commit simply makes several existing key types easier to import by re-exporting them at the top level of the crypto crate. It does not change any behavior, logic, or security properties of the code.

This change simply re-exports a few internal Rust crates through the public API of the `crypto` sub-crate so users don't have to add those dependencies manually. It is a routine dependency-management and API-ergonomics patch with no apparent security relevance.