Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months

Governance NNS proposal discussions
,
328

Proposal Reviews | Tim - CodeGov

Proposal 135569
Vote: Adopt
This proposal sets rewardable_nodes for node operator d4bin to 26. As seen using the decentralization tool, there are currently 27 nodes deployed under this node operator ID, so presumably an additional one has been added since this proposal was submitted.

Proposal 135570
Vote: Adopt
This proposal sets rewardable_nodes for node operator wuhly to 1, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135571
Vote: Adopt
This proposal sets rewardable_nodes for node operator ujq4k to 8, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135586
Vote: Adopt
This proposal sets rewardable_nodes for node operator mw64v to 27, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135587
Vote: Adopt
This proposal sets rewardable_nodes for node operator dvfhx to 27, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135588
Vote: Adopt
This proposal sets rewardable_nodes for node operator spsu4 to 14, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135589
Vote: Adopt
This proposal sets rewardable_nodes for node operator 2rqo7 to 14, corresponding to the number of nodes now deployed under this node operator ID.

Edit: Please see correction below for proposal 135589.

Proposal 135590
Vote: Adopt
This proposal sets rewardable_nodes for node operator gv77f to 24, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135591
Vote: Adopt
This proposal sets rewardable_nodes for node operator stqij to 28, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135596
Vote: Adopt
This proposal sets rewardable_nodes for node operator mjeqs to 28, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135597
Vote: Adopt
This proposal sets rewardable_nodes for node operator oorkg to 14, corresponding to the number of nodes now deployed under this node operator ID.

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.

1 Like
329

Proposal 135545 – LaCosta | CodeGov

Vote: REJECT

The proposal increases the type1.1 rewardable_nodes of Node Operator db7fe from 0 to 14 in order to include 14 nodes in the zh2 DC.

After some consideration due, and to comply with previous reviews and standards set for this proposals, I do agree to await for the nodes to be redeployed under this NO before making 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 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.

1 Like
330

Proposal 135552 – LaCosta | CodeGov

Vote: ADOPT

As part of the Steps for Gen-1 Node onboarding after 48 months, the Node Provider BlockFinance is creating the Node Operator ozfkj to hold 14 nodes in the mb1 DC that are being handed over by NP Fractal Labs AG.
All the required steps were followed:

  1. A Forum post by the buyer NP :white_check_mark:
  2. The self-declaration document was uploaded on the IC Wiki :white_check_mark:
  3. The Node Operator ID proposed is new :white_check_mark:
  4. A statement, published on the IC wiki, signed by both the current and the new node provider :white_check_mark:

Currently the NP has a total of 0 type1.1 nodes which means it can add the proposed 14 nodes and still have a possibility of adding an additional 28 nodes before meeting the maximum number of nodes 42.
NP Fractal Labs AG has currently 28 type1 nodes on DC mb1 controlled by NO 3xiew-2wo3x-tnbn2-o7kok-wwsnw-7koo2-gna5r-rlrt3-zotsh-dwpg6-kae, which matches the number of nodes and DC proposed.

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.

1 Like
331

@sat don’t know if this helps in the resolution of the problem regarding the node_allowance calculations not being subtracted correctly, I’ll use the warning emoji :warning: in order to show which NOs in the following proposals I’ve noticed having this problem

Proposal 135569 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator d4bin from 0 to 26 in order to include 26 nodes in the sg1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 27 nodes from which 26 match the ones mentioned in the proposal.

The Node Operator currently sits at node_allowance_remaining of 1, which still leaves space to add 1 more node and increase the type1.1 rewardable_nodes which will likely happen once the NP redeploys node svosx to this NO. Will be either two or one proposals if the NP chooses to update the rewardable_nodes once the dead node and left node are both ready to be rewardable or not.

Proposal 135570 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator wuhly from 0 to 1 in order to include node svosx from DC sg1.
The node’s Node Operator matches the one from the proposal and the NO already has 1 node which match the ones mentioned in the proposal.

@162DC could you explain why you chose to have two separate NOs, being that one has only one node where you performed ther HSM-less migration and the other doesn’t perform the migration.

Proposal 135571 :warning: – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator ujq4k from 0 to 8 in order to include 8 nodes in the fr2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 8 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 134782 with a node_allowance of 28, and currently sits at 28 after adding 8 nodes instead of 10.

Proposal 135586 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator mw64v from 25 to 27 in order to include 2 more nodes in the dl1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 27 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 134507 with a node_allowance of 28, and currently sits at 1 after adding 27 nodes, which still leaves space to add 1 more node and increase the type1.1 rewardable_nodes.

Proposal 135587 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator mw64v from 24 to 27 in order to include 3 more nodes in the pl1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 27 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 134660 with a node_allowance of 28, and currently sits at 1 after adding 27 nodes, which still leaves space to add 1 more node and increase the type1.1 rewardable_nodes.

Proposal 135588 :warning: – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator spsu4 from 0 to 14 in order to include 14 nodes in the at2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 14 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 135017 with a node_allowance of 14, and currently sits at 14 even after adding 14 nodes.

Proposal 135589 :warning: – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator 2rqo7 from 0 to 27 in order to include 27 more nodes in the or1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 26 with the left over node being in NO redpf from the same NP which match the ones mentioned in the proposal.

With the same justification as proposal 135545, I will await to cast my vote if @GiantLeaf can redeploy the node in question to this NO before the proposal deadline.

The Node Operator was created in proposal 135013 with a node_allowance of 28, and currently sits at 26 even after adding 26 nodes.

Proposal 135590 :warning: – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator gv77f from 0 to 24 in order to include 24 more nodes in the aw1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 25 nodes which 24 match the ones mentioned in the proposal.

The Node Operator was created in proposal 135018 with a node_allowance of 28, and currently sits at 28 even after adding 25 nodes.

The left over node that was included in this proposal was most likely dead or not yet redeployed to this NO at the time of the proposal but is now ready to be included as rewardable, so a further proposal is expected soon.

Proposal 135591 :warning: – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator stqij from 0 to 28 in order to include 28 more nodes in the jv1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 28 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 134929 with a node_allowance of 28, and currently sits at 24 even after adding 28 nodes.

Proposal 135596 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator mjeqs from 0 to 28 in order to include 28 nodes in the br1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 28 nodes which match the ones mentioned in the proposal.

Proposal 135597 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator oorkg from 0 to 14 in order to include 14 nodes in the br2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 14 nodes which match the ones 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 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.

2 Likes
332

Hi @LaCosta , thanks for flagging this. I was able to get this node redeployed. It now has ID “dcl2k-pc3rv-6fia5-dfcla-qovea-3nhkw-6w35x-ee4tm-ss6zm-zmeqe-fae” and has the correct Node Operator record ID.

I hope the community still decides to adopt this proposal seeing as the total rewardable nodes is still 27 and node ID’s change with every redeployment.

The previous node ID of this node was “ad6tc-euwqd-mflr6-rwpc5-pfhvn-vqrq2-oyula-2vdkb-c7bsn-gdrkk-uae”

3 Likes
333

Correction: I made a mistake in this one, probably from rushing a bit to keep on top of the current volume of proposals. The proposal sets rewardable_nodes for this node operator to 27, not 14. From the file I created on 28 Feb using the decentralization tool, I see that there were only 26 nodes attached to this node operator at the time, as pointed out by @LaCosta . I might have voted to reject the proposal if I had not overlooked this, but as explained above by @GiantLeaf this issue has now been rectified. I verified with the same tool that this node operator now has 27 nodes, so at this point I have no objection to adopting the proposal.

2 Likes
334

Proposal Reviews | Tim - CodeGov

Proposal 135604
Vote: Adopt
This proposal sets rewardable_nodes for node operator 5bnm2 to 23, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135605
Vote: Adopt
This proposal sets rewardable_nodes for node operator tcn4t to 12, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135606
Vote: Adopt
This proposal sets rewardable_nodes for node operator kguzs to 25, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135607
Vote: Adopt
This proposal sets rewardable_nodes for node operator gsps3 to 14, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135608
Vote: Adopt
This proposal sets rewardable_nodes for node operator 4lp6i to 26. As seen using the decentralization tool, there are currently 28 nodes deployed under this node operator ID, so presumably 2 more have been added since this proposal was submitted.

