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

Monitor upstream moves to CurveAffine #75

Closed
huitseeker opened this issue Jul 31, 2023 · 5 comments
Closed

Monitor upstream moves to CurveAffine #75

huitseeker opened this issue Jul 31, 2023 · 5 comments

Comments

@huitseeker
Copy link
Contributor

Consider:
zkcrypto/group#48
zcash/pasta_curves#75
Which may be relevant to the local integration of pasta curves, as well as the downstream integration in Nova ( microsoft/Nova#198 ).

/cc @CPerezz

@CPerezz
Copy link
Member

CPerezz commented Jul 31, 2023

I spoke to @str4d today at ZCon and by chance we exactly spoke about better trait support for curve cycles. He said is working on this. And I'm curious to see his final design. What he told me so far looks nice. And looks something we definitely will benefit from.

As soon as we get a new version of group, we will update all the macros accordingly!

Thanks for the ping!

@duguorong009
Copy link
Contributor

@CPerezz Should we keep this issue open?

AFAIK, the mentioned PRs have not been merged at all.
The PRs(zkcrypto/group#48, zcash/pasta_curves#75) are still open, and I don't see any intention or movement to take care of them.
Also, microsoft/Nova#198 is closed after some consideration. (microsoft/Nova#198 (comment))

What do you think? sir

@CPerezz
Copy link
Member

CPerezz commented Jan 11, 2024

Hey @duguorong009 i think we can close but not due to this, rather due to the fact that we are constantly checking this and writing the RFC proposal.

Thanks @huitseeker for the help on this, although closing, we will keep tracking ofc.

@duguorong009
Copy link
Contributor

Thanks! @CPerezz
I am sure you are indicating the correct reasons.
Can you close the issue with the appropriate comment?

@CPerezz
Copy link
Member

CPerezz commented Jan 11, 2024

@duguorong009 you should have permission to do so right?

In any case, Closing due to we're already monitoring. And for any updates we will file new issues with concrete tasks.

@CPerezz CPerezz closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2024
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

No branches or pull requests

3 participants