Cleveland Cavaliers 113 @ 102 Utah Jazz

Memphis Grizzlies 92 @ 105 Golden State Warriors

Charlotte Hornets 103 @ 99 Boston Celtics

Dear god I hope kokjo isn't given any actual responsibility in real life.

How does one enter the payout information in this new index.html?

New prop pool UnitedMiners.com

Here is the config for the pool

api_strip:','
role:mine

Bithopper looks at the total number of shares submitted for a round for any pool, not just yours. Deleting your stats won't change that, your number of submitted shares isn't relevant. If the number of total shares for a round exceeds a certain number then it hops to another pool below this threshold. If there are none then it drops down to the backup pool until one of the pool rounds end.

c00w: Why did you disable nofeemining in your recent commit? I'm confused because I don't see any recent mention of them in the thread. Adding a reason in the commits would be helpful I think.

Not sure how multiclone hops btcguld and slush since they have anti-hopping measures? Anyway Bithopper is a superior option as multiclone is essentially the same as someone running a copy of Bithopper on their server which everyone connects to. You can add more pools to the rotation in Bithopper if you want, it's quite straightforward.

Ah gotcha. Thanks very much.

Can someone explain the behaviour of this proxy please. Why is mine currently mining on my backup pool when there are no errors on any of the 4 pools that are configured? Is it because they have passed a certain number of total shares?

This was a few days before we got the third block. It went up to ~40GH/s at one point. It was quite late in the round so it probably isn't pool hoppers, so not sure what happened there.

How do we view the number of stales without using your mining client?

Should be fixed now...mostly. The issue is out of my hands really though. The url used to fetch the current worker speed (http://www.continuumpool.com/hashrate.php?worker=) seems to time out most of the time. This is also the case with the RPC, which was taking a huge amount of time to return the current round time for some reason. So I've decided to cache the pool stats (round start time and total hashrate) and run a cron job to fetch them every 5 minutes. This should make the page load noticeably faster now. There will still be errors if the continuumpool site times out but there isn't anything I can do about that, but it should work more often than before now.

And why would you do that? If you don't donate to the server the least you can do is allow a small ad on the page to help with server costs. There are times to use adblock but this isn't one of those times.

OP sounds like a real idiot. Can only assume he got himself hacked or something.

0.7 I think is the min I'll go

L4D2 is still available

Sure. Add me on Steam

http://steamcommunity.com/id/moussekateer

Variance old bean. The time taken to solve each share everyone is sent is random, but has an average related to the difficulty. On smaller pools the variance will be huge because there's so few workers and they could easily have a bad streak. Buy just as likely they can have a good streak. On larger pools you have less variance because you have much more workers so bad streaks/good streaks are averaged out. But it doesn't matter which pool you use because over a long time span they average out to your expected earnings (not taking fees into account), just depends whether you like frequent small payments, or infrequent large payments.