Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

[2] native "kraken" integration should not restrict markets #578

Open
nikhilsaraf opened this issue Nov 9, 2020 · 3 comments
Open

[2] native "kraken" integration should not restrict markets #578

nikhilsaraf opened this issue Nov 9, 2020 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@nikhilsaraf
Copy link
Contributor

see last set of comments here: #421

kraken currently limits markets, whereas it is not limited on centralized exchanges. this is because of the API limitations of kraken that requires us to manually override asset names in a custom asset converter function.

for this task we should find a list of all the names for each asset and update KrakenAssetConverter and KrakenAssetConverterOpenOrders to expand the options available.

@nikhilsaraf nikhilsaraf added the bug Something isn't working label Nov 9, 2020
@nikhilsaraf nikhilsaraf added this to the v1.10.1 milestone Nov 9, 2020
@nikhilsaraf nikhilsaraf modified the milestones: v1.10.1, v1.11.0 Nov 9, 2020
@Arno500
Copy link

Arno500 commented Jan 6, 2021

It seems that list is available @ https://api.kraken.com/0/public/AssetPairs
It's also available in the API client library as a public API.
The wsname key contains the name of both of the assets, separated by a /.

@nikhilsaraf
Copy link
Contributor Author

@Arno500 are there any assets you want to trade using Kelp but which are not currently supported?

@Arno500
Copy link

Arno500 commented Jan 6, 2021

@nikhilsaraf Yes, I'm in Europe, so using EUR :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants