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

Reduce scope of template generator, split it into a separate repo #9

Closed
ggutoski opened this issue Jul 9, 2020 · 0 comments
Closed
Labels
cleanup Suggestion to clean up the code

Comments

@ggutoski
Copy link
Contributor

ggutoski commented Jul 9, 2020

It's been decided that the template generator should generate only the following:

  • EC group code (g1.go, g2.go)
  • field tower (e2.go, e6.go, e12.go)
  • Frobenius constants (frobenius.go)

In particular, the template generator should not produce any pairing code (except for Frobenius constants). Pairing code is too dependent on the specific curve---generating this code inside the template is just a mess.

We should split the template generator into a separate repo, similar to goff. (Maybe merge the gurvy template generator into goff?) The gurvy repo should not contain any template code. Instead it should contain only the output of the template generator plus any curve-specific code such as pairing code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Suggestion to clean up the code
Projects
None yet
Development

No branches or pull requests

2 participants