gnark-crypto provides efficient cryptographic primitives, in Go.
It is actively developed and maintained by the team (gnark@consensys.net | HackMD) behind gnark: a framework to execute (and verify) algorithms in zero-knowledge.
Each of these curves has a twistededwards sub-package with its companion curve, which allows efficient elliptic curve cryptography inside zkSNARK circuits.
Additional (non pairing-friendly) curves: secp256r1 (P-256), secp256k1, grumpkin, stark-curve.
Small prime fields for STARK-style provers:
koalabear,babybear(31-bit, with AVX-512 and NEON vector kernels),goldilocks(64-bit)- Each with
extensions(degree 2/4/6),fft,poseidon2,sis(Ring-SIS) andiopsub-packages
ecdsa- ECDSA signatures, on every curve aboveeddsa- EdDSA signatures, on the companiontwistededwardscurvesmimc- MiMC hash function using Miyaguchi-Preneel constructionposeidon2- Poseidon2 permutation and compression functionhash- registry of field-typed hash functions
kzg- KZG commitment schemempcsetup- multiparty setup ceremony primitives (MMPORPG)shplonk/fflonk- batched polynomial commitment openingspedersen- Pedersen vector commitmentsfft- Fast Fourier Transformiop- polynomial IOP building blocks (multilinear, quotients, ratios)permutation- Permutation proofsfiatshamir- Fiat-Shamir transcript builder
field/generator- Finite field arithmetic code generator (blazingly fast big.Int)merkletree- Merkle tree accumulatoreisenstein/lattice- Eisenstein integer arithmetic and lattice reduction for scalar decomposition
gnark-crypto is not fully audited and is provided as-is, use at your own risk. In particular, gnark-crypto makes no security guarantees such as constant time implementation or side-channel attack resistance.
To report a security bug, please refer to gnark Security Policy.
gnark-crypto packages are optimized for 64-bit architectures (amd64 with AVX-512 where available, arm64 with NEON) and tested on Linux, macOS and Windows. Pure Go fallbacks are provided for all other platforms.
See list of audits for gnark and gnark-crypto
gnark-crypto requires Go 1.25 or newer (see go.mod); CI tests against Go 1.25.x.
go get github.com/consensys/gnark-cryptoNote that if you use go modules, in go.mod the module path is case sensitive (use consensys and not ConsenSys).
Most (but not all) of the code is generated from the templates in internal/generator.
The generated code contains little to no interfaces and is strongly typed with a field (generated by the gnark-crypto/field package). The two main factors driving this design choice are:
- Performance:
gnark-cryptoalgorithms manipulate millions (if not billions) of field elements. Interface indirection at this level, plus garbage collection indexing takes a heavy toll on perf. - Need to derive (mostly) identical code for various moduli and curves, with consistent APIs. Generics introduce significant performance overhead and are not yet suited for high performance computing.
To regenerate the files, see internal/generator/main.go. Run:
go generate ./...Benchmarking pairing-friendly elliptic curves libraries
The libraries are implemented in different languages and some use more assembly code than others. Besides the different algorithmic and software optimizations used across, it should be noted also that some libraries target constant-time implementation for some operations making it de facto slower. However, it can be clear that consensys/gnark-crypto is one of the fastest pairing-friendly elliptic curve libraries to be used in zkp projects with different curves.
If you use gnark-crypto in your research a citation would be appreciated.
Please use the following BibTeX to cite the most recent release.
@software{gnark-crypto-v0.21,
author = {Gautam Botrel and
Thomas Piellard and
Youssef El Housni and
Arya Tabaie and
Gus Gutoski and
Ivo Kubjas and
Yao J. Galteland},
title = {Consensys/gnark-crypto: v0.21.0},
month = aug,
year = 2026,
publisher = {Zenodo},
version = {v0.21.0},
doi = {10.5281/zenodo.5815453},
url = {https://doi.org/10.5281/zenodo.5815453}
}We use SemVer for versioning. For the versions available, see the tags on this repository.
This project is licensed under the Apache 2 License - see the LICENSE file for details.