Closed cydantor856 closed 3 years ago
For quick help - simply set "use_order_book" to false? Kucoin is not an officially supported exchange - so while it may work, certain things may not (like orderbook apparently) due to some exchange specifics.
Apart from that (in general, not necessarily related to this exchange in particular) - you should use use_order_book
consistently across buy and sell settings, otherwise you might encounter some odd effects (its not guaranteed the 2 values are 100% aligned by the exchange api's ... ).
FYI, i tried use_order_book
to false in the live run and it works fine but I would like to use use_order_book
in order to get a better entry price etc if possible. Can I know if this has to be fixed at kucoin or ccxt or freqtrade end? i tried even adding ccxt settings like below but not luck. don't know if I put it in the right manner.
"exchange": { "name": "kucoin", "key": "", "secret": "", "password": "", "ccxt_config": { "enableRateLimit": true, "limit ": 20 }, "ccxt_async_config": { "enableRateLimit": true, "rateLimit": 200, "limit ": 20 } },
I found this link in ccxt issues section and I am bit confused how to implement the code as mentioned there in freqtrade. kindly have a look : https://github.com/ccxt/ccxt/issues/8138
I feel like freqtrade code has to be modified according to those changes. i saw similar incident regarding bittrex at : https://github.com/freqtrade/freqtrade/issues/3865
Additionally, unlike Binance exchange settings, I had to add a password tag to the exchange config for the passphrase created at kucoin for each API other than key and secret (mentioned in the first post) so I think it is better if you can mention that on exchange specific notes section on freqtrade website. normally in Binance settings, we do not have to use the password attribute. that's why.
@cydantor856 please IMMEDIATELY revoke your exchange keys - i edited them out from the above post - but they'll stil be in the history.
Yes, it'll either need a custom setting (for kucoin) - or a change (subclassing) for the kucoin exchange.
It's not something that can be done by ccxt, but should be handled at freqtrade level (we do however not have the capacity to test all exchanges / implement all "oddities" for all exchanges).
in theory, you should be able to add the following to your exchange config:
"_ft_has_params": {
"l2_limit_range": [20, 100]
}
Additionally, unlike Binance exchange settings, I had to add a password tag to the exchange config for the passphrase created at kucoin for each API other than key and secret (mentioned in the first post) so I think it is better if you can mention that on exchange specific notes section on freqtrade website. normally in Binance settings, we do not have to use the password attribute. that's why.
You're correct, it's not mentioned, you're probably the first to use the kucoin exchange - and exchange-specific notes are there only for actively supported exchanges as they may have to change over time - and i can't maintain these notes for exchanges i don't use.
hi thanks a lot for reminding exchange keys. and kucoin is also very popular exchange and the fifth one at cmc ranking : https://coinmarketcap.com/rankings/exchanges/ just after big exchanges binance, coinbase, kraken etc. and lots of people using kucoin because it has listed lots of coins comparing other exchanges FYI. Please kindly if possible add the necessary kucoin specific changes to freqtrade code according to your schedule. love your work and thanks a lot for the support. i will check _ft_has_params
and let you know status.
_ft_has_params
seems to do the trick for now. Thanks a lot. I added as below in exchange config and running on live mode at the moment and I can confirm that error kucoin fetchOrderBook limit argument must be None, 20 or 100
not happening.
"_ft_has_params": { "l2_limit_range": [ 20, 100 ] }
With the latest develop version this should now work without this "config fix/hack".
obviously it'll populate to the next release ....
Describe your environment
Your question
I tried a strategy with live account which using order book enabled in kucoin exchange. below are the related config if helps
related terminal messages are here :
FYI in dry run mode all works just fine which does not use order book at all. Only this occur when I try live with order book with above config. And also key related I use structure lise this