Again, a so-called misprint, ROFL. Honestly, this might be possible. However, seeing your history about this topic, we dont think that your statement can be trusted that it was a misprint, and neither do we expect the dev team to do anything about the issue. It has been almost a year now since the topic was first brought to your attention, and nothing has changed so far.
As this is clearly a fault by Kraken, and you also admit to it, which has a dramatic impact on the OHCL charts and nothing is by Kraken to warn clients and to present the correct charts (at least until now) we have again the following questions:
1) Are you going to compensate people which are affected by your fault? And if yes, how are you going to compensate them? (This type of error clearly does not fall under the clients risk of online trading)
2) How can you justify to keep Kraken running when this type of error occurs and you do nothing to present the correct data after you have acknowledged the situation, not even in your own trading tools? Trading should be suspended until you found the exact reason and the solution to the problem (including to present the correct data).
3) Why are clients not informed about this problem as this can have serious impact on trading?
Please let us know how much you have lost due to this issue by opening a ticket and we'll look into this for you. Thanks for your patience and have a great day.
This does not answer all questions above though nor the ones posted with the previous occurrence, but maybe this is the first step of Kraken to take responsibility in this matter. Interesting. We will inform our buddy who is having this issue with you/Kraken about your statement. Let's see where this leads.
hey septimus,
do you remember this issue (actually the same as the current one). According to our info Kraken still denies to pay refunds/compensation for the case on April 3rd, or better let's put it this way, Kraken just does not reply to email communication about this issue, not even the legal department. Additionally, according to you the issue on 3rd April was a misprint, but the OHLC data of that day still shows the false peak. Are you going to take as much care of the current case as you did for the one on 3rd of April?
Maybe you really could finally clarify how a customer can distinguish between false and real peaks. For the problem on 3rd April you claimed it to be false peak, for the similar issues on May 24th and June 19th you call the peaks real (whereby the Kraken support claims they are false).
Furthermore, you never answered the questions posted about the issue on 3rd of April.
So, actually everything give the impression that Kraken does not care to solve this problem.