For one, I don’t think that we are talking about hiccups. Not by a long shot.
For two, if you can tell me with a straight face that Toomim didn’t factor in the fact that he was implicitly selling a piece of crypto history…a month ago…than I am not sure we are on the same page.
I won’t buy for a second that he was ignorant to hype and what it can do…after BTC…after LTC…after Dark…after a flunk ton of examples in the crypto world that have proven that ‘timing is everything’.
If this was a long haul argument, then he would be starting the auctions now, right? But he had to have known that there was going to be spikes. Otherwise, he wouldn’t have cared a month ago.
Let’s add in the fact that nothing worked as promised for the entirety of Day 1. He specifically stated that mining would start on the 28th and it never did. And conveniently, things are starting to ramp up, mining wise, when hype is pretty much over. There is so much BS associated with that scenario…
After almost 2 days I have ZERO solution from you either from supranova or flypool!! ZERO!
In this situation its so much more than long hauls vs short term mining profit (even though this is gone and “oh well some “hickups” happened.”
Its that you said one thing and do not and STILL have not done what you said you would do with all of your promises. You misrepresented your name and for me me it’s a matter of not wanting to be associated with YOU or your company at all. I dont like you and I no longer want to be a part of your business. I do not want more hash I do not want to visit your website for another 3 months and deal with you. I want a BTC refund and I would hope you will announce this sooner rather than later.
EDIT: It would be in your best interest to provide BTC refunds to those who want it sooner rather than later and when you stabilize your network, enough noobs who are not associated with this epic fail may even will buy into your company. With a bit of luck, you might even survive after this debacle but I hope you are a smart enough of a business man to know when your customers come before you, such as now.
Starting today after 8 PM I have received the first hashes. It is still way below what I have purchased.
I have just invested for the chance in participating in the first mined coins. This did not happen.
I am happy to send you all ZCASH that I have mined with the supplied hashes and receive my refund.
Because Toomim Bros cannot fulfill The hashrate Since Launch，And now i’m only getting 3h/s at flypoll.
I have made my mind for refund. Hope I can get my refund as fast as possible.
From my perspective: I have ordered the shortest available hashrate contract so I can profit from mining the first minute the network goes online. I speculated that with such hype and initial scarcity of coins, the first hours would make a huge difference and paying a premium for buying a contract should insulate me from the risk of missing out. I also missed out because of a false sense of security, I could have mined with AWS knowing it is my only chance on early coins and could have fared much better.
I finally figured out the NFS bandwidth saturation issue. We’ve been having our NFS server use around 950 Mbit/s of bandwidth on our LAN for hours straight, and it’s been rather problematic for us. At first, I thought it was due to a memory leak (which we do have) causing swapping (which we didn’t have). However, it turns out that the actual problem is the fglrx driver trying to read and write from /var/log/syslog and/or /var/log/kern.log. Those files were growing to around 30-100 MB in size, and apparently NFS was being dumb and reading the whole file each time a process wanted to append to the file. With over 40 rigs and 6 GPUs per rig, that ended up being a lot of 50 MB reads. I deleted those log files and the problem disappeared. I changed /var/log into a tmpfs just to make sure it won’t come back. Fixing this problem is a big deal, and should make everything work much better.
While debugging the NFS issue, I let more rigs fall offline than I should have. Sorry. We’re getting them back on now, so hashrate should be climbing again.
We were getting a lot of errors from us1-zcash.flypool.org and suprnova for a few hours. They were mostly connection reset errors (ECONNRESET), but with at least a few ETIMEDOUT errors too. They seem to come and go. I don’t think they’re a problem on our end, but I can’t be sure. They usually happen when we try to initiate a stratum connection, but they sometimes happen on stratum connections that have been open for a minute or so as well.
We’ve also made a few other improvements to our system that are smaller and not worth mentioning. Once we finish rebooting to roll out the changes, I expect we will be able to come very close to meeting all of our hashrate requirements, and may even exceed them (barring pool-side issues).
We are currently getting over 5000 Sol/s in accepted shares. That is more than the hashrate we sold to customers. As long as this holds, we should be able to start catching up on the backlog of hashes.
I’m not here to know the technical capabilities of your system and personally I don’t care about the details. That’s why I decided to cloud mine…pay you for the headache of getting online at launch. We all paid you (albeit overpriced) for a service…sol/s which many have seen none. You did not deliver.
Please spare me your technical problems, and please refund those who are asking for such so we can channel funds to more useful vendors.
Edit: Oh and yea I just checked of those 5000 s/s, ZERO are being mined on my selected pools. Further evidence of your hype.
It looks like there may have been some problems with a few of the orders that we added manually to the database, including yours, breasal. In your case, there was a problem with case. You gave us your account information with the username breasal, but when you signed up on the web order form, you used the username Breasal. We added an order for breasal, not Breasal. Mike is fixing it now.
Edit: Fixed. Let me know if your hashrate climbs above zero.