rust-bitcoin

This commit only bumps the version of a small helper library (hex-conservative) used for converting bytes to and from hexadecimal strings. No code behavior in rust-bitcoin itself is changed, and the commit message gives no indication that this is a security fix.

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 simply deletes old fuzzing test input files that were used with the honggfuzz tool. The project has switched to a different fuzzer (libfuzzer), so these files are no longer needed. No code changes were made, and there is no security fix or vulnerability introduced.

This commit fixes missing public re-exports of encoder/decoder types and their error types in the rust-bitcoin crate. It is a packaging/API consistency fix: the bitcoin crate is meant to expose everything primitives exposes, and primitives everything units exposes. The change adds those missing re-exports and updates the test scripts that check this property. There is no indication of a runtime vulnerability, memory corruption, or exploit path.

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 commit simply updates the version of the Rust nightly compiler used by the project's GitHub CI (continuous integration) from one nightly build to a newer one. It changes only one line in a configuration file. There is no code change, no bug fix, and no security-relevant change visible in the diff.

This commit fixes how several Bitcoin data-decoding error types print messages and report their underlying cause. The changes are cosmetic/correctness improvements to error formatting and the `source()` chain used by Rust's standard error handling. There is no evidence of a security vulnerability, remote exploit, or memory-safety bug in the diff.

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 simple internal code cleanup in the Bitcoin peer-to-peer networking code. It renames a generic array-based encoder to a more specific 'CommandStringEncoder' for the 12-byte command strings used in Bitcoin network messages. There is no change to behavior, data formats, or security properties.

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 removes an unused compiler configuration flag from a linting rule in the package manifest. It is a cleanup change with no security relevance.

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 adds missing test coverage for public API surface. It adds a new error type to an existing test struct and a new test that checks public types from the `result` module can be imported. There is no code behavior change, no bug fix, and no security relevance.

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 updates an internal test file that checks the public API surface of the `bitcoin_primitives` crate. It adds missing types (like `Ntxid`, `BlockChecked`, script buffer types) to compile-time API tests and enables a previously commented-out iterator field. There is no change to production code, no bug fix, and no security relevance.

This commit only updates generated API text files to reflect that a new public dependency called `encoding` is now exposed by several Rust Bitcoin crates. There are no code changes, no bug fixes, and no security-related content.

This commit simply makes an internal helper crate (consensus-encoding) visible at the top level of several related Rust crates. It is a routine API-organization change with no security implications.

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 commit simply reorders code in a single Rust source file. It moves the implementation of encoding/decoding traits above the helper 'encoder newtype' struct so the file matches the author's earlier stated intention. There is no functional change, no bug fix, and no security relevance.

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.