-
Notifications
You must be signed in to change notification settings - Fork 11
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
Standardised verifiable builds #110
Comments
Hi @sourabhniyogi , I can see the contracts that failed can not be built with cargo contract v3. Could you try changing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried Standardised verifiable builds on 4 cases (where all 4 cases were generated from ChainIDE WASM Contract templates and compiled in ChainIDE), and flipper compiled but the other 3 did not. Errors are included below:
NO ERRORS
We were happy that case 1 generated the same codehash as chainide but any insights to cases 2/3/4 would be appreciated!
@SkymanOne advises that this is not an issue with the (new!) "paritytech/contracts-verifiable" and recommended opening an issue here.
At the end of the day we wish for PSP22/34/Uniswapv2 contract code that can serve as templates that can be verified in paritytech/contracts-verifiable.
The text was updated successfully, but these errors were encountered: