rust-bitcoin

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.

This commit only adds a new automated test that checks the Debug text representation of two public error types is never empty. It does not change any library code, fix a bug, or alter behavior. There is no security issue in the diff itself.

This commit only adds a new automated test that checks two existing error types implement Rust's standard Error trait. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This commit only adds two lines to a test file, checking that a type called Hkdf can be safely used across threads (Send/Sync). It is purely a test-coverage improvement with no changes to production code, no bug fixes, and no security-relevant behavior changes.

This commit is a routine dependency and API cleanup in the rust-bitcoin project's hashing crate. It swaps an unstable hex-parsing helper for a newly released stable version and updates the error types that downstream code sees. There is no direct evidence of a security vulnerability being fixed; it is best understood as a maintainability and API-stability improvement.

This commit is a routine internal cleanup in the rust-bitcoin project's peer-to-peer (p2p) crate. It swaps some test and internal code from using an unstable version of a hex-encoding helper library to a newly released stable version. There is no user-facing behavior change, no bug fix, and no security fix visible in the diff.

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.