Proposal 134633
TLDR: I’ll adopt. Great proposal. The subnet is currently in violation of the IC Target Topology, and this proposal fixes that. See decentralisation stats below for more info.
2 removed node in Belgium and the US, replaced with a nodes in Canada and Georgia.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 78.457 km | 7565.72 km | 16464.988 km |
| PROPOSED | 78.457 km | 7593.895 km (+0.4%) | 16464.988 km |
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 | 4 | 11 | 13 | 11 | 13 | 13 |
| PROPOSED | 4 | 12 (+8.3%) | 13 | 13 (+15.4%) | 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 | 2 | 1 | 1 |
| PROPOSED | 5 (-16.67%) | 2 | 1 | 1 (-50%) | 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 | h3iv6 | UNASSIGNED | |
Americas | Canada | Vancouver (bc1) | Cyxtera | Blockchain Development Labs | feb2q |
| Add | ami6p | UNASSIGNED | |
Asia | Georgia | Tbilisi 1 (tb1) | Cloud9 | George Bassadone | yhfy4 |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| i4zve | UP | |
Oceania | Australia | Queensland 1 (sc1) | NEXTDC | ANYPOINT PTY LTD | srrm2 |
| 6t3hc | UP | |
Europe | Switzerland | Geneva (ge1) | HighDC | Archery Blockchain SCSp | yngfj |
| zcxej | UP | |
Europe | Switzerland | Zurich 6 (zh6) | Green.ch | Sygnum Bank | ciprs |
| 5az5s | UP | |
Asia | China | HongKong 1 (hk1) | Unicom | Pindar Technology Limited | vzsx4 |
| elons | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| k4ecc | UP | |
Asia | India | Panvel 2 (pl2) | Yotta | Krishna Enterprises | 7rw6b |
| 5hvab | UP | |
Asia | Korea (the Republic of) | Seoul 2 (kr2) | Gasan | Web3game | 5dwhe |
| cupz3 | UP | |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
| g3ug2 | UP | |
Europe | Slovenia | Ljubljana 2 (lj2) | Anonstake | Anonstake | eu5wc |
| kno7y | UP | |
Europe | Sweden | Stockholm 1 (sh1) | Digital Realty | DFINITY Stiftung | lgp6d |
| 5s6r2 | UP | |
Americas | United States of America (the) | Jacksonville (jv1) | Tierpoint | Rivonia Holdings LLC | wmrev |
*This comment references the latest comment in the Subnet Management - General Discussion thread only to generate an automated cross-link from the general thread (to improve topic navigation).
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.