We’ve made some major changes to how we allocate hashrate. Previously, we were trying to allocate one full rig to one customer for one share, and doing some crazy behind-the-scenes with firebase to try to allow persistent stratum+tcp connections in order to avoid having the difficulty reset. It sounded like a cool idea, but … it didn’t really work out that well.
We’ve switched over to having a single rig mine for a single customer for about 5 minutes before switching. You should see your pool be idle most of the time, and then get around 100-300 H/s hit it all at once for 5 minutes, then move on. This approach seems to be more efficient and a little less buggy.
We’re still seeing a lot of user accounts simply fail to work, though. Many of these are the “unauthorized worker” error that’s common with suprnova, but not all. We’re investigating and trying to fix.
seems like we are having difficulty delivering the hash power promised… what a shame
clear grounds for a refund according to your own terms and conditions.
I have now confiugred Supra and Nicehash both for several hours.
I did receive nothing! I am sure my worker config is correct, because I have tested it with my laptop.
Can you please post the workers that are failing. How long does it take until your confi kicks in?
We had a lot of crashing and restarting of our GPU. This crashing corrupted the netboot disk image that we were using to run all of our GPU rigs. We’re now recovering the image from a backup.
@jtoomim understandable, hopefully it gets resolved soon, I’m not that upset as i’ve already made my investment into your service back with the crazy action on Poloniex. I do hope that we can get some extra hash for our troubles.
