This proposal adds a new node operator ID for node provider 100 Count Holdings LLC. 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. This NP total does not currently have any registered nodes, but will have up to 28 once the nodes owned by MI Servers in data centre CH3 (currently 23) are handed over, 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 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.
This proposal is intended to add a new node operator ID for node provider BlockFinance but gives insufficient detail as to the reason for this change. The proposal states that “[t]he 14 nodes in the mb1 DC fall under the special arrangement to keep the network the same size” but is not stated whether these nodes are being handed over from another node provider, being added anew, or subject to some other arrangement. There may be an opportunity for BlockFinance to add this information in a forum discussion, but ideally the proposal text should contain these details so that it can serve as a source of truth for future reference. Additionally, the proposal text does not contain a link to a forum post. (Or rather, there is a post but a link to it doesn’t appear in the proposal.) This is not an absolute requirement but in this case it could potentially serve as a way to link the additional information back to 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 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.
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 is able to be verified on the Belgian KBO website.
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 & 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.
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 is able to be verified on the Belgian KBO website.
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 & 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.
Reason:
Registers 100 Count Holdings as a Node Provider.
Forum announcement and links to the wiki for the required documents as well as matching hashes were provided in the summary.
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:
NP ‘BlockFinance’ wants to add a NO ozfkj for 14 nodes in the MB1 DC, on one hand I am not familiar with the mentioned “special arrangement to keep the network the same size” ? and also the provided hash matches the uploaded file that is just DATA, and not complete. Proposals shoul be easy to understand by anyone in the community in order to cast a vote, and this one would require a forum post at least.
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 correct. It registers DeNoDe as a Node Provider.
Forum announcement and links to the wiki for the required documents as well as matching hashes were provided in the summary.
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 correct. It registers NODAO as a Node Provider.
Forum announcement and links to the wiki for the required documents as well as matching hashes were provided in the summary.
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.
Hey @borovan, I think there’s some confusion here. I’ve done contracting work for them over the years and continue to maintain the Golang Agent. I don’t have any stake in Aviate Labs or influence over their operations.
Was this not a very recent change (like a few weeks ago)? 28 node machines (the optimal number for maximal rewards per identity) all in one go seems like an absolutely massive investment to come from one person. Are you able to share how much you acquired each node for? Did the funds come out of your own pocket? I’d be concerned that there’s an asset protection strategy taking place here without further details being shared in the open.
I’m also a little frustrated by how probing questions tend to go unanswered on this thread. e.g.
Hey @Lorimer this may not be relevant to your current point, but thought I’d point out for broader understanding that 28 nodes is not the optimal number for maximal rewards for node providers with Gen1 node machines. That would have been the case if the original proposal 127044 for Gen1 nodes were still applicable because it included a reduction factor in the remuneration calculation. However, proposal 127044 was superseded by proposal 132553, which does not include the reduction factor. The remuneration a simple linear function proportional to number of nodes in each country with a cap at 42 nodes. Hence, the maximal rewards based on that proposal is 42 nodes located in countries that are more favorable by the topology (e.g. Singapore, Japan, Slovinia). However, proposal 132553 was superseded recently by proposal 135253 in regards to the optimal node provider rewards. Node providers are now offered a 10% adder over the previous country with the highest remuneration offer if their nodes are moved to a new country that is not on the previous remuneration chart. So as it stands today, the optimal node rewards would be to have 42 nodes located in a country that is not on our data center map today and is not part of the EU. A node provider in the US could earn 35% more remuneration by moving their nodes to a new country that qualifies…assuming that the data center and IP provider costs are the same (which is probably not the case).
Also, Gen2 node providers are subject to a different remuneration schedule that does include a reduction factor. Proposal 110174 was the original Gen2 remuneration model and Proposal 122281 is the current remuneration model. It is possible that 28 nodes is the optimal quantity for Gen2 nodes in some locations, but the reduction factor is different for several different locations, which makes the optimal number of nodes in those locations different.
However, almost all the node transfer that is occurring right now is Gen1 nodes due to the recently imposed 42 node limit and the fact that it was the Gen1 node providers who had over 42 nodes.
FWIW, there are 39 forum users with a handle that ends in 22, 52 that end in 23, 43 that end in 24, and (even though it’s only February of 2025), already 35 that end in 25.
It’s fairly common practice when the handle you want is taken and you’re advised by the system to try adding a number, for people to add the year. (Far safer than using your birth year which is also something that people sometimes revert to.)
Okay, thanks for confirming. They’re all very related to each other (though they’re reluctant to comment about this), and all have strangely chosen to have 23 in their name (for accounts not created in 2023, and even though the username without the 23 has not yet been claimed).
I note that your account is new this year. Do you mind me asking what the 23 denotes in your account name? Why not simply BlockFinance? (which is your actual NP name). I hope you don’t mind me asking.