Proposal 135609
Vote: Adopt
This proposal sets rewardable_nodes for node operator feb2q to 13 As seen using the decentralization tool, there are currently 14 nodes deployed under this node operator ID, so presumably another one has been added since this proposal was submitted.

Proposal 135610
Vote: Adopt
This proposal sets rewardable_nodes for node operator wrg4t to 27, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135611
Vote: Adopt
This proposal sets rewardable_nodes for node operator k4aor to 14, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135612
Vote: Adopt
This proposal sets rewardable_nodes for node operator z4wll to 14, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135616
Vote: Adopt
This proposal removes node operator dpt4y. As seen using the ic-admin and decentralization tools, the associated node provider Starbase no longer has any nodes attached to this node operator ID.

Proposal 135617
Vote: Adopt
This proposal sets rewardable_nodes for node operator qffmn to 11, corresponding to the number of nodes now deployed under this node operator ID.

Proposal 135618
Vote: Adopt
This proposal sets rewardable_nodes for node operator qxonx to 3, corresponding to the number of nodes now deployed under this node operator ID. I note that the nodes in this and the previous proposal are part way through transitioning to non-HSM deployment, as explained in the previous proposal’s text.

Proposal 135619
Vote: Adopt
This proposal sets rewardable_nodes for node operator vicvb to 27, corresponding to the number of nodes now deployed under this node operator ID.

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.

2 Likes
335

Proposal #135453 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Arceau NP LLC is adding 27 rewardable_nodes to NO xva5m in the CH2 DC in Chicago2.

Proposal #135454 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP 100 Count Holdings is adding 23 rewardable_nodes to NO kguzs in the CH3 DC in Chicago3.

Proposal #135545 — Zack | CodeGov

Vote: Rejected
Reason:
After consensus we agreed that all 14 nodes in the proposal need to be redeployed under this one NO db7fe before resubmitting.

Proposal #135552 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP BlockFinance is adding NO ozfkj for 14 nodes in the MB1 DC in Maribor, as per forum announcement for the excess nodes that were previously managed by Fractal Labs AG.

Proposal #135568 — Zack | CodeGov

Vote: Adopted
Reason:
NP OneSixtyTwo Digital Capital is removing old NO 5mhxl used in the SG3 DC in Singapore. The nodes were handed over to Protocol16.

Proposal #135569 — Zack | CodeGov

Vote: Adopted
Reason:
NP OneSixtyTwo Digital Capital is adding 26 rewardable_nodes to NO d4bin in the SG1 DC in Singapore.

Proposal #135570 — Zack | CodeGov

Vote: Adopted
Reason:
NP OneSixtyTwo Digital Capital is adding 1 rewardable_nodes to NO wuhly in the SG1 DC in Singapore.

Proposal #135571 — Zack | CodeGov

Vote: Adopted
Reason:
NP Virtual Hive Ltd is adding 8 rewardable_nodes to NO ujq4k in the FR2 DC in Frankfurt.

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.

1 Like
336

Proposal 135545 – Louise | Aviate Labs
Vote: REJECT
Review:
The proposal increases type1.1 rewardable nodes from 0 to 14 in the ZH2 DC, but there are currently only 5 nodes listed to that record as per the IC Dashboard.

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 Monitor tool, 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.

2 Likes
337

Proposal 135604 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator 5bnm2 from 0 to 23 in order to include 23 more nodes in the ph1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 23 nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 117653 with a node_allowance of 28, and currently sits at 5 after adding 23 nodes, which still leaves space to add 5 more nodes and increase the type1.1 rewardable_nodes.

Proposal 135605 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator tcn4t from 0 to 12 in order to include 12 more nodes in the st1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 12 nodes which match the ones mentioned in the proposal.

Proposal 135606 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator kguzs from 23 to 25 in order to include 2 more nodes in the ch3 DC.
The node’s Node Operator matches the one from the proposal and the NO has the nodes which match the ones mentioned in the proposal.

