Thanks very much and good luck.

Slush is providing miners with a choice of what to vote for and not taking a stance himself unfortunately. I have mixed opinions about this since it means the individual miners are actually making the decision but I feel pool operators have a responsibility to help display unity and effect coordinated change.

Yep that's the one. I'll be putting up a separate thread and proper announce with all the details of its running when I get time but it is operating with full functionality already, it's just that it's considered in beta and may be unstable so no guarantees exist for its operation just yet.

Wow I wake up and find over 200TH on the pool already and it's still running fine. Thanks everyone who helps at this testing stage and good luck! Remember the other pool is NOT a solo pool but shares rewards. Additionally if the pool is lucky early on while the last N share window is developing, remember that the early miners could be in for a big windfall.

Boom indeed. Fortunately I'm still awake and have fixed the problem and restarted it. "No shares have been lost" (heh), though this is why I need lots of testing thanks. If it's still running by my morning it'll be a minor miracle.

I lied, I've restarted the new pool and brought stats online much sooner because I couldn't wait.
http://ckpool.org

On the other hand full details and explanation and announce will be a little while later.
You will have to postulate on what the new fields mean  

Just remember, the shared pool is in BETA/testing so there are no guarantees at this stage.

Yes workers are the same, and stats will be json but with extra fields. It's not strictly PPLNS; that explanation will come with the announcement, but N is 5 x diff; however it ramps up faster than PPLNS.

For those curious to try the new pool, the beta pool code is up and running. I have yet to set up the website stats etc. the way the solo pool does so for now if you wish to start mining there you will do so blind without any stats. I will endeavour to get stats up and running in the next couple of days and then will work on an announce in a separate thread. Being beta the pool may be unstable but so far it has proved working nicely, solving quite a few blocks on testnet with a host of different miners.

If you wish to try it, point your miners to:
pool.ckpool.org:3333

As per the solo pool, you MUST use a valid bitcoin address as your username. The pool is ostensibly being called ckpool.org and for all intents and purposes, mining there will work identically as per the solo pool (apart from PPLNS type shared payouts).

This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1875058.0
Asked same question in 3 threads

You already asked in another thread and I answered.

Offtopic for this thread, but basically they're using it to attempt to fund a Bitcoin Unlimited takeover of the network by making people mine on a BU pool at the pool's loss; it's Roger Ver's owned pool and he's going to great lengths to garner support for BU.

I'm back from vacation and will be starting work on the shared pool shortly as enough people have expressed interest in the idea. Being away allowed me to think a lot on how to best implement it to fill a niche that no other pool currently does - listening to what people have been saying in all the pool threads. It will be slightly different to every other pool out there and very low fee (0.5%) so hopefully that will be incentive for people to join, but it will be very no-frills just as this solo pool and aimed at miners of any size. The announcement thread will have a lot more details about how it differs from other pools. I need to spend some time coding up the new pool and will probably start a new thread some time in the next week or two advertising the pool when it is in testing/beta.

This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1871444.0
Dupe

Weird, the screenshot shows something from the Burj Khalifa (the largest building in the world, in Dubai) - perhaps 'they' (whoever they are) met there, and some kind of UDP (graph?) Perhaps that's the DDoS since most DDoSes are UDP...

Hard to know where in the chain exactly but with 2 separate drives then yes it's extremely unlikely to be the drive itself. Sata controller/motherboard are more likely contenders in that case. I can't say for certain; I'm purely speculating based on the type of failure you're getting. I had similar failures to yours with a dodgy HD. It was also very intermittent, depending entirely on where on the platter it was trying to write.

Colour me unimpressed. I take it back. Luckily f2pool is much bigger than bitclubnetwork. After chatting with him, there are other forces at work here beyond the admin's control but indeed they're not signalling it now, even if they're running segwit compatible pool and bitcoin nodes.

Not at all (about bitclubnetwork). I know the admin of the pool and they are most definitely still signalling segwit; they've just had a run of bad luck and no blocks at all show up. I am also signalling segwit with solo.ckpool.org but since I find a block every 3 weeks on average, my pool doesn't show up either.

Either way, f2pool signalling segwit is sensational news... provided they're not just trolling and pull the pin on it again in the future. He certainly does like to keep us guessing but that last post seems conclusively in favour of segwit (by poll). Now let's see how the markets react since the value seems to parallel segwit support levels

Great, enjoy! That size mining is purely for fun and luck. At ~600GH total as you have described you will find a block on average every 44000 days at current diff... and diff keeps rising so realistically never; only if you're extremely lucky.

On the other hand if you really want to earn some intermittent dust sized payments instead at that hashrate you will be able to put it on my new pool which will support very small miners when I start working on it in the near future, knowing that dust is basically unspendable at the moment but may be worth more and spendable in the future.

Coming at about the rate you'd expect for only 1.11PH... that hashrate will only find a block every ~24 days on average. Want to see blocks fall faster? Find a couple of hundred PH and mine here.

Which makes their violent reaction to a BIP proposal that makes asicboost not work somewhat baffling. I guess they were more objecting to the intent in the move's aggression rather than the actual BIP, but it made most of the community convinced they were using it covertly.