libsecp256k1

High-performance high-assurance C library for digital signatures and other cryptographic primitives on the secp256k1 elliptic curve.

This library is intended to be the highest quality publicly available library for cryptography on the secp256k1 curve. However, the primary focus of its development has been for usage in the Bitcoin system and usage unlike Bitcoin's may be less well tested, verified, or suffer from a less well thought out interface. Correct usage requires some care and consideration that the library is fit for your application's purpose.

Features:

• secp256k1 ECDSA signing/verification and key generation.
• Additive and multiplicative tweaking of secret/public keys.
• Serialization/parsing of secret keys, public keys, signatures.
• Constant time, constant memory access signing and public key generation.
• Derandomized ECDSA (via RFC6979 or with a caller provided function.)
• Very efficient implementation.
• Suitable for embedded systems.
• No runtime dependencies.
• Optional module for public key recovery.
• Optional module for ECDH key exchange.
• Optional module for Schnorr signatures according to BIP-340.
• Optional module for ElligatorSwift key exchange according to BIP-324.
• Optional module for MuSig2 Schnorr multi-signatures according to BIP-327.
• Optional module for Silent Payments sending and receiving according to BIP-352.

Implementation details

• General
  • No runtime heap allocation.
  • Extensive testing infrastructure.
  • Structured to facilitate review and analysis.
  • Intended to be portable to any system with a C89 compiler and uint64_t support.
  • No use of floating types.
  • Expose only higher level interfaces to minimize the API surface and improve application security. ("Be difficult to use insecurely.")
• Field operations
  • Optimized implementation of arithmetic modulo the curve's field size (2^256 - 0x1000003D1).
    • Using 5 52-bit limbs
    • Using 10 26-bit limbs (including hand-optimized assembly for 32-bit ARM, by Wladimir J. van der Laan).
      • This is an experimental feature that has not received enough scrutiny to satisfy the standard of quality of this library but is made available for testing and review by the community.
• Scalar operations
  • Optimized implementation without data-dependent branches of arithmetic modulo the curve's order.
    • Using 4 64-bit limbs (relying on __int128 support in the compiler).
    • Using 8 32-bit limbs.
• Modular inverses (both field elements and scalars) based on safegcd with some modifications, and a variable-time variant (by Peter Dettman).
• Group operations
  • Point addition formula specifically simplified for the curve equation (y^2 = x^3 + 7).
  • Use addition between points in Jacobian and affine coordinates where possible.
  • Use a unified addition/doubling formula where necessary to avoid data-dependent branches.
  • Point/x comparison without a field inversion by comparison in the Jacobian coordinate space.
• Point multiplication for verification (aP + bG).
  • Use wNAF notation for point multiplicands.
  • Use a much larger window for multiples of G, using precomputed multiples.
  • Use Shamir's trick to do the multiplication with the public key and the generator simultaneously.
  • Use secp256k1's efficiently-computable endomorphism to split the P multiplicand into 2 half-sized ones.
• Point multiplication for signing
  • Use a precomputed table of multiples of powers of 16 multiplied with the generator, so general multiplication becomes a series of additions.
  • Intended to be completely free of timing sidechannels for secret-key operations (on reasonable hardware/toolchains)
    • Access the table with branch-free conditional moves so memory access is uniform.
    • No data-dependent branches
  • Optional runtime blinding which attempts to frustrate differential power analysis.
  • The precomputed tables add and eventually subtract points for which no known scalar (secret key) is known, preventing even an attacker with control over the secret key used to control the data internally.

Obtaining and verifying

The git tag for each release (e.g. v0.6.0) is GPG-signed by one of the maintainers. For a fully verified build of this project, it is recommended to obtain this repository via git, obtain the GPG keys of the signing maintainer(s), and then verify the release tag's signature using git.

This can be done with the following steps:

