|0.7.1||Jul 14, 2022|
|0.7.0||Sep 17, 2021|
|0.6.0||Jul 20, 2021|
|0.3.5||Feb 7, 2020|
|0.1.10||Nov 17, 2017|
#62 in Magic Beans
187,739 downloads per month
Used in 1,240 crates (89 directly)
SECP256K1 implementation in pure Rust
SECP256K1 implementation with
no_std support. Currently we have implementation for:
- Convert a private key to a public key.
- Sign messages.
- Signature verification.
- Public key recovery from signed messages.
- Shared secrets.
std: If disabled, works in
no_stdenvironment. Enabled by default.
hmac: Add certain features that requires the HMAC-DRBG. This includes signing. Enabled by default.
static-context: To speed up computation, the library uses a pre-computed table context for many
ecmultoperations. This feature flag puts the context directly as static variables. If disabled, the context must be created from heap manually. Increases binary size, enabled by default.
lazy-static-context: Instead of storing the pre-computed table context as static variables, store it as a variable that dynamically allocates the context in heap via
lazy_static. It overwrites
static-context. Impact bootstrap performance and only available in
std, disabled by default.
This repository uses
develop branch for development. Changes are periodically
All changes (except new releases) are handled through pull requests. Please open
your PR against
libsecp256k1 follows Semantic Versioning. An unreleased crate
in the repository will have the
-dev suffix in the end, and we do rolling
When you make a pull request against this repository, please also update the
affected crates' versions, using the following rules. Note that the rules should
be applied recursively -- if a change modifies any upper crate's dependency
(even just the
Cargo.toml file), then the upper crate will also need to apply
Additionally, if your change is notable, then you should also modify the
CHANGELOG.md file, in the "Unreleased" section.
If the affected crate already has
- If your change is a patch, then you do not have to update any versions.
- If your change introduces a new feature, please check if the local version already had its minor version bumped, if not, bump it.
- If your change modifies the current interface, please check if the local version already had its major version bumped, if not, bump it.
If the affected crate does not yet have
- If your change is a patch, then bump the patch version, and add
- If your change introduces a new feature, then bump the minor version, and add
- If your change modifies the current interface, then bump the major version,
If your pull request introduces a new crate, please set its version to