Topic: [ANN] KRAKEN.COM - Exchange with USD EUR GBP JPY CAD BTC LTC XRP NMC XDG STR ETH - page 168. (Read 629033 times)

Sent you a PM, thanks!

I can help you better if you DM me your support ticket number, but I think I found it and I asked the support team to look into it.

I've found it in their support FAQ:
(OK, now I'm answering my own questions! )

As my deposit was one hour ago, I've filed a support request... again. 
I guess kraken doesn't like me... 

How long does a deposit of XLM usually take on kraken?

BTW deposits lack some transparency, show at least incoming txs and required confs (x of y)!

I opened a ticket.
The guy said " I will look into the possibility to activate EUR withdrawals for you and get back to you."

Yes, we fixed an issue with one of our nodes that was throwing an unusually high number of errors and also added another node. The improvement was pretty dramatic as you can see from this screenshot from https://status.kraken.com/ on July 14th.

http://imgur.com/a/dpex4

Also glad you liked the communication on the hard fork yesterday and even more glad it went smoothly!

Hi - sorry it took me a while to respond. Please create a support request about this if you haven't done so already and PM me the ticket number so we can help you.

Yes and I liked the way how they they've kept me informed about the ethereum fork yesterday!

Kraken has definitely improved lately, love it.

I'm a U.S. citizen with a Kraken account.  Kraken doesn't let me do anything involving Euros.  I have an account with a bank in Europe.  I want to make SEPA transfers with my Polish bank account.  Help!

The issue is not how much collateral to allow clients. The issue is that in the case of losses we would have to take these currencies from your balance and now we have the problem of converting these amounts into other currencies. There are some fiat <> fiat conversions that we either cannot do or cannot do easily at the present time.   

You could simply use a fix conversion rate with a huge safety buffer. For example,  assign 1 GBP the same collateral power as 1 USD. Should 1 GBP approach the value of 1 USD in the future you may manually further decrease the collateral power.
Right now, it is pretty dangerous to sell BTC for, e.g., GBP when there are open positions because such a trade may result in an immediate margin call (since the decrease in BTC decreases the collateral and the increase in GBP doesn't compensate that).

Offering these as collateral creates conversion issues into other currencies that we cannot accommodate at the present time.

Sorry I didn't reply earlier, but I did see your request and got a reply from support to you.

If you PM me the ticket number I can help.

We may offer this at some point, but not anytime soon. Mathematically the order you close in doesn't really matter, but we understand that psychologically it can make a difference and that shouldn't be discounted.

There seems to be a misunderstanding about what happened on June 17th (incident report here: https://status.kraken.com/incidents/t4gc3kfd100m) that I want to clear up. It's not true that all API users had reliable access while all website UI users were universally locked out. It may be true that API users on average had more reliable access, but many API users had trouble accessing the site during this time and many website users were able to access.

The incident was also different from what happened to BitFinex (reported here https://bitfinex.statuspage.io/incidents/k4mq3gsn5c3v and here https://bitfinex.statuspage.io/incidents/hy64vfbk9r18). Bitfinex had some kind of internal network instability that was affecting the trade engine. If the trade engine was affected then presumably everyone may have been at risk of having their orders not execute correctly. In that case pausing trading seems like the right thing to do and Bitfinex handled it very well.

For the Kraken incident on the 17th, there were of course a significant number of clients who had trouble accessing the site, but we have no way of knowing exactly how many, and many clients were able to access and use the site OK. It's not clear to me that halting trading is the right thing to do every time a significant but unknown number of clients cannot access the site. I understand that it seems unfair whenever some cannot access the site while others can, but that doesn't mean that blocking access for everyone is the solution. Since Kraken isn't the only exchange, the markets will move without us and from that standpoint blocking access for everyone only creates a problem for a greater number.   

What is the reason for fiat currencies, such as CAD or GBP, not being eligible as collateral?

Kraken, the community of Nexus would greatly appreciate your add of Nexus to your Markets.  Nexus is growing organically and the community continues to expand and draw in real talent. Colin has made an excellent coin, has an excellent plan, and is going to grow Nexus into a top contender cryptocurrency. Outside investors are already entering into the crypto market through Nexus. Please take careful consideration and add Nexus to your exchange. Thank you!

https://bitcointalksearch.org/topic/nexus-pure-sha3-cpugpu-npos-15-active-innovations-more-to-come-657601 Nexus Thread


SHA3
571 bit keys
Decentral Checkpoints
New difficulty adjustments
CPU + GPU fair mining
Distribution Reward System
Reward Curve
Time Clocks
10x faster then bitcoin
Variable Proof of Stake(Interest) based on Trust, time and weight
Trust Keys
Lower Level Protocol
Lower Level Databases
Merkle Chains, Reversible Transactions and Cube Satellites broadcasting the blockchain to earth from space.

Nexus Earth - Crypto = Bitcoin Cube Satellites

https://www.youtube.com/watch?v=S-aRpb735rI

 Thank you for your kind words. I've only asked for a fair consideration by their part.

 Once again, I assume full responsibility from wrong choices, like not setting stops and then complaining after the fact. This was not the case. I was logged on to the website trying desperately to close my positions but the website was completely unresponsive.

 I wish to profit nothing from this of course. At the time if I closed all my position I would still be at loss. Such is the risk/reward game. You win some, you lose some.

 But to trust your funds to a service that at any given time can just crap out and allege there is nothing that can be done, and the userbase sustain losses in detriment to their gains, is not entirely transparent.

 If it had happened while I was asleep... sure, it would be my fault. Absolutely not case there.

 I was logged on before the major dump. Kept trying to close repeatedly during the whole episode, for more than an hour. I was logged on to Kraken, but the service was unresponsive. And during all this time, the books were rolling. -> This is the major issue here, and what made things really wrong.

Are API traders first class citizens, other than a technical millisecond-range advantage? Do Dark Pool traders have special bandwidth benefits?

 BitFinex went through a similar episode, and they responsibly halted the trading engine. They gave the chance to their customer base to act accordingly. They gave a specific time and warning to re-engage the engine. They acknowledged their service problem and provided a window of opportunity for their customers to protect themselves.

 I am completely confident we will find a friendly resolve. I wish not to gain from this of course, just not sustain this massive loss.

 Kraken is historically an example of a good practices company. Shit happens, I am completely sympathetic about it. I am confident good resolve will come out of this, for both parties.