Skip to content
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

Support new runtime_api/rpc calls query_call_info and query_call_fee_details #5092

Closed
1 of 4 tasks
muharem opened this issue Jul 20, 2022 · 1 comment · Fixed by #5094
Closed
1 of 4 tasks

Support new runtime_api/rpc calls query_call_info and query_call_fee_details #5092

muharem opened this issue Jul 20, 2022 · 1 comment · Fixed by #5094

Comments

@muharem
Copy link

muharem commented Jul 20, 2022

  • I'm submitting a ...
  • Bug report
  • Feature request
  • Support request
  • Other
  • What is the current behavior and expected behavior?

The new rpc calls are not supported.

  • What is the motivation for changing the behavior?

Calculate the weights and fees for a given Call.
Common use case is to provide a weight and calculate fees for xcm Transact operation.

More info in the origin issue:
paritytech/substrate#11665

PR introducing new runtime api calls:
paritytech/substrate#11819

Note:
Custom RPC calls are not exposed for these new runtime api calls.
state_call endpoint is supposed to be used.
Read more in origin issue.

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Jul 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants