You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once this PR is merged and live on testnets, users will be able to dry run XCM messages, calls or extrinsics to estimate their fees (both in origin and destination) and check the expected effects. The API should allow to call these new Runtime APIs through an optional input, dryRunCall, and as output give a list with the conjuction of the outputs given by XcmDryRunApi and XcmPaymentApi . Perhaps certain data is not so interesting for the API user, but for sure it would be nice to get the expected fees in the relevant asset and the execution result.
The text was updated successfully, but these errors were encountered:
Once this PR is merged and live on testnets, users will be able to dry run XCM messages, calls or extrinsics to estimate their fees (both in origin and destination) and check the expected effects. The API should allow to call these new Runtime APIs through an optional input,
dryRunCall
, and as output give a list with the conjuction of the outputs given byXcmDryRunApi
andXcmPaymentApi
. Perhaps certain data is not so interesting for the API user, but for sure it would be nice to get the expected fees in the relevant asset and the execution result.The text was updated successfully, but these errors were encountered: