Crypto

Convenience method which calculates the parts of the signature that are public knowledge (can be reconstructed) by anybody. Basically a tagged hash turned into a private key see: BIP340/challenge

Find the value of k which would be used to construct a valid BIP340 schnorr signature. A schnorr signature is 64-bytes given by (R,s) where the first 32 bytes are R = k*G. This function returns the value k.

Tweak an otherwise valid BIP340 signature with a curve point tweakPoint. The result is an "Adaptor Signature". Somebody with knowledge of the discrete logarithm (the private key) for tweakPoint will be able to repair the adaptor signature to reconstruct a valid BIP340 signature. See: BIP340 https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki See: https://suredbits.com/schnorr-applications-scriptless-scripts/

160 bits bitcoin hash, used mostly for address encoding hash160(input) = RIPEMD160(SHA256(input))

256 bits bitcoin hash hash256(input) = SHA256(SHA256(input))

Repair an "Adaptor Signature" using knowledge of the discrete logarithm of the tweakPoint. Note, this does not first check whether the adaptor signature is valid. For that you should first call verifySchnorrAdaptorSignature. See: BIP340 https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki See: https://suredbits.com/schnorr-applications-scriptless-scripts/

Sign data with a private key, using RCF6979 deterministic signatures

Sign according to BIP340 specification https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki

Tagged hash of input as defined in BIP340

Tweak a valid schnorr signature (R,s) with a scalar value t to create an adaptor signature (R - t*G, s - t, t*G). Anybody with knowledge oft` will be able to repair the resulting adaptor signature to reconstruct the valid original signature. Because knowledge of the signing key was not necessary to create the adaptor signature, this shows that adaptor signatures posess a denaibility property. see: https://suredbits.com/schnorr-applications-scriptless-scripts/

(Unsafe) Sign according to BIP340 specification https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki Note: this is unsafe! It is uses a less-tested, inefficient, but platform-independent implementation to do the signing. Prefer signSchnorr for anything in production.

(Unsafe) verification of signature according to BIP340 specification https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki Note: this is unsafe! It is a uses less-tested, inefficient, but platform-independent implementation. Prefer verifySignatureSchnorr for anything in production.

Verify an "Adaptor Signature." If verification is successful and the verifier knows the discrete logarithm (private key) for the tweakPoint, then verifier will be able to repair the adaptor signature into a complete and valid BIP340 schnorr signature by calling repairSchnorrAdaptorSignature. See: BIP340 https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki See: https://suredbits.com/schnorr-applications-scriptless-scripts/

Verify a BIP340 schnorr signature

Recover public keys from a signature and the message that was signed. This method will return 2 public keys, and the signature can be verified with both, but only one of them matches that private key that was used to generate the signature.