The Node Operator was created in proposal 135305 with a node_allowance of 28, and currently sits at 3 after adding 25 nodes, which still leaves space to add 3 more nodes and increase the type1.1 rewardable_nodes.

Proposal 135607 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator gsps3 from 11 to 14 in order to include 3 more nodes in the lv1 DC.
The node’s Node Operator matches the one from the proposal and the NO has the nodes which match the ones mentioned in the proposal.

Proposal 135608 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator 4lp6i from 0 to 26 in order to include 26 nodes in the to2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 26 nodes which match the ones mentioned in the proposal.

Proposal 135609 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator feb2q from 0 to 13 in order to include 13 nodes in the bc1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 13 nodes which match the ones mentioned in the proposal.

Proposal 135610 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator wrg4t from 0 to 27 in order to include 27 nodes in the to1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 27 nodes which match the ones mentioned in the proposal.

Proposal 135611 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator wrg4t from 0 to 14 in order to include 14 nodes in the an1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 14 nodes which match the ones mentioned in the proposal.

Proposal 135612 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator z4wll from 0 to 14 in order to include 14 nodes in the an1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 14 nodes which match the ones mentioned in the proposal.

Proposal 135612 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator z4wll from 0 to 14 in order to include 14 nodes in the an1 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 14 nodes which match the ones mentioned in the proposal.

Proposal 135616 – LaCosta | CodeGov

Vote: ADOPT

Removes the Node Operator dpt4y from NP Starbase. Using the decentralization tool I verified that no nodes are currently controlled by this Node Operator. All nodes that were controlled by this NO in DC ty2 were handed over to the newly created NO pgyq7 from NP Aksinia Stavskaya in proposal 134940.

Proposal 135617 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator qffmn from 0 to 11 in order to include 11 nodes in the sg2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 11 nodes which match the ones mentioned in the proposal.

Proposal 135618 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator qxonx from 0 to 3 in order to include 3 nodes in the sg2 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 3 nodes which match the ones mentioned in the proposal.

Proposal 135619 – LaCosta | CodeGov

Vote: ADOPT

The proposal increases the type1.1 rewardable_nodes of Node Operator vicvb from 0 to 27 in order to include 27 nodes in the sg3 DC.
The node’s Node Operator matches the one from the proposal and the NO already has 27 nodes which match the ones 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 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.

2 Likes
338

Proposal 135586 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator mw64v from 25 to 27 in DL1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under DL1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135587 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator dvfhx from 24 to 27 in order to include 3 more nodes in the PL1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under PL1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135588 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator spsu4 from 0 to 14 in order to include 14 nodes in the AT2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under AT2 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135589 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator 2rqo7 from 0 to 27 in order to include 27 more nodes in the OR1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under OR1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Note that the list of node IDs provided in the summary is not completely accurate, however, there are 27 nodes belonging to this Node Operator record, and the content of the payload is correct. Given that node IDs change with every redeployment, I vote to adopt. For more information, please see this post.

Proposal 135590 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator gv77f from 0 to 24 in order to include 24 more nodes in the AW1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under AW1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135591 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator stqij from 0 to 28 in order to include 28 more nodes in the JV1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under JV1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135596 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator mjeqs from 0 to 28 in order to include 28 nodes in the BR1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under BR1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135597 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator oorkg from 0 to 14 in order to include 14 nodes in the br2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under BR2 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135604 – Louise | Aviate Labs
Vote: Pending
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator 5bnm2 from 0 to 23 in order to include 23 nodes in the PH1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under PH1 data center :yellow_circle: one node is still offline. I will wait to cast my vote until this issue gets resolved.
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135605 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator tcn4t from 0 to 12 in order to include 12 nodes in the ST1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under ST1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135606 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator kguzs from 23 to 25 in order to include 2 additional nodes in the CH3 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under CH3 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135607 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator gsps3 from 11 to 14 in order to include 3 additional nodes in the LV1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under LV1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

Proposal 135608 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator 4lp6i from 0 to 26 in order to include 26 nodes in the TO2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under TO2 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

