Self-declaration and identity documents are uploaded on the IC Wiki.
Hashes of the self-declaration and identity document match the hashes in the proposal.
The identity document matches the format of the PRC Resident Identity Card seen in this and various other examples online.
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, API Boundary API Boundary Node Management, Node Admin and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons' Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
The proposal increases the type1.1 rewardable_nodes of Node Operator ozfkj from 0 to 14 in order to include nodes deployed the jv1 DC.
The node’s Node Operator matches the one in the proposal payload and the NO has the proposed 14 nodes.
This Node Operator was created in proposal 137217 (review), and follows the removal of the Node Operators from NP Rivonia Holdings LLC on proposals 137077 and 137077 that essentially removed the node_rewards relative to the sold nodes.
---- Proposal 137313 ----
The proposal increases the type1.1 rewardable_nodes of Node Operator dmqux from 0 to 13 in order to include nodes deployed the ny1 DC.
The node’s Node Operator matches the one in the proposal payload and the NO has the proposed 13 nodes.
This Node Operator was created in proposal 137216 (review), and follows the removal of the Node Operators from NP Rivonia Holdings LLC on proposals 137077 and 137077 that essentially removed the node_rewards relative to the sold nodes.
---- Both proposals ----
These are also exciting proposals since they are the firsts that followed all the KYC requirements that should be public, please refer to proposal 136573 (Pilot to Assess Node Provider Independence and Improve Decentralization) to verify that the documents provided on the IC Wiki check every box of public disclosure, and also underwent a comprehensive compliance assessment by JayBee which can be seen in their IC Wiki profile.
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 technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron's Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
The proposal registers a new NP Icswitch. The proposal follows the requirements stated here. Also regarding new KYC requirements that should be public please refer to proposal 136573 (Pilot to Assess Node Provider Independence and Improve Decentralization) to verify that the documents provided check every box of public disclosure.
This is a re-iteration from proposal 137251 that was rejected (review). The problems related to missing information in the proposal summary were solved so I’m voting to adopt the proposal.
Thanks @Icswitch for being so collaborative and seeking to improve it’s proposal despite the difficulties.
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 technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron's Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Reason:
The proposal is the 4th and final correct atempt to register Icswitch as a new Node Provider.
Proper Forum introduction.
Self-Declaration, Proof of Identity and Independence documents are uploaded on the IC Wiki.
Hashes of the documents match the hashes in the proposal.
NP id gtdcl-kijoz-5fk3p-acmop-gmocy-nhpeq-a5fay-7q5ol-4lmdk-ldz4m-aqe is new .
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 technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron's Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Reason:
The proposal was submitted before the audit by JayBee, and even so I find the audit to be superficial at best.
According to the documents submitted and the self-declaration, there is no
clear indication at this stage that the Company is engaged in any loan
arrangements, debt financing, or similar financial relationships with other
Node Providers or their respective UBOs.
This way we all could just trust Dfinity to take a look at documents and self-declaration, no need to pay a third party that only looks at this.
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 technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron's Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Proposal #137343 — Louise | Aviate Labs Vote: REJECT Review:
This proposal registers a new NP with principal gtdcl.
Forum Introduction
Self-declaration and proof of identity documents are on the wiki, link is provided to this page in the list of self declarations.
Hashes mentioned in the proposal match what is on the wiki and what I have computed locally. - Hashes were not provided in the proposal summary
While this proposal passes the normal checks, upon reviewing the format of the submitted documents, the documentation does not meet my interpretation of the standard.
Concretely, the contents for the updated Self Declaration and Independence Assessment were proposed and adopted in Proposal 136573. If you review the self-declaration and independence assessment published on this NP’s wiki, you’ll notice that the wording differs significantly from what was adopted.
Why does this matter? The language used in the self-declaration was intentionally and carefully crafted. It was voted on and adopted — allowing each NP to deviate from that standard undermines the purpose of having a declaration in the first place.
Similarly, for the independence assessment: while the motion is still recent and many of us know what questions the answers refer to, for the sake of clarity and transparency for those not involved in reviewing, we should stick to a standard format. For example, a simple “Yes/No” to “Q3” gives no context. Ideally, the entire questionnaire (both the questions and the answers) should be publicly posted.
@Icswitch — this is nothing against you personally. You’ve already submitted many proposals and done a lot of the legwork. The ambiguity in the onboarding process right now isn’t your fault, it’s a result of the current state where rules are still being finalized. With this in mind, I wouldn’t be strongly opposed to the community for voting to adopt this proposal.
That said, I’ve chosen to vote to reject based on principle and my interpretation of what the community agreed to in Proposal 136573. My decision is detail-driven, not personal. If others vote to adopt, I completely understand, as the proposal does pass the formal requirements that exist today.
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, Louise reviews and votes independently on ‘Node Admin’ and ‘Participant Management’ proposals on behalf of the Aviate Labs Neuron.
The Aviate Labs known neuron is configured to follow Louise 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 sets the rewardable_nodes count for the Node Operator 6zkgt-w7agd-kpvte-mia3x-sxucz-u2r7k-vfphb-tyhvv-i6hsm-h2ueo-uqe of Node Provider Decentralized Entities Foundation to 8.
@DEF received allowance to onboard nodes on the es1 data center under proposal 137203, after passing the Node Provider registration in proposal 134015. The current proposal finalizes the onboarding by enabling rewards for the 8 deployed nodes:
I voted to Adopt this proposal because it aligns with the current requirements for node reward activation, maintains transparency and procedural consistency:
The Node Provider was officially registered and later authorized to deploy nodes following the two-step process (registration + onboarding).
The number of nodes (8) matches the count of the nodes onboarded and awaiting for subnet.
Reward activation proposals such as this are a necessary final step after successful registration and onboarding. Given that the requirements have been met, this proposal is consistent with overall requirements.
About Krzysztof Żelazko
Independent reviewer and Governance Lead at ICP Hub Poland. Votes manually on NNS proposals related to decentralization, node operations, and governance integrity. Aims to support transparency and the long-term health of the Internet Computer ecosystem by making fair and well-reasoned decisions.
We would like to propose a new subnet of 13 nodes in Switzerland.
i found this hardware specifications / requirements:
wiki/Node_Provider_Machine_Hardware_Guide#Gen_2_Node_Machine_requirements
are there any newer ones, with gen 4 AMD CPUs? Epic 9xxx Series?
This proposal sets rewardable_nodes to 8 for node operator 6zkgt, corresponding to the number of nodes now deployed under this node operator ID by node provider Decentralized Entities Foundation. Node rewards type type3.1 is consistent with the use of Gen-2 node hardware. @DEF The proposal text should ideally include a link to a forum post for discussion.
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, API Boundary API Boundary Node Management, Node Admin and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons' Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
The proposal increases the type3.1 rewardable_nodes of Node Operator 6zkgt from 0 to 8 in order to include nodes deployed the es1 DC.
The node’s Node Operator matches the one in the proposal payload and the NO has the proposed 8 nodes.
This Node Operator was created in proposal 137203 (review), and follows the removal of the Node Operators from NP Carbon Twelve on proposals 137256 and 137257 that essentially removed the node_rewards relative to the sold 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 technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron's Fund 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, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
