Re: [ANN] KRAKEN.COM - Exchange with USD EUR GBP JPY CAD BTC LTC XRP NMC XDG STR ETH

The Price at Kraken DID NEVER reach 2000/BTC or higher yet.

These are bugs in trade engine or anything like that. That happens usually ~once a month, but in times like this it happens more often...

Nearly every exchange is unreliable at the moment.. also bitstamp has stuck orderbook quite often these days...

If it didn't reach that price why would Kraken site itself list it as the high price today? Were is it getting the data if not from its own trading engine?

Are you really sure no trades were executed at that high price after bypassing the entire order book?

Is there any place I can access a log of all trades executed?

Cause it is a bug in trade engine from kraken, not from the chart sites.
Only one single order is matched at this high price, skipping all the other orders.
(so yes one trade was executed at this high price, but I wanted to say, that it is correct that your sell order was not matched. The bug was that single high trade. And the bug happend several times withing the past 12 hours)

Dargo will explain shortly how the bug can happen.

But the explanation does not help much, since it is still a bug, that exists several years now and still not fixed...
Kraken is working on new trade engine... (slowly)

So the conclusion is that it did in fact bypass the entire order book and do a trade at an extremely high price. So, what happens with the poor guy that was liquidated or bought at that price?

Let's see if when Dargo comes back he can do a technical explanation of how the logic of the code can just ignore the next following price/order in the order book and go on higher before executing the trade.

Maybe if he shares the source code we could not only understand how and in what "exceptional" (?) circumstances it can happen but also contribute and fix it for once.

Yes, the spikes we are seeing right now are due to an issue with the trade engine. The spikes are low volume and due to small orders (or small parts of larger orders). It's not due to the logic of the code ignoring or skipping orders that it can see. It's rather due to the trade engine very briefly only seeing a few orders and as a result matching them out of context of the other orders. It's the first time I've heard of this particular issue, so I'm not sure how long it's been an issue, but the frequency of it right now is probably related to the current very high volume. We are working to mitigate the issue, but the permanent fix will probably come as @Serpens66 says with the new trade engine. The new trade engine is hopefully coming in a matter of weeks, but we don't have a specific ETA at this time.