A new proposal with ID 135540 has been submitted, please take a look.
Click here to open proposal details
Replace a node in subnet qxesv
Motivation:
- replacing dead node j7mu5
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 qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae:
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 -> 4.00 (-20%)
country: 5.00 -> 4.00 (-20%)
Mean Nakamoto comparison: 5.00 → 4.67 (-7%)
Overall replacement impact: (gets worse) the average log2 of Nakamoto Coefficients across all features decreases from 2.3219 to 2.2146
Impact on business rules penalties: 1000 → 0
Details
Nodes removed:
j7mu5-sfjx5-rflso-aqhd5-ymijf-glw4a-ovi6i-f3blz-o54sg-a2rfk-bae[health: dead]
Nodes added:
bs2f6-hqzox-bkqoe-aw3jj-7lso3-hyo33-tiq74-kuinv-ucdez-vtt4a-3ae[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 br1 1 Cloud9 1 Brussels Capital 1 BE 1
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bu1 1 Digital Realty 1 Bucuresti 1 CH 1 -> 2
6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe 1 cr1 1 Dotsi 1 -> 0 Hesse 1 CR 1
7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe 1 dl1 1 Equinix 1 HongKong 1 DE 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 0 -> 1 fr2 1 Everyware 0 -> 1 Lisbon 1 -> 0 GE 1
eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe 1 hk1 1 Flexential 1 Maribor 1 HK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 li1 1 -> 0 M247 1 New Delhi 1 IN 1
ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae 1 -> 0 mb1 1 Marvelous Web3 DC 1 San Jose 1 KR 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 nd1 1 Megazone Cloud 1 Seoul 1 PT 1 -> 0
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 sg2 1 Navegalo 1 Singapore 1 RO 1
ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae 1 sl1 1 Nine.Ch 1 Tbilisi 1 SG 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 tb1 1 Posita.si 1 Texas 1 SI 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 zh2 0 -> 1 Telin 1 Zurich 1 -> 2 US 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 zh4 1 Unicom 1
Business rules check results before the membership change:
- Subnet should have 1 DFINITY-owned node(s) for subnet recovery, got 0
UPDATE: To clarify, this was the only option available to bring back one DFINITY-owned node into the subnet. There was no possibility to achieve this without worsening the subnet decentralization, as tooling argumented in the proposal summary. Improvement should nevertheless be possible in follow-up proposals, when we’re able to replace 2 other nodes.