rust-bitcoin

This commit only changes build configuration files (Cargo.toml and lock files) to add a new internal crate dependency. It does not modify any executable code, fix a bug, or address a security issue. It is a routine refactoring step to resolve a dependency direction problem during library development.

This commit refactors how BIP-32 child key indexes are represented in the rust-bitcoin library. Previously, the index was a public enum with separate fields for normal and hardened variants, and the commit message notes a FIXME: because those fields were public, callers could directly create an out-of-range index (for example, a 'normal' index with the high bit set). The change turns the type into a private newtype around a raw u32 and forces construction through checked constructors that validate the range. It is a defensive hardening change that closes a potential invariant violation, but it does not by itself fix a demonstrated exploit.

This commit adds a scheduled GitHub Actions workflow that runs once a week to check for new releases of an internal maintainer tool (cargo-rbmt). If a newer release exists, it automatically opens a pull request updating a version-tracking file. There is no user-facing code change, no bug fix, and no security-sensitive behavior introduced.

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and brace style in five files. There are no functional code changes, no bug fixes, and no security-related alterations.

This change is a routine code cleanup, not a security fix. It removes an overly broad feature gate so that parts of the Taproot cryptographic module are available even when the optional 'alloc' feature is disabled, while keeping functions that actually need memory allocation behind the gate. There is no indication it fixes a vulnerability.

This commit is a small internal cleanup in the rust-bitcoin library. It changes how a Taproot signature is parsed from a hexadecimal string so that it no longer needs to allocate a temporary byte vector. The change removes an unnecessary memory allocation but does not alter the allowed signature formats or fix any vulnerability. It is a performance and dependency-reduction refactor, not a security fix.

This commit is a routine dependency cleanup. The project previously had to use two different versions of the same hex-encoding helper library (one stable, one unstable preview) because a needed feature was only available in the unstable version. Now that the stable library released version 1.1.0 with that feature, the commit removes the unstable dependency and switches everything to the single stable version. It is not a security fix and does not change how the software behaves to users.

This commit adds a standard trait implementation that lets the Hmac type be used with property-testing tools. It is a routine feature addition, not a security fix or vulnerability.

This commit is a routine API cleanup in the rust-bitcoin crypto library. It removes a method called as_inner that returned a reference to the underlying key data, and replaces internal uses with to_inner, which returns the key by value. The underlying key type is small and cheap to copy, so this is a consistency improvement, not a security fix. There is no indication this change addresses a vulnerability.

This commit narrows the visibility of internal helper methods named to_inner on Bitcoin public-key types. Previously any outside code could call these methods to extract the raw underlying secp256k1 key objects; now only code inside the same module can do so. This is a defensive encapsulation change that reduces the public API surface and makes future misuse or accidental exposure of internal cryptographic details less likely. It is not a fix for an active vulnerability.

This commit only changes the capitalization of hash algorithm names in comments and documentation strings (for example, 'sha256' becomes 'SHA256' and 'sha256d' becomes 'SHA256d'). No program logic, code behavior, or security properties were modified.

This commit only fixes typos and formatting in documentation comments and test file comments. No code behavior changes.

This commit is a routine code reorganization. It moves one function, `from_key_and_merkle_root`, out of a low-level crate (`taproot-primitives`) and into a higher-level crate (`bitcoin`) as an 'extension trait.' The goal is to remove an internal dependency so the low-level crate can stabilize sooner. The actual computation performed by the function is unchanged.

This is a minor internal code cleanup in a Rust formatting helper. It changes one function from borrowing a small value to copying it, following a common Rust style suggestion. There is no security relevance.

This commit only fixes code style and documentation warnings (lint errors) in the key-expression crate. It adds missing documentation comments, marks some functions with #[must_use], rewrites number literals with underscores, and makes minor test helper signature changes. There is no change to runtime behavior or security logic.

This commit is a routine code reorganization: it moves the BIP-32 (hierarchical deterministic wallet key) module from the main `bitcoin` crate into a new lower-level `key-expression` crate, then re-exports it so existing users of `bitcoin::bip32` see no change. There is no evidence in the commit of any security bug, vulnerability fix, or behavior change.

This is a trivial code cleanup: a developer replaced a wildcard import (`use super::*`) with a single explicit import (`use super::SerializedSignature`) in a small internal module. It has no security relevance; it only makes the code clearer and silences a Clippy lint.

This is a one-word documentation comment fix. It changes an incorrect reference to 'ARM SHA2 intrinsics' to the correct 'x86 SHA-NI intrinsics' in a code comment. No executable code was changed, and there is no security impact.

This commit is a routine performance optimization for SHA-256 hashing on modern CPUs. It rewrites the inner loop so that multiple 64-byte blocks are processed in one go, keeping the calculation state in CPU registers rather than reloading it each time. The change is purely about speed and does not fix or introduce any security-relevant behavior.

This commit is an automated code-formatting run by the rustfmt tool. It only adjusts whitespace and line breaks in four source files, making no changes to program logic, algorithms, or data handling. There is no security relevance.

This is a small code cleanup in how Taproot signatures are printed or formatted as text/hex. It removes a tiny bit of duplicated logic by reusing an existing serialization helper and adds two new formatting traits (LowerHex and UpperHex). There is no security issue visible in the change.

This commit only adds a new unit test for a bug fix that was already applied in the previous commit. It does not change any production code itself. The test verifies that a Taproot signature can be serialized back to the same hex string it was parsed from. Because the actual fix happened earlier, this commit alone does not introduce, fix, or worsen any security issue.

This commit fixes a crash when printing or formatting a Taproot serialized signature. The old code assumed every signature was the maximum possible length, but real signatures can be shorter. When a shorter signature was formatted, the code could panic or crash. The fix checks the actual length and formats with the correct size.

This commit is a routine code cleanup. It removes unnecessary '?' operators in functions that already return a Result. The behavior of the code is unchanged; it just makes the code slightly cleaner and avoids a clippy lint warning.

This commit simply moves the code that handles serializing and deserializing XOnlyPublicKey values (when the optional serde feature is enabled) from one location in the file to another location alongside similar implementations. The actual behavior of the code is unchanged; it is a pure code organization or cleanup change with no security relevance.