Quote from: Blackblanco on March 04, 2014, 04:23:31 AM

Quote from: cacahouette on March 04, 2014, 03:37:26 AM

Quote from: Nxtblg on March 04, 2014, 03:15:13 AM

Well...it was live for long enough for my 0.01 BTC test withdrawal to go through. To their credit, the BTC withdrawal really did go through once confirmed. Already recognized by my Multibit wallet and confirmed at Blockchain.info. I have to say, coinmarket.io got that one right...at least for me.

But sure enuff...back to Club 521 a minute after. Thankfully, I can report that a BTC withdrawal went through without any issues...as long as you can get to the Site...

i was able to initiate 2 BTC withdrawals for a total of 0.7 BTC but after 2 confirmations I can no longer get any further confirmation and it's been like that for 30mins. Is it possible that confirmations take a lot of time to add up ?

[EDIT] ok coins landed safely in my wallet!

Well that's good news. Unfortunately, I can't get in to the site but I guess I should keep trying. Strange what's going on... I hope it all works out as I do like this exchange.

i guess this is the problem, they posted days ago

Quote from: coinmarket.io on February 25, 2014, 05:15:09 PM

Why is the site going down so often today?
After moving large amounts of altcoins to cold (secure) storage, our wallets were left with a large amount of small unspent inputs.
These inputs are generated by people who mine directly to our deposit addresses, using small automatic payments from pools.
When a withdrawal fails because too many unspent inputs must be combined, the coindaemon throws an error: transaction too large.
What are we doing to prevent this? We will manually consolidate the inputs by sending coins to ourselves.
This can take some hours, but its not a major issue. After this, the coindaemon will be able to choose less inputs for withdrawals.

Our system is configured to stop on any unexpected condition, at all times.
This is why the server is going down - we have to manually restart it after a coindaemon error.
This is the same protection that has prevented people from exploiting bugs - its important to "crash" on any unexpected condition.
We carefully inspect all error messages before restarting the Node.js process. Having this protection will make us alot better in the long run.

Also, because of the Mt.Gox situation, withdraw volumes have increased on all exchanges.
Because of this, we have to re-fill our hot wallets, multiple times per day. Usually its the other way around.
Another effect of increasing withdrawal volumes is that the coindaemons run out of "large" unspent inputs and start combining the dust from mining deposits.