Different hashes produced in comparison to other signers about curvy

[libitx]

By default Curvy will hash the given message with sha256. libsecp256k1 assumes you have already hashed the message and are giving it a 32 byte digest.

You can chose for Curvy to not hash the message by using the hash: false option.

Curvy.sign(message, private_key, hash: false)
<<48, 68, 2, 32, 73, 102, 23, 43, 29, 88, 149, 68, 77, 65, 248, 57, 200, 155,
  43, 249, 154, 95, 100, 185, 121, 244, 84, 178, 159, 90, 254, 45, 27, 177, 221,
  218, 2, 32, 21, 214, 167, 20, 61, 86, 189, 86, 241, 39, 239, 70, ...>>

Note that Curvy is returning a DER-encoded signature here whereas ExSecp256k1 is returning a tuple in the format: {:ok, r, s, recovery_id}. But the signature is indeed the same.

[qcam]

@libitx Thank you for the help 🙏.