Subnet Management - w4rem (System Bitcoin)

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

Click here to open proposal details

Replace a node in subnet w4rem

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 w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe:

    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:

  • jiy6l-jx7ea-k7y2u-tznfb-dcrm2-5fhrt-r63pd-wdfse-2ubgq-6pfvi-lae [health: healthy]

Nodes added:

  • udlch-g42nv-er23m-bgpxk-oiymd-knkro-2dczg-hyv4x-2yiw6-q2jcz-hqe [health: healthy]
    node_provider                                                         data_center            data_center_owner       area            country   
    -------------                                                         -----------            -----------------       ----            -------   
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae  1    bu1               1    Cloud9             1    Arizona    1    AU       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  1    cr1               1    CyrusOne           1    Bucuresti  1    CA       1
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe  1    ct2               1    DEAC               1    Cape Town  1    CH       1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe  1    mn2               1    Digital Realty     1    Melbourne  1    CR       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe  1    mtl1              1    Equinix            1    Panvel     1    GE       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae  1    ph1               1    Green.ch           1    Quebec     1    IN       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe  1    pl2               1    Leaseweb           1    Riga       1    JP       1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1    rg1               1    M247               1    San Jose   1    LV       1
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe  1    sg1               1    NEXTDC             1    Singapore  1    RO       1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae  1    sh1               1    Navegalo           1    Stockholm  1    SE       1
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae  1    tb1               1    Telin              1    Tbilisi    1    SG       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  1    ty1               1    Teraco             1    Tokyo      1    US       1
    zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae  1    zh5          1 -> 0    Yotta              1    Zurich     1    ZA       1
                                                                          zh6          0 -> 1                                                      
2 Likes

Proposal 134987 | Tim - CodeGov

Vote: Adopt

This proposal replaces node jiy6l which appears in the dashboard as “Status: Active” for the stated reason “offboarding ZH5 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 134987 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 a nearby data centre.

Decentralisation Stats

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

Smallest Distance Average Distance Largest Distance
EXISTING 452.505 km 8883.905 km 18499.629 km
PROPOSED 452.505 km 8883.905 km 18499.629 km

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 4 1 1 1 1 1
PROPOSED 4 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 jiy6l UP :bar_chart: Europe Switzerland Zurich 5 (zh5) Green.ch Sygnum Bank 4ohfd
Add udlch UNASSIGNED :bar_chart: Europe Switzerland Zurich 6 (zh6) Green.ch Sygnum Bank ciprs
Other Nodes
Node Status Continent Country Data Center Owner Node Provider Node Operator
d6thv UP :bar_chart: Oceania Australia Melbourne 2 (mn2) NEXTDC Icaria Systems Pty Ltd l5lhp
yim23 UP :bar_chart: Americas Canada Quebec l1 (mtl1) Leaseweb Rivram Inc zhlzs
63rak UP :bar_chart: Americas Costa Rica San José 1 (cr1) Navegalo GeoNodes LLC eqv2i
7r7go UP :bar_chart: Asia Georgia Tbilisi 1 (tb1) Cloud9 George Bassadone yhfy4
tmevu UP :bar_chart: Asia India Panvel 2 (pl2) Yotta Krishna Enterprises 7rw6b
7s6kl UP :bar_chart: Asia Japan Tokyo (ty1) Equinix Starbase cqjev
vivoi UP :bar_chart: Europe Latvia Riga 1 (rg1) DEAC MB Patrankos šūvis jptla
ihb24 UP :bar_chart: Europe Romania Bucharest (bu1) M247 Iancu Aurel c5ssg
xu6mr UP :bar_chart: Asia Singapore Singapore (sg1) Telin OneSixtyTwo Digital Capital d4bin
7pwmx UP :bar_chart: Europe Sweden Stockholm 1 (sh1) Digital Realty DFINITY Stiftung lgp6d
fe7vt UP :bar_chart: Americas United States of America (the) Phoenix (ph1) CyrusOne MI Servers 5bnm2
jk3km UP :bar_chart: Africa South Africa Cape Town 2 (ct2) Teraco Kontrapunt (Pty) Ltd x7fjr

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

1 Like

Proposal #134987 — Zack | CodeGov

Vote: Adopted
Reason:
The proposal replaces cordoned healthy Active status node jiy6l in the ZH5 DC from Zurich5, with unassigned healthy Awaiting status node udlch from Zurich6, without any chnge to decentralization.
Motivation is offboarding of nodes in the ZH5 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 134987 – LaCosta | CodeGov

Vote: ADOPT

Replaces cordoned node jiy6l with node udlch on subnet w4rem.
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