-
Notifications
You must be signed in to change notification settings - Fork 78
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
CurveSNARK1 exposed from mcl #113
Conversation
Our previous approach with `rand.NewRand` was generating ids too big for the new curve and as a result we were losing information when marshalling/unmarshalling.
Question: do we want to just do the first commit as a PR (since it just bumps the dependency), and work on BLS-with-SNARK1 in a separate branch? |
I think the failing Docker image build (which I am working on right now) is the last outstanding thing here. My understanding is that if we have I still observe |
Hmmm, okay. Let's pick up the question about |
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.
Dat passing build tho.
Refs #31
After merging keep-network/go-dfinity-crypto#1 we update
revision
constraint forgo-dfinity-crypto
to the newest one.