Subnet Management - o3ow2 (Application)

Thanks @SvenF, this sounds good. I’ve voted to reject in this case (given that there’s no reference to this evidence). I’m very happy that this will be included in future proposals though.

1 Like

Voted to adopt proposal 134404.

This proposal replaces node 5resh which appears in the dashboard as “Status: Active”, for the purpose of making it available to other subnets in order to improve overall network topology. As shown in the proposal, decentralisation parameters are unchanged and remain within the requirements of the target topology.

Proposal 134404

Vote: REJECT

I have raised question regarding this kind of proposals previously and adopted them firstly expecting better explanation in the future as can be seen in this two reviews, 134191 and 134192. @SvenF

I’ve vote to adopt proposal 134404. The decentralisation coefficients were unchanged by the proposal. As can be observed using the IC-API, the 5p6xp node operator has 4 nodes (as stated in the proposal summary). Now that this proposal has executed, one of those nodes is unassigned (5resh).

Note that the IC-API is not open source. Since learning this, I’m in the process of switching over verifiable sources of this sort of information (rejecting because I’ve not had time to do this yet would be too harsh - even for me :wink:).

A new proposal with id 134554 has been submitted, please take a look.

Click here to open proposal details

Replace nodes in subnet o3ow2

Motivation:
The following nodes in subnet o3ow2 have been cordoned and need to be removed from the subnet:

Decentralization Nakamoto coefficient changes for subnet o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae:

    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)

Mean Nakamoto comparison: 5.00 → 5.00 (+0%)

Overall replacement impact: equal decentralization across all features

Details

Nodes removed:

  • gn3jh-ppjoz-hdh3g-3dckg-zdgk2-qspnh-5i7p6-dfcq3-ke6vc-n5l7d-sqe [health: healthy]
  • kby7l-tpmyp-ntea5-g4kn2-gkwrc-fbjbo-6pjgz-gaoz7-owtct-welil-pae [health: healthy]

Nodes added:

  • 5jbfj-wygyf-jzcjw-s6ali-nlazr-nbejd-sfw6h-v44fg-hh34c-khde2-lqe [health: healthy]
  • incp3-oydir-onuos-fifuz-6n4c4-4aawc-gxmxz-v4juj-xzupz-h22aj-aae [health: healthy]
    node_provider                                                              data_center            data_center_owner              area                                  country        
    -------------                                                              -----------            -----------------              ----                                  -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    an1          1 -> 0    Africa Data Centres       1    Flanders                    1 -> 0    AU            1
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    ch2               1    Cloud9                    1    Gauteng                          1    BE       1 -> 0
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  0 -> 1    hk3               1    Cyxtera                   1    HongKong                         1    CA            1
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe       1    jb2               1    Datacenter United    1 -> 0    Illinois                         1    CH            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    mb1               1    Digital Realty            1    Maribor                          1    FR       1 -> 0
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    mn2               1    Equinix                   1    Melbourne                        1    GE            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mr1          1 -> 0    Green.ch                  1    Navi Mumbai                      1    HK            1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    nm1               1    Megazone Cloud            1    Ontario                          1    IN            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae  1 -> 0    sg1          0 -> 1    NEXTDC                    1    Provence-Alpes-Cote d'Azur  1 -> 0    JP            1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sh1          0 -> 1    Posita.si                 1    Seoul                            1    KR            1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    sl1               1    Rivram                    1    Singapore                   0 -> 1    SE       0 -> 1
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    tb1               1    Telin                0 -> 1    Stockholm                   0 -> 1    SG       0 -> 1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    to2               1    Tierpoint                 1    Tbilisi                          1    SI            1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    ty1               1    hkcolo                    1    Tokyo                            1    US            1
                                                                               zh6               1                                   Zurich                           1    ZA            1
1 Like

Proposal 134554

TLDR: I’ll adopt. The proposal links directly to what appears to be discussion with the NP about the proposal. Decentralisation stats look acceptable (number of nodes in the same continent increases, but this isn’t a formal part of the IC Target Topology).

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 300.075 km 8092.598 km 16759.085 km
PROPOSED 504.693 km (+68.2%) 8339.341 km (+3%) 16605.64 km (-0.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). :+1:

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 5 13 13 13 13 13
PROPOSED 5 13 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 5 1 1 1 1 1
PROPOSED 6 (+20%) 1 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 kby7l UP :bar_chart: Europe Belgium Antwerp (an1) Datacenter United Allusion pgunx
Remove gn3jh UP :bar_chart: Europe Germany Marseille (mr1) Digital Realty DFINITY Stiftung ampm3
Add incp3 UNASSIGNED :bar_chart: Asia Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital d4bin
Add 5jbfj UNASSIGNED :bar_chart: Europe Sweden Stockholm 1 (sh1) Digital Realty DFINITY Stiftung lgp6d
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
23jbm UP :bar_chart: Oceania Australia Melbourne 2 (mn2) NEXTDC Icaria Systems Pty Ltd l5lhp
d4ndk UP :bar_chart: Americas Canada Toronto 2 (to2) Cyxtera Blockchain Development Labs 4lp6i
h3g2z UP :bar_chart: Europe Switzerland Zurich 6 (zh6) Green.ch Sygnum Bank ciprs
za7cm UP :bar_chart: Asia China HongKong 3 (hk3) hkcolo Power Meta Corporation 4lbqo
l7nbu UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
h3gd6 UP :bar_chart: Asia India Navi Mumbai 1 (nm1) Rivram Rivram Inc mpmyf
rv6cf UP :bar_chart: Asia Japan Tokyo (ty1) Equinix Starbase cqjev
sqw45 UP :bar_chart: Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3
nlghu UP :bar_chart: Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew
pgim3 UP :bar_chart: Americas United States of America (the) Chicago 2 (ch2) Tierpoint Rivonia Holdings LLC vkwql
hdkxy UP :bar_chart: 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.

