Rejected proposal 134582. There’s no time to review this and the 18 other proposals in the same batch properly over Xmas eve, Xmas and Boxing Day. This is a non-critical proposal.
More information and discussion on this thread.
Proposal 134582
Vote: ADOPT
Replaces cordoned nodes e72ys and mjcgv with nodes 2sjsi and d46vh on subnet yinp6.
The reason for this proposal is to offboard TO1 and AN1 DCs 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 and forum post match the ones from the node being removed in the proposal.
2 Likes
Voted to adopt proposal #134582.
The proposal replaces two cordoned nodes, one healthy Active status node e72ys from the TO1 Data Center in Toronto 1, and cordoned healthy Active status node mjcgv from the AN1 Data Center in Belgium, with unassigned healthy Awaiting status node 2sjsi from Toronto 2 and with unassigned healthy Awaiting status node d46vh from Korea, without any change to the decentralization of the subnet.
The motivation makes sense and the provided Forum link included in the summary provides further info, also it can be checked here.
1 Like
There’s an open Replace nodes in subnet yinp6
Motivation:
The following nodes in subnet yinp6 have been cordoned and need to be removed from the subnet:
- 6f7g4: offboarding MM1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #49 by GiantLeaf and Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #103 by katiep
- 7mwzk: offboarding the second rack of nodes in the GE1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #148 by Gwojda and Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #150 by katiep
Decentralization Nakamoto coefficient changes for subnet yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe:
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 -> 5.00 (+67%)
Mean Nakamoto comparison: 4.67 → 5.00 (+7%)
Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.1991 to 2.3219
Details
Nodes removed:
6f7g4-miwmh-hbks4-ecx4e-hgxyr-ylhdh-slh2y-wivah-ydt24-uvflm-2ae[health: healthy]7mwzk-chbqh-ydgzb-j3bvh-3l7fh-xc7xm-aud2g-hxyx2-bqcop-st67c-dae[health: healthy]
Nodes added:
fxdqu-epq5z-kmnok-ch46f-jxujv-of7ws-3ec4b-gszap-gtklj-sxfiv-wae[health: healthy]r5zha-ytiej-livta-dgmfr-j6kma-rdl4t-hldjg-hbydh-ogyjt-fow5r-4qe[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 br1 0 -> 1 Africa Data Centres 1 Brussels Capital 0 -> 1 BE 0 -> 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 Central Tower DC 1 Bucuresti 1 CA 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 -> 0 fr2 1 Cloud9 0 -> 1 Florida 1 -> 0 CH 2 -> 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 ge1 1 -> 0 Cyxtera 1 Gauteng 1 DE 1
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hu1 1 Digital Realty 1 Geneva 1 -> 0 GE 0 -> 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb2 1 Equinix 1 Hesse 1 IN 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 kr1 1 Everyware 1 Maribor 1 KR 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 0 -> 1 mb1 1 HighDC 1 -> 0 Navi Mumbai 1 PL 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 mm1 1 -> 0 KT 1 Ontario 1 RO 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 nm1 1 M247 1 Seoul 1 SG 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 sg1 1 Posita.si 1 Singapore 1 SI 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 0 -> 1 tb1 0 -> 1 Rivram 1 Tbilisi 0 -> 1 US 2 -> 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 to2 1 TRG 1 Texas 1 ZA 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 wa2 1 Telin 1 Warszawa 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 -> 0 zh2 1 Zurich 1
1 Like
A new proposal with id 134915 has been submitted, please take a look.
Click here to open proposal details
Replace nodes in subnet yinp6
Motivation:
The following nodes in subnet yinp6 have been cordoned and need to be removed from the subnet:
- 6f7g4: offboarding MM1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #49 by GiantLeaf and Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #103 by katiep
- 7mwzk: offboarding the second rack of nodes in the GE1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #148 by Gwojda and Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #150 by katiep
Decentralization Nakamoto coefficient changes for subnet yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe:
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 -> 5.00 (+67%)
Mean Nakamoto comparison: 4.67 → 5.00 (+7%)
Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.1991 to 2.3219
Details
Nodes removed:
6f7g4-miwmh-hbks4-ecx4e-hgxyr-ylhdh-slh2y-wivah-ydt24-uvflm-2ae[health: healthy]7mwzk-chbqh-ydgzb-j3bvh-3l7fh-xc7xm-aud2g-hxyx2-bqcop-st67c-dae[health: healthy]
Nodes added:
fxdqu-epq5z-kmnok-ch46f-jxujv-of7ws-3ec4b-gszap-gtklj-sxfiv-wae[health: healthy]r5zha-ytiej-livta-dgmfr-j6kma-rdl4t-hldjg-hbydh-ogyjt-fow5r-4qe[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 br1 0 -> 1 Africa Data Centres 1 Brussels Capital 0 -> 1 BE 0 -> 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 Central Tower DC 1 Bucuresti 1 CA 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 -> 0 fr2 1 Cloud9 0 -> 1 Florida 1 -> 0 CH 2 -> 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 ge1 1 -> 0 Cyxtera 1 Gauteng 1 DE 1
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hu1 1 Digital Realty 1 Geneva 1 -> 0 GE 0 -> 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb2 1 Equinix 1 Hesse 1 IN 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 kr1 1 Everyware 1 Maribor 1 KR 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 0 -> 1 mb1 1 HighDC 1 -> 0 Navi Mumbai 1 PL 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 mm1 1 -> 0 KT 1 Ontario 1 RO 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 nm1 1 M247 1 Seoul 1 SG 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 sg1 1 Posita.si 1 Singapore 1 SI 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 0 -> 1 tb1 0 -> 1 Rivram 1 Tbilisi 0 -> 1 US 2 -> 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 to2 1 TRG 1 Texas 1 ZA 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 wa2 1 Telin 1 Warszawa 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 -> 0 zh2 1 Zurich 1
2 Likes
Proposal 134915 Review | LORIMER Known Neuron
VOTE: YES
TLDR: Some decentralisation stats are improved, some worsened. The key ones are unchanged. There is a clear public declaration for each cordoned node which is referred to in the proposal summary.
2 cordoned nodes replaced with healthy nodes in Belgium and Georgia.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 95.554 km | 6561.363 km | 16518.328 km |
| PROPOSED | 0 km (-100%) | 5924.704 km (-9.7%) | 15986.483 km (-3.2%) |
This proposal reduces decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical reduction in localised disaster resilience). 
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 4 | 11 | 13 | 13 | 13 | 13 |
| PROPOSED | 4 | 12 (+8.3%) | 13 | 13 | 13 | 13 |
This proposal improves decentralisation in terms of jurisdiction diversity. 
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 | 7 | 2 | 1 | 1 | 1 | 1 |
| PROPOSED | 7 | 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)
Node Changes
| Action | Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|---|
| Remove |  |
||||||||
| Remove | |
||||||||
| Add | fxdqu | UNASSIGNED | |
Europe | Belgium | Brussels (br1) | Digital Realty | Allusion | mjeqs |
| Add | r5zha | UNASSIGNED | |
Asia | Georgia | Tbilisi 1 (tb1) | Cloud9 | George Bassadone | yhfy4 |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| d46vh | UP | |
Europe | Belgium | Seoul 3 (kr1) | KT | Pindar Technology Limited | iubpe |
| 2sjsi | UP | |
Americas | Canada | Toronto 2 (to2) | Cyxtera | Blockchain Development Labs | 4lp6i |
| rp2ka | UP | |
Europe | Switzerland | Zurich 2 (zh2) | Everyware | DFINITY Stiftung | s7dud |
| kvj4i | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| 25a7h | UP | |
Asia | India | Navi Mumbai 1 (nm1) | Rivram | Rivram Inc | mpmyf |
| mswad | UP | |
Europe | Poland | Warszawa 2 (wa2) | Central Tower DC | Bohatyrov Volodymyr | ygsal |
| kxmey | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| k6zrw | UP | |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
| mp3w3 | UP | |
Europe | Slovenia | Maribor (mb1) | Posita.si | Fractal Labs AG | 3xiew |
| 6pt6z | UP | |
Americas | United States of America (the) | Houston (hu1) | TRG | 43rd Big Idea Films | fthz3 |
| ulcre | UP | |
Africa | South Africa | Gauteng 2 (jb2) | Africa Data Centres | Karel Frank | bm2lc |
*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)
- CodeGov (actively reviews and votes on Subnet Management proposals, and is well informed on numerous other technical 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.
2 Likes
Proposal 134915 | Tim - CodeGov
Vote: Adopt
This proposal replaces nodes 6f7g4 and 7mwzk for the respective stated reasons “offboarding MM1 DC after 48 months” and “offboarding the second rack of nodes in the GE1 DC after 48 months”. Node 7mwzk is listed to be handed over in this post. 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 #134915 — Zack | CodeGov
Vote: Adopted
Reason:
The proposal replaces 2 cordoned healthy Active status node 6f7g4 from Miami and healthy Active status node 7mwzk from Geneva, with
unassigned healthy Awaiting status node fxdqu from Brussels and unassigned healthy Awaiting status node r5zha from Georgia. This improves the decentralization of the subnet.
The motivation makes sense and the provided Forum link included in the summary provides further info.
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 134915 – LaCosta | CodeGov
Vote: ADOPT
Replaces cordoned nodes 6f7g4 and 7mwzk with nodes fxdqu and r5zha on subnet yinp6.
The reason for this proposal is to offboard GE1 and MM1 DCs 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 and forum post match the ones from the node being removed in the proposal.
The GE1 node being removed was also stated here.
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
Replace a node in subnet yinp6
Motivation:
The following nodes in subnet yinp6 have been cordoned and need to be removed from the subnet:
- mp3w3: offboarding the second rack of nodes in the mb1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #152 by g_fractal
Decentralization Nakamoto coefficient changes for subnet yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe:
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:
mp3w3-ut6qr-ef4ax-cwxtg-kkdly-q2xpl-4bisk-vjncp-qcyfy-5t4uz-vqe[health: healthy]
Nodes added:
7tayv-2pmqc-gaiwu-3kd3h-fh4qh-3moqd-aawsb-4rq6o-ui7fp-dofcu-iqe[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 br1 1 Africa Data Centres 1 Brussels Capital 1 BE 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 Central Tower DC 1 Bucuresti 1 CA 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 fr2 1 Cloud9 1 Gauteng 1 CH 1
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hu1 1 Cyxtera 1 Hesse 1 DE 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb2 1 Digital Realty 1 Maribor 1 GE 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 kr1 1 Equinix 1 Navi Mumbai 1 IN 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 mb1 1 Everyware 1 Ontario 1 KR 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 nm1 1 KT 1 Seoul 1 PL 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 sg1 1 M247 1 Singapore 1 RO 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 tb1 1 Posita.si 1 Tbilisi 1 SG 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 to2 1 Rivram 1 Texas 1 SI 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 wa2 1 TRG 1 Warszawa 1 US 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 zh2 1 Telin 1 Zurich 1 ZA 1
1 Like
A new proposal with id 134986 has been submitted, please take a look.
Click here to open proposal details
Replace a node in subnet yinp6
Motivation:
- replacing cordoned node mp3w3 (offboarding the second rack of nodes in the mb1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #152 by g_fractal)
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 yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe:
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:
mp3w3-ut6qr-ef4ax-cwxtg-kkdly-q2xpl-4bisk-vjncp-qcyfy-5t4uz-vqe[health: healthy]
Nodes added:
jthcr-uruul-ytxuj-qbvv2-byyz2-tyyo4-yy4ku-2fu4d-aufm7-d5k6l-7ae[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 br1 1 Africa Data Centres 1 Brussels Capital 1 BE 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 Central Tower DC 1 Bucuresti 1 CA 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 fr2 1 Cloud9 1 Gauteng 1 CH 1
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hu1 1 Cyxtera 1 Hesse 1 DE 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb2 1 Digital Realty 1 Maribor 1 GE 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 kr1 1 Equinix 1 Navi Mumbai 1 IN 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 mb1 1 Everyware 1 Ontario 1 KR 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 nm1 1 KT 1 Seoul 1 PL 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 sg1 1 M247 1 Singapore 1 RO 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 tb1 1 Posita.si 1 Tbilisi 1 SG 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 to2 1 Rivram 1 Texas 1 SI 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 wa2 1 TRG 1 Warszawa 1 US 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 zh2 1 Telin 1 Zurich 1 ZA 1
2 Likes
Proposal 134986 | Tim - CodeGov
Vote: Adopt
This proposal replaces node mp3w3 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 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 134986 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 the same data centre.
As a side note - there is an IP address-related country discrepancy for this subnet (though unaffected by this proposal). Expand Country Discrepancies section below for more info.
Country Discrepancies (1)
| Node | Data Center | Claimed Country | According to api.ip2location.io |
According to ip-api.com |
According to domain WHOIS lookup |
|---|---|---|---|---|---|
| d46vh | Seoul 3 | Korea (the Republic of) | Belgium | China | China |
Geolocation for the d46vh node’s IP address places it in Belgium according to one provider, and in China according to two others. Note that there’s already another node in this subnet that’s located in Belgium (same location). This seems very odd to me. @SvenF are you able to shine a light on what’s happening here? It seems odd that by shear chance the IP address (according to one geolocation provider) puts this node at the same location as another node in this subnet, which is indeed expected to be in belgium (different NP and DC though). @MalithHatananchchige, you’re also knowledgeable with this sort of thing. Do you have any thoughts?
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 305.949 km | 6629.866 km | 16014.122 km |
| PROPOSED | 305.949 km | 6629.866 km | 16014.122 km |
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 4 | 13 | 13 | 13 | 13 | 13 |
| PROPOSED | 4 | 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 | 6 | 1 | 1 | 1 | 1 | 1 |
| PROPOSED | 6 | 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)
-
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 | |
||||||||
| Add | jthcr | UNASSIGNED | |
Europe | Slovenia | Maribor (mb1) | Posita.si | Fractal Labs AG | 3xiew |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| fxdqu | UP | |
Europe | Belgium | Brussels (br1) | Digital Realty | Allusion | mjeqs |
| 2sjsi | UP | |
North America | Canada | Toronto 2 (to2) | Cyxtera | Blockchain Development Labs | 4lp6i |
| rp2ka | UP | |
Europe | Switzerland | Zurich 2 (zh2) | Everyware | DFINITY Stiftung | s7dud |
| kvj4i | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| r5zha | UP | |
Asia | Georgia | Tbilisi 1 (tb1) | Cloud9 | George Bassadone | yhfy4 |
| 25a7h | UP | |
Asia | India | Navi Mumbai 1 (nm1) | Rivram | Rivram Inc | mpmyf |
| d46vh | UP | |
Asia | Korea (the Republic of) | Seoul 3 (kr1) | KT | Pindar Technology Limited | iubpe |
| mswad | UP | |
Europe | Poland | Warszawa 2 (wa2) | Central Tower DC | Bohatyrov Volodymyr | ygsal |
| kxmey | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| k6zrw | UP | |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
| 6pt6z | UP | |
North America | United States of America (the) | Houston (hu1) | TRG | 43rd Big Idea Films | fthz3 |
| ulcre | UP | |
Africa | South Africa | Gauteng 2 (jb2) | Africa Data Centres | Karel Frank | bm2lc |
*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.
2 Likes
@Lorimer Yes what you have found is true, yet this can be done due to different reasons
inet6num: 2a0c:b641:b20::/44
netname: CN-TANZHANG-20231117
country: CN
admin-c: PN5569-RIPE
tech-c: PN5569-RIPE
status: ALLOCATED-BY-LIR
org: ORG-TZ18-RIPE
mnt-by: SERVPERSO-MNT
mnt-by: PindarNOC-MNT
created: 2023-11-19T14:36:07Z
last-modified: 2023-11-19T14:36:07Z
source: RIPE
organisation: ORG-TZ18-RIPE
org-name: Tan Zhang
country: CN
org-type: OTHER
address: Yin xiang li, Wen Hua Xin Da Jie Room 209,Building D Beijing 100028, Beijing CN
abuse-c: AM51239-RIPE
mnt-ref: PindarNOC-MNT
mnt-by: PindarNOC-MNT
mnt-ref: SERVPERSO-MNT
mnt-by: SERVPERSO-MNT
created: 2023-11-19T14:35:04Z
last-modified: 2023-11-19T14:35:04Z
source: RIPE # Filtered
role: Pindar NOC
address: 4M, Dynasty Plaza, No. 411-417, Alameda Dr. Carlos d?Assumpcao, Macao
nic-hdl: PN5569-RIPE
abuse-mailbox: abuse@pindar.io
mnt-by: PindarNOC-MNT
created: 2023-11-17T10:01:37Z
last-modified: 2023-11-17T10:15:19Z
source: RIPE # Filtered
route6: 2a0c:b641:b20::/44
origin: AS215969
mnt-by: SERVPERSO-MNT
mnt-by: PindarNOC-MNT
created: 2023-11-20T17:07:13Z
last-modified: 2023-11-20T17:07:21Z
source: RIPE
The ASN data shows Pindar as the maintainer, registered under a Chinese organization (Tan Zhang). As shown in the NP self declaration address it is in fact maintained by Pindar
As per Pindar’s network presence, they appear to manage nodes in South Korea and Hong Kong. Therefore, it is logical and cost-effective to use BGP transit from these locations rather than purchasing new IP blocks. (Logical assumption)
Link to Servperso Systems and Tunnel Peering
According to BGP.tools, the parent of this IPv6 prefix (2a0c:b641:b21::/48 ) is Servperso Systems, based in Belgium. This explains why older databases may indicate Belgium as the origin location. You can see this here:
https://bgp.tools/prefix/2a0c:b641:b21::/48#asinfo
Servperso Systems provides tunnel peering services, which enables them to allocate and deliver IP subnets to clients like Pindar across different regions.
Evidence Supporting Seoul as the Location:
As seen here AS215969 Tan Zhang - bgp.tools
AS20473 (Vultr) is an Upstream Provider:
Vultr has a well-documented presence in Seoul, South Korea.
Since AS215969 (Tan Zhang/Pindar NOC) peers with AS20473 for connectivity, the node could logically be using Vultr’s Seoul PoP for routing.
I know that there is no clean quick way to check IP validity via IP tools as BGP is more complex routing. We can inquire NP and upstream provider to verify this infomation.
3 Likes
Thanks @MalithHatananchchige for the super detailed response! Awesome insights. Out of interest, how easy do you think it would be for a country to make it look as though nodes in that country actually reside in another country?
I’m interested in automating this sort of analysis. The next thing I’m thinking of doing is only flagging this up as an anomaly if the majority of geolocation databases agree on the discrepancy. In this case only one of the databases indicated Belgium.
3 Likes
Thats true and your IP geolocation mismatch is helpful, my analysis does not prove that the node is in a physical location as mention on the ICP dashboard, just a logical assumption. It is in fact a tunnel scenerio as the parent does this as a service. This can be flaged for further transparency from NP? I think in one of the NP workgroup we discuss on validating the actual physical location of a node than where it is advertised on ICP. One is to run latency test via local ISP to see if there is a difference. There was no solid methods so I think it was paused for later discussion. I think its fair to provide transparency on this, Good Catch!
3 Likes
Thanks for the context @MalithHatananchchige 
Here’s another case, but in this one every database I checked disagrees with what IC records claim → Subnet Management - uzr34 (II) - Governance / NNS proposal discussions - Internet Computer Developer Forum (see Country Discrepancies (2) section)
If a node’s physical location can be easily spoofed, it sort of calls into question the effort that goes into checking decentralisation coefficients 
1 Like
Proposal #134986 — Zack | CodeGov
Vote: Adopted
Reason:
The proposal replaces cordoned healthy Active status node mp3w3 in the MB1 DC from Slovenia, with unassigned healthy Awaiting status node jthcr from same DC and NP without any chnge to decentralization.
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
@geeta23, can I ask if your node referred to above is located in Columbia or Costa Rica? aajth
@tina23, can I ask if your node referred to above is located in Panama or the US? y7bml
You have very interestingly similar names. Do you mind me asking if that’s by coincidence or are your names following a common convention or something?
1 Like