Your node_allowance: 0 is zero. Not sure why that is ? it was set to 1 last time I checked.
It was set by proposal 134533 and executed 2024-12-22. And as can be seen :
So I would advise you to wait for a confirmation before submitting it.
Edit let’s jump to Matrix to try and sort this in order to not spam this thread any more. @bitmoon
Please remember that the node allowance is dynamic. Here’s an example:
NP sets the node allowance to 5.
NP onboards 3 nodes.
Node allowance dynamically reduces to 2.
NP onboards 2 more.
Node allowance dynamically becomes 0.
One node has an issue and is removed from the registry.
Node allowance dynamically increases to 1.
NP tries to onboard it, but something goes wrong. The node is in the registry (has a principal on the dashboard), but has an issue still. Node allowance is back to 0.
NP fixes the issue and needs to reonboard again to reinstall the OS.
Here’s where it gets tricky…
If the BMC hasn’t changed and the IPv6 hasn’t changed, then the NP should be able to onboard without doing anything else. The registry should recognize the IPv6, know that it’s the same server, and allow the new registration to replace the old one.
But if something has changed the BMC or the IPv6, then the registry will not know it’s the same server. It will refuse to allow the node to register because the node allowance is 0. In this case, the NP can maually use DFX to remove the registry entry, which will result in the node allowance becoming 1 again.
So this is why the node allowance is back to 0, because all 3 are in the registry.
This NP has an allowance of 28 nodes, and now they are setting rewards for 19 of them.
All of the 19 node IDs mentioned in the proposal do appear on the dashboard.
This proposal is also inline with the steps new NPs must follow if they are taking over the excess nodes from an existing NP.
Given the above information, 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.
This proposal configures rewards for the 2 nodes that were onboarded in LI2 data center
Both node IDs are present on the dashboard, indicating that they have successfully onboarded onto the IC
As the node allowance for the associated NO record is now set to 0, it shows the two nodes have joined successfully. More explanation about how the node allowance works can be found here.
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:
The proposal from NP Bitmoon sets rewardable_nodes for 2 nodes.
The NO ID nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae is correct and both listed node ID’s with type3.1 are correct in the LI2 DC.
Given the fact that the issue before was caused by not using “the right pem file” and “Nothing other has been changed” as confirmed by the NP and after the detailed explanation from Katie about how node allowance behaves in different cases the proposal should execute this time.
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.
Configures rewards for 2 nodes onboarded in the LI2 data center (current rewards: 0).
Node IDs are visible on the dashboard, confirming successful onboarding to the IC.
The NO ID (nvocp-...) is accurate, and both node IDs (type 3.1) in the LI2 DC are correct.
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 sets rewardable_nodes for node operator nvocp to 2. As seen in the dashboard for the relevant node provider, Bitmoon, there are 2 nodes registered for this node operator ID, thus matching the payload details.
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 sets rewardable_nodestype3.1 to 2 for the Node Operator nvocp from Node Provider Bitmoon. The two nodes provided in the proposal summary, 6hqi5 and lh2af, are operated by the given Node Operator so the payload is correct.
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.
This proposal adds Zarety LLC as a node provider. An appropriate forum introduction is provided. Hashes match for the self-declaration and identity documents. Matching information is found in the Delaware Division of Corporations online database.
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 Blue Ant LLC as a node provider. An appropriate forum introduction is provided. Hashes match for the self-declaration and identity documents. Matching information is found in the Delaware Division of Corporations online database.
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.
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:
This proposal follows forum introduction to add Node Provider Blue Ant LLC.
Self-Declaration and Proof of Identity documents, hashes all match.
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 hashes of the Self declaration and Proof of Identity documents match the hashes in the proposal
Although most new NPs that I have reviewed proposals from have uploaded their Proof of Identity as a .pdf this NP chose the .jpg format for this file. In the wiki it states on one hand quote “The documents should be delivered as a PDF file that is digitally signed.” but later it states “The two kinds of documents listed above in a format that is widely available, e.g. PDF. .zip files are not recommended.”. I don’t see any problem with this format and since the SHA-256 checksum for the file matches what is in the proposal, I’ve voted to adopt.
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.