-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add missing methods to Commitment signature #167
feat: add missing methods to Commitment signature #167
Conversation
…bytes`] and [`from_vec`] methods
/// | ||
/// WARNING: The provided secret keys and nonces are NOT bound to the challenge. This method assumes that the | ||
/// challenge has been constructed such that all commitments are already included in the challenge. | ||
pub fn sign_raw<C>( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this added? As far as I can see it's the same as sign
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we replace the sign
function by this sign_raw
, to convey the idea that we are making assumptions that the inputs are sensible ? Similarly to what was used in the SchnorrSignature
, via the signature api ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, I think this should be in another PR because we should also add a deprecation attribute to sign
which may involve a number of other changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy. PR description must be updated
Add [
from_vec
] and [from_bytes
] toCommitmentSignature
type.