Subnet Management - qxesv (Application)

Not to worry then, and thanks for clearing that up! I figured something like that might have happened, but wanted to make sure that there wasn’t an undiscovered glitch or anything that I needed to be concerned about. :slight_smile:

1 Like

A new proposal with id 134536 has been submitted for this subnet.

Click here to open proposal details

Replace a node in subnet qxesv

Motivation:

  • replacing dead node sbiuh-cg2ut-pmrik-jit6d-t5szz-4fp7i-pqodm-llgxp-ooht3-d3txm-bqe

Calculated potential impact on subnet decentralization if replacing:

  • 1 additional node would result in: equal decentralization across all features

Based on the calculated potential impact, not replacing additional nodes to improve optimization.

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is an explaination of how decentralization is currently calculated,
and there are also instructions for performing what-if analysis if you are wondering if another node would have improved decentralization more.

Decentralization Nakamoto coefficient changes for subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:

    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:

  • sbiuh-cg2ut-pmrik-jit6d-t5szz-4fp7i-pqodm-llgxp-ooht3-d3txm-bqe [health: dead]

Nodes added:

  • lyhuu-ljnh7-ba3zz-g5ftu-xepo5-a3bqy-sggtx-6wgu2-5sw77-cxnfk-iae [health: healthy]
    node_provider                                                              data_center            data_center_owner            area                        country        
    -------------                                                              -----------            -----------------            ----                        -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    aw1               1    Cloud9                  1    Brussels Capital       1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br1               1    Cyxtera                 1    Bucuresti              1    CA            1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       1    bu1               1    Digital Realty          1    HongKong          0 -> 1    CH            1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe       1    cr1               1    Dotsi                   1    Lisbon                 1    CR            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    hk1          0 -> 1    Equinix                 1    Ljubljana         1 -> 0    GE            1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    li1               1    Everyware               1    New Delhi              1    HK       0 -> 1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    lj1          1 -> 0    M247                    1    Ontario                1    IN            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    nd1               1    Marvelous Web3 DC       1    Pennsylvania           1    JP            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    sg2               1    Megazone Cloud          1    San Jose               1    KR            1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  0 -> 1    sl1               1    Navegalo                1    Seoul                  1    PT            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    tb1               1    Posita.si          1 -> 0    Singapore              1    RO            1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    to1               1    Telin                   1    Tbilisi                1    SG            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty2               1    Tierpoint               1    Tokyo                  1    SI       1 -> 0
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1 -> 0    zh2               1    Unicom             0 -> 1    Zurich                 1    US            1

Proposal 134536

TLDR: I’ll adopt. A DOWN node replaced with an UP node. This results in more nodes within the same continent, but that’s not a part of the formal IC Target Topology.

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 477.324 km 7270.059 km 18505.029 km
PROPOSED 493.808 km (+3.5%) 7703.353 km (+6%) 18505.029 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). :+1:

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 3 13 13 13 13 13
PROPOSED 3 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 sbiuh DOWN :bar_chart: Europe Slovenia Ljubljana (lj1) Posita.si Fractal Labs AG gl27f
Add lyhuu UNASSIGNED :bar_chart: Asia China HongKong 1 (hk1) Unicom Pindar Technology Limited vzsx4
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
ctwsk UP :bar_chart: Europe Belgium Brussels (br1) Digital Realty Allusion mjeqs
5v6bx UP :bar_chart: Americas Canada Toronto (to1) Cyxtera Blockchain Development Labs 6oxlv
uk6n5 UP :bar_chart: Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Stiftung vqe65
fvy7i UP :bar_chart: Americas Costa Rica San José 1 (cr1) Navegalo GeoNodes LLC eqv2i
sspbf UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
cxuqe UP :bar_chart: Asia India New Delhi 1 (nd1) Marvelous Web3 DC Marvelous Web3 ri4lg
kzlfn UP :bar_chart: Asia Japan Tokyo 2 (ty2) Equinix Starbase dpt4y
pmlsj UP :bar_chart: Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3
j7mu5 UP :bar_chart: Europe Portugal Lisbon 1 (li1) Dotsi Ivanov Oleksandr bnfpu
ys5ct UP :bar_chart: Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg
ii5t4 UP :bar_chart: Asia Singapore Singapore 2 (sg2) Telin OneSixtyTwo Digital Capital qffmn
w5nh3 UP :bar_chart: Americas United States of America (the) Allentown (aw1) Tierpoint Bigger Capital codio