Voted to adopt proposal #134554.

The proposal replaces two cordoned healthy Active status node gn3jh from the MR1 Data Center in France, and cordoned healthy Active status node kby7l from the AN1 Data Center in Antwerp, with unassigned healthy Awaiting status node 5jbfj from Sweden and with unassigned healthy Awaiting status node incp3 from Singapore, without any change to the decentralization of the subnet.
The motivation makes sense and the provided Forum link included in the summary provides further info, also it can be checked here.

A new proposal with id 134572 has been submitted, please take a look.

Click here to open proposal details

Replace a node in subnet o3ow2

Motivation:
The following nodes in subnet o3ow2 have been cordoned and need to be removed from the subnet:

Decentralization Nakamoto coefficient changes for subnet o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae:

    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)

Mean Nakamoto comparison: 5.00 → 5.00 (+0%)

Overall replacement impact: equal decentralization across all features

Details

Nodes removed:

  • pgim3-5bk4s-y4auc-ocnuj-gdsqb-iv2yk-qi4t7-75bpp-kbz2r-bdtuq-4qe [health: healthy]

Nodes added:

  • agtd6-f2qxq-ciadf-bterj-vpcos-7fapt-co3cv-ypvhs-zy6mk-ijrto-uae [health: healthy]
    node_provider                                                              data_center            data_center_owner              area                   country   
    -------------                                                              -----------            -----------------              ----                   -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    ch2          1 -> 0    Africa Data Centres       1    Arizona      0 -> 1    AU       1
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    hk3               1    Cloud9                    1    Gauteng           1    CA       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    jb2               1    CyrusOne             0 -> 1    HongKong          1    CH       1
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe       1    mb1               1    Cyxtera                   1    Illinois     1 -> 0    GE       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    mn2               1    Digital Realty            1    Maribor           1    HK       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    nm1               1    Equinix                   1    Melbourne         1    IN       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    ph1          0 -> 1    Green.ch                  1    Navi Mumbai       1    JP       1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  0 -> 1    sg1               1    Megazone Cloud            1    Ontario           1    KR       1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    sh1               1    NEXTDC                    1    Seoul             1    SE       1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sl1               1    Posita.si                 1    Singapore         1    SG       1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe  1 -> 0    tb1               1    Rivram                    1    Stockholm         1    SI       1
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    to2               1    Telin                     1    Tbilisi           1    US       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty1               1    Tierpoint            1 -> 0    Tokyo             1    ZA       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zh6               1    hkcolo                    1    Zurich            1              

Voted to adopt proposal 134554.

This proposal replaces 2 nodes, due to offboarding MR1 and AN1 data centres. Decentralisation parameters are unchanged and remain within the requirements of the target topology. Data centre details are consistent with the links provided in the proposal, although the linked post for data centre MR1 should ideally include further detail to specify exactly which data centres are being affected.

Proposal 134554

Vote: ADOPT

Replaces cordoned nodes gn3jh and kby7l with nodes 5jbfj and incp3 on subnet o3ow2.
The reason for this proposal is to offboard MR1 and AN1 DCs consistent with forum posts made on the forum thread used for posts regarding the renovation/sell of Gen-1 node machines by NPs.
Both the NP and DC stated in the forum post match the ones from the node being removed in the proposal.

Voted to reject proposal 134572 as this is part of a large batch of non-critical proposals timed such that the voting period clashes with national holidays, thereby allowing insufficient time for an appropriately detailed review to take place.

1 Like

Rejected proposal 134572. There’s no time to review this and the 18 other proposals in the same batch properly over Xmas eve, Xmas and Boxing Day. This is a non-critical proposal.

More information and discussion on this thread.

Proposal 134572

Vote: ADOPT

Replaces cordoned node pgim3 with node agtd6 on subnet o3ow2.
The reason for this proposal is to offboard CH2 DC consistent with forum posts made on the forum thread used for posts regarding the renovation/sell of Gen-1 node machines by NPs.
Both the NP and DC stated in the forum post match the ones from the node being removed in the proposal.

1 Like

Voted to adopt proposal #134572.

The proposal replaces cordoned healthy Active status node pgim3 from the CH2 Data Center in Illinois, with unassigned healthy Awaiting status node agtd6 from Arizona, without any change to the decentralization of the subnet.
The motivation makes sense and the provided Forum link included in the summary provides further info, also it can be checked here.

:point_up: There’s an open proposal to make o3ow2 a public subnet.