This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
neogo: add end-to-end test for ExportNeoGo Groth-16 BLS12-381 curve #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
|
Close as not planned, ref. Consensys/gnark#799 (comment). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref. Consensys/gnark#799.
Here's the example of end-to-end test that uses new
VerifyingKey.ExportToNeoGoAPI to build Neo Verifier smart contract written in Go. After that, the contract is being deployed to the Neo testing chain and invoked to verify some proof.This PR needs a proper version of https://github.com/Consensys/gnark to be set in go.mod for
TestExportNeoGo_EndToEndto pass successfully. I've tested it locally (a bit of magic is required to set proper dependency versions), and it passes successfully,