Token Transfer

Karura supports different types of tokens than Kusama, and allows various ways to transfer tokens. This guide will walk through tokens available on Karura, tools can be used for transfers, how to send transfer transactions, monitor and track these transactions.

Token Types


AssetRegistry registered the metadata info of this type token.


The lp share token for the trading pair of Karura DEX. The CurrencyId type of Karura DEX's lp token are CurrencyId::DexShare, and the decimals and minimal balance of lp token are same as the first token in DexShare. For example, CurrencyId::DexShare(Token(KAR), Token(KSM)) is the CurrencyId of lp token of KAR/KSM pair, its decimal is 12, and minimal balance is 0.1, these are same as KAR.

Currently, AssetRegistry does not register metadata info of any lp token.


Token issued by ERC20 contracts deployed in Karura EVM+. The CurrencyId type is Erc20(Address), Address is the ERC20 contract address on EVM+.


AssetRegistry registered the metadata info of this type token.


Tokens originated from other parachains. AssetRegistry registered the metadata info of this type token.

Query token's metadata on assetRegistry

  • Native Network Token

    • KAR

  • Native Protocol Tokens

    • LKSM: tokenized staked KSM from the Liquid Staking protocol

    • kUSD: multi-collateralized stablecoin

  • Foreign Tokens

    • KSM: crossed to Karura from Kusama Relay Chain

    • Tokens originated from other parachains

    • Tokens crossed from other blockchains such as ETH, renBTC or Compound CASH

  • ERC20 Tokens

    • Token issued by ERC20 contracts deployed in Karura EVM


Token balances

Query chain state to get token balances.

Native token (KAR) balances

Query system module to get native token (KAR) balances data.


  • Returns the AccountInfo of given account. For different types of balances, check the fields in

    • free: the free balance.

    • reserve: the reserved balance.

Other tokens

For non-native tokens, like KSM, LKSM, kUSD, query tokens module to get balances info.


  • Returns the OrmlAccountData of given account and currency ID. For different types of balances, check the fields:

    • free: the free balance.

    • reserved: the reserved balance.


  • Returns the BalanceLock of given account and currency ID. BalanceLock has two fields:

    • id: the lock identifier.

    • amount. the locked amount.

  • Note locks could be overlapped, and the same amount of tokens could be under locked by multiple locks.

Send Tokens





xtokens transfer by XCM

  • ORML's Xtokens Module supports token transfer by cross-consensus messages (XCM), and has a number of dispatchable functions to support different use cases.

  • xtokens transfer functions: xtokens.transfer xtokens.transfer_multiasset xtokens.transfer_with_fee




  • Can be used to send any supported tokens in the source and destination networks, including ERC20 tokens.

Receive Tokens

There are multiple ways to detect incoming balance transfers:

  • Monitor events

  • Subscribe storage changes

  • Monitor transactions

Monitor Events

Monitoring events is a recommended way to track incoming balance transfers. It can handle ALL types of transfer transactions including the one that is not initiated by a transaction directly (e.g. delayed proxy).





Storage changes RPC

  • state_subscribeStorage

    • Subscribe to a list of account balances. However, it does not guarantee subscription delivery due to connection errors or blockchain reorg.

Monitor Transactions

It is possible to fetch transactions in every block, check for transfer transactions, and check if the transfer transaction is successful. However, this may likely yield false-negative results i.e. deposit received but failed to recognize, due to the various ways for transfer.

Refer to Send Tokens section for direct transfer transactions. In additional, to sending transfer transactions individually, there are common utility methods to batch send transfer transactions:


  • This can be used to send batch transaction

  • NOTE: batched transactions will always emit success events.

    • utility.BatchCompleted event indicates that all transactions are successful

    • utility.BatchInterrupted event indicates which transaction failed. Transactions before the failed transaction are executed successfully and will not be reverted.


Last updated