-
Reference: https://github.com/ElementsProject/secp256k1-zkp
-
When computing tagged-hashes for Schnorr sigs the 3 methods (challenge, aux, nonce) first call `secp256k1_sha256_initialize` that sets the hashstate (ie. s[0] to s[7] and bytes) to their default SHA25…
-
We should maybe make this PoK do both G1 and G2 if we're going that route, no? I guess that's a seperate thing that depends upon only Engine.
-
Per #32, specifically,
> I think the generator side of this definitely needs some experimentation, because while there are logical reasons for choosing a particular generator as standard, they aren…
-
In wasm.rs, the `check_nizk()` test, also accepts, when changing the public inputs.
This should not be the case right?
In general: I really want to use your project, but as a non rust programmer I…
-
We want to allow multiple holders, owning less than the threshold (currently 40,000 BOA) to run a validator in a trustless / non-custodian manner.
From the point of view of the network, this would …
-
```
// Extremely large transactions with lots of inputs can cost the network
// almost as much to process as they cost the sender in fees, because
// computing signature hashes is O(nin…
-
First we need to decide how to deal with Taproot addresses in `SignMessage` and `VerifyMessage`, what to hash and whether to tweak the keys. Bitcoin Core supports message signing only for legacy addre…
-
This will allow trustless payments for buying decryption keys:
https://suredbits.com/ptlc-proof-of-concept/
-
Digest now makes use of several vaguely-named generic wrapper structs and type aliases to give them human-readable names.
This makes both the type names emitted by rustc and the resulting rustdoc h…