-
Notifications
You must be signed in to change notification settings - Fork 161
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
Adding Verification Function for Aggregate BLS Signatures #240
Conversation
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.
Make sure to run make lint
to make sure code is formatted and linted. Looks like you're on the right track though! I'll have a more in depth check once CI passes
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.
few small changes
let signatures: Vec<BlsSignature> = (0..num_sigs) | ||
.map(|x| private_keys[x].sign(data[x])) | ||
.collect(); |
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.
can do same as above
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.
What are others thoughts on the api for the function? From what I've seen all data that is signed in Cids so maybe the data input should be a slice of Cids to avoid having to convert to bytes before calling this? Also does anyone have thoughts on if we should be using the external Public key type also instead of bytes or we alias/ create our own type for pub keys?
I'm fine with this coming in as in but would be nice to iron down the function signature/ a specific test vector when it gets used
Summary of changes
Changes introduced in this pull request:
Issues with pull Request :