@Dargo and @Kraken-support staff

(Please, forward to Jesse Powell and Kraken Management Team:)

As for the trading engine lags which costed me so much money in the last couple of months, mainly as forced losses due to not being able to close position, ...
I've just decided to leave Kraken, and I've successfully withdrawn quite a large amount (more than 99.5%) of my coins ( btc withdrawal ). I keep only a very small amount of coins at kraken.

Kraken - today you have lost another big client
- and as you already assume right
- you can only blame yourself for it.



A note to all Kraken clients: Here is why I have withdrawn almost all my coins from Kraken:

1- most of the time I am unable to input orders / open long or short positions
2- most of the time I am unable to close positions

3- as a market-maker: My matched and crossed limit orders for opening/closing positions are not (or sometimes even too late) being executed.
4- as a mark-taker: My market and limit orders for opening/closing positions are not going through

5- Kraken engine needs always a very! long time to display an order has been accepted.
    Thus, when I try to close a long, Kraken does NOT confirm it in a timely manner on the screen.
    So I am unable to know: Was that position closed or not ?
    Once I see no reaction, I try to close the same long again, just to be sure it is closed.

    But what I am now ending up with is:
    1x closed long + 1x new opened short position
    - and due to the extremely big lag of their engine, I will figure that only after minutes (that's when it's usually to late).

   Imagine that:

    You want to close your long to take in profit or cut losses,
    but what you get is a new opened short which produces even more losses or cut even more profits - it's disastrous !

    IMO, a (hypothetical) responsible Kraken management would have CLOSED KRAKEN TRADING all together,
    to not only work on a fix but to re-code the malicious parts of the trading engine from the scratch.

I am hearing Kraken coded it's own in-house solution once they started out back in Oct 2013.
(Here we can learn that a custom-coded solution may sure have it's advantages, but may get you in deep trouble once that coder stops working for you.
If he once re-invented the wheal (code) it's hard to fix something so complex by any new coder.

So it looks to me like a dead-end street for Kraken:
(a) do nothing an loose clients and die slowly
(b) rewrite the code, test it, bring it live - ... if that takes too long, the result equals (a)

Good luck!