Skip to content
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.

BitFinex ticker API - incorrect symbol value for DASH #48

Closed
janakerman opened this issue Dec 15, 2017 · 5 comments
Closed

BitFinex ticker API - incorrect symbol value for DASH #48

janakerman opened this issue Dec 15, 2017 · 5 comments

Comments

@janakerman
Copy link
Contributor

When subscribing for the pair DASH/BTC from the BitFinex ticker, an symbol: invalid response is received. (This actually results in a NullPointerException 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?

@dozd
Copy link
Member

dozd commented Jan 5, 2018

Meta data json files are taken from Xchange library so if it's the fix you must propose a PR there.

@janakerman
Copy link
Contributor Author

Good point - I'll raise it there instead.

@electic
Copy link

electic commented Feb 5, 2018

Was there a resolution to this @janakerman? Did you figure it out?

@janakerman
Copy link
Contributor Author

@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:

"dshusd",
"dshbtc",

XChange's Bitfinex metadata doesn't have these pairs, so that's the problem I think. Haven't had the time to verify though.

@nonlinear5
Copy link

nonlinear5 commented Mar 2, 2018

I have the same issue, with additional currency pairs which are deemed "invalid":

{"channel":"book","pair":"ASHBTC","prec":"R0","len":"100","event":"error","symbol":"DASHBTC","msg":"symbol: invalid","code":10300} {"channel":"book","pair":"ASHUSD","prec":"R0","len":"100","event":"error","symbol":"DASHUSD","msg":"symbol: invalid","code":10300} {"channel":"book","pair":"CCBTC","prec":"R0","len":"100","event":"error","symbol":"BCCBTC","msg":"symbol: invalid","code":10300} {"channel":"book","pair":"CCUSD","prec":"R0","len":"100","event":"error","symbol":"BCCUSD","msg":"symbol: invalid","code":10300} {"channel":"book","pair":"CUBTC","prec":"R0","len":"100","event":"error","symbol":"BCUBTC","msg":"symbol: invalid","code":10300} {"channel":"book","pair":"CUUSD","prec":"R0","len":"100","event":"error","symbol":"BCUUSD","msg":"symbol: invalid","code":10300}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants