gitcoinbot
commented
2 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 60.0 BUSD (59.71 USD @ $1.0/BUSD) attached to it as part of the diadata-org fund.
- If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin's Discord
- $4,488,833.36 more funded OSS Work available on the Gitcoin Issue Explorer
This task consists in mapping token symbol tickers from crypto exchanges onto the full information uniquely defining the underlying asset. As an example, the symbol ticker DIA on Binance exchange should be mapped onto the asset with the properties Blockchain: Ethereum Address: 0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419
Native assets which don't have a proper address (such as FTM on Fantom blockchain) should be assigned the zero address 0x0000000000000000000000000000000000000000 on the respective blockchain.
The list of symbols to be identified can be found at this API endpoint: https://rest.diadata.org/v1/missingToken/ByBit
A list of candidates for symbol tokenSymbolTicker can be found at this API endpoint: https://rest.diadata.org/v1/token/:tokenSymbolTicker
Please submit your work two-fold:
Regarding the format of the submitted json file please use diadata/config/gitcoinverified/testfile.json in the master-ibm-tmp branch as a template. In case you are using a source other than the above mentioned API endpoint please make sure Ethereum addresses are EIP55 compliant.
We remark that although this is a somewhat straightforward task, some of the symbols might require a closer look. For instance REP traded on Kraken refers to the token with address 0x221657776846890989a759BA2973e427DfF5C9bB. However, looking into the underlying contract (for instance on etherscan) we can see that the symbol is REPv2.