There is no bug. Stop order is not created immediately. The system will attempt to create it when the stop price is reached, and if you don't have enough funds at that point then the order will not be created.
There is also a difference between stop and stop-limit orders. You should probably read up on how it works before making another molehill into a mountain.
Topic: Possible bug in Kucoin Stop-limit order. (Read 100 times)
I was working on selling some BTC for USDT. Not sure about what price to check in so this morning when price was under $23k I thought to set a limit order at $24,5xx for the whole amount I sent to the exchange. Earlier half an hour ago I thought to set a stop limit at $20k just not to miss much down when I saw $22.5xx. Obviously a little confuse what to try. The amount is not much anyway.
Interestingly, I forgot that I had a limit order set on $24,5xx for the whole amount. But then how my stop limit order was taken? So I checked the tabs and noticed that in both tabs (limit and stop-limit) I have the orders but the math does not add up.
Tabs
The amount that I sent to the exchange was 0.11
Limit order on $24,5xx was 0.11
Stop limit order 0.01 BTC
I now tried with 0.1 BTC in the stop-limit and walla, it was placed!
I tried with 1 BTC, placed! 2 BTC placed!! 4 BTC placed!!!
All stop limit.
When I try with the amount % buttons (25%, 50%, 75%, 100%) it does not bring up any amount (because all the amounts are already in use for the limit order) but when I type any BTC amount and hit the sell button it takes the order.
% buttons.
Amount box
Anyway, I hope now you get an understanding about the topic and the following bugs I spotted so far.
Bug1: Those % button works when the amounts are in used as limit order.
Bug2: The manual entry box (amount you want to sell) do not give any warning, in fact takes any amount you put there.
Bug3: If the amounts are not in use meaning not in limit order then in the % button it always shows your coins no matter if they are in use with limit-order.
Bug4: Any stop-limit do not make any affect in the total asset page. The amount always shows in the available balance instead
Bug5: Even though it's taking those wrong stop-limit trade calls but the system is cancelling the trades when the conditions are true. (I think because of this no messed up with it yet or kucoin would have massive loss)
Overall these are some front end validation works imo. This should be fixed soon.
Interestingly, I forgot that I had a limit order set on $24,5xx for the whole amount. But then how my stop limit order was taken? So I checked the tabs and noticed that in both tabs (limit and stop-limit) I have the orders but the math does not add up.
Tabs
The amount that I sent to the exchange was 0.11
Limit order on $24,5xx was 0.11
Stop limit order 0.01 BTC
I now tried with 0.1 BTC in the stop-limit and walla, it was placed!
I tried with 1 BTC, placed! 2 BTC placed!! 4 BTC placed!!!
All stop limit.
When I try with the amount % buttons (25%, 50%, 75%, 100%) it does not bring up any amount (because all the amounts are already in use for the limit order) but when I type any BTC amount and hit the sell button it takes the order.
% buttons.
Amount box
Anyway, I hope now you get an understanding about the topic and the following bugs I spotted so far.
Bug1: Those % button works when the amounts are in used as limit order.
Bug2: The manual entry box (amount you want to sell) do not give any warning, in fact takes any amount you put there.
Bug3: If the amounts are not in use meaning not in limit order then in the % button it always shows your coins no matter if they are in use with limit-order.
Bug4: Any stop-limit do not make any affect in the total asset page. The amount always shows in the available balance instead
Bug5: Even though it's taking those wrong stop-limit trade calls but the system is cancelling the trades when the conditions are true. (I think because of this no messed up with it yet or kucoin would have massive loss)
Overall these are some front end validation works imo. This should be fixed soon.
Jump to: