Yaay! You just created your community. Now, let's learn how to execute something on Kusama, from your Community.
Note: This tutorial assumes you're the admin of the community. If you already decentralized your community, and the admin is the community itself, you'll need to encode the final extrinsic and submit a referendum on your community track (this will be covered in the next part of this tutorials).
transactionPaymentCallApi.queryCallInfo
runtime call with the following params:call
, andlen
of the call (you can get it by measuring the encoded call len —without the 0x prefix— and dividing by 2).refTime
and proofSize
parameters.Note: Your Community owns two Sovereign Accounts. These accounts represent your Community on Kusama and other Parachains:
We'll soon submit a tool for you to know which are the Sovereign Accounts that represent your Community.
Deposit 0.1 KSM
on the Sovereign Account that represents your Community on Kusama.
This amount will be used for the existential deposit of the account, and is enough to cover the costs XCM execution, the fees of the call, and any other related costs required (like submit deposits for referenda).
We've prepared a base template to send some XCM instructions to Kusama needed to execute a call on the destination chain.
Note: This template is prepared to take a reasonable, conservative amount (
5 µKSM
) from your Community Sovereign Account in Kusama to cover for the base costs of executing the XCM instructions, and the costs of executing the call. Then, deposits the remaining amount back to the account.Normally, Kusama takes between
1 µKSM
and3 µKSM
, but some calls might charge a bit more. That's why we reserve5 µKSM
to cover for fees.
Transact
instruction, in the requireWeightAtMost
field, paste the values you saved for refTime
and proofSize
.Transact
instruction, in the call
field, paste the encoded call.DepositAsset
instruction, under the beneficiary
field, set your community number in the Plurality
id.