0. Introduction
I introduced the mining centralisation index a couple of days ago in this post. Judging by email, I haven't done a very good job explaining how to calculate it - so I've done it again, but with a visualisation to help.
Step 1. Arrange the block making miners in order of size
- Pick a time period, calculate the number of blocks created by known block creators.
- Unknown block creators are grouped into "Unknown".
- Sort the block creators from largest to smallest.
- Calculate the cumulative sum of blocks created by each entity.
- Split into groups consisting of the larger and smaller pools (in the plot below, red and blue respectively).
- Paraphrased, the red group is the largest block creators that make most 50% of network blocks for the time period, and the blue group is the smallest block creators that make at 50% of network blocks or just over.
- Calculate the mean blocks per block maker for each group.
Step3: Subtract from ratio of means from 1.
- Divide the mean of the smaller group by the mean of the larger group - in the example above that would be 27.9 / 164.3 = 0.1698.
- Near zero, the average block solve rate of the smaller makers is much less than the larger makers, and at 1 block solve rate of the smaller makers approaches that of the larger makers.
- This is opposite to the other indices, so subtract the ratio from 1
- 1 - 0.1698 = 0.8302.
Centralisation index:
1 - mean(block rate smaller makers) / mean(block rate larger makers)
Email me if I still haven't explained this well enough for you.
Organofcorti lives!
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 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!



No comments:
Post a Comment
Comments are switched off until the current spam storm ends.