liqui: symbols are not unified
See original GitHub issueHi, guys, this library is awesome!
Playing with different exchanges have found that ccxt
doesn’t unify symbols for Liqui:
> liqui.fetchOrderBook('BTC/USD');
> (node:13656) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): Error: liqui {"success":0,"error":"Invalid pair name: undefined"}
Fetching ‘BTC/USDT’ works.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Unified Soil Classification System
UNIFIED SOIL CLASSIFICATION AND SYMBOL CHART. COARSE-GRAINED SOILS. (more than 50% of material is larger than No. 200 sieve size.) ... Liquid limit...
Read more >Solved 5.9 Classify the following soils usin symbols an g
Question: 5.9 Classify the following soils usin symbols an g the Unified Soil Classification System (UScs). Give the group d the group name....
Read more >unified soil classification system with 2 symbol chart
Symbol chart of a unified soil classification system. ; sc, clayey sand course ; Fine-grained soils 50% or more passing the No.200 (0.0029mm) ......
Read more >File Standards Guide - Liquipedia Commons Wiki
Team logo "std" files are being phased out entirely and should no longer be created. A single unified file is going to act...
Read more >Batch fetch operations · Issue #7 · ccxt/ccxt
I see following three unified API operations which would ideally have their batch equivalent: fetchOrderBook (symbol): Fetch an order book ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm… I just assumed that if an exchange trades only USDT (e.g. w/o USD) it would be convenient to abstract it to plain USD.
But now I think that such abstraction will leak on exchanges with USDT/USD pairs.
Thanks!
@ManuelSchneid3r Kraken has both USD and USDT for withdrawal and trading. We will probably add substitutions for Bitfinex.