*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 #134536.

The proposal replaces dead Offline status node sbiuh from Slovenia, with unassigned healthy Awaiting status node lyhuu from Hong Kong, without any change to the decentralization of the subnet.

1 Like

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

Click here to open proposal details

Replace nodes in subnet qxesv

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

Decentralization Nakamoto coefficient changes for subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:

    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:

  • 5v6bx-3443d-zvacu-gas5w-uopbm-yxnob-i6rsh-rlxqh-hna7u-sy2aj-yae [health: healthy]
  • kzlfn-xeqoz-zcrlc-no4r5-pfjdw-flzfm-cq7zw-bbipw-fw3u7-bsoa6-4qe [health: healthy]

Nodes added:

  • x3rso-73u7b-3pyeo-3fmcu-g635n-ri47m-jv3kg-zjfub-aqxsb-tnxbq-nqe [health: healthy]
  • xzec6-ujfic-zvupf-3cgro-tqgtp-xi5ss-vtxfz-ycecq-n6jsb-t37nk-vqe [health: healthy]
    node_provider                                                              data_center            data_center_owner            area                        country        
    -------------                                                              -----------            -----------------            ----                        -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    aw1               1    Cloud9                  1    Brussels Capital       1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br1               1    Cyxtera            1 -> 0    Bucuresti              1    CA       1 -> 0
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       1    bu1               1    Digital Realty          1    Hesse             0 -> 1    CH            1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe       1    cr1               1    Dotsi                   1    HongKong               1    CR            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae  1 -> 0    fr2          0 -> 1    Equinix                 1    Lisbon                 1    DE       0 -> 1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    hk1               1    Everyware               1    Maribor           0 -> 1    GE            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    li1               1    M247                    1    New Delhi              1    HK            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    mb1          0 -> 1    Marvelous Web3 DC       1    Ontario           1 -> 0    IN            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    nd1               1    Megazone Cloud          1    Pennsylvania           1    JP       1 -> 0
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    sg2               1    Navegalo                1    San Jose               1    KR            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sl1               1    Posita.si          0 -> 1    Seoul                  1    PT            1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae  1 -> 0    tb1               1    Telin                   1    Singapore              1    RO            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    to1          1 -> 0    Tierpoint               1    Tbilisi                1    SG            1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  0 -> 1    ty2          1 -> 0    Unicom                  1    Tokyo             1 -> 0    SI       0 -> 1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae  0 -> 1    zh2               1                                 Zurich                 1    US            1

Voted to adopt proposal 134536.

This proposal replaces 1 dead node. As shown in the proposal, decentralisation parameters are unchanged and remain within the requirements of the target topology.

1 Like

Proposal 134536

Vote: ADOPT

The proposal replaces a dead node on subnet qxesv:
Removed node: dead node sbiuh, status Degraded.
Added node: node lyhuu.

There was no impact on the decentralization coefficients.

1 Like

Voted to reject proposal 134576 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.

2 Likes

Rejected proposal 134576. 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 134576

Vote: ADOPT

Replaces cordoned nodes 5v6bx and kzlfn with nodes x3rso and xzec6 on subnet qxesv.
The reason for this proposal is to offboard TO1 and TY2 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 and forum post match the ones from the node being removed in the proposal.

1 Like

Voted to adopt proposal #134576.

The proposal replaces two cordoned nodes, one healthy Active status node 5v6bx from the TO1 Data Center in Toronto, and cordoned healthy Active status node kzlfn from the TY2 Data Center in Tokyo, with unassigned healthy Awaiting status node x3rso from Germany and with unassigned healthy Awaiting status node xzec6 from Slovenia, 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.

1 Like

Replace a node in subnet qxesv

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

