[curves] curve25519-dalek: a pure Rust ECC library

Michael Scott mike.scott at miracl.com
Thu Dec 22 10:45:34 PST 2016

There is an another pure Rust ECC (and Pairings) library available here


Not sure how the speed compares. But things will definitely improves when
the i128 type (128-bit integers) is supported in version 1.17 (due out in
March 2017 I believe)

Mike Scott

On Sun, Dec 11, 2016 at 8:23 PM, Tony Arcieri <bascule at gmail.com> wrote:

> On Sun, Dec 11, 2016 at 11:14 AM, Dirkjan Ochtman <dirkjan at ochtman.nl>
> wrote:
>> Did you look at Brian Smith's *ring*, and if so, why did you decide
>> not to go with it?
> As a Rust crypto consumer, I view these libraries differently.
> *ring* is a fantastic library and one I've been using in my Rust crypto
> projects for awhile. However, it's a "safe" library in the same sort of
> lineage as NaCl and libsodium: it tries to expose a high-level,
> minimalistic API. Types like curve points/group elements are not directly
> exposed for safety reasons and remain part of the private API.
> curve25519-dalek seems much better suited for people implementing more
> exotic constructions using types *ring* does not (for good reasons) expose
> as part of its public API. These would include things like SPAKE2,
> hierarchical key derivation, semiprivate keys, blinded signatures, ring
> signatures, threshold multisignatures.
> Building any of the things I listed above above on top of *ring* would
> require forking *ring* and building atop its private API. Maybe some of
> those things should eventually wind up in *ring*, but I appreciate Brian
> being conservative about what he includes.
> --
> Tony Arcieri
> _______________________________________________
> Curves mailing list
> Curves at moderncrypto.org
> https://moderncrypto.org/mailman/listinfo/curves
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://moderncrypto.org/mail-archive/curves/attachments/20161222/39a1bfbe/attachment.html>

More information about the Curves mailing list