26th May 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• The solomining portion of the ASICMiner hashrate has been added. The weekly blocks and hashrates are calculated using blocks with the "Mined by ASICMiner" signature in the coinbase. I've done the same for 50BTC.com and HHTT.

Pools missing from results:

• Ozcoin - Ozcoin's data still looks a bit odd, and the results for this week are probably wrong.
• Coinotron - site's down, again.

Errors:

• Nil.

"ASIC ready" pools:

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

Pool hopping:

• None.

Thanks:

• Pool ops kinlo (Triplemining) and DrHaribo (Bitminter) for helping me figure out how to get the coinbase of each block without having to hammer blockexplorer.com too much. kinlo actually wrote me a bitcoind patch which I'm sure would have been very helpful if I had been able to compile bitcoind from source on my old macbook pro linux machine, which for some reason I can't.

Many pools had bad luck this week. This may have been due to a problem with getblocktemplate, which seems to have slowed many pools down until a patch was made available earlier in the week.

BTCGuild solved a comfortable 32.2% of blocks this week, so there are already calls for the PPS rate to be reduced. I doubt that will happen any time soon - BTCGuild could easily pop the 40% barrier if all the PPS miners returned.

ASICMiner's solomining has been added as a pool from this week on. Don't forget they have some hashrates at BitMinter and BTCGuild - only the solomined blocks show up on the tables and charts.

 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