Quote from: CryptoTeng on February 02, 2018, 07:20:34 PM

Quote from: Kraken-Septimus on February 02, 2018, 07:14:25 PM

Quote from: CryptoTeng on February 02, 2018, 07:11:26 PM

@Kraken-Septimus

Since you answered other request here, a little reminder. Dont forget about this little problem, please.

Quote from: CryptoTeng on February 02, 2018, 09:25:32 AM

@Kraken-Septimus

This is the reply our friend is getting from you frauds.

"Feb 1, 13:39 PST
Hello,
They are all showing the same spikes because they all get the data from us. The data is erroneous and trades did not take place. Also we are not affiliated with Tradingview, they display they data that they are given.
Regards,
Gil
Kraken Client Engagement"

Which leads for us to the point to repeat the warning to customers:

KRAKEN ADMITS MARKET MANIPULATION

Again, please contact the relevant authorities if you encounter damages by Kraken. We advised our friend to contact the SEC in the USA to report this extreme case of market manipulation and/or criminal negligence. (it is lucky for our friend that he can prove that trades DID take place and will be able to provide screenshots to the authorities. In contrast to Gil's lie stated above.)

Hi CryptoTeng. We can't discuss another client's account on social media for privacy reasons. If your friend is unhappy with the answer they received, please have them reply to the ticket again.

Thanks for reaching out. I hope this is resolved soon.

Maybe you can clarify how this criminal behavior is acceptable for any client. This does not need to involve any discussion of any specific customer privacy details.

And how about explaining that you do not keep to your own ToS when it comes to justified refunds.

Both points could be very much interesting to other users of this forum.

Quote from: Kraken-Septimus on February 03, 2018, 09:11:50 PM

Hi CryptoTeng. I've reached out to some colleagues and we're also looking into your friends particular issue. I don't have a different answer than in the ticket at this point, but we'll let you know once we've done a full investigation. We're not ignoring this issue, we're just trying to find the proper answer for you. Thank you for reaching out.

If you refer to the quoted email from Gil then this is a quite poor answer, and as said above, Gil's answer is an admission to market manipulation. Otherwise you might want to state the content of the answer to the ticket you refer to in general terms. We do not have insight in the dudes tickets. He promised to update us as soon as an useful answer from Kraken was received by him.

About your answer of having a look at the problem. Having a laugh right now. As this is the type of answer one usually gets from you, in our case since spring last year (2017). And since you haven't done anything about it since then, it is criminal negligence of the problem.

None the less. Next question, apart from trying to solve this issue. How are you going to compensate your users for this serious error? Again, to answer this question, you do not need to involve any user specific details.

Furthermore, the 2 questions from the previous post are in no way limited to the dudes ticket. These are very general questions on how you treat your own ToS, and how you can justify this type of market manipulation. So, we ca actually step away from the dudes ticket, and keep to the discussion of these general points, which might be interessting to every Kraken user.