Decentralization Nakamoto coefficient changes for subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:

    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:

  • xzec6-ujfic-zvupf-3cgro-tqgtp-xi5ss-vtxfz-ycecq-n6jsb-t37nk-vqe [health: healthy]

Nodes added:

  • zatyv-4l26n-3lecc-xpeme-ul34o-yiye2-3d447-aiiz4-5pxtm-v44nh-cqe [health: healthy]
    node_provider                                                         data_center       data_center_owner       area                   country   
    -------------                                                         -----------       -----------------       ----                   -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  1    aw1          1    Cloud9             1    Brussels Capital  1    BE       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  1    br1          1    Digital Realty     1    Bucuresti         1    CH       1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe  1    bu1          1    Dotsi              1    Hesse             1    CR       1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe  1    cr1          1    Equinix            1    HongKong          1    DE       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe  1    fr2          1    Everyware          1    Lisbon            1    GE       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe  1    hk1          1    M247               1    Maribor           1    HK       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae  1    li1          1    Marvelous Web3 DC  1    New Delhi         1    IN       1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae  1    mb1          1    Megazone Cloud     1    Pennsylvania      1    KR       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  1    nd1          1    Navegalo           1    San Jose          1    PT       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae  1    sg2          1    Posita.si          1    Seoul             1    RO       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  1    sl1          1    Telin              1    Singapore         1    SG       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1    tb1          1    Tierpoint          1    Tbilisi           1    SI       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae  1    zh2          1    Unicom             1    Zurich            1    US       1
1 Like

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

Click here to open proposal details

Replace a node in subnet qxesv

Motivation:

Calculated potential impact on subnet decentralization if replacing:

  • 1 additional node would result in: equal decentralization across all features

Based on the calculated potential impact, not replacing additional nodes to improve optimization.

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is an explaination of how decentralization is currently calculated,
and there are also instructions for performing what-if analysis if you are wondering if another node would have improved decentralization more.

Decentralization Nakamoto coefficient changes for subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:

    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:

  • xzec6-ujfic-zvupf-3cgro-tqgtp-xi5ss-vtxfz-ycecq-n6jsb-t37nk-vqe [health: healthy]

Nodes added:

  • 7tayv-2pmqc-gaiwu-3kd3h-fh4qh-3moqd-aawsb-4rq6o-ui7fp-dofcu-iqe [health: healthy]
    node_provider                                                         data_center       data_center_owner       area                   country   
    -------------                                                         -----------       -----------------       ----                   -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  1    aw1          1    Cloud9             1    Brussels Capital  1    BE       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  1    br1          1    Digital Realty     1    Bucuresti         1    CH       1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe  1    bu1          1    Dotsi              1    Hesse             1    CR       1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe  1    cr1          1    Equinix            1    HongKong          1    DE       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe  1    fr2          1    Everyware          1    Lisbon            1    GE       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe  1    hk1          1    M247               1    Maribor           1    HK       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae  1    li1          1    Marvelous Web3 DC  1    New Delhi         1    IN       1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae  1    mb1          1    Megazone Cloud     1    Pennsylvania      1    KR       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  1    nd1          1    Navegalo           1    San Jose          1    PT       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae  1    sg2          1    Posita.si          1    Seoul             1    RO       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  1    sl1          1    Telin              1    Singapore         1    SG       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1    tb1          1    Tierpoint          1    Tbilisi           1    SI       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae  1    zh2          1    Unicom             1    Zurich            1    US       1
2 Likes

Proposal 134985 | Tim - CodeGov

Vote: Adopt

This proposal replaces node xzec6 which appears in the dashboard as “Status: Active” for the stated reason “offboarding the second rack of nodes in the mb1 DC after 48 months”. As shown in the proposal, decentralisation parameters are unchanged and remain within the requirements of the target topology.

About CodeGov…

CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these topics and Synapse on most other topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron and KongSwap with a known neuron and credible Followees.

Learn more about CodeGov and its mission at codegov.org.

1 Like

Proposal 134985 Review | LORIMER Known Neuron

