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.

Sign up for GitHub

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

Jump to bottom

XCM FeeManager & PriceForSibling/ParentDelivery integration #1210

Open
Dinonard opened this issue Mar 28, 2024 · 1 comment
Open

XCM FeeManager & PriceForSibling/ParentDelivery integration #1210

Dinonard opened this issue Mar 28, 2024 · 1 comment
Labels
project Issue is part of an ongoing project

Comments

@Dinonard
Copy link
Member

Dinonard commented Mar 28, 2024 •
edited
Loading

Once the approach with PriceForSiblingDelivery and PriceForParentDelivery is more widely adopted, in respect to XCM fee estimation, integrate it into our runtimes.

A solution for better XCM price estimation should be available in the first half of 2024.

Related issues to usability:
@Dinonard Dinonard added the project Issue is part of an ongoing project label Mar 28, 2024
@ipapandinas
Copy link
Contributor

August update:

In uplift v1.11 we added XcmPaymentApi that provides an API to estimate XCM fees. On next uplift to v1.13, we should add DryRunApi to complete the implementation for dry run information on extrinsics and remote XCM. Example of runtimes integrating this: paritytech/polkadot-sdk#4634

Next V5 version brings a new mechanism to pay for fees: PayFees, that takes into account delivery fees in addition to remote execution fees. Related issue: paritytech/polkadot-sdk#5420

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
project Issue is part of an ongoing project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dinonard @ipapandinas