Understanding THORChain Asset Notation
THORChain uses a CHAIN.ASSET notation for all assets. TICKER and ID are added where required. The asset full notation is pictured.
L1 Asset Notation
There are three kinds of assets within THORChain:
- Layer 1 (L1) chains are always denoted as
CHAIN.ASSET, e.g. BTC.BTC.
- As two tokens can live on different blockchains, the chain can be used to distinguish them. Example: USDC is on the Ethereum Chain and Avalanche Chain and is denoted as
AVAX.USDCrespectively; note the contract address (ticker) was removed for simplicity.
- Tickers are added to denote assets and are required in the full name. For EVM based Chains, the ticker is the ERC20 Contract address, e.g.
ETH.USDC-0XA0B86991C6218B36C1D19D4A2E9EB0CE3606EB48. This ensures the asset is specific to the contract address. The pools list shows assets using the full notation.
- IDs are required for the Binance Beacon chain as BNB.RUNE is not sufficient to distinguish between Mainnet and Testnet assets. For example,
BNB.RUNE-B1Adenoted Mainnet RUNE and
BNB.RUNE-67Cdenoted Testnet RUNE.
THOR.RUNE is the only RUNE asset in use. All other RUNE assets on other chains are no longer in use and have no value within THORChain.
- Synthetic Assets are denoted as
CHAIN.ASSET, e.g. Synthetic BTC is
BTC/BTCand Synthetic USDT is
ETH/USDT.While Synthetic assets live on the THORChain blockchain, they retain their CHAIN identifier.
- Synthetic Assets can only be created from THORChain-supported L1 assets and are only denoted as
CHAIN/ASSET, no ticker or ID is required.
- Chain differentiation is also used for Synthetics, e.g.
AVAX/USDCare different Synthetic assets created and redeemable on different chains.
- Derived Assets, currently specific to Lending, are denoted as
THOR.BTCis Derived Bitcoin.
- All Derived Assets live on the THORChain blockchain and do not have a Chain identifier.
- Currently, Derived Assets are used internally within THORChain only.