3 unstable releases

0.22.3 May 22, 2022
0.21.4 Feb 21, 2022
0.9.2 Jan 16, 2024
0.5.3 May 22, 2022
0.5.2 May 21, 2022

#682 in Development tools

Download history 8/week @ 2024-01-01 12/week @ 2024-01-08 99/week @ 2024-01-15 57/week @ 2024-01-22 3/week @ 2024-02-05 12/week @ 2024-02-12 15/week @ 2024-02-19 41/week @ 2024-02-26 62/week @ 2024-03-04 24/week @ 2024-03-11 16/week @ 2024-03-18 30/week @ 2024-03-25 57/week @ 2024-04-01

108 downloads per month
Used in 18 crates (via sapio-secp256k1)

CC0 license

38K SLoC

C 35K SLoC // 0.0% comments Rust 1.5K SLoC // 0.0% comments GNU Style Assembly 753 SLoC // 0.1% comments Automake 226 SLoC // 0.1% comments Shell 188 SLoC // 0.2% comments Python 75 SLoC // 0.2% comments M4 61 SLoC // 0.1% comments

Contains (obscure autoconf code, 20KB) depend/secp256k1/configure.ac

Rust secp256k1-sys

Crate Info CC0 1.0 Universal Licensed API Docs Rustc Version 1.48.0+

Provides low-level bindings to the C FFI exposed by libsecp256k1.


The default build process is to build using the vendored libsecp256k1 sources in the depend directory. These sources are prefixed with a special rust-secp256k1-sys-specific prefix rustsecp256k1_v1_2_3_.

This prefix ensures that no symbol collision can happen:

  • When a Rust project has two different versions of rust-secp256k1 in its depepdency tree, or
  • When rust-secp256k1 is used for building a static library in a context where existing libsecp256k1 symbols are already linked.

To update the vendored sources, use the vendor-libsecp.sh script: ./vendor-libsecp.sh <rev>

  • Where <rev> is the git revision of libsecp256k1 to checkout. If you do not specify a revision, the script will simply clone the repo and use whatever revision the default branch is pointing to.

Linking to external symbols

Danger: doing this incorrectly may have catastrophic consequences!

This is mainly intended for applications consisting of various programming languages that intend to link the same library to save space, or bundles of multiple binaries coming from the same source. Do not use this to link to a random secp256k1 library you found in your OS! If you are packaging software that depends on rust-secp256k1, using this flag to link to another package, make sure you stay within the binary compatibility guarantees of that package. For example, in Debian if you need libsecp256k1 1.2.3, make sure your package requires a version strictly>= 1.2.3 << 1.2.4. Note also that unless you're packaging the library for an official repository you should prefix your package and the library with a string specific to you. E.g. if you have a set of packages called my-awesome-packages you should package libsecp256k1 as libmy-awesome-packages-secp256k1 and depend on that library/package name from your application.

If you want to compile this library without using the bundled symbols (which may be required for integration into other build systems), you can do so by adding --cfg=rust_secp_no_symbol_renaming' to your RUSTFLAGS variable.

Minimum Supported Rust Version

This library should always compile with any combination of features on Rust 1.48.0.