rust-bitcoin

This is a small performance improvement in the rust-bitcoin library's SHA256 double-hash code. It replaces a slower fallback code path with a faster, already-existing internal implementation when advanced CPU features are not available. There is no indication of a security bug or vulnerability.

This commit adds a new, highly optimized software-only implementation for computing a double SHA-256 hash on exactly 64 bytes of data. It is intended as a fallback for older CPUs that lack hardware-accelerated hashing instructions. There is no indication in the commit that this fixes a security bug; it appears to be a performance or portability improvement.

This commit is purely a code-formatting cleanup. It runs rustfmt across several files, which only changes whitespace, line breaks, and the order of import statements. No program logic, security checks, or behavior were changed.

This commit fixes a timing attack weakness in the ChaCha20-Poly1305 decryption code. Previously, the code compared the authentication tag using Rust's normal `==` operator, which can stop early when it finds a mismatch. That early-stop behavior can leak information about how much of the tag is correct if an attacker can measure tiny timing differences. The patch replaces it with a constant-time comparison that always scans all 16 bytes, so no timing information about the tag's contents is revealed.

This commit adds a small convenience method called `with_compressedness` to a public-key type in the rust-bitcoin library. It lets callers flip whether a Bitcoin public key is stored in compressed or uncompressed form without having to reach into lower-level secp256k1 cryptography types. The change is purely an API usability improvement and does not fix any bug or vulnerability.

This commit is a routine internal cleanup in the rust-bitcoin crypto library. It removes an older helper method named with_serialized from LegacyPublicKey and replaces its uses with a newer, simpler method called to_bytes. There is no indication of a bug fix or security patch in the change itself or the commit message.

This commit is a routine code reorganization. It moves two existing error types (SigFromSliceError and ParseSignatureError) into a new 'error' submodule within the taproot module and re-exports them publicly. There is no change to how signatures are validated, parsed, or what errors are returned. It is purely a structural cleanup to match the project's coding patterns.

This commit only fixes code style and documentation lint warnings in the crypto::taproot module. It adds missing documentation comments and formats an existing doc comment. There are no changes to program logic, security behavior, or cryptographic operations.

This commit is a routine code reorganization: it moves the Taproot signature types from the main `bitcoin` crate into a separate `crypto` crate and re-exports them so existing users keep working. There is no security fix or behavior change visible in the diff.

This commit removes two helper methods that wrote Taproot signatures to an output stream. It is a routine internal API cleanup to eliminate an unnecessary dependency on the `io` crate inside the crypto taproot module. There is no security vulnerability here; the change simply mirrors a prior cleanup done for ECDSA signature types.

This commit only updates generated API snapshot files that record what public functions and traits the library exposes. The actual code changes happened in an earlier commit; this one just refreshes the snapshots. There is no security-relevant change here.

This commit only updates a configuration file used by a mutation-testing tool. It tells the tool to skip certain automatically generated tests for a helper method. There is no change to the actual Bitcoin library code, no bug fix, and no security relevance.

This commit is a routine code cleanup that fixes compiler/style lints. It removes an unused helper constructor in a test file and makes a few type names explicit instead of relying on type inference. There is no security-relevant change.

This commit is a routine cleanup: it removes dozens of identical-looking helper functions that were made unnecessary by a previous change. There is no security issue here. The code still decodes data the same way; it just relies on a shared default implementation instead of repeating the same boilerplate in every file.

This commit is a routine internal code cleanup in the Rust Bitcoin library. It changes how decoders are created so that Rust's built-in Default mechanism is used instead of manually writing a decoder() function for every type. There is no change to how data is parsed, no bug fix, and no security relevance.

This commit only changes a CI (continuous integration) shell script that checks whether all types implementing a certain encoding trait are covered by fuzz tests. It adds a second check for roundtrip fuzz targets and updates comments and variable names. There is no change to the actual Bitcoin library code, cryptography, network handling, or any user-facing behavior. It is purely a testing/quality-assurance improvement.

This commit only adds new fuzz testing targets and updates build/CI configuration to run them. It does not change any production library code, so it cannot introduce a runtime security vulnerability in the released crate. It is a testing infrastructure change.

This commit only adds new fuzz-testing scripts and helper code. It does not change any production library code, fix a bug, or alter behavior visible to users. It is a testing/infrastructure addition meant to catch encoding bugs in the future, not a security patch for an existing issue.

This commit fixes a regression in the Bitcoin peer-to-peer message decoder. The old decoder verified that the number of bytes actually decoded matched the payload length declared in the message header, but a newer implementation skipped that check. The patch reintroduces the check by wrapping the inner decoder: it now counts consumed bytes and returns a new 'PayloadLengthMismatch' error if the decoded length does not match the header's claim. Without this check, a malformed or malicious message could be accepted even if its actual contents did not match the announced size, potentially causing parsing confusion or protocol issues.

This commit is a routine code reorganization for the rust-bitcoin crypto crate. It makes more modules available when the optional 'alloc' memory allocator feature is disabled, so the crate can be used in constrained environments. There is no indication of a security bug being fixed.

This commit simply moves existing unit tests from one place in the codebase to another. It does not change any production code, behavior, or fix any bug. There is no security impact.

This commit is a small internal cleanup in the rust-bitcoin library. It changes how an error message stores the unrecognized text a user typed, switching from a standard String to a special no-allocation string wrapper called InputString. The visible effect is only a slight rewording of the error message shown when someone types an invalid sighash type. There is no security vulnerability being fixed here.

This commit only updates a generated text file listing the public API surface of the crate. It records that an internal ArrayVec type now implements standard serde serialization/deserialization traits. The diff itself contains no source code changes, no bug fixes, and no behavior changes.

This commit adds the ability to serialize and deserialize a small fixed-capacity vector type (ArrayVec) used inside the rust-bitcoin library. It is a routine feature addition with explicit guards against overflowing the capacity during deserialization. There is no indication this fixes a security bug or introduces a vulnerability.

This commit removes two PSBT (Partially Signed Bitcoin Transaction) fuzz testing targets from the project's automated fuzzing setup and adds a clarifying comment about why an explicit version number is needed for a local dependency. There is no change to the actual Bitcoin library code that users rely on, and nothing in the commit suggests a security vulnerability was fixed or introduced.