Replacing nodes in subnet pjljw

[DRE-Team]

Replace a node in subnet pjljw

Motivation:
The following nodes in subnet pjljw have been cordoned and will be removed:

• z6jp6: offboarding DL1 DC after 48 months

Decentralization Nakamoto coefficient changes for subnet pjljw-kztyl-46ud4-ofrj6-nzkhm-3n4nt-wi3jt-ypmav-ijqkt-gjf66-uae:

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

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

Overall replacement impact: equal decentralization across all features

Details

Nodes removed:

• z6jp6-245uu-gh3cs-sblcy-f3jmj-s4ngl-v3z4u-lafz2-qudjr-6mbqx-vqe [health: healthy]

Nodes added:

• geihd-pwhjg-q3tno-beo64-ormih-pkjah-rrdlu-quwdk-nas5k-lmzoo-pae [health: healthy]

    node_provider                                                              data_center            data_center_owner              area                        country   
    -------------                                                              -----------            -----------------              ----                        -------   
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    aw1          0 -> 1    Africa Data Centres       1    Brussels Capital       1    AU       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br1               1    Digital Realty            1    Bucuresti              1    BE       1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe  0 -> 1    bu1               1    Equinix                   1    Gauteng                1    CH       2
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    dl1          1 -> 0    Everyware                 1    Geneva                 1    DE       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    fr2               1    Flexential           1 -> 0    Hesse                  1    HK       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ge1               1    HighDC                    1    HongKong               1    IN       1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  1 -> 0    hk3               1    KT                        1    Ljubljana              1    KR       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    jb2               1    M247                      1    Melbourne              1    RO       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    kr1               1    Marvelous Web3 DC         1    New Delhi              1    SG       1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    lj1               1    NEXTDC                    1    Pennsylvania      0 -> 1    SI       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    mn2               1    Posita.si                 1    Seoul                  1    US       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    nd1               1    Telin                     1    Singapore              1    ZA       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    sg2               1    Tierpoint            0 -> 1    Texas             1 -> 0              
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    zh2               1    hkcolo                    1    Zurich                 1              

Proposal id 134282

[sat]

related: Subnet Management - General Discussion - #87 by sat

[ZackDS]

Voted to adopt proposal #134282.

As part of post-48 months offboarding of DCs and NPs the proposal replaces cordoned healthy Active status node z6jp6 form Data Center DL1 Texas, US with Awaiting status node geihd from Pennsylvania, US decentralization stays the same.

[timk11]

Review from subnet thread:

@timk11

Voted to adopt proposal 134282. 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 relevant context is provided by this forum post and associated discussion. However, I voted before this reply was posted. The subsequent posts indicate that this proposal was submitted in error, so I would therefore now recommend a reject vote.

[timk11]

Re proposal 134282, please note the issue that I’ve flagged above.

@0rions @louisevelayo @zenithcode @skilesare @jerrybanfield @b3hr4d @Lorimer @wpb @LaCosta

[Lorimer]

Thanks @timk11, I agree, and I think this proposal highlights a much broader problem with how proposals are being handled. I think there are habits that need to broken.

@Lorimer

Thanks for being upfront about this @katiep. So Proposal: 134282 (at least) should be rejected (posted here)

My perspective is that verification is not about asking the proposing entity if the proposal is okay, and then believing them when they say it’s okay (for this sort of reason, or worse).

[timk11]

No problem, and I agree with the general point you’ve made in your earlier post. In the case of these proposals I think the proposal wording and the discussion around them presumed a lot of prior knowledge that would have been very familiar to the node provider community but not to others. The team has been very amenable to feedback so I’m hopeful that they’ll take these points on board when it comes to the next round of offboarding.