Changelog:
- New hashrate distribution plots
- Historical weekly percentage of network attributable to block makers.
- Historical daily percentage of network attributable to block makers.
Errorlog:
- Nil.
Notifications:
- Nil.
0. Network plateau continues.
949 blocks solved this week, with a 95% confidence interval upper bound of 1011 blocks. If the upper bound was less than 1008, the network would have contracting with 95% confidence.
1. Unknown percentage of network is up.
It might be that 12Taz8FFXQ3E2AGn3ZW1SZM5bLnYGX4xR6 and / or 1MFUheNfHBThbmkq6KZuockxXrAtDP4k4e are Bitfury addresses since they've been making fewer blocks since these two addresses showed up, but this could be a complete coincidence. If anyone knows who owns the unknown addresses on this weeks' list, please email me.
1. Unknown percentage of network is up.
It might be that 12Taz8FFXQ3E2AGn3ZW1SZM5bLnYGX4xR6 and / or 1MFUheNfHBThbmkq6KZuockxXrAtDP4k4e are Bitfury addresses since they've been making fewer blocks since these two addresses showed up, but this could be a complete coincidence. If anyone knows who owns the unknown addresses on this weeks' list, please email me.
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 |
---|---|---|---|---|---|
12Taz8FFXQ3E2AGn3ZW1SZM5bLnYGX4xR6 | 29 | 3.06 % | 21.01 % | 9056 Thps | 35 |
1MFUheNfHBThbmkq6KZuockxXrAtDP4k4e | 24 | 2.53 % | 17.39 % | 7494 Thps | 24 |
1GaKSh2t396nfSg5Ku2J3Yn1vfVsXrGuH5 | 18 | 1.90 % | 13.04 % | 5621 Thps | 68 |
1MoYfV4U61wqTPTHCyedzFmvf2o3uys2Ua | 16 | 1.69 % | 11.59 % | 4996 Thps | 50 |
1829SCzm1dYVvDsvUeLuMyAhuMwjPuYxw3 | 10 | 1.05 % | 7.25 % | 3123 Thps | 10 |
17ejWXwuio19fehgx5GT7xEVUYiP5SjBL7 | 8 | 0.84 % | 5.80 % | 2498 Thps | 8 |
1BwZeHJo7b7M2op7VDfYnsmcpXsUYEcVHm | 8 | 0.84 % | 5.80 % | 2498 Thps | 138 |
15B5LzRh2JnFnTrdSapCbzCkmnPjkhCDN2 | 4 | 0.42 % | 2.90 % | 1249 Thps | 4 |
1ELwSbFZfHPNtymepA2HF8RXHCzZvLbeSi | 4 | 0.42 % | 2.90 % | 1249 Thps | 4 |
1Nva32z8rTPdEKzYoMqn6hMQcHecMUyLsA | 4 | 0.42 % | 2.90 % | 1249 Thps | 4 |
1D4sLQibhyCNYYghRFfuJpGq88f5PtqMid | 3 | 0.32 % | 2.17 % | 937 Thps | 3 |
1GcF7j3YH8Qs8hvNEe7zbrQZftMU6sRLfu | 3 | 0.32 % | 2.17 % | 937 Thps | 486 |
1H7Xw9eirfDy3yM4hFZYeYuiJq8ZhvQQkV | 3 | 0.32 % | 2.17 % | 937 Thps | 3 |
15PxUiabFpqBArHtgx3Bw38kB9nT1kW3Py | 2 | 0.21 % | 1.45 % | 625 Thps | 7 |
1qtKetXKgqa7j1KrB19HbvfRiNUncmakk | 1 | 0.11 % | 0.72 % | 312 Thps | 16 |
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
the largest block makers 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.
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.
In progress:
### 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.
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.