Though this proposal appears to add 14 nodes, the proposer clarified that this is necessary for migrating to the HSM-less deployment method.
There appears to be multiple NO IDs on this site, however all point to the NP DFINITY Stiftung. And as 14 nodes appear under ZH2 on the dashboard under this NP, then the allowance proposed corresponds to this.
Additional Comments
From the NOs listed on the dashboard under ZH2, pi3wm-ofu73-5wyma-gec6p-lplqp-6euwt-c5jjb-pwaey-gxmlr-rzqmk-xqe seems to be the only one with rewardable nodes attached to it, showing: type1:13, indicating 13 Gen1 nodes on this site. I could not seem to find the other NO record that accounts for the 14th node. However, given that this transition will occur, I assume this will be addressed as well.
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.
Though this proposal appears to add 28 nodes, the proposer clarified that this is necessary for migrating the nodes in TY2 DC to the new NP: Aksinia Stavskaya.
The previous Node Operator ID associated with this data center (TY2) shows 28 nodes, matching the allowance proposed in this proposal.
It also lists the NPID of Starbase, which as proposal 134940 states, is the NP from which the excess nodes are coming from.
The old NO ID also verifies that these are Gen-1 nodes as indicated by the "type1": 28 when using ic-admin.
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.
This proposal adds a new node operator ID for node provider Bigger Capital. The node provider ID and data centre ID given in the proposal match the information in the node provider record in the dashboard. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure. The current nodes for this NP total 28, consistent with the agreed maximum of 42 and the statement of intent 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 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.
This proposal adds a new node operator ID for node provider Rivonia Holdings LLC. The node provider ID and data centre ID given in the proposal match the information for data centre JV1 in the dashboard. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure. The current nodes for this NP total 62, which exceeds the agreed maximum of 42 but will come down to 38 once this NP’s 24 nodes in data centre CH2 are sold as per the statement of intent 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 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.
This proposal removes 50 nodes from obsolete node operators ampm3 and ut325 as per the explanation in this post. The list of nodes in the payload corresponds to the full set of nodes from data centres MR1 and BO1, corresponding to the given node operator IDs.
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.
This proposal sets rewardable_nodes to 28 for node operator lgp6d, corresponding to the number of nodes now deployed in the associated data centre SH1 by node provider DFINITY Stiftung.
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.
This proposal removes node operator lz4fy. Using the ic-admin tool it can be seen that this node operator corresponds to node provider 87m Neuron and data centre PL1, in which the node provider no longer has any active 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 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.
This proposal adds a new node operator ID for node provider DFINITY Stiftung. The node provider ID and data centre ID given in the proposal match the information for data centre ZH2 in the dashboard. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure. The current nodes for this NP total 64, which exceeds the agreed maximum of 42 but this total will come down to 42 once this NP’s 22 nodes in data centre MR1 are sold as per the statement of intent 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 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.
Regarding proposal 134925 - I have already voted yes on this proposal. But it appears that the new NO ID being proposed already has a record with the DC ME3.
Will this proposal overwrite that? If so, this proposal should be rejected. If not, I suppose this proposal can be executed but then the NO ID proposed should be removed afterwards. Then a brand new NO ID can be added as these should be unique per DC per NP from what I understand.
Though I have already voted to ADOPT, I would advise the rest of the community reading this post to hold off on voting until this has been clarified.
Apologies for not catching this sooner. I have reviewed similar proposals in the past and it wasn’t part of my work flow to check if the NO ID being proposed is an existing NO ID as given the nature of the proposal, I would just assume it is a new NO ID.
The proposal removes 50 dead nodes from Node Operators ampm3, ut325 and Data Centers MR1 and BO1 according to the following post.
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 sets rewards for 28 nodes controlled by NO lgp6d for DC sh1 from NP DFINITY Stiftung.
All the nodes fit the requirements do be added (belong to the same NP, NO and DC)
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 Node Operator lz4fy from NP 87m Neuron, LLC and DC DL1. The nodes were moved to a new NO mw64v-jynex-7tu52-5a3te-ifbop-nh7y7-w7lno-ymmht-b7fmy-wfhha-gqe as can be seen in this proposal.
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 self-declaration and Proof of Identity documents were uploaded on the IC Wiki
The documents wiki doesn’t provide hashes for validation and this are minor details that DFINITY could improve in order to comply with the same requirements that other NPs have to follow.
Currently the NP has a total of 64 Gen-1 nodes which exceeds the maximum number of nodes by an NP 42 but 22 will be sold from DC MR1 as per the forum post.
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.
Reason:
Both proposals are in line with the HSM-less re deployment and are registering new NO ID’s.
While Node Provider Bigger Capital added the Node Operator ulzfw for 28 nodes in the DC aw1 it was already present and it FAILED with the following errors: [Registry Canister Error. Msg: Key already present: node_operator_record_ulzfw-coqfp-25trq-3lise-ajsop-a4g2h-m5sqr-2mbb4-teame-kgzig-4qe].
NP Rivonia Holdings is adding the Node Operator stqij for 28 nodes in the DC jv1.
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.
These 2 proposals add new node operators ID for node provider Giant Leaf LLC in data centres OR1 and AT1 respectively. The node provider ID and data centre IDs given in the proposals match the information in the node provider record in the dashboard. Identity document hashes match those given in the proposal. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure. The current nodes for this NP total 55, exceeding with the agreed maximum of 42, but this total will come down to 41 once this NP’s nodes in data centre MM1 are sold, in keeping with the statement of intent 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 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.
This proposal adds a new node operator ID for node provider Bigger Capital. The node provider ID and data centre ID given in the proposal match the information in the node provider record in the dashboard. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure. The current nodes for this NP total 28, consistent with the agreed maximum of 42 and the statement of intent here.
This also replaces proposal 134925 which failed due to the proposed node operator ID already being in use, as pointed out by @louisevelayo . Using the ic-admin tool I verified that the newly proposed node operator ID does not already appear in the network.
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.
Currently the NP has a total of 28 type1 nodes from the or1 DC controlled by NO redpf-rrb5x-sa2it-zhbh7-q2fsp-bqlwz-4mf4y-tgxmj-g5y7p-ezjtj-5qe which match the proposed number of nodes and the DC mentioned in the proposal.
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.
Currently the NP has a total of 14 type1 nodes from the at2 DC controlled by NO bmlhw-kinr6-7cyv5-3o3v6-ic6tw-pnzk3-jycod-6d7sw-owaft-3b6k3-kqe which match the proposed number of nodes and the DC mentioned in the proposal.
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.
Currently the NP has a total of 28 type1 nodes from the aw1 DC controlled by NO codio-e5e6p-ol6sn-o3mgw-r7v5p-4jmch-a7exl-7pifz-cw4gn-ah47y-6ae which match the proposed number of nodes and the DC mentioned in the proposal.
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.
