rust-bitcoin

This commit is a routine version bump for an internal Rust crate. It changes the package version from 0.0.0 to 0.1.0, updates dependency references and lock files, and records the migration of code into the crate in the changelog. There are no code logic changes and no security-relevant behavior changes visible in the diff.

This is a small code-quality change in how a Bitcoin-related Rust library reports parsing errors for a special sighash type. It makes the error message come directly from the underlying Taproot parser instead of being manually rebuilt. There is no direct security vulnerability here, but it slightly improves error-message accuracy and removes a tiny bit of duplicated logic.

This commit is a routine code cleanup in the rust-bitcoin crypto crate. It fixes compiler lint warnings by adding documentation comments, adjusting number formatting, and making minor style changes. There is no functional change to how signatures are created, validated, or parsed, and no security issue is present.

This commit only cleans up style warnings in a Rust source file. It replaces wildcard imports with explicit Self:: references, adds a documentation comment, and fixes a minor formatting issue in a doc comment. There is no change to program behavior or security.

This commit is a routine code reorganization: it moves some Bitcoin signature-hash type definitions (EcdsaSighashType, TapSighashType, and related error types) from the main bitcoin crate into a new bitcoin-crypto sub-crate, then re-exports them so existing users see no change. There is no functional change to how signatures or transactions are validated.

This commit is a simple internal code cleanup in the rust-bitcoin library. It moves two nearly identical helper functions into a shared internal trait, without changing what the code does or how it behaves. There is no security issue here.

This commit is a routine internal code reorganization. It moves the ECDSA signature module from the main 'bitcoin' crate into a smaller 'crypto' sub-crate, then re-exports it so existing users see no change. There is no security fix or vulnerability here.

This commit is a routine internal code reorganization. It moves a low-level ECDSA signing helper method from the main PrivateKey implementation into a new extension trait called PrivateKeyExt, and updates the one place that uses it to import the trait. There is no change to what the code does or any security fix.

This commit is a routine internal code reorganization. It moves a few public-key helper methods into Rust 'extension traits' so the underlying key types can be relocated to a different crate later. The actual behavior of the moved functions is unchanged, and there is no indication of a bug fix or security patch.

This commit is a routine fix to the project's automated fuzz-testing pipeline. It adds an installation step for the 'cargo-fuzz' tool in one CI job and updates a script that generates the workflow file. There is no change to the actual Bitcoin library code that users depend on, and nothing in the commit suggests a security vulnerability or fix.

This is a routine automated update that changes one line in the project's configuration file, bumping the recommended Rust compiler nightly version from April 10, 2026 to April 17, 2026. There is no code change, no bug fix, and no security-related content.

This is a routine code cleanup in an example file. It replaces an old, deprecated method name (`public_key`) with the newer recommended name (`to_public_key`). There is no security issue here; the change only affects example documentation code and does not alter how the library works.

This commit updates a test file to use newer, non-deprecated method names for private key operations. It is a routine code cleanup with no security relevance.

This commit only updates internal test code to stop using two recently-renamed type names (`Height` and `Time`) and instead use their new names (`NumberOfBlocks` and `NumberOf512Seconds`). It does not change any production code, behavior, or data formats, and it is not a security fix.

This commit removes a single duplicate Rust import statement that was causing a compiler lint warning about an unused import. It is a routine code cleanup with no security relevance.

This commit changes how test-only fake data is generated for an extended Bitcoin private key (Xpriv) when the optional 'arbitrary' feature is enabled. Previously, the generator always produced a 'master' key with depth 0. Now it can produce keys at any depth with proper parent fingerprint and child number fields. This is a code-quality/test-coverage improvement; it does not change production key handling or add a security vulnerability.

This is a routine automated update that changes one line in the project's configuration file, bumping the recommended stable Rust compiler version from 1.94.1 to 1.95.0. There is no code change, no bug fix, and no security patch in the diff itself.

This commit adds two convenience methods, `nth` and `peek_chunk`, to a Rust iterator that walks over encoded bytes. It is a routine feature addition with no apparent security relevance. The code includes comments warning callers that using the iterator after it has finished is a bug, but that is normal API documentation, not a vulnerability disclosure.

This commit is a routine internal cleanup in the rust-bitcoin library's data-encoding machinery. It removes unnecessary 'Option' wrappers from several encoder types and stops guaranteeing that encoders return an empty slice after they are exhausted. Instead, calling 'current_chunk()' on an exhausted encoder may now panic in some composite cases. The change is framed by the author as a performance and code-simplification improvement, not as a security fix. There is no evidence in the commit or supplied references of an exploitable vulnerability.

This commit only adds documentation comments to a Rust trait called Encoder. It explains how callers should use the trait, what happens when the encoder runs out of data, and warns that behavior is unspecified after that point. No code logic was changed, so there is no security issue in the commit itself.

This commit adds a new example program to the rust-bitcoin library's p2p crate. It demonstrates how to perform a Bitcoin peer-to-peer handshake and respond to ping messages with pong messages. It is documentation/example code only and does not change any library behavior or fix any security issue.

This commit fixes missing or incorrect public re-exports of error types in the rust-bitcoin crate. It does not change how amounts, locktimes, or transactions are validated; it only changes which error types are visible to downstream users of the library. There is no indication this is a security fix.

This commit only adds new automated tests for Bitcoin hash types. It checks that converting hash values to and from byte arrays and hexadecimal strings works correctly. There are no changes to production code, so it cannot introduce a security vulnerability or fix one.

This commit only adds and improves unit tests for the block module. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit is purely a code-formatting cleanup. It only changes whitespace, import order, line breaks, and trailing blank lines. There are no functional changes, no bug fixes, and no security-related modifications.