![]() or a tuple (BaseAsset_dict, QuoteAsset_dict).the pair retrieval function should return:.On the 'pair retrieval and check' side: to make the check, if a value: using this value to filter the data as I implemented it originally.if None, then no filtering, the full bunch of QuoteAssetis kept.an additional parameter, specific here to Coingecko: quote_asset: str = None.the 'pair' in cryptofeed wording (which is then here the BaseAsset).on Coingecko feed side, that the user enters.Then whith WhaleAlert, I implemented that supports a full bunch of parameters.To prevent returning the full list of an asset price in all QuoteAsset provided by Coingecko, and to stick to initial cryptofeed layout, I proposed to use a pair. QuoteAsset in case of CoinGecko acts as a filter.We have to find a way to distinguish them.īeta Was this translation helpful? Give about what I initially implemented: The crypto-currencies digital-assets ecosystem is extending quickly and we have assets sharing the same symbol! For example, CoinGecko supports six assets with the same GOLD symbol: CoinGecko idĬurrently, Cryptofeed is using the same normalized GOLD to refer to all these six different assets. If we do NOT find a simple way to list the pairs, we may have to limit the CoinGecko capabilities, or to adapt Cryptofeed to accept retrieving pairs that are unknown at startup time.īUT there is another big issue. The pairs combinations of 60 quote assets and 232 base assets is about 14000, not so far from 13000. From my investigations, Cryptofeed retrieves market info for about 232 unique base assets. Let's say, we use the above endpoint and we append USDT => We have 60 quote assets. But USDT is missing in this list, and maybe some other ones.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |