Pages

Sunday, 1 December 2013

December 1st 2013 weekly pool and network statistics




Other weekly pool and network statistics posts


Welcome, miners.

Changelog:
  • Nil
Usual pools missing from results:
  • 50BTC.com, BTCMine, Triplemining: No blocks solved this week.
Errors:
  • Nil
Pools with coinbase signature:
Recent coinbase messages:

Pool hopping:
  • Nil.

1. BTCGuild and GHash.IO 
GHash.IO keep increasing their share of the network, most likely due to CEX.IO trading. I'm not sure how I feel about this - it's an increase in the proportion controlled by a single entity, but in effect any pool has the same control of hashes. It should make no difference that (as far as I'm aware) CEX.IO maintains the hash sources locally rather than the sources being distributed. Is there a downside I'm not understanding?

2. The network hashrate has increased 20629 % in the last 12 months
I was looking over a few old posts and found this one from a year ago. 50BTC.com was top dog, BTCGuild and Deepbit shared second place. Now it's BTCGuild and GHash.IO (which didn't even exist then) and Deepbit and 50BTC.com are at ~ 1Thps each. Fortunes change rapidly in bitcoinworld.

3. My apologies for not returning emails over the past week or two.
I'm stuck on a very interesting problem which has lead me down a rabbit hole, and as a result I've been putting off responding to emails. I hope to get on to that shortly.

Anyway, I must go. The rabbit hole awaits....


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 ten errors:



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


<weeklypoolstatistics>

No comments:

Post a Comment

Comments are switched off until the current spam storm ends.