Kraken gets mad when you configure unknown pairs #24

New issue

Closed

opened 2018-12-17 15:40:45 -08:00 by scionaltera · 2 comments

scionaltera commented

2018-12-17 15:40:45 -08:00

(Migrated from github.com)

May need to add some sort of per-exchange filtering of currency pairs to fix this. The getTickers() call throws an exception when you have pairs in your configuration that the exchange doesn't support. I suspect other exchanges are working because they don't implement getTickers() and when the individual getTicker() calls fail it just happens silently?

May need to add some sort of per-exchange filtering of currency pairs to fix this. The `getTickers()` call throws an exception when you have pairs in your configuration that the exchange doesn't support. I suspect other exchanges are working because they don't implement `getTickers()` and when the individual `getTicker()` calls fail it just happens silently?

scionaltera commented

2019-01-05 22:16:46 -08:00

(Migrated from github.com)

Another approach might be a list of supported pairs per-exchange rather than having any global list. It'd be more typing but the configuration would be a lot more expressive. You could also potentially set properties for each pair, such as whether margin is supported and what the fees are.

scionaltera commented

2019-01-12 21:51:09 -08:00

(Migrated from github.com)

Closed by #47. Just don't list pairs on your exchange that the exchange doesn't support.

Commenting is not possible because the repository is archived.