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

Move to actual group traits and create GroupExt for the extra extensions of the Group trait #198

Closed
CPerezz opened this issue Jul 10, 2023 · 4 comments

Comments

@CPerezz
Copy link
Contributor

CPerezz commented Jul 10, 2023

One thing I've noticed and it's quite confusing from this repo is that it re-implements the Group trait.
I've been playing arround with this and I think it should be possible to use the original group::Group trait and create here a GroupExt trait that extends the missing features of Group to be able to do everything needed (have the attached commitment scheme traits for example..).

This would reduce duplication of code and also reduce the complexity of the lib significantly. Also, we can later check with the Zcash people to see which things would make sense to upstream to their group crate.

If that's something interesting, I'd love to work on it! So just let me know!

@CPerezz CPerezz changed the title Move to actual group and ff traits Move to actual group traits and create GroupExt for the extra extensions of the Group trait Jul 10, 2023
@srinathsetty
Copy link
Collaborator

Hi @CPerezz! Thanks for the suggestion! Yes, it would certainly be interesting to investigate this.

@ashWhiteHat
Copy link
Contributor

I think that makes sense to me to add Base field type to upstream group

@srinathsetty
Copy link
Collaborator

I think this issue may not longer be necessary as much of the original Group crate has been refactored into the provider module.

@CPerezz
Copy link
Contributor Author

CPerezz commented Nov 24, 2023

I think this issue may not longer be necessary as much of the original Group crate has been refactored into the provider module.

Makes sense! In any case, my hope is that we can at some point refactor ff and group on a way on which we can just get ridd of the provider module directly.

@CPerezz CPerezz closed this as completed Nov 24, 2023
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

Successfully merging a pull request may close this issue.

3 participants