Asset Notation
Understanding THORChain Asset Notation
Last updated
Was this helpful?
Understanding THORChain Asset Notation
MAYAChain uses a CHAIN.ASSET notation for all assets. TICKER and ID are added where required. The asset full notation is pictured.
There are three kinds of assets within MAYAChain:
Layer 1 Assets - CHAIN.ASSET
Synthetic Assets - CHAIN/Asset
Bitcoin
BTC.BTC (Native BTC)
Bitcoin
BTC/BTC (Synthetic BTC)
Bitcoin
MAYA.BTC (Derived BTC)
Ethereum
ETH.ETH
USDT
ETH.USDT-0xdac17f958d2ee523a2206206994597c13d831ec7
DASH
DASH.DASH (Native)
DASH
DASH/DASH (Synth)
CACAO
THOR.RUNE
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 Arbitrum Chain and is denoted as ETH.USDC and ARB.USDC respectively; 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.
Synthetic Assets are denoted as CHAIN/ASSET instead of CHAIN.ASSET, e.g. Synthetic BTC is BTC/BTC and Synthetic USDT is ETH/USDT. While Synthetic assets live on the MAYAChain blockchain, they retain their CHAIN identifier.
Synthetic Assets can only be created from MAYAChain-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. ETH/USDC and ARB/USDC are different Synthetic assets created and redeemable on different chains.
Last updated
Was this helpful?
Was this helpful?