We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since 1.3 fellowship release is live, users are able to dry run XCM messages, calls or extrinsics to estimate their fees and check the expected effects with the new DryRunAPI runtime API (see PRs paritytech/polkadot-sdk#4621 , paritytech/polkadot-sdk#3872 , polkadot-fellows/runtimes#380.
DryRunAPI
It would be good to update Sidecar's transaction dry run endpoint to use this new runtime API. See AT API implementation for useful reference.
The text was updated successfully, but these errors were encountered:
filvecchiato
Successfully merging a pull request may close this issue.
Since 1.3 fellowship release is live, users are able to dry run XCM messages, calls or extrinsics to estimate their fees and check the expected effects with the new
DryRunAPI
runtime API (see PRs paritytech/polkadot-sdk#4621 , paritytech/polkadot-sdk#3872 , polkadot-fellows/runtimes#380.It would be good to update Sidecar's transaction dry run endpoint to use this new runtime API. See AT API implementation for useful reference.
The text was updated successfully, but these errors were encountered: