-
Notifications
You must be signed in to change notification settings - Fork 424
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
ink! V4 Metadata JSON schema #1564
Comments
Yes, there are plans but it probably won't happen until some of the other 4.0 related issues get sorted (as mentioned here). The 4.0 metadata format has been finalized, so there's nothing blocking this other than developer time. Is this something you'd be interesting in picking up? |
So, I did a quick-and-dirty patch across the three repos I validated the schema against example contracts Flipper, Incrementer and our own Crowdfund contract built with You can find the V4 schema here: https://gist.github.com/XY-Wang/b54d3b4a14d12df7e273c5eece274682 Please let us know if it works for you 😺 |
Formal definition has been updated on master. And some groundwork has been done to automatically generate the definition in #1765 We are now just left with use-ink/cargo-contract#1090 |
Closed via use-ink/cargo-contract#1090 |
Hi,
We're currently working on our W3F grant to decode verified ink! contract messages and events for our contracts explorer. Since verification is only possible for contracts written with ink! v4.0.0-alpha.3 onward, we would need a
ink-v4-schema.json
to validate metadata prior to decoding.We are currently using a manually-patched version on top of the
ink-v3-schema.json
provided in this repo but ideally we would want to use the officially generated version.Is there any plan to provide the V4 schema or a tool to generate it?
Thanks!
The text was updated successfully, but these errors were encountered: