Having downtime is expected from time to time while we are in beta.If you see a cloudflare error page, you dont have to post to this thread.Asking others if the site down when you know that it is (you can read, dont you?) - is just silly.

Those people are worried about their account, that is why they have right to ask even if they can read!And in the mean time, you can give a solid explanation why it is closed down now.Everybody knows it is in Beta. We can read since we are already writing, but you must know that already.

Having downtime is expected from time to time while we are in beta.If you see a cloudflare error page, you dont have to post to this thread.Asking others if the site down when you know that it is (you can read, dont you?) - is just silly.

I'm not asking other users, I am posting here to get a developper response as to why the site is down without a notice up front. Don't forget that it is other people's money you are working with, usually people like to know what happens to that. If you are having timed downtime because of a website update put up a notice, if it is unwanted downtime post a reply here that you are aware and working on it. That's all we need to ease our minds.

We are just concerned and the website could be down for a certain set of geographical people not everyone.

I understand its in Beta and the painful process of ironing out all the kinks.

If you are aware of the downtime should you not post a quick twitter message, but if you are unaware why your sites gone down even more post a quick message alerting your growing user database. Everyone understands downtime

Sorry for the downtime. We have resumed normal operation.The bitcoin daemon started throwing us errors about double spends.We executed the bitcoind -resync command and everything is OK now.We guess this happens from time to time, because our wallet.dat is very big (over 100MB).

Some deposits may got stuck during the downtime, we will process them shortly.

Sorry for the downtime. We have resumed normal operation.The bitcoin daemon started throwing us errors about double spends.We executed the bitcoind -resync command and everything is OK now.We guess this happens from time to time, because our wallet.dat is very big (over 100MB).

Some deposits may got stuck during the downtime, we will process them shortly.

The transactions are queued in the memory pool for some reason and will be re-broadcasted soon.There is nothing we can do at this point, its just how bitcoin works.Because we send a lot of transactions, some of them dont always instantly appear on the blockchain (delays of 1 hour are possible).

We will be switching to the sendmany method to prevent this in the future.After the update, our system will send outgoing transactions every minute,making a smaller number of transactions with more "outputs" to different people who recieve them.Those should be considered higher priority by the nodes and would be relayed to other peers more reliably.

The transactions are queued in the memory pool for some reason and will be re-broadcasted soon.There is nothing we can do at this point, its just how bitcoin works.Because we send a lot of transactions, some of them dont always instantly appear on the blockchain (delays of 1 hour are possible).

We will be switching to the sendmany method to prevent this in the future.After the update, our system will send outgoing transactions every minute, using multiple outputs.Those should be considered higher priority by the nodes and would be relayed to other peers more reliably.

So my transaction is not completely lost i hope? because im sending 2 transactions at the time, and the one who didnt get through has 1 btc on it

The transactions are queued in the memory pool for some reason and will be re-broadcasted soon.There is nothing we can do at this point, its just how bitcoin works.Because we send a lot of transactions, some of them dont always instantly appear on the blockchain (delays of 1 hour are possible).

We will be switching to the sendmany method to prevent this in the future.After the update, our system will send outgoing transactions every minute, using multiple outputs.Those should be considered higher priority by the nodes and would be relayed to other peers more reliably.

So my transaction is not completely lost i hope? because im sending 2 transactions at the time, and the one who didnt get through has 1 btc on it

There is no permanent problem, it will arrive without any magic from our end.

Other exchanges have the same problem (it affects less than 1% of withdrawals), but they dont show you a TXID as soon as you make the withdrawal.So, in effect, you dont realize this on the other exchanges and just assume they are slow The problem will go away, we guess in less than 1 hour.

Edit: confirmed all stuck LEAF, KARM and SMC deposits.

Edit: will be switching to the sendmany method later today.A script will run every minute to combine all confirmed withdraw requests into a single transaction.This way it will be much more efficent and should always instantly appear on the blockchain.

This transaction: 17999f5d3db03170e9330f1f8dfb2c5aef600a148cc6ab10a1bd116ade69e7fc to this Wallet: 1DnLR9KGmRCMtzLV7g1DFa7o7pvGeoKCUB Never credited, though the funds appear to have been transferred out of the wallet address. I sent a PM prior to funds being transferred out, but didn't receive a response. Please advise. What's going on? It's been days now.