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

Hello everyone! I just noticed that I missed this forum post!
This means that MM1 will be offboarded/sold, as this is the other DC that GiantLeaf owns. We will reference these posts in proposals.

3 Likes

Hello everyone,

Here is my cross post. Please find the necessary information regarding our nodes under the new remuneration structure.

Self-Declaration Link: BLP22, LLC

Node Count: 14 under the new remuneration structure

Data Center: AT2

Node Deployment Confirmation: Two nodes have been deployed with IPv4 addresses and domain names in this data center.

Start Date for New Reward Values: Feb 1, 2025

Contact Information: Element/Matrix - @blporteratl1:matrix.org

Let me know if you have any questions.

Kind regards,

2 Likes

Proposal 134672 – LaCosta | CodeGov

Vote: ADOPT

The proposal sets rewards for 19 nodes controlled by the newly created NO dvfhx for DC pl1 (see proposal 134660) from NP Uvaca Labs LLC.
All the nodes fit the requirements to be added (belong to the NP, NO and DC provided)

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.

2 Likes

Proposal 134675 Review | Louise - Aviate Labs

Vote: REJECT
Review:

  • This proposal aims to update the 28 nodes belonging to NP Iancu Aurel to the reward configuration type 1.1. This is inline with the steps Gen-1 NPs must follow.
  • However, the Node Provider ID was used instead of the Node Operator ID
  • Furthermore, the proposal links to the wrong forum post.
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, 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.

2 Likes

Proposal 134699 Review | Louise - Aviate Labs

Vote: REJECT
Review:

  • This proposal seems to have the identical payload to proposal 134675.
  • It does however have the correct link to the Forum
  • However, the Node Operator ID should be included in the payload and not the Node Provider ID, I vote to reject this proposal.
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, 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.

2 Likes

Proposal 134700 Review | Louise - Aviate Labs

Vote: ADOPT
Review:

  • Thanks for updating the proposal @mabalaru !
  • This proposal will update the reward configuration for the nodes in bu1, belonging to the node provider Iancu Aurel such that it uses the type1.1 reward scheme (the remuneration scheme for Gen-1 NPs after 48 months.)
  • This is inline with the steps for NPs to transition their gen-1 nodes to the post-48-month reward configuration. A forum post detailing the steps can be found here.
  • All of the node IDs mentioned on the payload are present on the dashboard as well under NP and DC ID.
  • Given the reasons above, 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 Monitor tool, 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.

2 Likes

Proposal #134666, #134667, #134672 Review | Roald - Aviate Labs

Proposal #134666

Vote: ADOPT

  • Proposal is part of the HSM-less transition steps for 87m Neuron.
  • Node Allowance: setting rewards for 8.
  • Node IDs: All 8 IDs in the proposal are valid, check at https://dashboard.internetcomputer.org/node/insert node id

Proposal #134667

Vote: ADOPT

  • Proposal is part of the HSM-less transition steps for 87m Neuron.
  • Node Allowance: setting rewards for 19.
  • Node IDs: All 19 IDs in the proposal are valid, check at https://dashboard.internetcomputer.org/node/insert node id

Proposal #134672

Vote: ADOPT

  • Proposal is part of the HSM-less transition steps for Uvaca Labs LLC.
  • Node Allowance: setting rewards for 19.
  • Node IDs: All 19 IDs in the proposal are valid, check at https://dashboard.internetcomputer.org/node/insert node 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, 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.

2 Likes

Proposal 134675, 134699, 134700 Review | Roald - Aviate Labs

Proposal 134675

Vote: REJECT
Review:

  • About this proposal: update the 28 nodes belonging to NP Iancu Aurel to the reward configuration type 1.1.
    Rejected based on:
  • Node Provider ID used instead of the Node Operator ID

Proposal 134699

Vote: REJECT
Review:

  • About this proposal: same as Proposal 134675, update the 28 nodes belonging to NP Iancu Aurel to the reward configuration type 1.1.
    Rejected based on:
  • Node Provider ID used instead of the Node Operator ID

Proposal 134700

Vote: ADOPT
Review:

  • the proposal updates the reward configuration of these nodes to type1.1, further context here
  • correct Node Operator ID was used c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
  • all nodes in proposal are present in bu1 belonging to the correct 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, 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.

2 Likes

Proposal #134675 — Zack | CodeGov

Vote: Rejected

Reason:
Instead of the node_operator_id the node_provider_id was used by mistake.

