iov-one / asset-directory Goto Github PK

Add certik CTK

CI should be there with basic tests/checks related to addition to assets

• Must include verification of added asset's symbol existence on coingecko
• Should check if every asset has required props ( can be done with tsc )

Project currently stores asset with their key being asset's symbol, which creates conflict when same coin is registered with same symbols on different networks

We should find a way to support assets on multiple networks
For example:

{ 
   id: "usd-coin", 
   symbol: "usdc", 
   name: "USD Coin" 
},
{
   id: "usd-coin-avalanche-bridged-usdc-e",
   symbol: "usdc",
   name: "USD Coin Avalanche Bridged (USDC.e)",
},

Are 2 different coins but with same symbol and are on different network

Drop the C-Chain text.

• ROWAN is Sifchain's token https://sifchain.finance/
  • symbol: ROWAN
  • name: Sifchain
  • logo: https://dex.sifchain.finance/images/tokens/ROWAN.svg
• DSM is Desmos' token https://www.desmos.network/
  • symbol: DSM
  • name: Desmos
  • logo: https://www.desmos.network/img/desmos-logo.svg

People can't find DAI in the Starname Manager's list of coins because we have it named Multi-collateral DAI. People just look for DAI and, since the coin list is sorted alphabetically, they don't find our Multi-collateral DAI.

Here's more info about "Polygon MATIC" - https://coinmarketcap.com/currencies/polygon/

Here's more info about "Dogeparty XDP" - https://coinmarketcap.com/currencies/dogeparty/

• Drop UCRegistry as its an obsolete package now
• Remove usage of caip19 prop for assets as we were using it just for integration with wallets but we already have this on manager with IBC config
• Have asset's data in its own directory ( dont use separate metadata dirs for each asset )
• Check status of each asset beforehand if found in trustwallet asset ( like active or abandoned ) discard abandoned letting user know
• Check asset symbol on coinGecko first else exit with msg
• Simplify aggregation script
• Add support of TypeSscript ( thus easy imports )

We will still use trustwallet as a submodule as we rely on their info just to make it easy on the user but we will surely have the option to override things and provide manually... if we dont agree on naming / other prop for an asset

This will help locating exact coin from coins list from coingecko and can be used via third parties easily

WIOV is dead. Drop ERC20 version of the IOV token.
Change AVAX C-Chain to AVAX

our partner and starname user Request network is adding a new asset to their app and they ask us to add it into our asset list

this is a ERC20, contract id: https://explorer.celo.org/address/0x765de816845861e75a25fca122bb6898b8b1282a/transactions

Coingecko api should be queried first

Advantages:

• Will prevent breaking.. payment behaviour of starname app
• Found coin's name after api call can be used as a fallback name if not found on trustwallet registry and should be showed to user for suggestion