ccxt: EXMO fetchCurrencies() is missing currencies

Thanks again @kroitor !

@davidonlaptop i’ve uploaded the fix for USDT, however, on BCH they say this: https://exmo.me/en/news_view?id=2989

Sorry to insist, but the latest version (1.27.91) brings ATOM and GBP, however we lost BCH and USDT. USDT is present in the fees section.

*** exmo: Missing currencies: BCH HP USDT XTZ

I see, it’s not in the fees section.

Okay that works!

P.S. The new build will arrive in version 1.27.90 in 15 minutes.

@davidonlaptop i’ve uploaded an update to EXMO metainfo, that fixes ATOM and GBP. However, we can’t find anything about HP or XTZ here:

• https://exmo.me/ctrl/feesAndLimits
• https://exmo.com/ctrl/feesAndLimits

So, you might really want to forward your question on HP / XTZ to EXMO.

On the script - thank you very much for it! The problem is that it false alarms, since 4BCH, 4BTC are not currencies – those are just the way for Bibox to label their stuff. You would still use the BCH, BTC currencies to withdraw and deposit, not 4BCH nor 4BTC – those are the names of perpetual contracts. Bibox uses those 4xxx symbols to differentiate spot pairs from contracts. So a general script does not help resolve this – we still have to look into each exchange and their rules in particular. If you find more bugs like EXMO – let us know. We will fix the specific exchanges, where there is a bug indeed.

Closing this for now if you don’t mind. Feel free to reopen it or just ask further questions if you have more. Thx again for the feedback, we really appreciate your involvement!

Contents of file bug-report.js:

const ccxt = require('ccxt');

// Synopsis: node bug-report.js <exchange> <apiKey> <secret>
// Synopsis: node bug-report.js <exchange> <apiKey> <secret> <uid>
const args = process.argv.slice(2);
const exchangeCode = args[0];
const apiKey = args[1];
const secret = args[2];
const uid = args[3];  // Optional

function unique(arr) {
  return arr.filter((value, idx, theArray) => theArray.indexOf(value) === idx);
}

(async () => {
  const exch = new ccxt[exchangeCode]({
    enableRateLimit: true, 
    apiKey, 
    secret,
    uid
  });

  const markets = await exch.loadMarkets(true);

  console.info("Markets found: %s", Object.keys(markets).sort().join(' '));
  console.info("Currencies found: %s", Object.keys(exch.currencies).sort().join(' '));
  
  const missingCurrencies = [];
  for (const market of Object.values(markets)) {
    if (!(market.base in exch.currencies)) {
      missingCurrencies.push(market.base);
    }

    if (!(market.quote in exch.currencies)) {
      missingCurrencies.push(market.quote);
    }
  }

  const sortedAndUnique = unique(missingCurrencies.sort());
  if (sortedAndUnique.length > 0) {
    console.warn("*** %s: Missing currencies: %s", exchangeCode, sortedAndUnique.join(' '));
  }
})();

It can be executed with:

node bug-report.js bibox MYKEY MYSECRET

or

node bug-report.js bibox MYKEY MYSECRET UID

If it finds missing currencies it will print:

*** bibox: Missing currencies: 4BCH 4BTC 4EOS 4ETH 4LTC

Ah great! thanks 😃

Thanks @kroitor , it’s true that XTZ_BTC does not seem tradeable, but BTC/GBP appears to be so, and GBP is missing.

When digging in the source of fetchCurrencies() it seems to rely on fetchFundingFees() but lost the track from there: https://github.com/ccxt/ccxt/blob/4e279314b5a9cec22e5a83e37370b9e83ea1ee21/js/exmo.js#L523