rust-bitcoin

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.

This commit adds a new helper type for storing Bitcoin legacy public keys in their serialized form without needing a heap allocation. It is a routine internal API improvement and does not fix any security bug or change how keys are validated.

This commit only updates a generated text file listing the public API surface of the crate. It records that a new error type, FromHexError, is now part of the public API. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit is a routine code organization change. It makes an existing error type (FromHexError) visible in more places by re-exporting it, so users of the library can import it more conveniently. There is no change to how errors are handled or any security-sensitive behavior.

This commit is a routine code reorganization. It moves an existing error type (ReadError) into a dedicated public submodule and changes how it is re-exported in documentation. There is no functional change to how the code behaves, no bug fix, and no security improvement or regression.

This commit adds symbolic links (shortcuts that point to another folder) inside each Rust crate to a shared 'include' directory at the workspace root, and updates source code to use these symlinks. It is a build/packaging fix so that code shared across crates can be found when the crates are published individually to crates.io. There is no security-relevant change here.

This commit only updates generated API snapshot text files to reflect that two existing types (Target and Work) now also implement Binary and Octal formatting traits in addition to the formatting traits they already supported. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit adds new ways to print two internal numeric types (Target and Work) in binary and octal formats, and reorganizes existing hexadecimal printing code. It is a routine formatting/ergonomics improvement with no security relevance.

This commit only updates generated API text snapshots for the rust-bitcoin 'units' crate. It records that some public error types now use new wrapper types (IncompatibleHeightError/IncompatibleTimeError) instead of raw numeric types. There is no actual code change, no bug fix, and no security-relevant behavior change in this commit itself.

This is a routine code cleanup in the rust-bitcoin library. It wraps two error values inside new dedicated error types so callers can no longer directly read the raw number inside. The change does not alter what errors are produced, only how they are packaged. There is no security fix here.

This commit only updates generated API text files that list what types and functions are publicly visible in the library. It does not change any actual code, behavior, or fix any bug. It is a documentation-like snapshot of the public interface and has no security relevance on its own.