Acala Wiki
V1.0.1, English
Search…
⌃K
Links

Token Transfer

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

Token Types

Token

Symbol
Description
CurrencyId
Decimals
Minimal Balance
ACA
native token of Acala network
Token(ACA)
12
0.1 ACA
aUSD
multi-collateralized stablecoin
Token(AUSD)
12
0.1 aUSD
DOT
crossed to Acala from Polkadot Relay Chain
Token(DOT)
10
0.01 DOT
LDOT
tokenized staked DOT from the Liquid Staking protocol
Token(LDOT)
10
0.05 LDOT
AssetRegistry registered the metadata info of this type token.

DexShare

The lp share token for the trading pair of Acala DEX. The CurrencyId type of Acala 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(ACA), Token(AUSD)) is the CurrencyId of lp token of ACA/aUSD pair, its decimal is 12, and minimal balance is 0.1, these are same as ACA.
Currently, AssetRegistry does not register metadata info of any lp token.

Erc20

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

LiquidCrowdloan

Symbol
Description
CurrencyId
Decimals
Minimal Balance
LcDOT
tokenized liquid receipt of crowdloaned DOT
LiquidCrowdloan(13)
10
0.01 LcDOT
AssetRegistry registered the metadata info of this type token.

ForeignAsset

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

Query token's metadata on assetRegistry

query asset metadata

Tools

Token balances

Query chain state to get token balances.

Native token (ACA) balances

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

system.account

  • Returns the AccountInfo of given account. For different types of balances, check the fields in AccountInfo.data
    • free: the free balance.
    • reserve: the reserved balance.

Other tokens

For non-native tokens, like DOT, LDOT, aUSD, query tokens module to get balances info.

tokens.accounts

  • 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.

tokens.lock

  • 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

Transactions

currencies.transfer

currencies.transferNativeCurrency

balances.transfer

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).

balances.transfer

currencies.transfer

currencies.deposit

xtokens.transferred

xtokens.transferredmultiasset

Storage changes RPC

    • 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:

utility.batch

  • 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.

utility.batchAll