Skip to content
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

Aggregate public keys #205

Closed
4 tasks
Kynea0b opened this issue Mar 31, 2021 · 0 comments
Closed
4 tasks

Aggregate public keys #205

Kynea0b opened this issue Mar 31, 2021 · 0 comments
Labels
C: proposal Classification: Proposal for specification, algorithm, architecture, or communication G: epic Granularity: Epic issue P: nice to have Priority: nice to have Stale For github bot

Comments

@Kynea0b
Copy link
Contributor

Kynea0b commented Mar 31, 2021

Ref #204

Summary

Computational complexity is less when public keys are aggregated at the time of aggregation signature creation rather than at verification.

Problem Definition

If you sign the same message and aggregate the signatures, use this function for verification.
https://github.com/herumi/bls-eth-go-binary/blob/master/bls/bls.go#L843
However, this internally aggregates the public key array for each verification. This takes time, so if you aggregate the public keys when creating the aggregate signature and use that key, we only need to aggregate the keys once.

Proposal

We can use this function to aggregate public keys
https://github.com/herumi/bls-eth-go-binary/blob/master/bls/bls.go#L461


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@Kynea0b Kynea0b self-assigned this Mar 31, 2021
@Kynea0b Kynea0b removed their assignment Sep 21, 2021
@torao torao added C: proposal Classification: Proposal for specification, algorithm, architecture, or communication G: epic Granularity: Epic issue P: nice to have Priority: nice to have labels Sep 29, 2021
@github-actions github-actions bot added the Stale For github bot label Feb 26, 2022
@github-actions github-actions bot closed this as completed Mar 2, 2022
@Kynea0b Kynea0b reopened this Mar 8, 2022
@github-actions github-actions bot removed the Stale For github bot label Mar 9, 2022
@github-actions github-actions bot added the Stale For github bot label Mar 20, 2022
@torao torao closed this as completed Jan 6, 2023
@Finschia Finschia deleted a comment from torao Aug 7, 2023
@Finschia Finschia deleted a comment from torao Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: proposal Classification: Proposal for specification, algorithm, architecture, or communication G: epic Granularity: Epic issue P: nice to have Priority: nice to have Stale For github bot
Projects
None yet
Development

No branches or pull requests

2 participants