28th April 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• Nil.

Pools missing from results:

• Nil. 

"ASIC ready" pools:

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

Pool hopping:

• None. Am I going to be the only one to test out my Avalon this way? When it arrives, I mean.

Another hack this week - Slush's pool. Luckily Slush managed to prevent to from becoming a catastrophe, but with the recent uptick in DDOS attacks it seems pools are becoming a significant target. I wonder if the attackers realise how little most pool ops get to keep from their (mostly) tiny fees?

Thanks to all who donated to Ozcoin. Some of the coins were returned, its miners have been paid and the pool is back on its feet.

 BTCGuild has dropped to about 35% of network blocks ad anout 40% of the network hashrate. Hopefully some miners are taking eleuthria seriously and have moved to other, smaller pools - such as Bitparking (now a top 5 pool after almost doubling its hashrate this week), Eligius, EclipseMC and Itzod. 50BTC also picked up a lot of extra hashes this 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 and blockchain.info for use of their network statistics.

organofcorti.blogspot.com is a reader supported blog:

12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r