VOTE: YES

TLDR: Decentralisation stats are unchanged and there is a clear public declaration for the cordoned node which is referred to in the proposal summary. 1 cordoned node replaced with another node belonging to the same NP at the same data centre.

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 305.949 km 6739.351 km 18504.433 km
PROPOSED 305.949 km 6739.351 km 18504.433 km

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 3 13 13 13 13 13
PROPOSED 3 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 6 1 1 1 1 1
PROPOSED 6 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 xzec6 UP :bar_chart: Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew
Add 7tayv UNASSIGNED :bar_chart: Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
ctwsk UP :bar_chart: Europe Belgium Brussels (br1) Digital Realty Allusion mjeqs
uk6n5 UP :bar_chart: Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Stiftung vqe65
fvy7i UP :bar_chart: North America Costa Rica San José 1 (cr1) Navegalo GeoNodes LLC eqv2i
x3rso UP :bar_chart: Europe Germany Frankfurt 2 (fr2) Equinix Virtual Hive Ltd 3nu7r
sspbf UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
lyhuu UP :bar_chart: Asia Hong Kong HongKong 1 (hk1) Unicom Pindar Technology Limited vzsx4
cxuqe UP :bar_chart: Asia India New Delhi 1 (nd1) Marvelous Web3 DC Marvelous Web3 ri4lg
pmlsj UP :bar_chart: Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3
j7mu5 UP :bar_chart: Europe Portugal Lisbon 1 (li1) Dotsi Ivanov Oleksandr bnfpu
ys5ct UP :bar_chart: Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg
ii5t4 UP :bar_chart: Asia Singapore Singapore 2 (sg2) Telin OneSixtyTwo Digital Capital qffmn
w5nh3 UP :bar_chart: North America United States of America (the) Allentown (aw1) Tierpoint Bigger Capital codio

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

Proposal #134985 — Zack | CodeGov

Vote: Adopted
Reason:
The proposal replaces cordoned healthy Active status node xzec6 in the MB1 DC from Slovenia, with unassigned healthy Awaiting status node 7tayv from same DC and NP without any chnge to decentralization.
Motivation is offboarding the second rack of nodes in the MB1 DC after 48 months, in line with the forum post.

About CodeGov (click to expand).

CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these topics and Synapse on most other topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron and KongSwap with a known neuron and credible Followees.


Learn more about CodeGov and its mission at codegov.org.

1 Like

Proposal 134985 – LaCosta | CodeGov

Vote: ADOPT

Replaces cordoned node xzec6 with node 7tayv on subnet qxesv.
The reason for this proposal is to offboard the second rack of nodes from the MB1 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.

About CodeGov…

CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these topics and Synapse on most other topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron and KongSwap with a known neuron and credible Followees.

Learn more about CodeGov and its mission at codegov.org.

1 Like

A new proposal with ID 135304 has been submitted, please take a look.

Click here to open proposal details

Replace a node in subnet qxesv

Motivation:

  • replacing dead node uk6n5

Calculated potential impact on subnet decentralization if replacing:

  • 1 additional node would result in: equal decentralization across all features

Based on the calculated potential impact, not replacing additional nodes to improve optimization.

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is an explaination of how decentralization is currently calculated,
and there are also instructions for performing what-if analysis if you are wondering if another node would have improved decentralization more.

Decentralization Nakamoto coefficient changes for subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:

    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

Impact on business rules penalties: 1000 → 0

Details

Nodes removed:

  • uk6n5-nw7vs-zeydi-qdmgp-xbevs-fnhce-35je2-3m5fu-l2wzj-wrcxb-5ae [health: dead]

