Changelog:
- In progress. Still!
Errorlog:
- Nil.
Notifications:
- This is a work in progress, and will be continuously optimised (fiddled with). Feel free to comment - you might just see your suggestion appear.
0. Network expansion pauses.
The network only solved 997 blocks this week. Given the +/- 6% error that is not significantly less than the 1008 blocks per week which would maintain the current difficulty at the next retarget, but it certainly doesn't suggest any kind of increase in the size of the network.
1. GHash.IO loses second place to AntPool
The top two block makers are now both Chinese pools. Well done, guys who share my hemisphere! We are winners, eh? This puts GHash.IO in fourth place, but with the number of people posting that they will be moving to GHash.IO, this may not be the case for long.
2. Bitfury gets the prize for "Most consistent maximiser of transactions fees per block".
Unfortunately this is an unofficial "prize" offered by me, and the recipient gains nothing other than kudos. However, Bitfury have done a great job in ensuring that they have maximised the transaction fee per block consistently. Other pools that share their transaction fee income with miners have also started to become better at maximising transaction fees per block.
This is something that pools should be focusing on now. The next reward halving is only about 18 months away, but transaction fees are only making up about a half of a percent of the overall block reward.
This is something that pools should be focusing on now. The next reward halving is only about 18 months away, but transaction fees are only making up about a half of a percent of the overall block reward.
Solved block statistics table. This
table lists all statistics that can be derived from the number of
blocks a hashrate contributor has solved for the past week. Block
attributions are either from primary sources such as those claimed by a particular pool website, or secondary sources such as coinbase signatures, or known generation addresses. When
dependent on secondary sources only, data may be inaccurate and miss
some blocks if a particular block-solver has gone to some trouble to
hide solved blocks. This will result in an underestimate of the block-solver hashrate.
Note
that actual pool hashrates when derived from shares submitted per unit
time will be more accurate than the hashrate estimates given in this
table.
"Unknown"
is not an entity but the group of blocks to which I cannot give
attribution using the methods given above. "BitAffNet" is Bitcoin
Affiliate Network.
Although I update regularly, I don't correct old posts.
Reused but unknown generation addresses
Unknown
generation addresses that are not reused are probably solominers or
private mining concerns that don't have share-holders wanting to follow
transactions. However, reused addresses are probably from hash
contributors that do not wish to remain anonymous. These need to be
identified so they can be removed from the "Unknown" group. I'm not
interested in identifying those who wish to remain completely anonymous,
so I'm not trying to trace originating IP addresses (as Blockchain.info does).
| Unknown recurring generation address | Blocks solved this week | Percentage of network | Percentage of unknown | Estimate of hashrate | Blocks solved ever |
|---|---|---|---|---|---|
| 12ZRejaK1cZtRwbKKRU9cmpSRssB35ACUZ | 14 | 1.40 % | 14.14 % | 4372 Thps | 14 |
| 1GcF7j3YH8Qs8hvNEe7zbrQZftMU6sRLfu | 13 | 1.30 % | 13.13 % | 3988 Thps | 483 |
| 1TqmiWzmyYsn1tqDeiCWM4xDi1R4ZCjaZ | 13 | 1.30 % | 13.13 % | 4059 Thps | 13 |
| 1GaKSh2t396nfSg5Ku2J3Yn1vfVsXrGuH5 | 11 | 1.10 % | 11.11 % | 3364 Thps | 50 |
| 1MoYfV4U61wqTPTHCyedzFmvf2o3uys2Ua | 8 | 0.80 % | 8.08 % | 2474 Thps | 34 |
| 14rMVqzic3R3MVcZaKikJGJyLqBexr4YiA | 7 | 0.70 % | 7.07 % | 2020 Thps | 7 |
| 12Taz8FFXQ3E2AGn3ZW1SZM5bLnYGX4xR6 | 6 | 0.60 % | 6.06 % | 1874 Thps | 6 |
| 1owN2ZN5g1wvGAAcyXpEEDyPZYobHY9iV | 6 | 0.60 % | 6.06 % | 1826 Thps | 6 |
| 15PxUiabFpqBArHtgx3Bw38kB9nT1kW3Py | 5 | 0.50 % | 5.05 % | 1561 Thps | 5 |
| 1Nep2BTfQw33aYwoXt8UrPiN7esdKj5aSi | 5 | 0.50 % | 5.05 % | 1561 Thps | 5 |
| 1ARGFoKoroyd13LAYesT78ehTVHxf4gXwk | 4 | 0.40 % | 4.04 % | 1249 Thps | 4 |
| 1BwZeHJo7b7M2op7VDfYnsmcpXsUYEcVHm | 3 | 0.30 % | 3.03 % | 913 Thps | 130 |
| 1NG3s36TvSzNoDTXgbeff4XtCHK3uCLX2Q | 1 | 0.10 % | 1.01 % | 289 Thps | 6 |
| 1Nhx4RU5bbUiHEXJLFEdQaewwHYnpSNAvD | 1 | 0.10 % | 1.01 % | 312 Thps | 3 |
Block makers: stacked histogram percentage of network blocks
A visual representation of the "Percentage of network" data aggregated in the table.
Block makers: actual and cumulative percentage of network blocks
Another
visualisation of the data in the table. The unshaded section indicates
the largest block makers that control 50% of the network between them.
Comparison of transaction fee per block
Block makers that consistently perform better than average are attempting to earn as much from each block as possible, which probably means more transactions per block and a better functioning network.
Block makers that consistently earn less than average transactions per block are either including too many low priority (no fee) transactions or are trying to reduce their orphan rate by reducing the size of their blocks.
In progress:
##### Block makers:
### Hashrate distribution: top 10 block maker proportion of network
### Historical hashrate distribution heatmap: all block makers
### Centralisation visualisation
### total tx fee per kb size, by pool
organofcorti.blogspot.com is a reader supported blog:
1QC2KE4GZ4SZ8AnpwVT483D2E97SLHTGCG
Created using R and various packages, especially dplyr, data.table, ggplot2 and forecast.
Recommended reading:
- For help on ggplot2.
- For help on forecasting.
Thank you to blockchain.info and coinometrics.com for use of their transaction and address data, and coincadence.com for their p2pool miner data.
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 0.01 btc 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!
I write in British English.
<weeklypoolstatistics>
No comments:
Post a Comment
Comments are switched off until the current spam storm ends.