#libsecp256k1 #ecdsa #bitcoin #secp256k1 #crypto

no-std cashweb-secp256k1

Rust bindings for Pieter Wuille’s libsecp256k1 library. Implements ECDSA for the SECG elliptic curve group secp256k1 and related utilities.

3 unstable releases

Uses old Rust 2015

0.20.0 Dec 31, 2020
0.19.1 Jan 2, 2021
0.19.0 Dec 31, 2020
0.17.3 Jul 1, 2020
0.17.2 Jul 1, 2020

#6 in #libsecp256k1

Download history 24/week @ 2024-03-15 23/week @ 2024-03-22 39/week @ 2024-03-29 26/week @ 2024-04-05 22/week @ 2024-04-12 22/week @ 2024-04-19 19/week @ 2024-04-26 17/week @ 2024-05-03 18/week @ 2024-05-10 20/week @ 2024-05-17 15/week @ 2024-05-24 13/week @ 2024-05-31 14/week @ 2024-06-07 19/week @ 2024-06-14 22/week @ 2024-06-21 9/week @ 2024-06-28

66 downloads per month
Used in 7 crates (6 directly)

CC0 license

160KB
3.5K SLoC

Build Status

Full documentation

cashweb-rust-secp256k1

cashweb-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.29.

A note on Rust 1.29 support

The build dependency cc might require a more recent version of the Rust compiler. To ensure compilation with Rust 1.29.0, pin its version in your Cargo.lock with cargo update -p cc --precise 1.0.41. If you're using secp256k1 in a library, to make sure it compiles in CI, you'll need to generate a lockfile first. Example for Travis CI:

before_script:
  - if [ "$TRAVIS_RUST_VERSION" == "1.29.0" ]; then
    cargo generate-lockfile --verbose && cargo update -p cc --precise "1.0.41" --verbose;
    fi

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=rust_secp_fuzz in your RUSTFLAGS variable.

Dependencies

~0.5–1.2MB
~21K SLoC