Pages

▼

Sunday 11 August 2013

August 11th 2013 weekly pool and network statistics

Welcome, miners.

Changelog:
Usual pools missing from results:
  • Maxbtc - planned closure.
  • Coinotron - planned closure. 
  • Bitcoinpool - Website down and as far as I know no blocks solved since May. I'm assuming they are closed.
Errors:
  • Blockexplorer.com hasn't updated since block height 250458. Since I use Blockexplorer.com for the network's hashrate every 144 blocks, that statistic is incomplete this week. The weekly average hashrate, blocks solved and so on I calculate using my own data so that is unaffected.

Pools with coinbase signature:

and the generated coin was paid to this address:
1CjPR7Z5ZSyWk6WtXvSFgkptmpoi4UM9BC
which has been actively solving blocks since the 6th July.

Pool hopping:
  • Nil.

1. Unknown hashing sources at 1.9% of network
Blocks solved by unknown  sources are now down to 1.9% - that's only 25 blocks out of a total of 1323 for this week. That total is 31.25% more than it should be, so I don't see the skyrocketing network hashrate start slowing down anytime soon - especially with all the new sources of hashes recently available.

2. Gigavps' Semi-private pool
I added Gigavps' Semi-private pool this week, starting on the charts with a massive 7% of the network. Interestingly, Figure 8 shows the pool has a much higher minimum hashrate than for other pools. Specifically, the minimum hashrate is ~7Ghps, and the top four user accounts have between 1.2 and 7.8 Thps. This is an all-ASIC pool (or at least very close to it). I think most pools hashrate distributions will look similar to that in the future.

3. Lest we forget
Also this week we say farewell to Coinotron's BTC pool and MaxBTC, both in a planned closure. Coinotron seems to want to focus on alt-coins, and MaxBTC's pool op will concentrate on Kraken.com, a very nice trading platform - give it a try, if you trade. ABCPool.com  has also closed but being a proxy pool they were not included in the weekly statistics.

Bitcoinpool.com is still offline with a 404 error from an nginx server somewhere. They haven't solved a block since May, so I think they won't be back.

In honour of the pools that have gone to the God of the Blocks' happy hashing grounds, I've produced a chart of the percentage of hashrates of all the dead pools for which I have records, in order of the last week in which they solved a block.

I'll update the chart when the next sad occasion arises - which I think will be when BTCDig.com arises phoenix-like from the ashes of btcmine.com, or perhaps it will be Bitclockers.com, which have had payment and website issues recently and today were down to a total pool hashrate of 1 Ghps.

So, with sadness and nostalgia I present the Dead Pools.


Please take some time to think about the pool operators who ran these pools, loved them as if they were their own children, and did their part to help secure the network. Also, don't forget about the many other pools that didn't make it -  Arsbitcoin and Continuum pool (the first pool to use the Geometric method of reward distribution, the progenitor of DGM) come to mind, but there have been many others, especially those that were unable to change from a proportional reward method.



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, 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
<weeklypoolstatistics>
at

No comments:

Post a Comment

Comments are switched off until the current spam storm ends.