Subnet Management - mpubz (Application)

Proposal 132181

TLDR: I’ve voted to adopt this proposal.

  • One degraded node replaced with an up node :+1:
  • One node that’s currently contributing to the violation of the data center nakamoto coefficient replaced with a diversified node👍
Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 3.534 km 6951.098 km 15939.448 km
PROPOSED 3.534 km 7783.34 km (+12%) 16347.516 km (+2.6%)

This proposal increases decentralisation in terms of geographic distance (and therefore there’s a potential increase in localised disaster resilience). :+1:

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers
EXISTING 3 9 13 12 13
PROPOSED 4 (+25%) 10 (+10%) 13 13 (+7.7%) 13

This proposal improves decentralisation in terms of jurisdiction and data center ownership diversity. Note that this subnet is currently violating the IC target topology regarding the data center nakamoto coefficient, and this proposal brings it back into the acceptable limits. :+1:

Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →

Continent Country Data Center Owner Node Provider
EXISTING 6 4 1 2 1
PROPOSED 6 3 (-25%) 1 1 (-50%) 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
--- Asia Singapore Singapore 2 (sg2) Telin OneSixtyTwo Digital Capital i5xgw-uzqkn-xrfkd-7nqdz-3yvas-lujhr-mvs5w-sxv5u-m7zrn-hrd2k-pqe DEGRADED
--- Americas United States of America (the) San Jose (sj2) Digital Realty BlockTech Ventures, LLC epwlh-zpyza-66uqs-7zrr5-hvtpz-srxfs-acqqj-or2oy-zvky3-3eo2q-6ae UP
+++ Oceania Australia New South Wales 1 (ns1) Latitude.sh Conic Ventures j3pcf-ielts-wwr24-73hhq-flvsq-d7yh3-ly5li-r6csx-5tczk-wkpc3-5ae UNASSIGNED
+++ Asia Singapore Singapore 3 (sg3) Racks Central OneSixtyTwo Digital Capital rgacz-r4m53-3mwgy-63dqd-txx4i-o6aw6-5wwdt-eizs3-6lh2z-hxzlv-3ae UNASSIGNED
Europe Belgium Brussels 2 (br2) AtlasEdge Allusion rhy7d-pjsmu-5ljz7-vuaio-ihiaq-iysyk-np226-tirem-kuw7n-v2i2w-iqe UP
Europe Switzerland Geneva (ge1) HighDC Archery Blockchain SCSp ag3bm-tdrfp-kki7m-yfwop-aoc4g-f4sjz-grd33-7zy3x-xq3tr-hpbuh-zqe UP
Europe Switzerland Zurich 4 (zh4) Nine.Ch Tomahawk.vc d2ffc-r2mqq-yx3u5-f5j47-davp4-lske5-57oal-ilwph-o2hex-tqaz2-7qe UP
Asia Japan Tokyo 2 (ty2) Equinix Starbase cwb7w-kd3lm-4jzgx-mljqg-ptquz-665kh-w2svb-22eca-fab6l-jelhv-3ae UP
Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners kegk5-wu5c5-xpe2p-athmd-4dzq6-4gucp-n4ne3-uj2zk-e2jjl-3253l-6qe UP
Europe Romania Bucharest (bu1) M247 Iancu Aurel b3knf-xg5xg-p3oyq-dgpdw-xjz2l-n35mj-pdoyl-4dgas-u2t5l-bndrp-hqe UP
Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG yttmc-lxazf-6ctyr-aqchl-g5est-gut4i-qltuy-gds2b-7vhfu-43xey-2qe UP
Europe Sweden Stockholm 1 (sh1) Digital Realty DFINITY Operations SA 4xhpj-gsmak-akpfh-z7rro-63yfp-5ewvu-i4o6g-yyrix-yd7xj-cus4y-hqe UP
Americas United States of America (the) Allentown (aw1) Tierpoint Bigger Capital g4eis-jmdlu-iiivf-75n73-uto6l-miezg-kluob-ogj6z-2llqc-pomjl-jae UP
Americas United States of America (the) Chicago 3 (ch3) CyrusOne MI Servers dafyf-uvzhi-ypecj-c6ujq-e7aae-m6y2m-5f4pp-v64pz-lfebd-awmre-cqe UP
Americas United States of America (the) Tampa (tp1) Flexential Giant Leaf, LLC ey524-belml-leby7-hvt63-znr5b-xwkgp-5epra-kdmez-ynelx-2m4ys-hqe 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:

  • CodeGov (will soon be committed to actively reviewing and voting on Subnet Management proposals based on those reviews)

  • WaterNeuron (the WaterNeuron DAO frequently discuss proposals like this in order to vote responsibly based on DAO consensus)

1 Like