-
Notifications
You must be signed in to change notification settings - Fork 34
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
Return ZK #380
base: dev
Are you sure you want to change the base?
Return ZK #380
Conversation
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.
@tyshkor thanks for the PR that goes in an interesting direction. Unfrotunately, I don't manage to get it to compile. Here's a slightly modified branch I used to get past the trivial errors, such as unused imports:
https://github.com/huitseeker/arecibo/tree/return-zk
.. and that seems to not compile.
What OS are you using for it? |
@tyshkor What OS would you like me to test on? I've done OSX & a linux box, but I don't expect Rust trait implementation failures to be platform-dependent. Here's a compilation log on Linux: A rebase and fixing linting issues would let you get detailed and rapid feedback from our CI. |
hey! we noticed the last PR on this code was June 18, but it would be very useful for us to see the code upstreamed and maintained, so that we can have zk-based proving in systems like supernova/hypernova. do you have any timeline or sense of the priority of this so that can plan around that? would it be useful for us to help at all (i.e. fixing the tests and linting)? |
No description provided.