Subnet Management - cv73p (Application)

This topic is intended to capture Subnet Management activities over time for the cv73p subnet, providing a place to ask questions and make observations about the management of this subnet.

At the time of creating this topic the current subnet configuration is as follows:

Expand
{
  "version": 44477,
  "records": [
    {
      "key": "subnet_record_cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae",
      "version": 44477,
      "value": {
        "membership": [
          "jemyk-uhint-w6ftv-s3xpy-ne4hr-xbcpu-aqskm-6a4cy-orm5q-aqqwd-gqe",
          "dnorv-obqlt-6fl2s-ylxsf-o6pwv-fssdj-63kdj-jjw5d-luhdg-xe2zn-2ae",
          "m2yt5-mn7lw-76bqj-ijlgn-55n3k-xbjzl-43olv-6xi4p-2ecp4-eipxu-xae",
          "lkrgq-rqmms-blrdo-24alx-2jrtz-xl5qm-dk6xc-o5fvc-o2huw-bxtqs-wqe",
          "eu2gw-3uj2c-vhwzo-kx3tz-cmnte-3gymk-tza4c-z66f6-uuksx-x3g2m-xqe",
          "jsaui-j3qrn-3i3m3-xdn2s-bad3f-5kwlu-36gej-i75ik-5fjrg-z3jge-bqe",
          "i7u4k-qo5lu-w2ynn-m7iec-lit7d-prf44-3fy7c-hvwqw-wwhdw-f6tdr-uae",
          "njsmq-lvuj4-fo325-pt3od-f5zqr-j64dp-u5l6n-kdffj-3gvvr-3rbfa-wqe",
          "ek3yy-o3qk4-xivlj-qik4h-tgbwt-kmyyv-po3lm-hhwll-o7p3w-qrc4s-hqe",
          "4d2sj-eqwzi-m7s5g-uj33s-wieqq-kgzyk-qzywl-ptltz-7zryd-sdbsc-uqe",
          "hgvcj-xdftg-62bcj-s66dr-rsshe-rmj6x-mzlvg-65ytj-3wapx-ig6js-mqe",
          "3fgii-zd73c-ftxy2-ypsbx-hnqf2-nzhc6-veurh-bru27-mz6bg-j62qd-xqe",
          "tfw5b-kpj3p-bniym-lllfz-fzcuq-4c65m-xqv3y-dy44l-fvmsn-yebii-pqe"
        ],
        "nodes": {},
        "max_ingress_bytes_per_message": 2097152,
        "max_ingress_messages_per_block": 1000,
        "max_block_payload_size": 4194304,
        "unit_delay_millis": 1000,
        "initial_notary_delay_millis": 600,
        "replica_version_id": "2c0b76cfc7e596d5c4304cff5222a2619294c8c1",
        "dkg_interval_length": 499,
        "start_as_nns": false,
        "subnet_type": "application",
        "features": {
          "canister_sandboxing": false,
          "http_requests": true,
          "sev_enabled": false
        },
        "max_number_of_canisters": 120000,
        "ssh_readonly_access": [],
        "ssh_backup_access": [],
        "ecdsa_config": null,
        "chain_key_config": null
      }
    }
  ]
}

There’s an open proposal for changing subnet membership - https://dashboard.internetcomputer.org/proposal/131417. This information is presented below:

  • red marker represents a removed node
  • green marker represents an added node
  • highlighted patches represent the country a node sits within

