Other weekly pool and network statistics posts
Welcome, miners.
Changelog:
- Prettified the pie chart a bit more.
- 50BTC.com, Bitparking, Deepbit, GIVE-ME-COINS.com, Triplemining: No blocks solved this week.
- Nil.
- ASICMiner: "Mined By ASICMiner"
- Alydian5335: "Alydian5335"
- Bitparking: "bitparking"
- BitMinter: "BitMinter"
- BTCGuild: "Mined by BTC Guild", "BTC Guild DE", "BTC Guild 2", "BTC Guild US2", "BTC Guild GW"
- CoinLab: "CoinLab"
- Discus Fish: "七彩神仙鱼" and "Made in China"
- EclipseMC: "EMC"
- Eligius: "Eligius"
- 50BTC.com: "Hi from 50BTC.com" and "50BTC.com"
- GHash.IO: "ghash.io" (not current)
- GIVE-ME-COINS.com: "Mined at GIVE-ME-COINS.com"
- HHTT: "HHTT"
- Megabigpower "megabigpower.com"
- 175btc.com": "Mined By 175btc.com"
- Ozcoin: "ozcoin"
- Pierce and Paul: "For Pierce and Paul"
- Triplemining: "Triplemining.com"
- Slush's pool: "slush"
- 258692 "To my honey, by bitfish."
- 259575 259622 259625 "EMC: Organofcorti lives!"
- 263952 "btcpoolman"
Pool hopping:
- Nil.
Well, somewhere between 9.4 and 10.5 Phps anyway. Although the block solve rate was reduced to 1185 blocks this week, I imagine that will pick up again after the Christmas / New Years holidays are over and deliveries continue as usual.
2. Discus Fish continues to grab more of the network
Discus Fish, a Chinese pool, has increased its share of the network continuously for the last six weeks, and has increased by more than 600% over the last nine weeks. Don't Chinese miners mine anywhere else? Or does the pool have something that others don't? If Discus Fish does have some quality that makes it attractive to miners and they start courting English speaking miners, GHash.IO could be in trouble. In any case, it's nice to see a small pool move up to the top 5 in such an explosive fashion.
Another nice thing that Discus Fish does is immortalise its miners - if you're lucky enough to solve a block for them, they add your name to their coinbase signature, for example in block height 277468:
"\003\xdc;\004七彩神仙鱼\xe2\xf7\a\032.N%\006\x96\xcf|o\x9b\xb65\031[-\xaa)\xe3\xc8&\xc7\xf7\xe7+\xf6\003\\\020\004X\xe7Ɩ\b\n|Mined by user yangzhiqing"
3. Pierce and Paul
Pierce and Paul are only known by their/its coinbase signature, for example this one from block height 276311:
"\003W7\004YQ\x84\x9a4]\xeeu\xfd'eN\xe3\xdd\xf6\t\xff\xbc\xf83"\025\016\xd0(N\xa4\xfb\xba%\x90G\004Й\xb3\005\001\xd5For Pierce and Paul"
I have been assuming it's a private hashing entity rather than a private pool since the hashrate has remained steady (and the proportion of the network slowly decreasing) since they started signing the coinbase. This week sees a very large increase in the hashrate for them, so either a bunch of new ASIC hashers have been purchased by them, or they've become a private pool.
4. Happy new year everyone!
That is all.
Organofcorti lives!
As usual, please post comments if there's anything you don't understand, with which you disagree, or just think is wrong.
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.
organofcorti.blogspot.com is a reader supported blog:
1QC2KE4GZ4SZ8AnpwVT483D2E97SLHTGCG
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:
Please refer to the most recent blog post for current rates or rule changes.
I'm terrible at proofreading, so some of these posts may be worth quite a bit to the keen reader.
Exceptions:
- Errors in text repeated across multiple posts: I will only pay for the most recent errors rather every single occurrence.
- Errors in chart texts: Since I can't fix the chart texts (since I don't keep the data that generated them) I can't pay for them. Still, they would be nice to know about!
<weeklypoolstatistics>
No comments:
Post a Comment
Comments are switched off until the current spam storm ends.