Proposal 134619
TLDR: I’ve voted to reject, because the proposal does not follow procedure. There’s no reference to a public declaration from the node operator, with which to verify their request.
Motivation:
replacing z6jp6 as per user request: Requested by the node operator in order to redeploy all nodes in the DC after 48 months, and switch to a new node operator ID.
1 removed online US node replaced with an unassigned node in the US
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 0 km | 7325.541 km | 16759.085 km |
| PROPOSED | 0 km | 7270.354 km (-0.8%) | 16759.085 km |
This proposal slightly reduces decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical reduction in localised disaster resilience). 
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 5 | 11 | 13 | 13 | 13 | 13 |
| PROPOSED | 5 | 11 | 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 | 7 | 2 | 1 | 1 | 1 | 1 |
| PROPOSED | 7 | 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)
Node Changes
| Action | Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|---|
| Remove |  |
||||||||
| Add | k67we | UNASSIGNED | |
Americas | United States of America (the) | Jacksonville (jv1) | Tierpoint | Rivonia Holdings LLC | wmrev |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| yjbaw | UP | |
Oceania | Australia | Melbourne 2 (mn2) | NEXTDC | Icaria Systems Pty Ltd | l5lhp |
| vdvh4 | UP | |
Europe | Belgium | Brussels (br1) | Digital Realty | Allusion | mjeqs |
| fqczw | UP | |
Europe | Belgium | Seoul 3 (kr1) | KT | Pindar Technology Limited | iubpe |
| gtjga | UP | |
Europe | Switzerland | Geneva (ge1) | HighDC | Archery Blockchain SCSp | yngfj |
| 4bokb | UP | |
Europe | Switzerland | Zurich 2 (zh2) | Everyware | DFINITY Stiftung | xcne4 |
| 5ei6o | UP | |
Asia | China | HongKong 3 (hk3) | hkcolo | Power Meta Corporation | 4lbqo |
| dd3ye | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| 5fpzb | UP | |
Asia | India | New Delhi 1 (nd1) | Marvelous Web3 DC | Marvelous Web3 | ri4lg |
| tkoxk | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| vtbf4 | UP | |
Asia | Singapore | Singapore 2 (sg2) | Telin | OneSixtyTwo Digital Capital | qffmn |
| c6on3 | UP | |
Europe | Slovenia | Ljubljana (lj1) | Posita.si | Fractal Labs AG | gl27f |
| yszpk | UP | |
Africa | South Africa | Gauteng 2 (jb2) | Africa Data Centres | Honeycomb Capital (Pty) Ltd | 3bohy |
*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.