Proposal #134699 — Zack | CodeGov

Vote: Rejected

Reason:
Duplicate of the previous proposal.

Proposal #134700 — Zack | CodeGov

Vote: Adopted

Reason:
The proposal from NP Iancu Aurel sets rewardable_nodes to 28 nodes.
The NO ID c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae is correct and all the listed node ID’s with type1.1:28 are correct in the BU1 DC.

About CodeGov (click to expand).

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.

2 Likes

Proposal Reviews | Quint - Aviate Labs

Proposal #134672

Vote: ADOPT

  • Node Allowance: NP (dvfhx-...) setting rewards for 19.
  • Node IDs: All 19 IDs in the proposal are valid.
  • All Nodes have status ‘Awaiting’.

Proposal #134675

Vote: REJECT

  • NP ID instead of NO ID.

Proposal #134699

Vote: REJECT

  • Duplicate of #134675.

Proposal #134700

Vote: ADOPT

  • Updates reward configuration for nodes in bu1 (Node Operator ID: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae) to the type1.1 reward scheme for Gen-1 NPs post-48 months.
  • Aligns with transition steps for Gen-1 NPs as detailed in the forum.
  • All node IDs match the NP - and DC 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, 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.

2 Likes

Proposal Reviews | Tim - CodeGov

Proposals 134675 & 134699

Vote: Reject

These two proposals are identical except for the included links (which are wrong in the case of proposal 134675) and are intended to set rewardable_nodes for the given node operator to 28. However, the proposal payloads incorrectly contain the node provider ID instead of the node operator ID.

Proposal 134700

Vote: Adopt

This proposal is a correction of the previous 2 proposals and sets rewardable_nodes for node operator c5ssg to 28. As seen in the dashboard for the relevant node provider, Iancu Aurel, there are 28 nodes registered for this node operator ID. The proposal is in keeping with the steps outlined earlier in this thread for reconfiguring Gen1 node machines. I note that the linked forum post gives the data centre owner name in place of the data centre ID, but this does not affect the proposal itself.

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.

3 Likes

Proposals 134714 & 134715 | Tim - CodeGov

Vote: Adopt

These 2 proposals remove node operators sambh and it7v7 respectively. Using the ic-admin tool I verified that the node operator IDs specified in the proposal payloads correspond to the data centres stated in the proposal texts and to the node provider ID for 87m Neuron. In both cases rewardable_nodes = node_allowance, indicating that there are no longer any currently registered nodes attached to these node operators. The proposal is in keeping with the steps outlined earlier in this thread for reconfiguring Gen1 node machines.

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.

3 Likes

Proposal 134675 – LaCosta | CodeGov

Vote: REJECT

The proposal aims to set rewards for 28 nodes controlled by a specific NO. But the payload is incorrect since it used the NP ID in the field node_operator_id

Proposal 134699 – LaCosta | CodeGov

Vote: REJECT

Duplicate of proposal 134675 with the same problem.

Proposal 134700 – LaCosta | CodeGov

Vote: ADOPT

Duplicate from proposals 134699 and 134700 but with the playload’s field node_operator_id now correct with Node Operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae.
The proposal sets rewards for 28 nodes controlled by the newly created NO c5ssg for DC bu1 from NP Iancu Aurel.
All the nodes fit the requirements belonging to the NO in the payload, NP and DC.

Proposal 134714 – LaCosta | CodeGov

Vote: ADOPT

Removes the Node Operator sambh from NP 87m Neuron, LLC. Using the decentralization tool I verified that no nodes are currently controlled by this Node Operator. All nodes that were controlled by this node in DC dl1 are now controlled by the newly created NO mw64v in proposal 134507. This comes as part of the Steps for Gen-1 Node onboarding after 48 months and a series of proposals and posts on this thread.

Proposal 134715 – LaCosta | CodeGov

Vote: ADOPT

Removes the Node Operator it7v7 from NP 87m Neuron, LLC. Using the decentralization tool I verified that no nodes are currently controlled by this Node Operator. All nodes that were controlled by this node in DC lv1 are now controlled by the newly created NO gsps3 in proposal 134506. This comes as part of the Steps for Gen-1 Node onboarding after 48 months and a series of proposals and posts on this thread.

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.

2 Likes

Proposal #134714 — Zack | CodeGov

Vote: Adopted

