Just checked with the informant. He hasn't been contacted by you, Kieren, or any other Kraken representative yet. Any news from your side Septimus?
Hi CryptoTeng. After speaking at length with the trading team we've come to some conclusions that I'd like you share. First off, I had made an error in stating that trades had gone through in those instances. Based on the information that we have now, that was an error on my part. I'm sorry about that.
A misprint looks a lot like any other candle with excessive real volume, which is why they are so hard to narrow down. In the ETH/EUR case of June 19, there was a misprint for a few minutes. A moment's pause in our internal system caused this. Normally, the system is cleared out and the visual interface should reflect this but rarely, a misprint can happen.
When the system pause happens, there is no actual volume traded. At the end of this pause, however, the cancelled volume falsely appears within the minute of system restart. This means that a 1 minute candle collects the data for more than a minute. As a result, a few minutes volume becomes falsely visible within a 1 minute candle.
Our site went down for roughly 2 minutes and when it came back online there was still old data that should have been cleared out that caused a misprint in the chart. Sell orders were not executed because no clients were actually buying at that price range.
As for the DASH/BTC issue in May, there was downtime with our API. The 15 minute candle starting from May 23 UTC 22:00 is where there is an unnatural spike. When disconnection occurred the data should have been wiped, but there was an error and the data falsely appears (like the previous case) within the 15 minute candle. In this case, the exaggerated candle would not reflect actual trades that went through, but instead reflects stale data clumped into a small frame of time.
As for the ticket and whether it is solved or not at this time, that would need to be addressed in the ticket. It's at a specialized team at the moment because we take legal threats and market manipulation accusations very seriously. Any further communication from us will be through that ticket. Thanks for understanding.
Interesting, so it is a "misprint" again. At least you are now in line with the Kraken support. If your statement can be trusted is another issue. You have lied before, so why shouldn't you do so again? A bit suspicious, because Kraken seems not to be able to check their data for consistency after server restarts. A year should have been enough to build some kind of automated check whether the data is correct or not. And this is issue is going on for more than a year.
Then regardless of what is happening to the ticket, I still have the question why you (Kraken) are not correcting the OHLC data? As long as you knowingly present false/faulty OHLC data you are conducting market manipulation, at the very least by neglecting to correct. Those peaks create a very deceptive picture for traders. And since countless occurrences have been reported to you since the very least May 2017, you are knowingly (maybe even intentionally) presenting false data.
(Note: This is a general question, and not about the ticket itself, so it should be no problem to answer it.)
Just for your info: "Manipulation according to SEC
https://www.sec.gov/fast-answers/answerstmanipulhtm.htmlManipulation is intentional conduct designed to deceive investors by controlling or artificially affecting the market for a security. Manipulation can involve a number of techniques to affect the supply of, or demand for, a stock. They include: spreading false or misleading information about a company; improperly limiting the number of publicly-available shares; or rigging quotes, prices or trades to create a false or deceptive picture of the demand for a security. Those who engage in manipulation are subject to various civil and criminal sanctions."
About the ticket. Then let's hope you (or someone else from the Kraken support) will reply there. To my knowledge our informant is still waiting for a reply to his last email about this case.