Skip to content

Conversation

@lighter-zz
Copy link
Contributor

the Sign algorithm now has three APIs:

  • sign arbitrary bytes (new): in this setup, the message is uniquely hashed to a set of elements
  • sign canonical bytes (previously sign bytes): in this setup, the message must already be in the right shape: serialized bytes from canonical form of the field elements. otherwise the sign will fail. this is for backwords compatibility; it needs to be called with extreme care, and should be deprecated
  • sign field elements: the message field elements be in the right shape. the sign will fail if the field elements is not in the right form

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants