0516ddeb8d
Add code to the CI script, guarded on env var `DO_FMT` to run the formatter. Add a formatting job to the nightly CI job as a separate step, in a similar fashion to how the other nightly steps are done. |
||
---|---|---|
.github/workflows | ||
contrib | ||
examples | ||
githooks | ||
no_std_test | ||
secp256k1-sys | ||
src | ||
tests | ||
.gitignore | ||
CHANGELOG.md | ||
Cargo.toml | ||
LICENSE | ||
README.md | ||
clippy.toml | ||
rustfmt.toml |
README.md
rust-secp256k1
rust-secp256k1
is a wrapper around libsecp256k1,
a C library by Pieter Wuille for producing ECDSA signatures using the SECG curve
secp256k1
. This library
- exposes type-safe Rust bindings for all
libsecp256k1
functions - implements key generation
- implements deterministic nonce generation via RFC6979
- implements many unit tests, adding to those already present in
libsecp256k1
- makes no allocations (except in unit tests) for efficiency and use in freestanding implementations
Contributing
Contributions to this library are welcome. A few guidelines:
- Any breaking changes must have an accompanied entry in CHANGELOG.md
- No new dependencies, please.
- No crypto should be implemented in Rust, with the possible exception of hash functions. Cryptographic contributions should be directed upstream to libsecp256k1.
- This library should always compile with any combination of features on Rust 1.41.1.
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.
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 --features=recovery
.
Fuzzing
If you want to fuzz this library, or any library which depends on it, you will
probably want to disable the actual cryptography, since fuzzers are unable to
forge signatures and therefore won't test many interesting codepaths. To instead
use a trivially-broken but fuzzer-accessible signature scheme, compile with
--cfg=fuzzing
in your RUSTFLAGS
variable.
Note that cargo hfuzz
sets this config flag automatically.