1. Obtain the GPG keys listed in SECURITY.md.
2. If possible, cross-reference these key IDs with another source controlled by its owner (e.g. social media, personal website). This is to mitigate the unlikely case that incorrect content is being presented by this repository.
3. Clone the repository:

   git clone https://github.com/bitcoin-core/secp256k1
   

4. Check out the latest release tag, e.g.

   git checkout v0.7.1
   

5. Use git to verify the GPG signature:

   % git tag -v v0.7.1 | grep -C 3 'Good signature'
   
   gpg: Signature made Mon 26 Jan 2026 07:42:46 PM UTC
   gpg:                using RSA key 2840EAABF4BC9F0FFD716AFAFBAFCC46DE2D3FE2
   gpg: Good signature from "Pieter Wuille <pieter@wuille.net>" [unknown]
   gpg:                 aka "Pieter Wuille <pieter.wuille@gmail.com>" [full]
   gpg:                 aka "[jpeg image of size 5996]" [undefined]
   gpg: WARNING: This key is not certified with a trusted signature!
   gpg:          There is no indication that the signature belongs to the owner.
   Primary key fingerprint: 133E AC17 9436 F14A 5CF1  B794 860F EB80 4E66 9320
        Subkey fingerprint: 2840 EAAB F4BC 9F0F FD71  6AFA FBAF CC46 DE2D 3FE2
   

Building with Autotools

$ ./autogen.sh       # Generate a ./configure script
$ ./configure        # Generate a build system
$ make               # Run the actual build process
$ make check         # Run the test suite
$ sudo make install  # Install the library into the system (optional)

To compile optional modules (such as Schnorr signatures), you need to run ./configure with additional flags (such as --enable-module-schnorrsig). Run ./configure --help to see the full list of available flags.

Building with CMake

To maintain a pristine source tree, CMake encourages to perform an out-of-source build by using a separate dedicated build tree.

Building on POSIX systems

$ cmake -B build              # Generate a build system in subdirectory "build"
$ cmake --build build         # Run the actual build process
$ ctest --test-dir build      # Run the test suite
$ sudo cmake --install build  # Install the library into the system (optional)

To compile optional modules (such as Schnorr signatures), you need to run cmake with additional flags (such as -DSECP256K1_ENABLE_MODULE_SCHNORRSIG=ON). Run cmake -B build -LH or ccmake -B build to see the full list of available flags.

Cross compiling

To alleviate issues with cross compiling, preconfigured toolchain files are available in the cmake directory. For example, to cross compile for Windows:

$ cmake -B build -DCMAKE_TOOLCHAIN_FILE=cmake/x86_64-w64-mingw32.toolchain.cmake

To cross compile for Android with NDK (using NDK's toolchain file, and assuming the ANDROID_NDK_ROOT environment variable has been set):

$ cmake -B build -DCMAKE_TOOLCHAIN_FILE="${ANDROID_NDK_ROOT}/build/cmake/android.toolchain.cmake" -DANDROID_ABI=arm64-v8a -DANDROID_PLATFORM=28

Building on Windows

The following example assumes Visual Studio 2022. Using clang-cl is recommended.

In "Developer Command Prompt for VS 2022":

>cmake -B build -T ClangCL
>cmake --build build --config RelWithDebInfo

Usage examples

Usage examples can be found in the examples directory. To compile them you need to configure with --enable-examples.

• ECDSA example
• Schnorr signatures example
• Deriving a shared secret (ECDH) example
• ElligatorSwift key exchange example
• MuSig2 Schnorr multi-signatures example
• Silent Payments send and receive example

To compile the examples, make sure the corresponding modules are enabled.

Benchmark

If configured with --enable-benchmark (which is the default), binaries for benchmarking the libsecp256k1 functions will be present in the root directory after the build.

To print the benchmark result to the command line:

$ ./bench_name

To create a CSV file for the benchmark result :

$ ./bench_name | sed '2d;s/ \{1,\}//g' > bench_name.csv

Reporting a vulnerability

See SECURITY.md

Contributing to libsecp256k1

See CONTRIBUTING.md