Pages

Sunday, 17 March 2013

17th March 2013 weekly pool and network statistics



Welcome, miners.

Changelog:
  • Nil

Pools missing from results:



"ASIC ready" pools:



Pool hopping:



Lots of drama this week. The hard fork had a significant effect on the midweek hashrate, so the retarget difficulty was a little less than estimated.  Figure 4 shows how pool's hashrates were affected by the downtime.

Earlier in the week while BTCGuild pool op eleuthria was upgrading a merged mining server to bitcoin 0.8.0, a bug allowed miners to credit their accounts with far more bitcoin than they were due. This personally cost eleuthria 1250 btc - about US $60 000 at current exchange rates. So far only one miner has returned any of the coins. CryptoCluster returned the 47.8 btc (US $2 300) without even a request email - that's certainly one way to increase your standing in a community that is mostly anonymous. On the other hand, a miner (whose details eleuthria has not released) responded to eleuthria's polite request to return the overpayment with scorn. I hope we learn his username, since I wouldn't want to do business with such a community member.

Eclipse Mining Consortium was DDoS'd for much of the week. I'm not sure whether his response to this has affected the API was using for his pool data, but I expect to have it fixed for next week. This means the "Unknown" section of the pir chart is about 1.5 Thps larger than it would be if Eclipse had been included. This means that "Unknown" is down to about 6%. It appears not much solomining mining is being done by ASICs.

Both Eligius and BitMinter overtook Deepbit this week, and thanks to some hefty ASIC power added Eligius' hashrate jumped to 5 Thps for a day or so.

Bitcointalk forum member gyverlb posted an excellent guide to mining on p2Pool. Since mining on p2Pool can net you more coin than mining on other centralised pools, this post is important reading for any geeky miner.

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 50BTC.com hashrate 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 fulltime miner earnings loss at a proportional pool caused by pool hoppers, expressed as expected PPS earnings for fulltime miners. Currently only for Bitlc and Deepbit. Only valid if strategic pool hopping is actually occurring (see figure 7). 














Thanks to blockexplorer.com and blockchain.info for use of their network statistics.

Donations help give me the time to analyse bitcoin mining related issues and post the results.

If you enjoy my posts or if I've saved you some coins or helped you earn more, please consider a small bitcoin donation:

12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r

No comments:

Post a Comment

Comments are switched off until the current spam storm ends.