Case remains unsolved. no email communication to our informant about his case, and also no answers to the questions in the previous post.
Yep, it is always the same with these Kraken frauds. Since, no communication has happened, it must be assumed that no one from Kraken is actually doing something about this issue. In other words, it is a lie that a specialized team is taking care of this case. Unless it is the special "lets-ignore-unfavorable-customers-requests" team. Then they are doing an excellent job. ROFL.
CryptoTeng,
Once there are any updates regarding your informant's support request, they will be contacted. As my colleague, Septimus, has already mentioned, we take legal threats and market manipulation accusations very seriously so please understand that any further discussion will be communicated via the original support request. In regards to any other questions you might have, we would encourage you to open a support request, as well, so our trading team can directly look into and answer any questions or concerns that you may have.
ROFL.
Nope, these questions can and should be discussed here. In particular as they concern an earlier statement of Septimus on recognition of false and real peaks. An open discussion might be of interest to every customer, especially as they are about market manipulation.
And from own experience, opening a ticket does not lead anywhere, as you simply ignore them. Been there before.
About the informants ticket. How many times do you want to repeat this lie? The last email communication from your side to our informant about this case is roughly 1 month ago. And let's not start on earlier cases, then Kraken's denial to solve this problem is going on for much longer. And your answer here is particularly questionable, because Kraken claims to know what the cause of the problem is. You simply just try to solve the case by doing nothing. Yeah. Kraken is taking this issue VERY serious. LOL (Just look back for how long this type of issue is being discussed here in this forum. Same problem reoccurring again and again, and always the same type of answer and no improvement by Kraken.)