Proposal 134486
TLDR: I’ve voted to adopt this proposal, as it improves decentralisation metrics (see decentralisation stats below).
However it will very likely need to be followed up with another proposal, given that one of the nodes being added to the subnet is actually DOWN (as pointed out by @ZackDS above). Given that this proposal also removes a DOWN node from the subnet, the number of UP nodes would remain unchanged. Rejecting this proposal would impose an unwarranted cost to the proposing neuron (it doesn’t worsen the subnet).
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 95.554 km | 6292.975 km | 15377.131 km |
| PROPOSED | 477.324 km (+399.5%) | 7545.121 km (+19.9%) | 16759.085 km (+9%) |
This proposal slightly increases decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical increase in localised disaster resilience). 
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 3 | 12 | 13 | 13 | 13 | 13 |
| PROPOSED | 4 (+25%) | 13 (+7.7%) | 13 | 13 | 13 | 13 |
This proposal improves decentralisation in terms of jurisdiction diversity.
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 | 6 | 2 | 1 | 1 | 1 | 1 |
| PROPOSED | 5 (-16.67%) | 1 (-50%) | 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)
Node Changes
| Action | Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|---|
| Remove |  |
||||||||
| Remove | |
||||||||
| Add | jbgo7 | DOWN | |
Oceania | Australia | Melbourne 2 (mn2) | NEXTDC | Icaria Systems Pty Ltd | l5lhp |
| Add | sjtwn | UNASSIGNED | |
Asia | Korea (the Republic of) | Seoul 1 (sl1) | Megazone Cloud | Neptune Partners | ukji3 |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| tlrvk | UP | |
Europe | Belgium | Brussels (br1) | Digital Realty | Allusion | mjeqs |
| mtca7 | UP | |
Americas | Canada | Toronto (to1) | Cyxtera | Blockchain Development Labs | 6oxlv |
| 45huy | UP | |
Europe | Switzerland | Zurich 2 (zh2) | Everyware | DFINITY Operations SA | y4c7z |
| ctgsx | UP | |
Asia | China | HongKong 1 (hk1) | Unicom | Pindar Technology Limited | vzsx4 |
| s2p3k | UP | |
Asia | Georgia | Tbilisi 1 (tb1) | Cloud9 | George Bassadone | yhfy4 |
| saw4q | UP | |
Asia | Japan | Tokyo 3 (ty3) | Equinix | Starbase | a5glg |
| cvx4p | UP | |
Europe | Lithuania | Vilnius 1 (bt1) | Baltneta | MB Patrankos šūvis | mbnsu |
| vsuqg | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| 6rib4 | UP | |
Asia | Singapore | Singapore 3 (sg3) | Racks Central | OneSixtyTwo Digital Capital | 5mhxl |
| a3biv | UP | |
Europe | Slovenia | Ljubljana (lj1) | Posita.si | Fractal Labs AG | gl27f |
| 3md72 | UP | |
Americas | United States of America (the) | Allentown (aw1) | Tierpoint | Bigger Capital | codio |
You may wish to follow D-QUORUM if you found this analysis helpful.
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.
Additional good neurons to follow:
- D-QUORUM (a highly decentralized neuron that follows neurons that have been elected by the NNS)
- Synapse (currently follows the LORIMER and CodeGov known neurons for Subnet Management, and is a generally well informed known neuron to follow on numerous other topics)
- CodeGov (actively reviews and votes on Subnet Management proposals, and is well informed on numerous other technical topics)
- WaterNeuron (the WaterNeuron DAO frequently discuss proposals like this in order to vote responsibly based on DAO consensus)
Note that this analysis involved data provided by the IC-API, which is not open source. I’m in the process of switching over to more verifiable sources of this sort of information for future proposal reviews. See here for related discussion.