-
These would range from Curve tests which would verify canonical functions are appropriately canonical (as possible) to algorithm tests which would verify signature share validation works as expected.
-
At the time of writing, Rooch doesn't support Bitcoin related protocol.
nostr, on the other hand, supports Bitcoin protocols, and by supporting nostr on Rooch, we can further support Bitcoin networ…
-
I wanted to know if it is based on ED25519 or SR25519 or some other curve?
-
**Feature Description**
One of the biggest blockers for schnorr sigs, zkp & any crypto primitives that requires scalar manipulation natively is lack of 32-byte / 256-bit math in Clarity.
@FriendsF…
-
Right now, we are showing the nonce as an hex string.
I think this should be changed as fast as possible.
The reason is, when taproot activate, we will want to move from ECDSA Adaptor sigs to Schn…
-
According to BIP-340, XOnly keys have 32 bytes and signatures have 64 bytes.
If X + Parity is used, signatures would be 65 bytes and Keys 33 bytes. Really, they just require one bit, but the minimu…
-
Quoted from Discord to make sure the questions don't get lost and the answers are saved here.
> Hey people, I'm trying to use the Leather wallet signmessage functionality (https://leather.gitbook.…
-
The CFRG is currently working to specify [an interoperable version FROST](https://cfrg.github.io/draft-irtf-cfrg-frost/draft-irtf-cfrg-frost.html). As this project implements FROST as the threshold Sc…
-
Grin should already support in the near future:
* multisig using aggregate (formerly Schnorr) signatures ;
* time-locked transactions.
Using these primitives, figure out how to implement vaults…
-
This will be necessary to support Schnorr-Ristretto or other signature schemes which @burdges is investigating.
As we generalize more work over signature schemes, it may prove useful to have a set …