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?