The proposal removes offboarded nodes in DCs AT1, FM1, TP1, SJ1 inline with the following forum post by DFINITY. Except that 3 of this nodes from DC FM1 belong to @NoviSystems and as can been seen here the NP has not intention of removing this nodes.
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 it’s mission at codegov.org.
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 it’s mission at codegov.org.
There’s no point in recreating a data center record with the same GPS details. That’s the only relevant part of the DC record for decentralization calculations. Furthermore, any proposal to remove a data center that’s still referenced by node records should fail due to validation checks in the Registry Canister, which ensures the integrity of the network configuration.
That said, it would make sense to rethink the purpose of a DC record, as it only reflects physical risks, not operational risks.
This proposal aims to remove 106 “offboarded” nodes from four data centers.
Three nodes in DC FM1 were mistakenly included in this proposal. @NoviSystems has confirmed their intention to keep these nodes operational.
For these reasons, I vote to reject this proposal.
not really as of now, but I just followed the latest comments here about making recording time spent a requirement. I agree with the majority and don’t think we should do this. but maybe it makes sense in a case where reviewers think that a task is underfunded in general as you mentioned above (cc @cryptoschindler)
I also agree with that. recording the “real” time spent on the reviews accurately might be tricky.
Reason:
This is the resubmitted proposal 134664 for removing the offboarded nodes from AT1, FM1, TP1, SJ1 in line with the announcement, but this time leaving out the 3 nodes with status Awaiting in the FM1 DC from NP NoviSystems.
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.
Thank you to those who caught the FM1 issues over the weekend. This appears to have been a case where the left hand was unaware of what the right hand was doing.
I was the one handling all the aggregated stuff for the aggregate d nodes in FM1.
Sven was the one handling everything Gen-2 related at the time that Novisystems onboarded.
I was not aware that another NP even had nodes in FM1. I did not know that we had allowed Gen-2 nodes to go in DCs that were already being used. Obviously I could have looked, but I’m dealing with so many records and abbreviations that I did not notice.
Sven has not really been involved in removing these aggregated nodes, so he didn’t realize that I wasn’t aware of Novi’s FM1 nodes!
I did a check to make sure that our proposal included all of the NOs that we had to get rid of, but I did not think to check and make sure that extras weren’t included, because it did not occur to me that there were extra nodes from someone else in FM1! I was just looking at DCs.
So… yeah… that’s what happened, and I’m grateful for the extra eyes who caught we we missed!
The proposal removes offboarded nodes from DCs AT1, FM1, TP1 and SJ1. A previous proposal 134664 was rejected since it included 3 nodes from NP NoviSystems, LLC that were not part of the agreement for Gen-1 nodes. This time the nodes were excluded from the proposal and all the nodes check out.
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.
The proposal removes Gen-1 nodes from DCs AT1, FM1, TP1 and SJ1 that are nearing the end of their 48 month deal.
A previous proposal 134664 explains this in detail. However, it was rejected as it included 3 Gen-2 Nodes, that were not part of the agreement for Gen-1 nodes.
Aviate Labs is a team dedicated to supporting node providers since 2020. Our mission is to make high-performance infrastructure management on the Internet Computer (ICP) as seamless as possible, while adhering to the principles of decentralization.
We are known for our contributions to the ecosystem, including the go-agent and developer work packages on GitHub, as well as the Node Monitortool, which alerts Node Providers as soon as any of their nodes go down.
In the NNS, our team—Roald, Louise, and Quint—reviews and votes independently on ‘Node Admin’ and ‘Participant Management’ proposals. Currently we don’t vote at all on other proposals.
The Aviate Labs known neuron is configured to follow our team for these topics and other trusted entities for broader proposals. We strive to be a credible and reliable Followee, committed to voting on every proposal and supporting decentralization within the ICP ecosystem.
The proposal removes Gen-1 node operator records from DCs AT1, FM1, TP1 and SJ1 that are nearing the end of their 48 month deal.
Between all these sites, all nodes are offline except those belonging to @NoviSystems.
I verified that the NO record of this NP is not included in the proposal.
A previous proposal is off boarding all of the offline nodes.
Given the information above, I vote to adopt
About Aviate Labs
Aviate Labs is a team dedicated to supporting node providers since 2020. Our mission is to make high-performance infrastructure management on the Internet Computer (ICP) as seamless as possible, while adhering to the principles of decentralization.
We are known for our contributions to the ecosystem, including the go-agent and developer work packages on GitHub, as well as the Node Monitortool, which alerts Node Providers as soon as any of their nodes go down.
In the NNS, our team—Roald, Louise, and Quint—reviews and votes independently on ‘Node Admin’ and ‘Participant Management’ proposals. Currently we don’t vote at all on other proposals.
The Aviate Labs known neuron is configured to follow our team for these topics and other trusted entities for broader proposals. We strive to be a credible and reliable Followee, committed to voting on every proposal and supporting decentralization within the ICP ecosystem.
Reason:
This follows proposal 134673 for removing node operators that were operating offboarded nodes from AT1, FM1, TP1, SJ1, in line with the announcement.
The NO ID hoqyg-qkf6b-ulmyi-zfk6z-fuvlo-pekr6-goigz-qweij-xhghd-vibjl-jqe that belongs to NP NoviSystems used for 3 remaining nodes in the FM1 DC is not in the list.
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.
Removes Gen-1 node operator records from DCs AT1, FM1, TP1, and SJ1, nearing the end of their 48-month deal. Follows proposal 134673 and offboards all offline nodes per the announcement.
About Aviate Labs
Aviate Labs is a team dedicated to supporting node providers since 2020. Our mission is to make high-performance infrastructure management on the Internet Computer (ICP) as seamless as possible, while adhering to the principles of decentralization.
We are known for our contributions to the ecosystem, including the Go Agent and developer work packages on GitHub, as well as the Node Monitortool, which alerts Node Providers as soon as any of their nodes go down.
In the NNS, our team—Roald, Louise, and Quint—reviews and votes independently on ‘Node Admin’ and ‘Participant Management’ proposals. Currently we don’t vote at all on other proposals.
The Aviate Labs known neuron is configured to follow our team for these topics and other trusted entities for broader proposals. We strive to be a credible and reliable Followee, committed to voting on every proposal and supporting decentralization within the ICP ecosystem.
Proposal 134673 removes 103 nodes from 4 data centres as per the explanation in this post. The list of nodes in the payload corresponds to the full set of nodes from these 4 data centres, with the exception of 3 nodes owned by NoviSystems LLC, which are unrelated to the 4-year arrangement affecting all the other nodes as clarified earlier in this thread.
Proposal 134692 removes the node operators associated with these 4 data centres. Using the ic-admin tool I verified that all the listed node operator IDs were attached to the 4 data centres concerned and not to any others, and that the list did not include the node operator ID used by NoviSystems.
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.
The proposal removes Node Operators that were operating offboarded nodes from DCs at1, fm1, sj1, and tp1. Using the decentralization tool I confirmed that all the nodes that were removed in proposal 134673 matched all the nodes operated by this Node Operators. Also verified that the NO hoqyg from NP NoviSystems, LLC was not included since this was a problem previously.
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.
(cc 