Voted to adopt proposal 134280. 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.
Voted to adopt proposal 134409.
This proposal replaces node dafyf which appears in the dashboard as āStatus: Activeā. As shown in the proposal, decentralisation parameters are unchanged and remain within the requirements of the target topology.
The stated purpose of this change is āoffboarding CH3 DC after 48 monthsā. Removal of the nodes for this purpose is consistent with this post from the node provider, the processes described in the same forum thread and the information in the MI Servers node provider record in the IC dashboard. Additionally, the self-declaration documents provided match the provided hashes. I note that there are 3 other nodes assigned to subnets with the same DC and same NP that will probably also need removal for the same reason.
1 Like
Proposal 134409
Vote: ADOPT
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.
Iāve voted to adopt proposal 134409. Iāve verified that decentralisation coefficients weāre not modified by this proposal. The proposal links directly to what appears to be discussion with the NP about the proposal. However, Iām uncomfortable about adopting a proposal using this sort of evidence (given the ease with which such posts could be forged by the proposer).
Iām currently thinking about starting a discussion, and an associated motion proposal, about how to make this sort of thing more verifiable.
A new proposal with id 134552 has been submitted, please take a look.
Click here to open proposal details
Replace a node in subnet mpubz
Motivation:
The following nodes in subnet mpubz have been cordoned and need to be removed from the subnet:
- rgacz: offboarding SG3 DC after 48 months; New Node Provider Proposals - #581 by 162DC
Decentralization Nakamoto coefficient changes for subnet mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae:
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:
rgacz-r4m53-3mwgy-63dqd-txx4i-o6aw6-5wwdt-eizs3-6lh2z-hxzlv-3ae[health: healthy]
Nodes added:
wz42c-ah6mx-lt7c6-vnqcm-kjnd7-52x65-2yfqw-ibpxs-th23v-7z3hl-qae[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 br2 1 AtlasEdge 1 Brussels Capital 1 AU 1
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bu1 1 Cyxtera 1 Bucuresti 1 BE 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 fr2 1 Datasite 1 Florida 1 CA 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 ge1 1 Digital Realty 1 Geneva 1 CH 2
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 hk1 1 Equinix 1 Hesse 1 DE 1
g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe 1 mb1 1 HighDC 1 HongKong 1 HK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 mn2 1 M247 1 Maribor 1 KR 1
ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe 1 or1 1 Megazone Cloud 1 Melbourne 1 RO 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 sg1 0 -> 1 NEXTDC 1 Ontario 1 SE 1
ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae 1 sg3 1 -> 0 Nine.Ch 1 Seoul 1 SG 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 sh1 1 Posita.si 1 Singapore 1 SI 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 sl1 1 Racks Central 1 -> 0 Stockholm 1 US 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 to2 1 Telin 0 -> 1 Zurich 1
zh4 1 Unicom 1
1 Like
Proposal 134552
TLDR: Iāll adopt. The proposal links directly to what appears to be discussion with the NP about the proposal. Decentralisation stats look good.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) ā
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 0 km | 7280.28 km | 16759.085 km |
| PROPOSED | 0 km | 7280.28 km | 16759.085 km |
Subnet characteristic counts ā
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 4 | 12 | 13 | 13 | 13 | 13 |
| PROPOSED | 4 | 12 | 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 | 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 |  |
||||||||
| Add | wz42c | UNASSIGNED | |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| onv2n | UP | |
Oceania | Australia | Melbourne 2 (mn2) | NEXTDC | Icaria Systems Pty Ltd | l5lhp |
| rhy7d | UP | |
Europe | Belgium | Brussels 2 (br2) | AtlasEdge | Allusion | oorkg |
| 7r7kx | UP | |
Americas | Canada | Toronto 2 (to2) | Cyxtera | Blockchain Development Labs | 4lp6i |
| ag3bm | UP | |
Europe | Switzerland | Geneva (ge1) | HighDC | Archery Blockchain SCSp | yngfj |
| d2ffc | UP | |
Europe | Switzerland | Zurich 4 (zh4) | Nine.Ch | Tomahawk.vc | paxme |
| ked4e | UP | |
Asia | China | HongKong 1 (hk1) | Unicom | Wancloud limited | z6cfb |
| 4rpiz | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| kegk5 | UP | |
Asia | Korea (the Republic of) | Seoul 1 (sl1) | Megazone Cloud | Neptune Partners | ukji3 |
| b3knf | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| yttmc | UP | |
Europe | Slovenia | Maribor (mb1) | Posita.si | Fractal Labs AG | 3xiew |
| 4xhpj | UP | |
Europe | Sweden | Stockholm 1 (sh1) | Digital Realty | DFINITY Stiftung | lgp6d |
| ad6tc | UP | |
Americas | United States of America (the) | Orlando (or1) | Datasite | Giant Leaf, LLC | redpf |
*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.
Voted to adopt proposal #134552.
The proposal replaces cordoned healthy Active status node rgacz from the SG3 Data Center in Singapore 3, with unassigned healthy Awaiting status node wz42c from Singapore 1, 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.
Voted to adopt proposal 134552.
This proposal replaces 1 node, due to offboarding SG3 data centre. Decentralisation parameters are unchanged and remain within the requirements of the target topology. Data centre details are consistent with the links provided in the proposal.
Proposal 134552
Vote: ADOPT
Replaces cordoned node rgacz with node wz42c on subnet mpubz.
The reason for this proposal is to offboard SG3 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.
Thereās an open A new proposal with id 134911 has been submitted, please take a look.
Click here to open proposal details
Replace a node in subnet mpubz
Motivation:
The following nodes in subnet mpubz have been cordoned and need to be removed from the subnet:
- ag3bm: 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 mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae:
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 -> 5.00 (+25%)
Mean Nakamoto comparison: 4.83 ā 5.00 (+3%)
Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2683 to 2.3219
Details
Nodes removed:
ag3bm-tdrfp-kki7m-yfwop-aoc4g-f4sjz-grd33-7zy3x-xq3tr-hpbuh-zqe[health: healthy]
Nodes added:
bfj6y-cmhcf-6fxs7-ku2u4-tucww-b2eej-2dmap-snurk-3yaks-ss7xe-rae[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 br2 1 AtlasEdge 1 Brussels Capital 1 AU 1
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bu1 1 Cyxtera 1 Bucuresti 1 BE 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 fr2 1 Datasite 1 Florida 1 CA 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 -> 0 ge1 1 -> 0 Digital Realty 1 Geneva 1 -> 0 CH 2 -> 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 hk1 1 Equinix 1 Hesse 1 DE 1
g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe 1 mb1 1 HighDC 1 -> 0 HongKong 1 HK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 mn2 1 M247 1 Maribor 1 IN 0 -> 1
ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe 1 or1 1 Megazone Cloud 1 Melbourne 1 KR 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 pl2 0 -> 1 NEXTDC 1 Ontario 1 RO 1
ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae 1 sg1 1 Nine.Ch 1 Panvel 0 -> 1 SE 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 sh1 1 Posita.si 1 Seoul 1 SG 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 sl1 1 Telin 1 Singapore 1 SI 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 to2 1 Unicom 1 Stockholm 1 US 1
zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae 0 -> 1 zh4 1 Yotta 0 -> 1 Zurich 1
2 Likes
Proposal 134911 Review | LORIMER Known Neuron
VOTE: YES
TLDR: Numerous decentralisation stats are improved by this proposal. There is a clear public declaration for the cordoned node which is referred to in the proposal summary.
1 cordoned node replaced with a healthy node in India.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) ā
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 0 km | 7280.28 km | 16759.085 km |
| PROPOSED | 321.16 km (+ā%) | 7572.368 km (+4%) | 16759.085 km |
This proposal increases decentralisation, considered purely in terms of geographic distance (and therefore thereās a slight theoretical increase in localised disaster resilience). 
Subnet characteristic counts ā
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 4 | 12 | 13 | 13 | 13 | 13 |
| PROPOSED | 4 | 13 (+7.7%) | 13 | 13 | 13 | 13 |
This proposal slightly 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 | 6 (-14.29%) | 1 (-50%) | 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 | |
||||||||
| Add | bfj6y | UNASSIGNED | |
Asia | India | Panvel 2 (pl2) | Yotta | Krishna Enterprises | 7rw6b |
Other Nodes
| Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
|---|---|---|---|---|---|---|---|---|
| onv2n | UP | |
Oceania | Australia | Melbourne 2 (mn2) | NEXTDC | Icaria Systems Pty Ltd | l5lhp |
| rhy7d | UP | |
Europe | Belgium | Brussels 2 (br2) | AtlasEdge | Allusion | oorkg |
| 7r7kx | UP | |
Americas | Canada | Toronto 2 (to2) | Cyxtera | Blockchain Development Labs | 4lp6i |
| d2ffc | UP | |
Europe | Switzerland | Zurich 4 (zh4) | Nine.Ch | Tomahawk.vc | paxme |
| ked4e | UP | |
Asia | China | HongKong 1 (hk1) | Unicom | Wancloud limited | z6cfb |
| 4rpiz | UP | |
Europe | Germany | Frankfurt 2 (fr2) | Equinix | Virtual Hive Ltd | 3nu7r |
| kegk5 | UP | |
Asia | Korea (the Republic of) | Seoul 1 (sl1) | Megazone Cloud | Neptune Partners | ukji3 |
| b3knf | UP | |
Europe | Romania | Bucharest (bu1) | M247 | Iancu Aurel | c5ssg |
| wz42c | UP | |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
| yttmc | UP | |
Europe | Slovenia | Maribor (mb1) | Posita.si | Fractal Labs AG | 3xiew |
| 4xhpj | UP | |
Europe | Sweden | Stockholm 1 (sh1) | Digital Realty | DFINITY Stiftung | lgp6d |
| ad6tc | UP | |
Americas | United States of America (the) | Orlando (or1) | Datasite | Giant Leaf, LLC | redpf |
*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 134911 | Tim - CodeGov
Vote: Adopt
This proposal replaces node ag3bm which appears in the dashboard as āStatus: Activeā for the stated reason āoffboarding the second rack of nodes in the GE1 DC after 48 monthsā. This node 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.
2 Likes
Proposal #134911 ā Zack | CodeGov
Vote: Adopted
Reason:
The proposal replaces cordoned healthy Active status node ag3bm from Geneva, with
unassigned healthy Awaiting status node bfj6y from Panvel India. 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 134911 ā LaCosta | CodeGov
Vote: ADOPT
Replaces cordoned node ag3bm with node bfj6y on subnet mpubz.
The reason for this proposal is to offboard the GE1 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.
The 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
@DRE-Team @sat @SvenF @katiep
I see that Dfinity has voted to reject proposal 134911 and held off voting on a few others. Is there some new information that was involved in this decision?
2 Likes
In the internal proposal review we realized that the same nodes are being used in one other proposal: https://dashboard.internetcomputer.org/proposal/134902
The DRE tooling was not checking for this particular type of open proposals and assumed that the nodes are free to be added to other subnets. The execution of the second proposal would have failed with this error but we preferred to stay on the safe side and just reject the proposal, in spite of the 25 ICP that were lost this way.
The code was updated in fix: check for open AddApiBoundaryNodes proposals in network command by sasa-tomic Ā· Pull Request #1228 Ā· dfinity/dre Ā· GitHub
5 Likes
I also perform this check, but Iāve limited this to other open Subnet Management proposals. It didnāt occur to me that nodes can be similarly affected by a non-SM topic. Very interesting, Iāll update the steps I go through to avoid making the same oversight in the future. Thanks @sat
2 Likes
Replace nodes in subnet mpubz
Motivation:
The following nodes in subnet mpubz have been cordoned and need to be removed from the subnet:
- ag3bm: 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
- yttmc: 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 mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae:
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 -> 5.00 (+25%)
Mean Nakamoto comparison: 4.83 ā 5.00 (+3%)
Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2683 to 2.3219
Details
Nodes removed:
ag3bm-tdrfp-kki7m-yfwop-aoc4g-f4sjz-grd33-7zy3x-xq3tr-hpbuh-zqe[health: healthy]yttmc-lxazf-6ctyr-aqchl-g5est-gut4i-qltuy-gds2b-7vhfu-43xey-2qe[health: healthy]
Nodes added:
scjri-zcrz3-27aoo-a2ggm-alu4o-fcu4t-r5jy4-7hdeh-prukj-4cols-qae[health: healthy]2dzst-xscbm-fudmf-67coh-wopas-z46qm-2awcg-d2xjh-xxlnz-ru3pg-rqe[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 br2 1 AtlasEdge 1 Brussels Capital 1 AU 1
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bu1 1 Cyxtera 1 Bucuresti 1 BE 1
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 fr2 1 Datasite 1 Florida 1 CA 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 -> 0 ge1 1 -> 0 Digital Realty 1 Geneva 1 -> 0 CH 2 -> 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 hk1 1 Equinix 1 Hesse 1 DE 1
g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe 1 mb1 1 HighDC 1 -> 0 HongKong 1 HK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 mn2 1 M247 1 Maribor 1 IN 0 -> 1
ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe 1 or1 1 Megazone Cloud 1 Melbourne 1 KR 1
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 pl2 0 -> 1 NEXTDC 1 Ontario 1 RO 1
ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae 1 sg1 1 Nine.Ch 1 Panvel 0 -> 1 SE 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 sh1 1 Posita.si 1 Seoul 1 SG 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 sl1 1 Telin 1 Singapore 1 SI 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 to2 1 Unicom 1 Stockholm 1 US 1
zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae 0 -> 1 zh4 1 Yotta 0 -> 1 Zurich 1
1 Like