21st April 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• Bitminter and Ozcoin added to figure 8 (proportion of hashrate per user per pool).

Pools missing from results:

• Ozcoin - couldn't connect to site today, understandable due to recent events. 

"ASIC ready" pools:

• BTCGuild
• 50BTC.com
• Slush's pool
• Ozcoin
• HHTT
• Bitminter
• EclipseMC
• Eligius
• Bitparking
• Itzod
• Triplemining

Pool hopping:

• None. Really. Not even a little bit. You'd think ASIC owners would want to maximise their profits but that doesn't seem to be the case.

The big news this week was the hack of Ozcoin. Pool op Graet had just arranged for a large backlog of shares to be paid out, and the entire payout was stolen by an unknown individual. If you're interested in following the coin trail and trying to find the cuprit, the trail starts with address 16cDeEFn6sraUEJrDCt2Yg3r7j2oazSYEd.

 My best wishes go out to Graet, who has been an important part of the mining community for years, and who has spent time and effort providing a low cost pool, helping miners mine better, and supporting the community generally. If you'd like to help support Ozcoin you can send hashes to yourbtc.net or bitcoin donations to 1Gzcbs8dDYzf16qFWKHc5kWKuH8nji3pVt

Since Ozcoin is not in this week's stats, the unknown proportion of the network hashrate is higher.

BTCGuild crossed the line of 40% of the average network hashrate this week. However, due to ongoing bad luck there, BTCGuild only has 37.6% of network blocks, an increase of 0.9% since last week. There was no significant change in the average network hashrate this week, so BTCGuild has gained a few hashes - despite the penalties eleuthria will be putting in place if the pool grows much larger.

As usual, please post comments if there's anything you don't understand, with which you disagree, or just think is wrong.


The charts

Table: Table of all pools with public data and their various statistics averaged for the last seven days - for smaller pools the average may be more or less than seven days, depending on number of blocks solved for the week. Network hashrate and 50BTC.com hashrate are estimates, the upper and lower 95% confidence interval bounds are included.
Figure 1: Pie chart of the percentage of network blocks hashrate by pool. "Unknown" combines those pools for which I can't scrape statistics, solominers and private pools. The percentage of network hashrate will only be approximate since the exact network hashrate is unknown.

Figure 2: Chart of network hashrate, hashrate of the largest mining pool, combined hashrates of the three largest mining pools, and a line representing 50% of the network hashrate. Handy if you're worried about 51% attacks. The upper and lower 95% confidence interval bounds for the network hashrate are in between the shaded areas.

Figure 3: Chart of chronology of pool hashrates, averaged per week.

Figure 4: Chart of average hashrates per pool per round for the week, and per 144 rounds for the network. The upper and lower 95% confidence interval bounds for the network hashrate are in between the shaded areas.

Figure 5: Chart of chronology of negative binomial CDF probability of shares submitted and blocks produced for the week.

Figure 6: Chart of chronology of round length divided by difficulty, averaged per week.

Figure 7: Chart of hashrate vs round length for hoppable pools (the larger the hashrate increase at the start of a round, the larger the loss to strategic miners).

Figure 8: Chart of pool user hashrate distribution. Note that for some pools this average is over twenty four hours, some pools are averaged over an hour or more and some for only fifteen minutes, so expect some variance in the results.

Thanks to blockexplorer.com and blockchain.info for use of their network statistics.

organofcorti.blogspot.com is a reader supported blog:

12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r