-
Notifications
You must be signed in to change notification settings - Fork 124
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
Investigate extended usage of metadata #416
Comments
It seems that what the comment suggests and what is done in subxt is something entirely different. Subxt does only verify the generic call metadata hash without the arguments of what has been generated at compile time in their macro matches the the hash of the pallet-prefix and the call-name of the supplied call. Hence, subxt verifies the same thing as we already do with:
Be aware that subxt has more need for validation than us, as it relies on statically generated code that it wants to check against the actual metadata that the client connects to, while the api-client does only know the latter. but I like the Idea. What could we do with the metadata? :) |
I see. Didn't look too deeply into that. Nonetheless, something like integritee-network/worker#970 (comment) was possible. Not sure if that's verifiable with the metadata, but I think it should be worth it to investigate a little. |
I suggest timeboxing this task to 8h. If there's a promising lead after investigation, it should be done in a different task. |
There is an extensive discussion on how to change the metadata, especially for (offline-) light clients, and there is an ongoing proposal on polkadot on how to implement this. I suggest waiting for some results there: https://forum.polkadot.network/t/the-ledger-app-debate-united-we-stand-divided-we-fall/3177/9. |
We have full access to the metadata, but it's hardly used yet. Can we do more with that?
E.g. like this comments suggests:
substrate-api-client/compose-macros/src/lib.rs
Lines 38 to 39 in 7e5962b
Check out subxt example: https://github.com/paritytech/subxt/blob/master/subxt/src/tx/tx_client.rs#L56-L73
The text was updated successfully, but these errors were encountered: