Subnet Management - 4ecnw (Application)

This topic is intended to capture Subnet Management activities over time for the 4ecnw 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": 44600,
  "records": [
    {
      "key": "subnet_record_4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe",
      "version": 44600,
      "value": {
        "membership": [
          "6kfcs-57wu7-37qb6-mkh2a-sl2gt-z7cwa-jwihc-o5ui4-zu3lw-nf5xq-nae",
          "ns7kv-kp2mu-mw7yi-krd4z-eqcvq-qeeej-mxtwb-c2ujq-xtq6x-orzoj-3qe",
          "c3syk-l56ky-owcvg-y4ogf-3qfti-elv4e-2bqp7-k5v32-ibzm6-o4k6s-eqe",
          "b5pgw-6wtjo-dzwgu-zkfz6-3l5f3-cw6ka-y4crr-dikku-fkjbe-lfzki-qae",
          "kqtlh-qojsl-k4xyd-baow4-ihgyb-y47y7-nvrhv-k35k3-432ti-l4ci6-tae",
          "5ttnf-xhdip-7e2uw-iuikh-5dlli-r6jdc-nxjp7-bjumm-5usid-rpiqn-jqe",
          "7f5c7-l7cuq-7jnfc-yexo3-bytd3-yf6xa-ctk76-wywln-jsy2n-ds2lp-tqe",
          "rfe2u-pdp5u-frzdb-r2ga3-5jept-24323-5pere-7lerg-toh4w-cwdsl-cqe",
          "656go-lv4fr-us6n5-uiyjx-ca6i2-pqidc-qowpr-z6npc-gihub-r6of4-tqe",
          "m4e6a-3t7oi-ooshc-2b2vq-56xpu-pyo7q-qafn2-3sem2-cvtck-6xfqy-vae",
          "o42ny-ab3zt-iknyx-eo4ji-utgbe-xmae4-ybmwp-wdkzt-efffe-oq6nh-oae",
          "lvac3-kgilc-zs5x5-skq6a-4ajcq-xkd6g-6twwm-ltyum-rphgd-f3iei-lqe",
          "d7uw7-epfl6-7vcof-oband-nmx6z-hvowm-kjcdj-xlyww-3bzft-ymnv4-hae"
        ],
        "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": "3d0b3f10417fc6708e8b5d844a0bac5e86f3e17d",
        "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/131703. This information is presented below:

  • 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 a node sits within (red if the country is removed, green if added, otherwise grey)

Table
Country Data Center Owner Node Provider Node Status
--- Korea (the Republic of) Seoul 2 (kr2) Gasan Web3game 6kfcs-57wu7-37qb6-mkh2a-sl2gt-z7cwa-jwihc-o5ui4-zu3lw-nf5xq-nae DEGRADED
+++ Slovenia Ljubljana (lj1) Posita.si Fractal Labs AG hhixb-o5xrj-s5pty-esitz-m6s46-wgsez-c7thd-6h27w-7hikq-ae5n7-pae UNASSIGNED
Australia Queensland 1 (sc1) NEXTDC ANYPOINT PTY LTD 7f5c7-l7cuq-7jnfc-yexo3-bytd3-yf6xa-ctk76-wywln-jsy2n-ds2lp-tqe UP
Belgium Antwerp (an1) Datacenter United Allusion 656go-lv4fr-us6n5-uiyjx-ca6i2-pqidc-qowpr-z6npc-gihub-r6of4-tqe UP
Canada Toronto 2 (to2) Cyxtera Blockchain Development Labs ns7kv-kp2mu-mw7yi-krd4z-eqcvq-qeeej-mxtwb-c2ujq-xtq6x-orzoj-3qe UP
Switzerland Geneva 2 (ge2) SafeHost Archery Blockchain SCSp m4e6a-3t7oi-ooshc-2b2vq-56xpu-pyo7q-qafn2-3sem2-cvtck-6xfqy-vae UP
China HongKong 1 (hk1) Unicom Pindar Technology Limited c3syk-l56ky-owcvg-y4ogf-3qfti-elv4e-2bqp7-k5v32-ibzm6-o4k6s-eqe UP
India Navi Mumbai 1 (nm1) Rivram Rivram Inc kqtlh-qojsl-k4xyd-baow4-ihgyb-y47y7-nvrhv-k35k3-432ti-l4ci6-tae UP
Japan Tokyo 2 (ty2) Equinix Starbase lvac3-kgilc-zs5x5-skq6a-4ajcq-xkd6g-6twwm-ltyum-rphgd-f3iei-lqe UP
Lithuania Siauliai 1 (si1) Bacloud Vladyslav Popov 5ttnf-xhdip-7e2uw-iuikh-5dlli-r6jdc-nxjp7-bjumm-5usid-rpiqn-jqe UP
Romania Bucharest (bu1) M247 Iancu Aurel o42ny-ab3zt-iknyx-eo4ji-utgbe-xmae4-ybmwp-wdkzt-efffe-oq6nh-oae UP
Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital b5pgw-6wtjo-dzwgu-zkfz6-3l5f3-cw6ka-y4crr-dikku-fkjbe-lfzki-qae UP
Sweden Stockholm 1 (sh1) Digital Realty DFINITY Operations SA rfe2u-pdp5u-frzdb-r2ga3-5jept-24323-5pere-7lerg-toh4w-cwdsl-cqe UP
United States of America (the) Tampa (tp1) Flexential Jeffrey Schnettler d7uw7-epfl6-7vcof-oband-nmx6z-hvowm-kjcdj-xlyww-3bzft-ymnv4-hae UP

The removed node is replaced with a node based in Slovenia. I’ve checked that the old node is degraded and the new node is currently unassigned.

DFINITY will submit an NNS proposal today to reduce the notarization delay on the subnet, 4ecnw, 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 133070. The initial_notary_delay_millis is set to 300 and the subnet_id is correct.

1 Like

Voted to adopt proposal 134271. The proposal seeks to remove a cordoned node from the subnet and specifies that the associated data centre is being offboarded “after 48 months”. Decentralisation parameters are unchanged. The necessary context is provided by this forum post and associated discussion. For future proposals of this type I recommend that the background context be included in the proposal text for ease of verification.

I’ve voted to reject proposal 134271. It makes claims that I see no clear way of verifying, and supporting statements regarding the ownership of the data centre are inconsistent with records held in the IC registry. The proposal was announced here.

Voted to adopt proposal 134271. This proposal is part of a sequence of steps to remove cordoned nodes from subnets as the associated data centeres are being offboarded after 48 months of their respective DC contracts that are still private and were signed up before the Genesis. There is a great and detailed explanation of this changes in this forum post and the forum thread it is in. In the wiki there is a series of Steps for Gen-1 Node onboarding after 48 months that need to be followed in order for the nodes to continue earning rewards which starts by making a forum post in the following thread. As we can verify no one as come forward with nodes from the DCs in this proposals so I don’t see any issues with the removal of this nodes.