2nd June 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• Entities responsible for signing in the coinbase "Made in China", "七彩神仙鱼" ("Discus fish" in English),  and "st mining corp" have been added. Hashrates are calculated from the number of blocks solved in one week.
• From next week, Ozcoin's data will also be calculated from the number of blocks solved in one week, using their coinbase signature.
• "ASIC ready" list removed (since all pools should now be "ASIC ready") and has been replaced by the "Coinbase signatures" list.
• New hashrate distribution chart (Figure 8)

Pools missing from results:

• Coinotron - site's up, but having trouble scraping them.
• p2Pool - p2Pool.info is having some problems at the moment.

Errors:

• Ozcoin's data for this week is using the site data, and is incorrect as far as I can tell.

Pools with coinbase signature:

• ASICMiner: "Mined By ASICMiner"
• 50BTC.com: "Hi from 50BTC.com
• Bitparking: "bitparking"
• BitMinter:  "BitMinter"
• BTCGuild :  "Mined by BTC Guild", "BTC Guild DE", "BTC Guild 2"
• Discus Fish: "七彩神仙鱼"
• EclipseMC: "EMC"
• Eligius: "Eligius"
• HHTT: "HHTT"
• Made In China: "Made in China"
• Ozcoin: "ozcoin"
• Triplemining: "Triplemining.com"
• Slush's pool: "slush"
• ST Mining Corp: "st mining corp"

Pool hopping:

• None.

I'm certain the Ozcoin data is wrong, but I can't figure out how. It seems to be incorrect at the website, but I could be wrong. Until I can figure out the source of the inaccuracy, from next week onward I will change to calculating their hashrate from the number of blocks solved in the week.

 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 for use of their network statistics.

organofcorti.blogspot.com is a reader supported blog:

12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r