Subnet Management - lhg73 (Application)

What happened to the established workflow, proposer 61?
:point_down:

Proposal: 133320 - ICP Dashboard (internetcomputer.org)

The above proposal doesn’t contain a reference to a forum post where voters can go see critical discussion about the proposal (to inform their vote, or share their insight). There was no forum post to reference, because the proposal wasn’t announced. I don’t think proposals like this are conducive to effective decentralisation, and responsible voting behaviour, so I’ll be rejecting this proposal. I’d be happy to adopt a replacement proposal that follows established procedure.


Proposal 133320

2 removed down/degraded nodes replaced with unassigned node in the US and Switzerland.

Decentralisation Stats

Subnet node distance stats (distance between any 2 nodes in the subnet) →

Smallest Distance Average Distance Largest Distance
EXISTING 317.676 km 8678.125 km 18505.029 km
PROPOSED 300.075 km (-5.5%) 8719.449 km (+0.5%) 18505.029 km

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers
EXISTING 5 13 13 13 13
PROPOSED 5 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
EXISTING 4 1 1 1 1
PROPOSED 4 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
Continent Country Data Center Owner Node Provider Node Status
--- Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG jfryc-owgdd-a7pp4-lao2c-anza2-nryvi-gqkmu-m2moj-4hzai-zfdiy-4qe DOWN
--- Americas United States of America (the) Chicago 3 (ch3) CyrusOne MI Servers cilsw-jxcbi-qvp5o-7cylv-up5nj-2yykt-jtzha-s2uao-ee7uy-nprfm-vae DEGRADED
+++ Europe Switzerland Zurich 7 (zh7) Green.ch Sygnum Bank 7jjmd-p43kv-2h3bp-yrcuv-gc3ia-zaess-2rj6p-p4xgr-f43xy-6hk55-xqe UNASSIGNED
+++ Americas United States of America (the) Tampa (tp1) Flexential Mika Properties, LLC ffsue-5rmb7-frfqk-gvfpg-gu2bo-udoa3-zputb-kexzk-gd667-fit5k-rae UNASSIGNED
Oceania Australia Queensland 1 (sc1) NEXTDC ANYPOINT PTY LTD 56ovz-lrvyd-gggsl-qtenl-uuokx-p7t3t-rg6mc-6lc5l-usfqb-fygiv-aqe UP
Europe Belgium Antwerp (an1) Datacenter United Allusion mihvd-umv3j-cjsl2-bfsdu-td7aw-2y6if-aw4fn-cghkm-v2oxd-kj75q-cae UP
Americas Canada Vancouver (bc1) Cyxtera Blockchain Development Labs ddbl6-37efl-b75e4-jpfsb-zioa6-ilvzo-tldwy-fnbhm-nbuoy-66cza-uqe UP
Americas Costa Rica Bogota 1 (bg1) EdgeUno Geeta Kalwani ihttm-45oz5-an5mg-i2jtb-fayst-s47j6-vmuwr-fqotf-mp2il-n5s5x-cae UP
Europe Germany Marseille (mr1) Digital Realty DFINITY Operations SA rsp26-d2hko-kvacs-6mdca-dumka-qxiyw-4yzkp-cuwgr-lj7je-v7e6z-4qe UP
Europe Estonia Tallinn 2 (ta2) Telia DC Vladyslav Popov bptaj-nejw4-osqqa-zwrej-ysl2o-5ffgj-hkjr6-2w6fi-jczex-vjutw-iae UP
Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone ognrk-q4exl-3wf25-yrrsy-mtezk-e3qww-k6s5v-2pikz-gto6z-dyl2y-eae UP
Asia India Navi Mumbai 1 (nm1) Rivram Rivram Inc pdo46-iehoo-x2gfu-t5qu5-y3e64-cdymo-eioop-h6f4a-zebwa-fenb4-xae UP
Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ixo23-jxvux-ktqca-bje7d-py56s-yvjy5-zpxrk-fmlxt-zhuhg-wu5bc-wqe UP
Asia Singapore Singapore 2 (sg2) Telin OneSixtyTwo Digital Capital cpywp-n4j5f-ja44p-oykxm-umz7h-fk6v2-rowix-bkwc4-ly4fw-tvu6c-mae UP
Africa South Africa Gauteng 2 (jb2) Africa Data Centres Honeycomb Capital (Pty) Ltd 5v4on-bsceg-rdgxe-zcqqf-l5wnq-fpxw7-x3ktj-3x4fs-o2cny-uzhor-vqe UP

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:

  • 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)

  • 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)

1 Like