Nodes added:

  • 6qxes-2iftw-fq3we-unkdt-y7wnk-4v26t-fftzu-chgeh-t2ljb-qtevx-iae [health: healthy]
    node_provider                                                         data_center       data_center_owner       area                   country   
    -------------                                                         -----------       -----------------       ----                   -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  1    aw1          1    Cloud9             1    Brussels Capital  1    BE       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  1    br1          1    Digital Realty     1    Bucuresti         1    CH       1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe  1    bu1          1    Dotsi              1    Hesse             1    CR       1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe  1    cr1          1    Equinix            1    HongKong          1    DE       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe  1    fr2          1    Everyware          1    Lisbon            1    GE       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe  1    hk1          1    M247               1    Maribor           1    HK       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae  1    li1          1    Marvelous Web3 DC  1    New Delhi         1    IN       1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae  1    mb1          1    Megazone Cloud     1    Pennsylvania      1    KR       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  1    nd1          1    Navegalo           1    San Jose          1    PT       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae  1    sg2          1    Posita.si          1    Seoul             1    RO       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  1    sl1          1    Telin              1    Singapore         1    SG       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1    tb1          1    Tierpoint          1    Tbilisi           1    SI       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae  1    zh2          1    Unicom             1    Zurich            1    US       1

Business rules check results before the membership change:

  • Subnet should have 1 DFINITY-owned node(s) for subnet recovery, got 0
1 Like

Proposal 135304 Review | LORIMER - CO.DELTA △

VOTE: YES

TLDR: Replaces an offline node with an unassigned node, at the same data center and NP. This is the DFINITY-owned node of this subnet, so it’s important that it’s replaced with another node owned by DFINITY (making disaster recovery smoother).

Decentralisation Stats remain unchanged :+1:

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 305.949 km 6739.351 km 18504.433 km
PROPOSED 305.949 km 6739.351 km 18504.433 km

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 3 13 13 13 13 13
PROPOSED 3 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 6 1 1 1 1 1
PROPOSED 6 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 uk6n5 DOWN :bar_chart: Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Stiftung vqe65
Add 6qxes UNASSIGNED :bar_chart: Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Stiftung pi3wm
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
ctwsk UP :bar_chart: Europe Belgium Brussels (br1) Digital Realty Allusion mjeqs
fvy7i UP :bar_chart: North America Costa Rica San José 1 (cr1) Navegalo GeoNodes LLC eqv2i
x3rso UP :bar_chart: Europe Germany Frankfurt 2 (fr2) Equinix Virtual Hive Ltd 3nu7r
sspbf UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
lyhuu UP :bar_chart: Asia Hong Kong HongKong 1 (hk1) Unicom Pindar Technology Limited vzsx4
cxuqe UP :bar_chart: Asia India New Delhi 1 (nd1) Marvelous Web3 DC Marvelous Web3 ri4lg
pmlsj UP :bar_chart: Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3
j7mu5 UP :bar_chart: Europe Portugal Lisbon 1 (li1) Dotsi Ivanov Oleksandr bnfpu
ys5ct UP :bar_chart: Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg
ii5t4 UP :bar_chart: Asia Singapore Singapore 2 (sg2) Telin OneSixtyTwo Digital Capital qffmn
7tayv UP :bar_chart: Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew
w5nh3 DOWN :bar_chart: North America United States of America (the) Allentown (aw1) Tierpoint Bigger Capital codio


You may wish to follow the CO.DELTA known neuron (coming soon) if you found this analysis helpful.

CO.DELTA △

We’re a verifiably decentralised collective who review IC deltas (changes applied by NNS proposals). We follow a common code:

  • Look: We observe the details and context of NNS proposals
  • Test: We test and verify the claims made by those proposals
  • Automate: We automate as much as possible by building increasingly sophisticated tools that streamline and strengthen the reviewal process.

Every vote cast by CO.DELTA is the result of consensus among diligent, skilled and experienced team members acting independently. The CO.DELTA neuron follows the vote of D-QUORUM on NNS topics that the CO.DELTA team does not handle directly. You can therefore follow CO.DELTA on all topics and rely on the highest quality of vote.


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.

1 Like

Proposal 135304 | Tim - CodeGov

Vote: Adopt

This proposal replaces node uk6n5 which appears in the dashboard as “Status: Offline”. As shown in the proposal, decentralisation parameters are unchanged with respect to country and remain within the requirements of the target topology.

About CodeGov

CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons’ Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.

Learn more about CodeGov and its mission at codegov.org.

1 Like