Subnet Management - nl6hn (Application)

Voted to adopt proposal 134553.

This proposal replaces 2 nodes, due to offboarding TO1 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.

1 Like

Proposal 134553

Vote: ADOPT

Replaces cordoned nodes 5d6pj and 77fe5 with nodes zxph7 and zk4lm on subnet nl6hn.
The reason for this proposal is to offboard TO1 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.

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

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

Click here to open proposal details

Replace a node in subnet nl6hn

Motivation:

  • replacing dead node u7niu

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 nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe:

    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:

  • u7niu-lhdw7-x2lje-t4vif-jan6i-wzanp-twrqw-sv3so-ft3x5-iqmnv-kqe [health: dead]

Nodes added:

  • k2dew-yan2e-q6mzr-flizg-jqndd-3zcln-zg35a-ejv2j-waiff-le2rt-6qe [health: healthy]
    node_provider                                                              data_center            data_center_owner            area                        country   
    -------------                                                              -----------            -----------------            ----                        -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    br2               1    AtlasEdge               1    Brussels Capital       1    AU       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    dl1          0 -> 1    Cloud9                  1    Florida           1 -> 0    BE       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    fr2               1    Cyxtera                 1    Geneva                 1    CA       1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    ge2               1    Digital Realty          1    Greater Noida          1    CH       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    gn1               1    Equinix                 1    Hesse                  1    DE       1
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    hk4               1    Flexential         0 -> 1    HongKong               1    GE       1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    jv1          1 -> 0    Megazone Cloud          1    Ljubljana              1    HK       1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  0 -> 1    lj1               1    NEXTDC                  1    Melbourne              1    IN       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mn2               1    Posita.si               1    Ontario                1    KR       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg1               1    SafeHost                1    Seoul                  1    SE       1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe  1 -> 0    sh1               1    Telin                   1    Singapore              1    SG       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    sl1               1    Tierpoint          1 -> 0    Stockholm              1    SI       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    tb1               1    Yotta                   1    Tbilisi                1    US       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    to2               1    hkntt                   1    Texas             0 -> 1              
1 Like

Proposal 135303 Review | LORIMER - CO.DELTA △

VOTE: YES

TLDR: An offline node replaced with an unassigned node in the same country. Important decentralisation metrics remain unchanged, and the average distance between nodes is slightly improved.

Note that there’s 1 node country discrepancy for this subnet. The countries are close to one another, so the response latency approach employed by ipinfo.io may not be pinpointing location accurately enough (something to revisit…)

Country Discrepancies (1)
Node Data Center Claimed Country According to api.ip2location.io According to ipinfo.io
5aaq4 Geneva 2 Switzerland Germany Germany
Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 316.333 km 7601.024 km 16616.248 km
PROPOSED 316.333 km 7613.246 km (+0.2%) 16616.248 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 4 13 13 13 13 13
PROPOSED 4 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 5 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)

  • Black dotted line connects to a small black marker that shows where the IP address indicates the node is located (according to api.ip2location.io). This is only displayed if it conflicts with where IC records indicate the node is located. See Country Discrepancies section above for more info.

Node Changes
Action Node Status Continent Country Data Center Owner Node Provider Node Operator
Remove u7niu DOWN :bar_chart: North America United States of America (the) Jacksonville (jv1) Tierpoint Rivonia Holdings LLC wmrev
Add k2dew UNASSIGNED :bar_chart: North America United States of America (the) Dallas (dl1) Flexential 87m Neuron, LLC mw64v
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
6bt7p UP :bar_chart: Oceania Australia Melbourne 2 (mn2) NEXTDC Icaria Systems Pty Ltd l5lhp
zk4lm UP :bar_chart: Europe Belgium Brussels 2 (br2) AtlasEdge Allusion oorkg
zxph7 UP :bar_chart: North America Canada Toronto 2 (to2) Cyxtera Blockchain Development Labs 4lp6i
5aaq4 UP :bar_chart: Europe Switzerland Geneva 2 (ge2) SafeHost Archery Blockchain SCSp 5atxd
d2hzh UP :bar_chart: Europe Germany Frankfurt 2 (fr2) Equinix Virtual Hive Ltd 3nu7r
fwpkp UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
cvryq UP :bar_chart: Asia Hong Kong HongKong 4 (hk4) hkntt Origin Game aaxec
pojjf UP :bar_chart: Asia India Greater Noida 1 (gn1) Yotta ACCUSET SOLUTIONS slaxf
lz3ap UP :bar_chart: Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3
mt54u UP :bar_chart: Europe Sweden Stockholm 1 (sh1) Digital Realty DFINITY Stiftung lgp6d
diz6c UP :bar_chart: Asia Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital d4bin
5jxvk UP :bar_chart: Europe Slovenia Ljubljana (lj1) Posita.si Fractal Labs AG gl27f


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.

Proposal 135303 | Tim - CodeGov

Vote: Adopt

This proposal replaces node u7niu 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

Proposal #135303 — Zack | CodeGov

Vote: Adopted
Reason:
The proposal replaces dead Offline status node u7niu from the JV1 DC in Florida, with unassigned healthy Awaiting status node k2dew from Dallas, without any change to decentralization.

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 & Neuron’s 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 decentralization 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

Proposal 135303 – LaCosta | CodeGov

Vote: ADOPT

The proposal replaces a dead node on subnet nl6hn:
Removed node: dead node u7niu
Added node: node k2dew

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 & Neuron’s 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 decentralization 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