Table
Country Data Center Owner Node Provider Node
--- Germany Munich (mu1) q.beyond Staking Facilities 4d2sj-eqwzi-m7s5g-uj33s-wieqq-kgzyk-qzywl-ptltz-7zryd-sdbsc-uqe
+++ Romania Bucharest (bu1) M247 Iancu Aurel wihnn-o5yix-kkneh-33pvm-ybil3-4rdf3-vu3w2-6lmg4-76yu3-feyyd-cae
Belgium Brussels (br1) Digital Realty Allusion ek3yy-o3qk4-xivlj-qik4h-tgbwt-kmyyv-po3lm-hhwll-o7p3w-qrc4s-hqe
Canada Fremont (fm1) Hurricane Electric Adam Dymecki m2yt5-mn7lw-76bqj-ijlgn-55n3k-xbjzl-43olv-6xi4p-2ecp4-eipxu-xae
Switzerland Geneva 2 (ge2) SafeHost Archery Blockchain SCSp hgvcj-xdftg-62bcj-s66dr-rsshe-rmj6x-mzlvg-65ytj-3wapx-ig6js-mqe
Switzerland Zurich 2 (zh2) Everyware DFINITY Operations SA lkrgq-rqmms-blrdo-24alx-2jrtz-xl5qm-dk6xc-o5fvc-o2huw-bxtqs-wqe
China HongKong 1 (hk1) Unicom Wancloud limited jemyk-uhint-w6ftv-s3xpy-ne4hr-xbcpu-aqskm-6a4cy-orm5q-aqqwd-gqe
Japan Tokyo (ty1) Equinix Starbase tfw5b-kpj3p-bniym-lllfz-fzcuq-4c65m-xqv3y-dy44l-fvmsn-yebii-pqe
Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital 3fgii-zd73c-ftxy2-ypsbx-hnqf2-nzhc6-veurh-bru27-mz6bg-j62qd-xqe
Slovenia Ljubljana 2 (lj2) Anonstake Anonstake dnorv-obqlt-6fl2s-ylxsf-o6pwv-fssdj-63kdj-jjw5d-luhdg-xe2zn-2ae
Slovenia Maribor (mb1) Posita.si Fractal Labs AG njsmq-lvuj4-fo325-pt3od-f5zqr-j64dp-u5l6n-kdffj-3gvvr-3rbfa-wqe
United States of America (the) Allentown (aw1) Tierpoint Bigger Capital eu2gw-3uj2c-vhwzo-kx3tz-cmnte-3gymk-tza4c-z66f6-uuksx-x3g2m-xqe
United States of America (the) Orlando (or1) Datasite Giant Leaf, LLC i7u4k-qo5lu-w2ynn-m7iec-lit7d-prf44-3fy7c-hvwqw-wwhdw-f6tdr-uae
United States of America (the) Portland (pl1) Flexential 87m Neuron, LLC jsaui-j3qrn-3i3m3-xdn2s-bad3f-5kwlu-36gej-i75ik-5fjrg-z3jge-bqe

The removed node is replaced with a node based in Romania. I’ve verified that this node is currently unassigned.

The proposal mentions that his change is needed due to the Munich (mu1) data centre being due for decommissioning. See here for more discussion and references.

1 Like

DFINITY will submit an NNS proposal today to reduce the notarization delay on the subnet, cv73p, similar to what has happened on other subnets in recent weeks (you can find all details in this forum thread).

2 Likes

Voted to adopt proposal 133073. The initial_notary_delay_millis is set to 300 and the subnet_id is correct.

1 Like

Voted to adopt proposal 134179, as the reasoning is sound and the description matches the payload. This proposal replaces 2 healthy nodes, both of which appear as “Active” on the IC dashboard. The proposed change improves decentralisation with respect to country and brings the target topology parameters to within the requirements.

4 Likes

Proposal 134179

TLDR: I’m planning to adopt. This proposal brings this subnet inline with the IC Target Topology, by reducing the max number of nodes per country from 3 to 2.

This does however increase the max number of nodes per continent from 6 to 8. Nevertheless, countries are considered to be more important than continents (and are a formal part of the IC Target Topology, whereas continents are not).

Motivation:

  • replacing node m2yt5-mn7lw-76bqj-ijlgn-55n3k-xbjzl-43olv-6xi4p-2ecp4-eipxu-xae to optimize network topology
  • replacing node jsaui-j3qrn-3i3m3-xdn2s-bad3f-5kwlu-36gej-i75ik-5fjrg-z3jge-bqe to optimize network topology

2 American nodes replaced with 2 European nodes.

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 0 km 6851.289 km 15377.131 km
PROPOSED 0 km 6014.926 km (-12.2%) 15377.131 km

This proposal slightly reduces decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical reduction in localised disaster resilience). :-1:

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 3 10 13 13 13 13
PROPOSED 3 11 (+9.1%) 13 13 13 13

