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

CurveSNARK1 exposed from mcl #113

Merged
merged 10 commits into from
May 17, 2018
Merged

CurveSNARK1 exposed from mcl #113

merged 10 commits into from
May 17, 2018

Conversation

pdyraga
Copy link
Member

@pdyraga pdyraga commented May 15, 2018

Refs #31

After merging keep-network/go-dfinity-crypto#1 we update revision constraint for go-dfinity-crypto to the newest one.

Piotr Dyraga added 6 commits May 15, 2018 23:48
@Shadowfiend
Copy link
Contributor

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?

@pdyraga
Copy link
Member Author

pdyraga commented May 17, 2018

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 Did we get it? true for all members, then SNARK1 works as expected.

I still observe Did we get it? false from time to time but I see it also on master...

@Shadowfiend
Copy link
Contributor

Hmmm, okay. Let's pick up the question about false in flowdock. 👍 re: the build.

Copy link
Contributor

@Shadowfiend Shadowfiend left a 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.

@Shadowfiend Shadowfiend merged commit 8af1b3e into master May 17, 2018
@Shadowfiend Shadowfiend deleted the snark1-for-go-step3 branch May 17, 2018 15:33
@Shadowfiend Shadowfiend added this to the Relay Milestone 1 milestone May 17, 2018
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 this pull request may close these issues.

2 participants