rust-bitcoin

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.

This commit only expands the project's API test file. It adds more type coverage, checks that Debug output is non-empty for additional types, and verifies that a specific error type can be formatted with Debug. There are no changes to production code, no bug fixes, and no security-related behavior changes.

This commit simply turns on an existing, faster way to calculate Merkle roots for Intel/AMD (x86 and x86_64) processors. It was already enabled for ARM64 (aarch64). There is no security bug here; it is a small performance portability change.

This commit fixes a typo in a code comment. The comment on the decoder for the older Bitcoin address message format (AddrV1) incorrectly said it decoded the newer format (AddrV2). No actual code behavior changed.

This commit adds a performance optimization for computing SHA-256 hashes on modern x86 processors that support Intel's SHA-NI instructions. It is a routine feature addition, not a security fix or vulnerability patch. There is no indication in the commit that it addresses a security issue.

This commit is a performance optimization for Bitcoin's double-SHA256 hashing on modern Intel/AMD processors. It rewrites a low-level routine to compute two independent hashes at once instead of one, filling idle CPU cycles. There is no security fix or vulnerability here; it is purely about making hashing faster.

This commit adds a new, highly optimized x86 implementation for computing a double SHA-256 hash (SHA256d) on exactly 64 bytes of input. It uses Intel SHA-NI CPU instructions and precomputed constants to speed up Bitcoin-style hashing. There is no indication in the commit that this fixes a security bug; it appears to be a pure performance optimization.

This change is purely about making more error types publicly visible from a Rust library module. It does not alter how errors are handled, what data they contain, or any runtime behavior. There is no security issue here.

This is a minor code-quality fix inside test code only. It adjusts the way optional Rust features are checked so that a warning about an unused import disappears when building with only the 'alloc' feature. There is no change to production code and no security impact.

This commit only changes comments in the SHA-256 code. It makes the round-number labels consistent between different versions of the optimized code (ARM and x86). No actual program logic, math, or behavior was changed, so it cannot affect security or correctness.

This commit updates an internal shell script used to generate a Rust test file. The script now also checks that types from a secondary crate (`bitcoin_units`) are correctly re-exported by the main `bitcoin` crate. It is a build/test tooling improvement with no runtime code changes and no security relevance.

This commit adds missing public re-exports of types in the main 'bitcoin' crate so that downstream users can access types that are defined in the internal 'primitives' and 'units' crates. It is a build/API consistency fix with no apparent security relevance.

This commit refactors how Bitcoin peer-to-peer network messages are encoded and decoded in the rust-bitcoin library. It replaces an older, all-in-one encoding approach with a new system that delegates encoding and decoding to type-specific handlers for each message variant. The change is primarily a code modernization and cleanup, but because it touches the core message parsing path, any mistake could affect how the library reads untrusted network data. The diff itself does not appear to introduce an obvious vulnerability, but it is a large rewrite of security-sensitive parsing code, so the risk comes from potential subtle behavioral differences rather than from a clear bug.

This commit is a pure file reorganization: it splits the SHA-256 cryptographic implementation from one large file into several smaller files. The author explicitly states there is no logic change, and the diff shows the same code being moved into new modules with only minor module wiring adjustments. There is no security-relevant change visible.

This commit simply removes a two-line TODO comment from a test file. No code behavior changes, no security fix or vulnerability is introduced.

This commit only updates a test file. It adds two new data types (Target and Work) to an existing regression test that checks serialization behavior, and refreshes a binary test fixture. There is no change to production code, no security fix, and no vulnerability.