rust-bitcoin

This commit simply removes two outdated lines from a code comment. The removed text incorrectly claimed that the function always sets an even parity, but the function actually accepts a parity argument supplied by the caller. There is no code change and no security issue.

This commit is a routine dependency cleanup. It removes the external hex_lit crate and switches test/example code to use built-in hex macros from the project's own hex-conservative crate. There is no user-facing behavior change and no security fix or vulnerability introduced.

This commit is a routine API rename with no security bug. It renames functions in the Rust Bitcoin library that handle private key bytes so their names include the word 'secret' (for example, 'to_vec' becomes 'to_secret_vec' and 'from_byte_array' becomes 'from_secret_bytes'). The goal is to make it more obvious to developers when they are working with sensitive secret material. The actual behavior of the code is unchanged.

This commit is a build-system cleanup, not a security fix. It removes crate-wide switches that made entire Rust sub-crates disappear when the 'alloc' feature was off, and instead marks individual functions and types as requiring 'alloc'. The stated reason is to fix linking problems in no-alloc builds, not to patch a vulnerability. There is no evidence in the commit of an exploitable bug.

This commit fixes a bug in how the library reads PSBT (Partially Signed Bitcoin Transaction) keys. A recent change accidentally made it possible for a malformed input to cause an arithmetic underflow when calculating how many bytes of key data remain. In debug builds that would panic (crash); in release builds it could wrap around and behave incorrectly. The fix uses a safe checked subtraction and returns a proper parsing error instead.

This commit is a maintenance change that switches the project's fuzz testing framework from Honggfuzz to libfuzzer (cargo-fuzz). It updates build files, CI configuration, documentation, and fuzz target source files to use the new framework. There is no change to the actual Bitcoin library code that end users or applications depend on, and no security vulnerability is introduced or fixed.

This change removes the ability to accidentally print a Bitcoin private key using Rust's standard '{}' formatting. Before, code like println!("{}", private_key) would expose the secret key. Now developers must explicitly call .to_wif() or similar methods, making secret leakage less likely through casual logging or error messages. It is a defensive hardening improvement, not a fix for an active exploit.

This commit removes the ability to use square-bracket slicing (like `private_key[..]`) on a Bitcoin private key. The change is part of a longer-term effort to prevent secret key material from being accidentally exposed through Rust's indexing features. It is a hardening cleanup rather than a fix for an active security flaw.

This commit adds a human-readable hex display format for Taproot signatures in the rust-bitcoin library, matching a similar feature already available for ECDSA signatures. It is a straightforward feature addition with tests and does not fix any security bug.

This commit adds a new feature: the ability to parse a Taproot cryptographic signature from a hexadecimal text string. Previously only ECDSA signatures could be parsed this way. The change is purely additive and does not fix any known bug or vulnerability. It simply exposes a new parsing function to users of the library.

This commit is a code-quality and linting cleanup for the `hashes` crate in rust-bitcoin. It moves the crate to use shared workspace lint rules, adds clippy allow attributes, fixes minor style issues (semicolons, doc formatting, import lists), and adds documentation comments. There are no functional changes to hash algorithms or public APIs, and no security bug is introduced or fixed.

This commit simply moves an existing internal Rust macro from one file to another shared location. The code itself is unchanged; it is a pure refactoring to prepare for splitting a crate. There is no security-relevant change.

This commit only changes the wording and formatting of documentation comments at the top of seven source files. It makes crate header titles uniform by adding '#' markers and adjusting capitalization. There are no code changes, no security fixes, and no behavior changes.

This commit only changes two words in code comments, replacing 'Creates' with 'Constructs' in documentation. There is no change to actual program logic, no security fix, and no behavior change.

This is a tiny documentation-style change to an example file. It swaps one way of saying 'use the Bitcoin main network' for another equivalent way, with no effect on actual code behavior or security.

This commit is a routine internal cleanup in the rust-bitcoin library. It swaps one hex-decoding helper for another equivalent one so the library no longer depends on an 'unstable' public API from a dependency. There is no indication this fixes a security bug or changes behavior visible to users in a dangerous way.

This commit swaps out an unstable, experimental hex-decoding helper for a stable, project-owned one. It is a cleanup/refactoring change to keep the public API from depending on a crate version that is not yet finalized. There is no direct security bug being fixed; the main risk is that if done incorrectly, error handling could change slightly for users parsing hex strings.

This commit simply moves existing code around in two files. It relocates the implementation blocks for SHA256 and SipHash24 hash types to appear earlier in their respective files, right after the hash type is declared. No code behavior was changed, no bugs were fixed, and no security issues were introduced.

This commit only moves existing code around in the same file. It takes several implementation blocks for the Hmac type and places them directly below the Hmac struct definition instead of further down after another struct. No code behavior, logic, or public interface was changed.

This is a routine API cleanup, not a security fix. The change removes the requirement for callers to supply their own random number generator when creating a new keypair. Instead, the function now creates the generator internally, matching how the related PrivateKey API already works. There is no vulnerability here; it is a convenience and consistency change.

This commit creates a brand-new, empty placeholder crate named 'bitcoin-key-expression' inside the rust-bitcoin workspace. It contains no code, no logic, and no changes to existing behavior. It is purely a structural preparation step for future development.

This commit is a small API cleanup in a Rust Bitcoin library. It changes one constructor so callers must provide a 'parity' value directly instead of setting it afterward. Existing callers are updated to preserve the same behavior as before. There is no indication this fixes a security bug or changes any security-relevant behavior.

This commit is a routine API cleanup, not a security fix. It changes one function so it takes its input by value instead of by reference, matching normal Rust conventions for small copyable types. There is no bug being fixed and no security relevance stated.

This commit only lowers the minimum required version of a small helper crate called `cpufeatures` in a lockfile used for testing the oldest supported dependency versions. It is a routine housekeeping change with no security relevance.

This commit is a performance optimization for the finalization step of several cryptographic hash functions (RIPEMD-160, SHA-1, SHA-256, SHA-512). It rewrites how padding bytes are added so the code writes directly into an internal buffer instead of calling the general input() function multiple times. The commit message and diff show only speed improvements; there is no indication of a security fix or behavior change in the hash output.