Reason:
This follows proposal for node rewards after 48 months and is in line with the related discussion in this forum thread.
The old NO ID sambh-2izbh-p3bex-lamdj-retvw-g2uob-nptqo-bhcng-k6w44-vzenu-5ae that belongs to NP 87m Neuron used in the DL1 DC is being removed.

Proposal #134715 — Zack | CodeGov

Vote: Adopted

Reason:
This follows proposal for node rewards after 48 months and is in line with the related discussion in this forum thread.
The old NO ID it7v7-gb556-xhrhm-aaprs-ou5tu-evlk7-u5u2e-cvl5h-7lw6s-httyn-zqe that belongs to NP 87m Neuron used in the LV1 DC is being removed.


Voted to adopt proposals 134716, 134717, 134718 and 134719 as they are all correct as in they set rewardable type1 nodes to 0.

Adopted proposals 134744 and 134745 as both are correct and set rewardable_nodes to 11 respectively 22 for node operators gsps3 and mw64v.


Adopted proposals 134774 resubmission of 134700 as described and 134782 that correctly adds a new node operator ID for NP Virtual Hive Ltd in line to enable migration to HSM-less re deployment of 28 nodes.

About CodeGov (click to expand).

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.

2 Likes

Hello everyone,

Please find the necessary information regarding our nodes under the new remuneration structure.

  1. Self-Declaration Link: Sygnum - Internet Computer Wiki
  2. Node Count: 42 under the new remuneration structure
  3. Data Centers: zh6, zh7
  4. Node Deployment Confirmation: Two nodes have been successfully deployed with IPv4 addresses and a domain name in each of the specified data centers
  5. Start Date for New Reward Values: Feb 1, 2025
  6. Contact Information: Element/Matrix alias: @sygn:matrix.org

Let us know if you have any questions.

Best regards,

3 Likes

Reference for those who are tracking proposals: This means that ZH5 is being sold, so you will see proposals being submitted to remove subnets for those nodes.

3 Likes

Proposal 134714 Review | Louise - Aviate Labs

Vote: ADOPT
Review:

  • This proposal will remove old NO ID for DL1 DC - sambh-2izbh-p3bex-lamdj-retvw-g2uob-nptqo-bhcng-k6w44-vzenu-5ae
  • This old NO ID belonged to 87m Neuron and as stated on their wiki page, this step is needed as they are preforming the HSM less migration. This is inline with the steps provided in this forum post by DFINITY.
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, 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.

1 Like

Proposal 134715 Review | Louise - Aviate Labs

Vote: ADOPT
Review:

  • This proposal will remove old NO ID for LV1 DC - it7v7-gb556-xhrhm-aaprs-ou5tu-evlk7-u5u2e-cvl5h-7lw6s-httyn-zqe
  • This old NO ID belonged to 87m Neuron and as stated on their wiki page, this step is needed as they are preforming the HSM less migration. This is inline with the steps provided in this forum post by DFINITY.
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, 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.

1 Like

Hi @katiep, @sat and @SvenF ,

I have a question regarding the proposal 134716. Proposal 134716 sets the rewardable nodes (type 1) to 0 for the NO record of NO ID c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae . According to the workflow chart for Gen-1 Node onboarding after 48 months this step is necessary only if the Node Provider has performed an HSM-less migration.


In this case, it appears the Node Provider updated their existing Node Operator record to type 1.1 without undergoing an HSM-less migration, aligning with the leftmost path of the chart.

Therefore, setting the rewardable nodes (type1) to 0 may not be required. To maintain consistency with the chart, I would vote to reject this proposal. However, if there are additional considerations or updates to the process that necessitate this step (and I assume so as this proposal was submitted by DFINITY), could you kindly elaborate so the other reviewers are aware, as well as update the documentation so that NPs are aware too.

Thanks a lot!

cc @timk11 @LaCosta @ZackDS @roald-av8 @quint

3 Likes

Proposal 134717 Review | Louise - Aviate Labs

Vote: ADOPT
Review:

  • This proposal will set rewardable nodes - type 1 to 0 for the old NO ID for LV1 DC - it7v7-gb556-xhrhm-aaprs-ou5tu-evlk7-u5u2e-cvl5h-7lw6s-httyn-zqe
  • This old NO ID belonged to 87m Neuron and as stated on their wiki page, this step is needed as they are preforming the HSM less migration. This is inline with the steps provided on the wiki.
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, 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.

2 Likes