https://github.com/bitcoin/secp256k1/blob/master/src/group.h#L37
Particularly being able to access the generator point is useful.
Expose 'secp256k1_ge_consts_t *secp256k1_ge_consts' to public API #12
issue genjix opened this issue on May 8, 2014-
genjix commented at 1:16 AM on May 8, 2014: none
-
gmaxwell commented at 1:22 AM on May 8, 2014: contributor
Can you explain why its useful?
It might be the case that eventually the library has no reason to internally have the generator represented in a 'typical' friendly form. If you wish to use the generator for multiplication with a scalar then having the generator in a special precomputed form is important for performance, and necessary for the implementation of a multiply that doesn't have a timing side-channel.
-
genjix commented at 1:29 AM on May 8, 2014: none
Well as long as there is a function to multiply by the generator point and get the result somehow. i.e new signature schemes in Bitcoin, HD keys or stealth addresses all need this ability.
-
gmaxwell commented at 1:32 AM on May 8, 2014: contributor
Sure, thats how you generate a public key from a private key.
-
genjix commented at 1:51 AM on May 8, 2014: none
https://github.com/bitcoin/secp256k1/blob/master/include/secp256k1.h#L101 int secp256k1_ecdsa_pubkey_create(unsigned char *pubkey, int *pubkeylen, const unsigned char *seckey, int compressed);
right.
- genjix closed this on May 8, 2014
