February 9th 2014 Weekly Hashrate Contributor and Network StatisticsOther Weekly Hashrate Contributor and Network Statistics postsWelcome, miners.
Changelog:
Changed the hashrate scaling for figure 6 to Thps.
Improved the generation address ownership algorithm, resulting in slightly fewer "Unknown" blocks.
Usual pools missing from results:
I haven't rebuilt this part yet - still TBA.
Errors:
I still haven't found any.
0. No orphaned block charts yet
I think I've found the best way to chart orphaned blocks, I just need time to do it. Hopefully I'll find time this week or the next.
1. The network hashrate continues to increase, as do unknown contributors
Another 1226 blocks solved this week, 218 more than expected. Of these, 104 blocks are from unknown contributors. If you turn to table 3, you can see that one of the generation addresses has now been assigned a total of 24 blocks, five in this week alone. Interestingly, none of the block reward has moved from this address yet. It seems there are some new cloud-hashers around. Maybe KNC has gotten their data centre going already?
That's all I have time for this week. Enjoy the chartporn, and see if you can find out to whom some of the richer unknown generation addresses belong.
Explanation of the tables and charts.
Table 2: Pool reported block history statistics. This table lists all statistics that can be derived from the number of blocks a hashrate contributor has solved for the past week using all solved blocks - both valid and orphaned - and difficulty 1 shares per round.
A much more accurate estimate of the hashrate, confidence intervals are unnecessary.
Orphan races lost, and percentage of solved blocks that were not added to the blockchain.
"Luck" is the usual difficulty 1 equivalent shares per round / mining difficulty, or (equivalently) accepted shares / expected shares.
CDF: The cumulative density function (CDF) measures the percentage of the time this number accepted shares / expected shares would be less than the calculated value, given the number of valid + invalid blocks.
Bitcoin per Gigashare. This figure is not an indicator of how much a miner should have expected per one million Difficulty 1 shares (or one thousand difficulty 1000 shares, etc), since it doesn't take into account the reward method or fees charged. Rather, it should be considered as a "luck" index that also incorporates the number of orphaned blocks and the current reward per block.
Since BTC Guild doesn't report shares per block but does report transaction hashes for all blocks, luck calculations cannot be calculated but orphaned blocks can. Pools such as "Discus Fish" that don't have a public pool interface can not be included.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2F4.bp.blogspot.com%2F-ooIjg1chz6Q%2FUvcaSrcKTzI%2FAAAAAAAALhA%2Ftx9pw4_aNKQ%2Fs1600%2F0.table3.09022014.png&t=665&c=yyBFU4eE3LaVcQ)
Figure 3: Percentage of blocks solved each week for the current top ten contributors.
Data is calculated from the number of blocks each contributor added to the blockchain during the week. The points are the actual data; the lines are exponentiated smoothing splines of the log of the data.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2F2.bp.blogspot.com%2F-M0ib9Qx3P0M%2FUvcv_REvykI%2FAAAAAAAALio%2F2w4StGX3sTQ%2Fs1600%2F3.top10pcnet.09022014.png&t=665&c=L8ExoiJP_F6LbQ)
Figure 5: Pool "luck" (valid + invalid solved blocks)
The orange dots are the usual accepted shares / expected shares (equivalently, shares per round / network Difficulty). The background colours are accepted shares / expected shares confidence intervals for the number of blocks solved for the week. The greater the number of blocks solved (the higher the percentage of the network) the narrower the bounds.
The "luck" data points should be outside the upper or lower boundaries only rarely. Many data points outside this range indicate unusual and unlikely "luck".
Data only goes back for the last twelve months at most - any more data points than this becomes hard to read, and recent data is most important.
Note that all solved blocks are used, otherwise the data would no longer be Erlang distributed and a CDF could not be calculated.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2F4.bp.blogspot.com%2F-XwHfxUlavtk%2FUvcacbVh_YI%2FAAAAAAAALh4%2FKrSPcEcWKOg%2Fs1600%2F5.luck.09022014.png&t=665&c=ilacH0ExAADKVQ)
As usual, please post comments if there's anything you don't understand, with which you disagree, or just think is wrong.
You can view all of this weeks charts at
http://organofcorti.blogspot.com.au/2014/02/february-9th-2014-weekly-hashrate.htmlYou can view all previous charts at
http://organofcorti.blogspot.com.au/search/label/weeklypoolstatistics and other posts and fun things at
http://organofcorti.blogspot.com. Follow me on Twitter @oocBlog for notification of new posts as soon as I publish.