Pages

▼

Sunday 15 December 2013

December 15th 2013 Weekly Pool and Network Statistics




Other weekly pool and network statistics posts


Welcome, miners.

Changelog:
  • Nil
Usual pools missing from results:
  • BTCDig, Triplemining, Deepbit: No blocks solved this week.
Errors:
  • The hashrate (or possibly luck, or both) estimates for either BTCGuild or GHashIO are incorrect. I'm not sure which.
Pools with coinbase signature:
Recent coinbase messages:

Pool hopping:
  • Nil.

1. BTCGuild and GHash.IO 
You might notice that although BTCGuild's hashrate is higher than GHash.IO's hashrate, it solved fewer blocks. This would indicate a worse luck for BTCGuild than for GHash.IO, and yet the results show the reverse.

I'm not sure which of the results are in error - my BTCGuild script is complicated and the script for GHash.IO is new. I'll be spending tonight trying to figure out what the problem is.


Organofcorti lives!

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, per 144 rounds for the network, and per hour for BTCGuild. 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

Find a typo or spelling error? Email me with the details at organofcorti@organofcorti.org and if you're the first to email me I'll pay you per ten errors:



Please refer to the most recent blog post for current rates or rule changes.

I'm terrible at proofreading, so some of these posts may be worth quite a bit to the keen reader.
Exceptions:
  • Errors in text repeated across multiple posts: I will only pay for the most recent errors rather every single occurrence.
  • Errors in chart texts: Since I can't fix the chart texts (since I don't keep the data that generated them) I can't pay for them. Still, they would be nice to know about!


<weeklypoolstatistics>

at

No comments:

Post a Comment

Comments are switched off until the current spam storm ends.