-
Notifications
You must be signed in to change notification settings - Fork 448
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
Verifiers for NEAR protocol #303
Comments
The problem we've had is that we don't have the bandwidth or experience to review/audit these generators. When I have some time, I plan to prototype a plugin system for these generators but that won't be any time soon. |
Ok, no problem, whenever you're ready to support the plugins just sent me a message. Meanwhile, in case you have a reference on unofficial contracts that support other chains, I'd be happy to add our implementations there. For reference: |
I'm down to hack on this soon if that's ok! |
@veigajoao maybe this can help with groth16: https://github.com/DoraFactory/snarkjs-bellman-adapter |
I'm going to close this because we aren't accepting new verifiers since we can't ensure the correctness of them. You should follow #340 which will enable custom verifier packages once implemented. |
Hello guys,
I built Groth16 and Plonk verifiers as smart contracts for the NEAR protocol that are compatible with snarkjs. They are written in Rust with WASM as a target.
Would it be possible/interesting to you to add them to the main lib?
The text was updated successfully, but these errors were encountered: