Quote from: yuchuanzhen on September 13, 2013, 07:00:27 AM

Quote from: JaredR26 on September 13, 2013, 06:53:56 AM

Quote from: yuchuanzhen on September 13, 2013, 06:41:50 AM

What about the solo plan?

Quote from: buzzdave on September 09, 2013, 10:44:27 AM

We'll go solo this week - the pool mining is just a temporary measure while the mine is too small to deliver reliable dividends to the shareholders.

See this post:

https://bitcointalk.org/index.php?topic=140366.msg3131545#msg3131545

The solo plan is a very high priority still, but it is hard for me to justify the time and cost to go solo for a 2-3% gain rather than optimizing rigs for a +45% gain or more.

What about this ?

Quote from: SebastianJu on September 11, 2013, 08:12:40 PM

They should set up a p2pool server. Then they would get the same they would get with solomining, with less variance and with faster blocks so they can see errors occuring fast.

I'm not opposed to it, but I don't have experience setting it up. I do know that other Asics like Asicminer blades originally had trouble working with P2Pool, and I haven't read of people who have made it work for Bitfury's software base(has anyone done so??). Especially at our scale- We have hundreds of devices online now and multiple stratum proxies to manage the distribution and connection flow. I worry about the stale rates- Our connection is good but with that volume of devices and extra stratum layer(s), would that cause a stale rate worse than the BTCGuild?

Moreover, it would still be a temporary stopgap- we'd still want to solo mine very soon, so all the changes would have to be redone for solo.

If someone can convince me that the stale rate fear is overblown and the switch process is seamless enough, I might be able to get to it sometime Sunday->Tuesday, but it won't change the prioritization of solo mining(which would eliminate any stale rates and return to the raw statistics/luck we should be running with).