August 18th 2013 weekly pool and network statistics

Welcome, miners.

Changelog:

• Nil

Usual pools missing from results:

• Nil

Errors:

• Nil

Pools with coinbase signature:

• ASICMiner: "Mined By ASICMiner"
• 50BTC.com: "Hi from 50BTC.com
• Bitparking: "bitparking"
• BitMinter:  "BitMinter"
• BTCGuild :  "Mined by BTC Guild", "BTC Guild DE", "BTC Guild 2", "BTC Guild US2", plus a new signature, "BTC Guild GW"
• CoinLab: "CoinLab"
• Discus Fish: "七彩神仙鱼" and "Made in China"
• EclipseMC: "EMC"
• Eligius: "Eligius"
• HHTT: "HHTT"
• Ozcoin: "ozcoin"
• Triplemining: "Triplemining.com"
• Satoshi Sysems: "Satoshi Systems"
• Slush's pool: "slush"
• ST Mining Corp: "st mining corp"

Pool hopping:

• Nil.

1. bghash.io

The entity signing "bghash.io" in the coinbase has stopped adding that signature since last week. They still seem to be mining, as their payout address shows:

1CjPR7Z5ZSyWk6WtXvSFgkptmpoi4UM9BC

The current blocks belonging to them no longer have coinbases signed with an obvious unique identifier.

2. 1320 blocks solved by the network this week.
No sign of the network hashrate slowing any time soon. Even with some reduction in the increase of additional hashing sources, the network could be at 500 Thps by next week -  and at that rate, 1 Phps in 4 to 6 weeks.

3. BTCGuild luck
BTCGuild had enormous luck this week, with a CDF of 0.02. This is about a once in a year event, so I hope the BTCGuild miners enjoyed it.

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>