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

minor update to the transact through sovereign function #910

Merged
merged 1 commit into from Apr 29, 2024
Merged

minor update to the transact through sovereign function #910

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion .../interoperability/xcm/remote-execution/substrate-calls/xcm-transactor-pallet.md
View file
Open in desktop
Expand Up @@ -157,7 +157,7 @@ The XCM Transactor Pallet provides the following extrinsics (functions):
=== "Parameters"

- `dest` - the XCM versioned multilocation for a chain in the ecosystem where the XCM message is being sent to (the target chain)
- `feePayer` - the address that will pay for the remote XCM execution in the corresponding [XC-20 token](/builders/interoperability/xcm/xc20/overview/){target=\_blank}
- `feePayer` - (optional) the address that will pay for the remote XCM execution in the corresponding [XC-20 token](/builders/interoperability/xcm/xc20/overview/){target=\_blank}. If you don't specify the `feePayer`, the XCM execution fees will be paid by the Sovereign account on the destination chain
- `fee` - the asset to be used for fees. This contains the `currency` and the `feeAmount`:
- `currency` - defines how you are specifying the token to use to pay for the fees, which can be either of the following:
- `AsCurrencyId` - the currency ID of the asset to use for the fees. The currency ID can be either:
Expand Down