Changelog:
- Added "Dot pool".
- Added Huobi.
Errorlog:
- Nil.
Notifications:
- Nil.
0. Unknowns down to 5%
I was able to find a couple of new block makers, or perhaps old ones that just started signing their coinbase transactions, so let me introduce ...
1. "Dot pool"
Since they have just signed their coinbase with varying numbers of dots (depending on the generation address used, and probably indicating a particular cluster), they have have lost the right to name themselves. Dot pool, this is why f2pool is *still* known as "Discus fish"! I think I know who Dot pool is, but I need to do some clustering of historical generation addresses first.
2. Huobi
No prizes for guessing who this is, but it's nice that they're starting with a clear signature and not a cryptic series of punctuation marks.
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.
Since they have just signed their coinbase with varying numbers of dots (depending on the generation address used, and probably indicating a particular cluster), they have have lost the right to name themselves. Dot pool, this is why f2pool is *still* known as "Discus fish"! I think I know who Dot pool is, but I need to do some clustering of historical generation addresses first.
2. Huobi
No prizes for guessing who this is, but it's nice that they're starting with a clear signature and not a cryptic series of punctuation marks.
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 |
|---|---|---|---|---|---|
| 16osefsZzzDCh86QutVadGtbwik8fviSBk | 10 | 0.98 % | 20.00 % | 3157 Thps | 10 |
| 1BwZeHJo7b7M2op7VDfYnsmcpXsUYEcVHm | 6 | 0.59 % | 12.00 % | 1849 Thps | 158 |
| 1EESB4Adcpj1KxKLwKzbVHa5Hhnaccw9rt | 6 | 0.59 % | 12.00 % | 1894 Thps | 6 |
| 16EKK7jG5yGW8SUiSQKzVLhRn1HZGw2cZg | 5 | 0.49 % | 10.00 % | 1578 Thps | 5 |
| 1H54AZuzcZs5EUiBzdiG7KDYkAm3hsv8KW | 5 | 0.49 % | 10.00 % | 1511 Thps | 5 |
| 1JxdrJwz9BX97ZVSTNFcExHkXhCsgENKH1 | 5 | 0.49 % | 10.00 % | 1465 Thps | 5 |
| 1GyTBMYL2rpsvguV8pwjU4MyRrivb6Jfi9 | 4 | 0.39 % | 8.00 % | 1263 Thps | 4 |
| 16vSD9vnoDmKJZNztcSNVvVa2CpVgpmkcV | 3 | 0.29 % | 6.00 % | 947 Thps | 3 |
| 17L54QRj652Qm6N7CXrHbDPcYxbhi7KNSL | 1 | 0.10 % | 2.00 % | 293 Thps | 5 |
| 1GcF7j3YH8Qs8hvNEe7zbrQZftMU6sRLfu | 1 | 0.10 % | 2.00 % | 316 Thps | 506 |
Hashrate distribution: Stacked histogram percentage of network blocks
A visual representation of the "Percentage of network" data aggregated in the table.
Hashrate distribution: Actual and cumulative percentage of network blocks
Another
visualisation of the data in the table. The unshaded section indicates
block makers with the largest hashrates that control 50% of the network
between them.
Hashrate distribution: Heatmap of historical percentage of network blocks attributable to block makers.
The data in the above hashrate distribution histogram is a subset of the weekly data data below.
Hashrate distribution: Daily proportion of network for current block makers.
The
next three plots group hashrate distribution into three tiers: The
block makers with the largest proportion of the network, block makers
with an average proportion of the network, and block makers with the
smallest proportion of the network.
Because the data is a daily summary, the kernel smoothing shows quite clearly the variance in hashrate distribution that occurs in block making. It will also show the intra-week hashrate movements which were previously unavailable.
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.
Historical centralisation of bitcoin network block creation
This
chart shows the changes in the amount of the network controlled by the
largest block maker, second largest, and so on up to the twentieth
largest (should that number of block makers exist during the week the
estimate was made).
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.
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.
No comments:
Post a Comment
Comments are switched off until the current spam storm ends.