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

Additional transport costs in XCM bridge #1429

Closed
svyatonik opened this issue May 31, 2022 · 1 comment
Closed

Additional transport costs in XCM bridge #1429

svyatonik opened this issue May 31, 2022 · 1 comment

Comments

@svyatonik
Copy link
Contributor

related to #1318 and #1417

So in encoded calls messaging the total message_delivery_and_dispatch_fee had three main components:

  1. cost of message delivery transaction;
  2. cost of message dispatch;
  3. cost of delivery confirmation transaction.

With XCM coming, iiuc there's an additional problem - our (bridge target) chain may not match the message target chain (where message needs to be dispatched. For example - we're sending message from Millau to RialtoParachain, but the message needs to be dispatched at the Rialto itself, so we (XCM executor/router?) need to use UMP (?) to deliver message to Rialto.

The question is: who's paying cost of this UMP transfer? Is it handled by the XCM executor by some instruction? Or we need to withdraw this fee from the message sender at the source chain? I don't have idea right now and it needs to be explored.

@svyatonik
Copy link
Contributor Author

The fee will be paid at the source chain (not at bridge hub as it has been designed before). It shall cover all costs. The issue is not relevant anymore

svyatonik pushed a commit that referenced this issue Jul 17, 2023
* Update Readme for integration-tests

* Update parachains/README.md

Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>

Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant