Currently, we use two files:
There is a coins list in coins.json. One coin can be presented as follows:
"name": "Aptos Coin",
source- enum data type with strict value check. If you’d like to add the new value into it, fill the form. Usually source is the name of a partner's company to add many coins into the list. We support now following sources:
aptos- for the native Aptos Coin.
partners- for other coins.
celer- for coins provided by Celer.
layerzero- for coins provided by Layer Zero.
wormhole- for coins provided by Wormhole.
name- coins' full name. We update this value by a request to the node. It is used on Picture 1 as a bottom string after the dot (on the picture it is Bitcoin).
chainId- for mainnet value is 1. Currently, testnet coins stored in the
testnetbranch of this repo.
decimals- how many decimals supports your coin. We update this value by a request to the node.
symbol- it is used to construct a coin alias, which can be equal to symbol as on Picture 1 in the top string.
type- full type of coin. String with following structure ADDRESS::MODULE::COIN, e.g.
caution- if we need to show warning icon near the coin - we will add the caution field.
order- order of coin in coins list. Current logic:
60 BUSD / BNB
1000 other coins
coinX- full type of coin. String with following structure ADDRESS::MODULE::COIN, e.g.
coinY- full type of coin. String with following structure ADDRESS::MODULE::COIN, e.g.
⚠️ Coins should be sorted.
curve- to strictly point curve type use the following values:
- selectable - will keep switcher for a curve type available for declared coins pair.
- uncorrelated - keep only uncorrelated curve pool on UI.
- stable - keep only stable curve pool on UI.