August 4th 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• Nil

Usual pools missing from results:

• Bitcoinpool.com - site unavailable.

Errors:

• Nil

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", "BTC Guild 2"
• CoinLab: "CoinLab"
• Discus Fish: "七彩神仙鱼" and "Made in China"
• EclipseMC: "EMC"
• Eligius: "Eligius"
• HHTT: "HHTT"
• Ozcoin: "ozcoin"
• Triplemining: "Triplemining.com"
• Satoshi Sysems: "Satoshi Systems"
• Slush's pool: "slush"
• ST Mining Corp: "st mining corp"

Pool hopping:

• Nil.

There are lots of new ASIC miners around, and if you're not tied to any particular pool already I have a suggestion. Look at chart 8, which shows the user hashrate distribution for each pool. Look for pools with the largest density of user accounts above 50 to 100 Ghps - those will be the pools that have happy ASIC owners and few GPU owners. If they are small pools, why not give them a try? Ozcoin and HHTT are the pools with the largest number of ASIC users at the moment.

Also, congrats to p2Pool - really picking up steam. The ASIC problems there must have been solved.

Finally, anyone else noticed that the network hashrate has increased exponentially (linearly on the exponential scale) since February this year. Why could that possibly be, Avalon? Anyone game to guess when the increase will revert to linear?

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 that of some pools 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


<weeklypoolstatistics>