Pages

▼

Sunday, 10 November 2013

November 10th 2013 weekly pool and network statistics




Other weekly pool and network statistics posts


Welcome, miners.

Changelog:
  • Added GIVE-ME-COINS.com.
  • A reader reported that the confidence intervals for the network hashrate in figure 2 were very hard to see. I have removed the gray background and reduced the line width to make the confidence interval a bit clearer.
  • The gray background has also been removed from the pie chart - it also has some transparency so I think a white background will allow better contrast.
Usual pools missing from results:
  • 50BTC and Deepbit - no blocks solved this week.
Errors:
  • Nil
Pools with coinbase signature:
Recent coinbase messages:

Pool hopping:
  • Nil.







  
1. Network drops back even further - 1150 blocks solved this week.
Perhaps it's the effect of KNC finishing shipping and the changes in difficulty this caused, but the number of blocks solved this week was 1150 - only 14% more than expected. Hopefully the next change in difficulty won't be as extreme as the last few.

2. Most big pools have bad luck this week.
In order of crappiness of luck (worst luck to best luck):

                Pool Mean shares/round/difficulty  CDF
1              Itzod           1.19                0.73
2        Giga's pool           1.12                0.75
3           GHash.IO           1.11                0.96
4              Slush           1.08                0.76
5           BTCGuild           1.05                0.82
6          Bitminter           1.04                0.65
7            Eligius           0.94                0.22
8         Bitparking           0.79                0.36
9             p2Pool           0.71                0.11
10           Polmine           0.69                0.24
11           Eclipse           0.68                0.04

This means it was probably a bad luck week for the network. However, it should be noted that the CDF for all pools were within a 95% confidence interval and so when averaged over the week none had unusually good or bad luck.

4. 50BTC still at 4Ghps.
Still no news, almost no-one mining, but lots of anger in the 50BTC thread on the bitcointalk.org forum.

5. Polmine: more bouncy hashrates.
(see figure 4) A commenter on last week's post named 'lenny' had this to say:
Polmine's spikes in hashrate happening, because main server is running out of processing power. Right now, according to main pool operator - megavega, background thread is processing backlog of accepted shares during last couple of days, process has reached 60% so far. That's why hashrate right now seems to be higher than it's really is, and was reported lower than it really was in last couple of days.
This may be correct, however the "hashrate spikes" have been occurring since the start of the dataset - so while this may explain one of last week's spikes, it doesn't explain them all. Any other ideas?

Polmine's hashrate per round:

         Date   Thps
1 2013-11-04  14.36
2 2013-11-04   6.17
3 2013-11-05 178.77
4 2013-11-07  11.78
5 2013-11-09   5.23

6. Proofreading
Proofreading payments total so far: 0.105 btc.

Thanks to everyone who has submitted error reports so far! I appreciate all the help I can get. Note that with the recent increase in the exchange rate, the current payment per error has automatically dropped to 0.001 btc.


Organofcorti lives! (thanks to Eclipse )

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 error:
 

I'm terrible at proofreading, so some of these posts may be worth quite a bit to the keen reader.


<weeklypoolstatistics>

at

No comments:

Post a Comment

Comments are switched off until the current spam storm ends.