This NP has an allowance of 28 for this DC, however as 2 of the 28 nodes are currently offline/degraded, the proposal to add these 2 nodes to the type1.1 reward configuration (I assume) will come at a later date.

Proposal 135609 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator feb2q from 0 to 13 in order to include 13 nodes in the BC1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under BC1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

This NP has an allowance of 14 for this DC, however as 1 of the 14 nodes is currently offline, the proposal to add this node to the type1.1 reward configuration (I assume) will come at a later date.

Proposal 135610 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator wrg4t from 0 to 27 in order to include 27 nodes in the TO1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under TO1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

This NP has an allowance of 28 for this DC, however as 2 of the 28 nodes are currently offline/degraded, the proposal to add these 2 nodes to the type1.1 reward configuration (I assume) will come at a later date.

Proposal 135611 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator k4aor from 0 to 14 in order to include 14 nodes in the AN1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under AN1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

node_allowance for this site is 0, indicating this NP has onboarded the maximum amount of nodes they are permitted to for this site.

Proposal 135612 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator z4wll from 0 to 14 in order to include 14 nodes in the AN1 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under AN1 data center :white_check_mark:
  • type1.1 reward configuration is used :white_check_mark:

node_allowance for this site is 0, indicating this NP has onboarded the maximum amount of nodes they are permitted to for this site.

@LaCosta thanks for flagging the proposals with issues with the node_allowance :pray:

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 Monitor tool, 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.

2 Likes
339

Proposal #135586 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP 87m Neuron is Updating config of NO mw64v by adding 2 more rewardable_nodes for a total of 27 in the DL1 DC in Dallas.

Proposal #135587 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Uvaca Labs is Updating config of NO dvfhx by adding 3 more rewardable_nodes for a total of 27 in the PL1 DC in Portland.

Proposal #135588 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Giant Leaf is Updating config of NO spsu4 by adding 14 rewardable_nodes for a total of 14 in the AT2 DC in Atlanta.

Proposal #135589 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Giant Leaf is Updating config of NO 2rqo7 by adding 27 rewardable_nodes for a total of 27 in the OR1 DC in Orlando.

Proposal #135590 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Bigger Capital is Updating config of NO gv77f by adding 24 rewardable_nodes for a total of 24 in the AW1 DC in Allentown.

Proposal #135591 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Rivonia Holdings is Updating config of NO stqij by adding 28 rewardable_nodes for a total of 28 in the JV1 DC in Jacksonville.

Proposal #135596 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Allusion is Updating config of NO mjeqs by adding 28 rewardable_nodes for a total of 28 in the BR1 DC in Brussels1.

Proposal #135597 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Allusion is Updating config of NO oorkg by adding 14 rewardable_nodes for a total of 14 in the BR2 DC in Brussels2.

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.

1 Like
340

Proposal #135604 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP MI Servers is Updating config of NO 5bnm2 by adding 23 rewardable_nodes for a total of 23 in the PH1 DC in Phoenix.

Proposal #135605 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP MI Servers is Updating config of NO tcn4t by adding 12 rewardable_nodes for a total of 12 in the ST1 DC in Sterling.

Proposal #135606 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP 100 Count Holdings is Updating config of NO kguzs by adding 2 more rewardable_nodes for a total of 25 in the CH3 DC in Chicago3.

Proposal #135607 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP 87m Neuron is Updating config of NO gsps3 by adding 3 more rewardable_nodes for a total of 14 in the LV1 DC in Las Vegas.

Proposal #135608 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Blockchain Development Labs is Updating config of NO 4lp6i by adding 26 rewardable_nodes for a total of 26 in the TO2 DC in Toronto.

Proposal #135609 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Blockchain Development Labs is Updating config of NO feb2q by adding 13 rewardable_nodes for a total of 13 in the BC1 DC in Vancouver.

Proposal #135610 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP 0X52 is Updating config of NO wrg4t by adding 27 rewardable_nodes for a total of 27 in the TO1 DC in Toronto.

