The `hashes` crate has a bunch of similar types defined by a bunch of similar macros and impl blocks, all of which makes it difficult to tell exactly what is implemented where. In an effort to make the code easier to read order the `from_byte_array` constructor in the same place across the crate. Note also we typically put constructors up the top, also `from_byte_array` is the likely most used constructor so put it first. FWIW I discovered this while polishing the HTML docs. Internal change only. |
||
---|---|---|
.. | ||
contrib | ||
embedded | ||
src | ||
tests | ||
CHANGELOG.md | ||
Cargo.toml | ||
README.md |
README.md
Bitcoin Hashes Library
This is a simple, no-dependency library which implements the hash functions needed by Bitcoin. These are SHA1, SHA256, SHA256d, SHA512, and RIPEMD160. As an ancillary thing, it exposes hexadecimal serialization and deserialization, since these are needed to display hashes anway.
Minimum Supported Rust Version (MSRV)
This library should always compile with any combination of features on Rust 1.63.0.
Contributions
Contributions are welcome, including additional hash function implementations.
Githooks
To assist devs in catching errors before running CI we provide some githooks. If you do not already have locally configured githooks you can use the ones in this repository by running, in the root directory of the repository:
git config --local core.hooksPath githooks/
Alternatively add symlinks in your .git/hooks
directory to any of the githooks we provide.
Running Benchmarks
We use a custom Rust compiler configuration conditional to guard the bench mark code. To run the
bench marks use: RUSTFLAGS='--cfg=bench' cargo +nightly bench
.