Proposal 134258
TLDR: Looks good, I’ll vote to adopt this proposal. The DFINITY-controlled node in this subnet is down, and is being replaced with an unassigned DFINITY-controlled node. This means that after this proposal executes, there should be 1 functional DFINITY node in this subnet, which is a requirement for DFINITY to be able to action subnet recovery steps in disaster scenarios.
Decentralisation metrics remain unchanged by this proposal.
Motivation:
- replacing dead node wzr5d-7qa2x-tduot-6mkkq-ou4sc-5ktje-4hxqa-a75d5-gunkc-3xhyt-6qe
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 191.173 km | 8868.804 km | 18480.492 km |
| PROPOSED | 191.173 km | 8868.804 km | 18480.492 km |
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 5 | 12 | 13 | 13 | 13 | 13 |
| PROPOSED | 5 | 12 | 13 | 13 | 13 | 13 |
Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →
| Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 4 | 2 | 1 | 1 | 1 | 1 |
| PROPOSED | 4 | 2 | 1 | 1 | 1 | 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.
Another good neuron to follow is Synapse (follows the LORIMER and CodeGov known neurons for Subnet Management, and is a generally well informed known neuron to follow on numerous other topics)