This proposal slightly improves decentralisation in terms of jurisdiction diversity. :+1:

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 3 1 1 1 1
PROPOSED 8 (+33.34%) 2 (-33.34%) 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 Operator Node Status Performance
--- Americas Canada Fremont (fm1) Hurricane Electric Adam Dymecki 4q2h5 m2yt5-mn7lw-76bqj-ijlgn-55n3k-xbjzl-43olv-6xi4p-2ecp4-eipxu-xae UP :bar_chart:
--- Americas United States of America (the) Portland (pl1) Flexential 87m Neuron, LLC lz4fy jsaui-j3qrn-3i3m3-xdn2s-bad3f-5kwlu-36gej-i75ik-5fjrg-z3jge-bqe UP :bar_chart:
+++ Europe Spain Madrid 3 (ma3) IPCore Maksym Ishchenko wtsc7 2mmpk-6kvr3-3syvq-twao3-g3fxc-gz3n2-o3tgf-34irb-idruv-cogfq-sqe UNASSIGNED :bar_chart:
+++ Europe Lithuania Vilnius 1 (bt1) Baltneta Ivanov Oleksandr y3du2 ax6zb-r4jnm-5aswz-ahoqx-ujs2a-mcvds-6gmdt-4ggxg-tkwdr-3323l-vqe UNASSIGNED :bar_chart:
Europe Belgium Brussels (br1) Digital Realty Allusion mjeqs ek3yy-o3qk4-xivlj-qik4h-tgbwt-kmyyv-po3lm-hhwll-o7p3w-qrc4s-hqe UP :bar_chart:
Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Operations SA wqyl3 lkrgq-rqmms-blrdo-24alx-2jrtz-xl5qm-dk6xc-o5fvc-o2huw-bxtqs-wqe UP :bar_chart:
Asia China HongKong 1 (hk1) Unicom Wancloud limited z6cfb jemyk-uhint-w6ftv-s3xpy-ne4hr-xbcpu-aqskm-6a4cy-orm5q-aqqwd-gqe UP :bar_chart:
Europe Germany Geneva 2 (ge2) SafeHost Archery Blockchain SCSp 5atxd hgvcj-xdftg-62bcj-s66dr-rsshe-rmj6x-mzlvg-65ytj-3wapx-ig6js-mqe UP :bar_chart:
Asia Japan Tokyo (ty1) Equinix Starbase cqjev tfw5b-kpj3p-bniym-lllfz-fzcuq-4c65m-xqv3y-dy44l-fvmsn-yebii-pqe UP :bar_chart:
Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg wihnn-o5yix-kkneh-33pvm-ybil3-4rdf3-vu3w2-6lmg4-76yu3-feyyd-cae UP :bar_chart:
Asia Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital d4bin 3fgii-zd73c-ftxy2-ypsbx-hnqf2-nzhc6-veurh-bru27-mz6bg-j62qd-xqe UP :bar_chart:
Europe Slovenia Ljubljana 2 (lj2) Anonstake Anonstake eu5wc dnorv-obqlt-6fl2s-ylxsf-o6pwv-fssdj-63kdj-jjw5d-luhdg-xe2zn-2ae UP :bar_chart:
Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew njsmq-lvuj4-fo325-pt3od-f5zqr-j64dp-u5l6n-kdffj-3gvvr-3rbfa-wqe UP :bar_chart:
Americas United States of America (the) Allentown (aw1) Tierpoint Bigger Capital codio eu2gw-3uj2c-vhwzo-kx3tz-cmnte-3gymk-tza4c-z66f6-uuksx-x3g2m-xqe UP :bar_chart:
Americas United States of America (the) Orlando (or1) Datasite Giant Leaf, LLC redpf i7u4k-qo5lu-w2ynn-m7iec-lit7d-prf44-3fy7c-hvwqw-wwhdw-f6tdr-uae UP :bar_chart:

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.

Another good neuron to follow is 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)

3 Likes

Voted to adopt proposal #134179.

The proposal replaces 2 healthy Active status nodes form Fremont and Portland, both from US this way reducing Country from 4 to 2, in order to optimize network topology.

2 Likes

Voted to adopt proposal 134179. The proposal replaces two nodes from subnet cv73p:
Removed Nodes: m2yt5, jsaui.
Added Nodes: 2mmpk and ax6zb.
The proposal was verified using the DRE tool to verify the metrics stated. All nodes replaced are healthy but this replacements improve the network topology on the country metric reducing the number of nodes in the US from 4 to 2.

2 Likes

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

Click here to open proposal details

Replace a node in subnet cv73p

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

Decentralization Nakamoto coefficient changes for subnet cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae:

    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: 3.00 -> 3.00    (+0%)

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

Overall replacement impact: (gets better) the number of nodes controlled by dominant Country actors decreases from 6 to 5

Details

Nodes removed:

  • njsmq-lvuj4-fo325-pt3od-f5zqr-j64dp-u5l6n-kdffj-3gvvr-3rbfa-wqe [health: healthy]

