-
Notifications
You must be signed in to change notification settings - Fork 222
BitFinex ticker API - incorrect symbol value for DASH #48
Comments
Meta data json files are taken from Xchange library so if it's the fix you must propose a PR there. |
Good point - I'll raise it there instead. |
Was there a resolution to this @janakerman? Did you figure it out? |
@electic - I haven't submitted a ticket specifically for this instance, but I have raised one for a similar scenario. Also BitFinex's symbol's API is now working as expected and shows the following pairs in the response:
XChange's Bitfinex metadata doesn't have these pairs, so that's the problem I think. Haven't had the time to verify though. |
I have the same issue, with additional currency pairs which are deemed "invalid":
|
When subscribing for the pair
DASH/BTC
from the BitFinex ticker, ansymbol: invalid
response is received. (This actually results in aNullPointerException
but that is a separate issue.)This is the request message that is sent out:
{"event":"subscribe","channel":"ticker","pair":"DASHBTC","prec":null,"len":null}
This is the response received:
{"channel":"ticker","pair":"ASHBTC","event":"error","symbol":"DASHBTC","msg":"symbol: invalid","code":10300}
When you play with the BitFinex's websocket API on their websocket playground, it behaves the same, but when you use the pair
DSH/BTC
it starts to send updates. I can only assume that this is DASH as the base, because their/symbols
API doesn't work as advertised.Looks like BitFinex API simply expects a different currency symbol that the
Currency
- probably just a configuration update for that exchanges meta data json file?The text was updated successfully, but these errors were encountered: