secp256k1
secp256k1 copied to clipboard
Optimized C library for EC operations on curve secp256k1
Two primary changes based on the way include statements are handled for the project. 1. Headers defined by the secp256k1 library are now imported via `#include "secp256k1.h"`. 2. Changes to...
The context callbacks and `nonce_function` take non-const data pointers but the functions calling them take const pointers. I think this is somewhat confusing, in particular for the user-exposed `ecsda_sign()` that...
From IRC: `` The documentation for secp256k1_fe_equal_var suggest both inputs have to have magnitude 1; however only the first input needs to have magnitude 1. `` thus this call to...
- avoid overly-wide multiplications - save a few multiplies, masks and shifts - final residual left in r[9] instead of r[2] @gmaxwell It looks faster to me, but if you...
Has just added shamir secret sharing as experimental module on secp256k1's field, at [this commit](https://github.com/cubeyo/secp256k1/commit/3dc4e2e56dea599e8e757fa543302c94748a04d7) Currently support secret sharing creation and one party recovery based on lagrange interpolation polynomial. Does...
This changeset introduces a level of indirection between the EC secret key compact representation (a big endian 32 byte value) and the secp256k1_seckey type. This allows for the type to...
This adds additional logic to autoconf for future support of versioning. I picked 0.8 fairly arbitrarily to represent unstable, 0.9 would be the API stabilization series working to a 1.0...
As the library approaches 1.0 we should provide a symbol to ask for the version of `libsecp256k1` An example such as what is provided by OpenSSL - https://www.openssl.org/docs/man1.1.0/man3/OPENSSL_VERSION_NUMBER.html Before the...
We're under-covered currently for tests that simulate crazy callers. The practise of asserting on statically wrong use limits the space of things that can / need to be tested here,...
https://github.com/bitcoin-core/secp256k1/issues/573 and a recent discussion on IRC show that it would be nice to have human-readable messages in some ARG_CHECK cases, e.g., when the context was created with the wrong...