Nodes added:

  • qtcl6-k4m2v-zr4fp-2jvwf-2h46j-l3mg5-lwlxy-3wsh7-hghcp-afdsa-6qe [health: healthy]
    node_provider                                                              data_center            data_center_owner            area                        country        
    -------------                                                              -----------            -----------------            ----                        -------        
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae       1    aw1               1    Anonstake               1    Brussels Capital       1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br1               1    Baltneta                1    Bucuresti              1    CH            2
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe       1    bt1               1    Datasite                1    Florida                1    ES            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    bu1               1    Digital Realty          1    Geneva                 1    HK            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ge2               1    Equinix                 1    HongKong               1    JP            1
    g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe       1    hk1               1    Everyware               1    Ljubljana              1    KR       0 -> 1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    kr1          0 -> 1    IPCore                  1    Madrid                 1    LT            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    lj2               1    KT                 0 -> 1    Maribor           1 -> 0    RO            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    ma3               1    M247                    1    Pennsylvania           1    SG            1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  0 -> 1    mb1          1 -> 0    Posita.si          1 -> 0    Seoul             0 -> 1    SI       2 -> 1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    or1               1    SafeHost                1    Singapore              1    US            2
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sg1               1    Telin                   1    Tokyo                  1                   
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1 -> 0    ty1               1    Tierpoint               1    Vilnius                1                   
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae       1    zh2               1    Unicom                  1    Zurich                 1                   
2 Likes

Proposal 134976 | Tim - CodeGov

Vote: Adopt

This proposal replaces node njsmq 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 improved 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 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 134976 Review | LORIMER Known Neuron

VOTE: YES

TLDR: Decentralisation stats are slightly improved (see Decentralisation Stats below) and there is a clear public declaration for the cordoned node which is referred to in the proposal summary. 1 cordoned node in Europe replaced with an unassigned node in Asia.

Country Discrepancies (2)
Node Data Center Claimed Country According to api.ip2location.io According to ip-api.com According to domain WHOIS lookup
hgvcj Geneva 2 Switzerland Germany Switzerland Germany
qtcl6 Seoul 3 Korea (the Republic of) Belgium China China

See here for related discussion

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 104.032 km 6044.448 km 16654.257 km
PROPOSED 224.918 km (+116.2%) 6586.338 km (+9%) 16654.257 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 10 13 13 13 13
PROPOSED 3 11 (+9.1%) 13 13 13 13

This proposal slightly improves decentralisation in terms of jurisdiction diversity. :+1:

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 8 2 1 1 1 1
PROPOSED 7 (-12.5%) 2 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 njsmq UP :bar_chart: Europe Slovenia Maribor (mb1) Posita.si Fractal Labs AG 3xiew
Add qtcl6 UNASSIGNED :bar_chart: Asia Korea (the Republic of) Seoul 3 (kr1) KT Pindar Technology Limited iubpe
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
ek3yy UP :bar_chart: Europe Belgium Brussels (br1) Digital Realty Allusion mjeqs
hgvcj UP :bar_chart: Europe Switzerland Geneva 2 (ge2) SafeHost Archery Blockchain SCSp 5atxd
lkrgq UP :bar_chart: Europe Switzerland Zurich 2 (zh2) Everyware DFINITY Stiftung wqyl3
2mmpk UP :bar_chart: Europe Spain Madrid 3 (ma3) IPCore Maksym Ishchenko wtsc7
jemyk UP :bar_chart: Asia Hong Kong HongKong 1 (hk1) Unicom Wancloud limited z6cfb
tfw5b UP :bar_chart: Asia Japan Tokyo (ty1) Equinix Starbase cqjev
ax6zb UP :bar_chart: Europe Lithuania Vilnius 1 (bt1) Baltneta Ivanov Oleksandr y3du2
wihnn UP :bar_chart: Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg
3fgii UP :bar_chart: Asia Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital d4bin
dnorv UP :bar_chart: Europe Slovenia Ljubljana 2 (lj2) Anonstake Anonstake eu5wc
eu2gw UP :bar_chart: North America United States of America (the) Allentown (aw1) Tierpoint Bigger Capital codio
i7u4k UP :bar_chart: North America United States of America (the) Orlando (or1) Datasite Giant Leaf, LLC redpf

*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 #134976 — Zack | CodeGov

Vote: Adopted
Reason:
The proposal replaces cordoned healthy Active status node njsmq in the MB1 DC from Slovenia, with unassigned healthy Awaiting status node qtcl6 from Korea, with slight improvement to the decentralization of the subnet.
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 134976 – LaCosta | CodeGov

Vote: ADOPT

Replaces cordoned node njsmq with node qtcl6 on subnet cv73p.
The reason for this proposal is to offboard 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