Inter Kusama Transfer
Last updated
Was this helpful?
Last updated
Was this helpful?
Karura is an experimental network, or a 'canary network', for Acala. It's an early unaudited release of the Acala code that holds real economic value. It is highly experimental.
⚠️ Exchanges do NOT currently support direct withdraw/deposit KSM to/from Karura network. Please do NOT send KSM to an exchange address on Karura App. Read more .
KSM is the native token of Kusama. It is used as the fee token, staking token to provide network security and governance token on the Kusama Relay chain. The launch of Karura's parachain unlocks new use cases for KSM:
Participate in trustless trading with other tokens via
Use as liquidity for KSM-based trading pairs in Karura Swap, use KSM to power the KAR/KSM pair (learn about becoming a liquidity provider & risks involved ). This will also enable KSM as transaction fees on Karura. Read more .
Use as a collateral asset to mint the kUSD stablecoin, which can then be used for leveraged trades and other use cases.
Stake in Karura's Liquid KSM staking pool to mint LKSM, which can then be used as collaterals, transferred, or traded.
LKSM is a programmable staking asset as the building block for many other protocols and applications
Liquidity mining program coming soon.
Cross-chain transfer uses the Polkadot’s technology, specifically the as the basis for sending and receiving generic cross-chain messages. For sending and receiving fungible tokens, Karura has used the xtokens fungible token transfer implementation developed by Acala.
You can find the source code: and .
You can also find the Cross-chain Message (XCM) Format developed by Parity .
Note: The account you logged into the Karura App must have some KSM (also be mindful of Existential Deposits).
Select Kusama
as the From Chain
, and Karura
as the To Chain
. Your KSM balance (on Kusama) shall be displayed then. Then select the To Account
, which can be the current account that you logged in to the Karura App.
The Origin Chain Transfer Fee
is charged by Kusama
The Destination Chain Transfer Fee
is charged by Karura, modeled closely with the Statemine chain
Then click `Transfer`, please be patient and it might take a few moments for the Kusama Relay chain to send and confirm your KSM to Karura 🚀
There are two transactions involved, one was on Kusama sending the KSM to parachain, the second is on Karura sending the KSM to the designated account.
On Kusama Side
On Karura Side
Select Karura
as the From Chain
, and Kusama
as the To Chain
. Your KSM balance (on Karura) shall be displayed then. Then select the To Account
, which can be the current account that you logged in to the Karura App. Make sure your account is set as Allow use on any chain
on the Polkadot{js} extension.
The ‘Origin Chain Transfer Fee` is charged by Karura
The `Destination Chain Transfer Fee` is charged by Kusama
Then click `Transfer`, please be patient and it might take a few moments for your KSM arrive back to Kusama 🚀
There are two transactions involved, one was on Karura sending the KSM to Kusama Relay chain, the second is on Kusama sending the KSM to the designated account.
On Karura Side
On Kusama Side
Use the , go to Cross Chain
tab then select Inter Kusama Transfer
.
There are two parts to the transaction fees (read more on fees )
Go to the , search with your Kusama account, and you shall see the relevant xcmpallet
transaction in the Extrinsics table.
A Subquery will be implemented to make it easier to search and find your cross-chain transactions. Right now you can go to Karura Subscan to search Events where module = parachainsystem
and event = downwardmessagesprocessed
. OR to navigate there.
Use the , goto Cross Chain
tab then select Inter Kusama Transfer
.
There are two parts to the transaction fee (read more on fees )
A Subquery will be implemented to make it easier to search and find your cross-chain transactions. Right now you can go to to search Events where module = xtoken
and account = sender account
. OR to navigate there.
Go to the , search with your Kusama account, and you shall see the relevant xcmpallet
transaction in the Extrinsics table.