- Aug 16, 2014
-
-
Andrew Poelstra authored
Simpler `random_32_bytes`.
-
Dawid Ciężarkiewicz authored
-
Andrew Poelstra authored
As @dpc observes, embedded systems do not necessarily have allocators, so we should avoid using them if it is not too much hassle. (And it is no hassle at all.)
-
- Aug 12, 2014
-
-
Andrew Poelstra authored
-
Andrew Poelstra authored
Verifying signatures does not require any randomness, but requires the user to create a `Secp256k1` object nonetheless (this is just a way to guarantee that `init` is called --- an alternate API would be to have an independent unsafe `verify` function). If a Rng can't be created, rather than failing the `Secp256k1` initialization, fail the functions that actually try to use the Rng. This way signing and verifying, which require no randomness beyond that input to them, will work correctly. To avoid checking for a working Rng on each call to `generate_keypair` and `generate_nonce` (which is probably trivial next to the cost of actually generating the randomness, but w/e, user knows best), the user should use the generation functions in the `key` module, which take an Rng as input.
-
Andrew Poelstra authored
-
Andrew Poelstra authored
-
Andrew Poelstra authored
-
Andrew Poelstra authored
-
Andrew Poelstra authored
-
Andrew Poelstra authored
-
- Aug 10, 2014
-
-
Dawid Ciężarkiewicz authored
-
- Aug 05, 2014
-
-
Dawid Ciężarkiewicz authored
Fix unused imports and add a gitignore
-
- Aug 04, 2014
-
-
Steve Klabnik authored
-
Steve Klabnik authored
-
Dawid Ciężarkiewicz authored
The way compact signatures are working was explain to me: https://github.com/bitcoin/secp256k1/issues/45
-
- Jul 23, 2014
-
-
Dawid Ciężarkiewicz authored
-
- Jul 07, 2014
-
-
Dawid Ciężarkiewicz authored
-