Proposal #135611 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP NODAO is Updating config of NO k4aor by adding 14 rewardable_nodes for a total of 14 in the AN1 DC in Antwerp.

Proposal #135612 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP DeNoDe is Updating config of NO z4wll by adding 14 rewardable_nodes for a total of 14 in the AN1 DC in Antwerp.

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.

1 Like
341

Proposal #135616 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

This proposal removes the Node Operator record with ID dpt4y of TY2 DC for the Node Provider Starbase. This is part of the steps required for handing over the TY2 site to a new node provider.

  • node_allowance is 28, which is equal to the old amount of type1 rewardable nodes, indicating that this NO ID no longer has any nodes registered to it. :white_check_mark:
  • When checking the IC dashboard, TY2 no longer displays any nodes belonging to Starbase. :white_check_mark:
  • NO record being removed uses type1 reward configuration :white_check_mark:
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 Monitor tool, 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.

342

Proposal 135617 – Louise | Aviate Labs

Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator qffmn from 0 to 11 in SG2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under SG2 data center. :white_check_mark:
  • type1.1 reward configuration is used. :white_check_mark:
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 Monitor tool, 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.

343

Proposal 135618 – Louise | Aviate Labs

Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator qxonx from 0 to 3 in SG2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under SG2 data center. :white_check_mark:
  • type1.1 reward configuration is used. :white_check_mark:

Combining the amount of nodes in this proposal with the amount mentioned in proposal 135167, a total of 14 nodes has been added to the type1.1 reward configuration for SG2 across the two node operator records qffmn and qxonx. This is the maximum amount of nodes permitted to receive rewards on this site.

@sat just wanted to flag that the node_allowance for the qxonx NO record is not displaying correctly. Currently, it shows 14, when normally it would show 11 if 3 nodes are already onboarded using this NO ID.

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 Monitor tool, 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.

344

Proposal 135619 – Louise | Aviate Labs

Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator vicvb from 0 to 27 in SG3 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under SG3 data center. :white_check_mark:
  • type1.1 reward configuration is used. :white_check_mark:
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 Monitor tool, 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.

345

Proposal 135621 – Louise | Aviate Labs

Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator 3nu7r from 0 to 19 in FR2 DC.

  • All node IDs mentioned in the proposal are listed as healthy on the public dashboard under FR2 data center. :white_check_mark:
  • type1.1 reward configuration is used. :white_check_mark:

Note: The rewardable nodes configured here, combined with the amount configured in proposal 135571 is equal to 27. This leaves room for 1 additional node to be added to the reward configuration at a later date as this node is offline based on the IC dashboard.

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 Monitor tool, 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.

346

Proposal #135616 — Zack | CodeGov

Vote: Adopted
Reason:
NP Starbase is removing old NO dpt4y used in the TY2 DC in Tokyo. The nodes were handed over to Aksinia Stavskaya.

Proposal #135617 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP OneSixtyTwo Digital Capital is Updating config of NO qffmn by adding 11 rewardable_nodes for a total of 11 in the SG2 DC in Singapore.

Proposal #135618 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP OneSixtyTwo Digital Capital is Updating config of NO qxonx by adding 3 rewardable_nodes for a total of 3 in the SG2 DC in Singapore.

Proposal #135619 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP OneSixtyTwo Digital Capital is Updating config of NO vicvb by adding 27 rewardable_nodes for a total of 27 in the SG3 DC in Singapore.

Proposal #135621 — Zack | CodeGov

Vote: Adopted
Reason:
In line with node rewards after 48 months for gen1, NP Virtual Hive Ltd is Updating config of NO vicvb by adding 19 rewardable_nodes for a total of 19 in the FR2 DC in Frankfurt.

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.

1 Like
347

Proposal #135623 — Zack | CodeGov

Vote: Rejected
Reason:
No forum post no link in summary and so on.

The first node in the list b74lr belongs to Archery Blockchain SCSp as does the NO yngfj .
To whom it may concern please resubmit the proposal with the required forum post linked in the summary, so that the community can also verify the proposal.

If any of you have the time to chase the NP on Matrix please do so @louisevelayo @timk11 @LaCosta

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.

1 Like