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

Add possibility of dry running XCM messages, calls, extrinsics #412

Open
IkerAlus opened this issue May 31, 2024 · 0 comments · May be fixed by #433
Open

Add possibility of dry running XCM messages, calls, extrinsics #412

IkerAlus opened this issue May 31, 2024 · 0 comments · May be fixed by #433
Assignees
Labels
enhancement New feature or request

Comments

@IkerAlus
Copy link
Contributor

IkerAlus commented May 31, 2024

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.

@IkerAlus IkerAlus added the enhancement New feature or request label May 31, 2024
@marshacb marshacb self-assigned this Jun 3, 2024
@marshacb marshacb linked a pull request Sep 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants