Seems that lumens are not recognised and fall back to undefined

[KIC]

I use kraken exchange and I query the ordery by using fetchMyTrades. It seems that Lumens (XLM) are not supported by the generalized API.

6:05:07 PM:   Object {
6:05:07 PM:     "action": "buy",
6:05:07 PM:     "amount": ??,
6:05:07 PM:     "info": Object {
6:05:07 PM:       "cost": "??",
6:05:07 PM:       "fee": "??",
6:05:07 PM:       "id": "TNS6ZE-O67HH-XXXXXX",
6:05:07 PM:       "margin": "0.00000000",
6:05:07 PM:       "misc": "",
6:05:07 PM:       "ordertxid": "O6VUNT-ZS3L5-XXXXX",
6:05:07 PM:       "ordertype": "limit",
6:05:07 PM:       "pair": "XXLMZEUR",
6:05:07 PM:       "price": "",
6:05:07 PM:       "time": ,
6:05:07 PM:       "type": "buy",
6:05:07 PM:       "vol": "",
6:05:07 PM:     },
6:05:07 PM:     "price": 0.015805,
6:05:07 PM:     "symbol": undefined,
6:05:07 PM:   },

[kroitor]

Hi! Thanks for reporting, i'll take a look into it and will get back to you asap!

[kroitor]

This issue should be fixed in version 1.9.224+. Can you please update the library and retry the same code again? We will be thankful if you report back whether it works for you or not (it should). Thx, standing by for your reply.

[KIC]

Thanks for your really fast reaction. Sadly I still have an undefined symbol on the following transaction

 Object {
  "cost": "000000",
  "fee": "0.0000",
  "id": "TNS6ZE-O67HH-XXXXXX",
  "margin": "0.00000000",
  "misc": "",
  "ordertxid": "O6VUNT-ZS3L5-XXXXXX",
  "ordertype": "limit",
  "pair": "XXLMZEUR",
  "price": "0.01580500",
  "time": 1502625003.5281,
  "type": "buy",
  "vol": "0000000",
}

I have upgraded to 1.9.227

npm list
AwesomeProject@0.1.0 C:\Users\KIC\AwesomeProject
+-- ccxt@1.9.227
| +-- crypto-js@3.1.9-1
| +-- node-fetch@2.0.0-alpha.8
| `-- qs@6.5.0
+-- expo@21.0.2

[kroitor]

@KIC

Sadly I still have an undefined symbol on the following transaction

You're looking at unparsed 'info' substructure, you should look into fetchMyTrades parsed return for symbol should be there. Try this:

"use strict";
const ccxt = require ('ccxt')
(async function main () {

    const kraken = new ccxt.kraken ({
        apiKey: "YOUR_API_KEY",
        secret: "YOUR_SECRET",
    }) 

    const trades = await kraken.fetchMyTrades ()

    trades.forEach (trade => console.log (trade.id, trade.datetime, trade.symbol))
}) ()

[KIC]

this is what I do:

kraken.fetchMyTrades()
          .then(ob => {
            //console.log(ob.map(o => { return { action: o.side, symbol: o.symbol, amount: o.amount, price: o.price, info: o.info  }}))
            console.log(ob.reduce((res, o) => {
              res[o.symbol] = res[o.symbol] || [];
              res[o.symbol].push({ symbol: o.symbol, amount: o.amount * (o.side == "buy" ? 1 : -1), price: o.price })
              if (o.symbol == undefined) console.warn(o.info)
              return res;
            }, {}))
          })

the result is still undefined:
],
11:25:25 AM: "undefined": Array [
11:25:25 AM: Object {
11:25:25 AM: "amount": 000000,
11:25:25 AM: "price": 0.015805,
11:25:25 AM: "symbol": undefined,
11:25:25 AM: },
11:25:25 AM: ],

[kroitor]

Try this:

kraken.fetchMyTrades().then(ob => {
    ob.forEach (trade => console.log (trade.symbol))  
})

Does it output undefined symbols? If it does, we will debug it further.

[KIC]

I don't see how this should be different but here we go:

11:44:15 AM: ETH/EUR
11:44:15 AM: ETC/EUR
11:44:15 AM: LTC/EUR
11:44:15 AM: undefined
11:44:15 AM: ZEC/EUR

[KIC]

or kraken.fetchMyTrades().then(ob => { ob.forEach (trade => console.log (trade.symbol, trade.info.pair))})

results in:
11:47:50 AM: undefined XXLMZEUR

Hmmm I am pretty sure this pair is not traded anymore. But anyhow for historic P/L claculations I would prefer not to be forced using the unparsed info field.

[kroitor]

The problem is indeed caused by the Kraken not returning market info for XLM/EUR anymore. We can't add it to the list of active markets, because users will be confused and will try trading it. I will add a workaround for that, so that it will be defined in trades and orders.

[kroitor]

@KIC ok, can you please update to 1.9.228+ and try the same code again? XLM/EUR should be recognized and parsed correctly now. Let us know if it works for you or not. Thx!

[KIC]

yes thats it! thx!