Proposal 132181
TLDR: I’ve voted to adopt this proposal.
- One degraded node replaced with an up node
- One node that’s currently contributing to the violation of the data center nakamoto coefficient replaced with a diversified node👍
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
Smallest Distance | Average Distance | Largest Distance | |
---|---|---|---|
EXISTING | 3.534 km | 6951.098 km | 15939.448 km |
PROPOSED | 3.534 km | 7783.34 km (+12%) | 16347.516 km (+2.6%) |
This proposal increases decentralisation in terms of geographic distance (and therefore there’s a potential increase in localised disaster resilience).
Subnet characteristic counts →
Continents | Countries | Data Centers | Owners | Node Providers | |
---|---|---|---|---|---|
EXISTING | 3 | 9 | 13 | 12 | 13 |
PROPOSED | 4 (+25%) | 10 (+10%) | 13 | 13 (+7.7%) | 13 |
This proposal improves decentralisation in terms of jurisdiction and data center ownership diversity. Note that this subnet is currently violating the IC target topology regarding the data center nakamoto coefficient, and this proposal brings it back into the acceptable limits.
Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →
Continent | Country | Data Center | Owner | Node Provider | |
---|---|---|---|---|---|
EXISTING | 6 | 4 | 1 | 2 | 1 |
PROPOSED | 6 | 3 (-25%) | 1 | 1 (-50%) | 1 |
See here for acceptable limits → Motion 132136
The above subnet information is illustrated below, followed by a node reference table:
Map Description
- Red marker represents a removed node (transparent center for overlap visibility)
- Green marker represents an added node
- Blue marker represents an unchanged node
- Highlighted patches represent the country the above nodes sit within (red if the country is removed, green if added, otherwise grey)
- Light grey markers with yellow borders are examples of unassigned nodes that would be viable candidates for joining the subnet according to formal decentralisation coefficients (so this proposal can be viewed in the context of alternative solutions that are not being used)
Table
Known Neurons to follow if you're too busy to keep on top of things like this
If you found this analysis helpful and would like to follow the vote of the LORIMER known neuron in the future, consider configuring LORIMER as a followee for the Subnet Management topic.
Other good neurons to follow:
-
CodeGov (will soon be committed to actively reviewing and voting on Subnet Management proposals based on those reviews)
-
WaterNeuron (the WaterNeuron DAO frequently discuss proposals like this in order to vote responsibly based on DAO consensus)