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

Governance NNS proposal discussions
,
143

Proposal 134782 | Tim - CodeGov

Vote: Adopt

This proposal adds a new node operator ID for node provider Virtual Hive Ltd. The node provider ID and data centre ID given in the proposal match the information for data centre FR2 in the dashboard. Identity document hashes match those given in the proposal. 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. The current nodes for this NP total 28, 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 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.

1 Like
144

Proposal 134716 | Louise - Aviate Labs

Vote: ADOPT
Review:

  • This proposal sets the rewardable nodes for DC bu1, with NO ID c5ssg-... to 0 for the type1 reward configuration. More information here.
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
145

Proposal 134774 | Louise - Aviate Labs

Vote: ADOPT
Review:

  • Two proposals recently modified the configuration of Node Operator c5ssg. Proposal 134700 updated the rewardable_nodes for type1.1 to 28, while proposal 134716 set the rewardable_nodes for type1 to 0.
  • However, since proposal 134716 was executed later, it overwrote the changes made by proposal 134700. This proposal replicates the changes from proposal 134700 to restore its intended updates.
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
146

Proposal #134782 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • Though this proposal appears to add 28 nodes, the proposer clarified that this is necessary for migrating to the HSM-less deployment method. They also committed to deprecating the old record once the nodes in this data center have been onboarded, keeping this aligned with the IC target topology.
  • The previous Node Operator ID associated with this data center (FR2) shows 28 nodes, matching the allowance proposed in this proposal.
  • The old NO ID also verifies that these are Gen-1 nodes as indicated by the "type1": 28 when using ic-admin.
1 Like
147

Proposal Reviews | Quint - Aviate Labs

Proposal #134774

Previous proposals:

Vote: ADOPT
Review:

  • Resubmission of #134700 as described in the proposal.

NOTE: It is a little confusing that a later proposal is to be expected to execute after one that has been submitted before…

Proposal #134782

Proposal adds 28 nodes to enable migration to HSM-less deployment method.

Vote: ADOPT
Review:

  • Proposer committed to deprecating the old record after onboarding new nodes in this data center.
  • Aligns with IC target topology.
  • Previous NO ID (fr2) shows ('type1': 28) nodes, matching the proposal.
1 Like
148

Hello everyone,

Archery Blockchain SCSp sold 42 nodes to Extragone and 14 nodes to Decentralized Entities Foundation.
Extragone will continue to operate the 42 nodes with same node provider ID : 7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe and nodes will be deployed with same HSM key. Rewards will goes to the same principal as before.
Decentralized Entities Foundation will operate the 14 remaining nodes in ge1, and thoses nodes will be deployed in ge1

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

1. Self-Declaration Link: [Extragone - Internet Computer Wiki](https://wiki.internetcomputer.org/wiki/Extragone)
2. Node Count: 42 under the new remuneration structure.
 * from ge2-dll01 to ge2-dll25 + the 3 staging nodes to reinstall. -> 28 nodes
* from ge1-dll01 to ge1-dll14 -> 14 nodes
3. Data Centers: ge1, ge2
4. Node Deployment Confirmation: Two nodes have been successfully deployed with IPv4 addresses and a domain name in each of the specified data centers ge1-dll01 and ge1-dll02 + ge2-dll01 and ge2-dll02
5. Start Date for New Reward Values: Feb 1, 2025
6. Contact Information: Element/Matrix alias: @gwojda:matrix.org, https://matrix.to/#/#ic-node-provider-7ryes:matrix.org

1. Self-Declaration Link: [Decentralized Entities Foundation - Internet Computer Wiki](https://wiki.internetcomputer.org/wiki/Decentralized_Entities_Foundation)
2. Node Count: 42 under the new remuneration structure.
* ge1-dll15 to ge1-dll25 + 3 remaining previous staging nodes -> 14 nodes in total. 
3. Data Centers: ge1
4. Node Deployment Confirmation: Two nodes have been successfully deployed with IPv4 addresses and a domain name in each of the specified data centers ge1-dll15 and ge1-dll16
5. Start Date for New Reward Values: Feb 1, 2025
6. Contact Information: Element/Matrix alias: @gwojda:matrix.org, https://matrix.to/#/#ic-node-provider-7ryes:matrix.org

Edit :
I’m posting this message on behalf of Extragone and Decentralized because I’m the technical person in charge of maintaining the ge1 and ge2 datacenters, and for simplicity’s sake it’s been agreed that I’ll continue to maintain the nodes for the two different companies.

Let us know if you have any questions.

Best regards,

2 Likes
149

Greetings! DFINITY Foundation is adjusting our start date for new Gen-1.1 reward values for SH1 and ZH2 to Jan 1 to align with the calendar year. We will submit the proposal soon.

2 Likes
150

Please note (for community reference) as of this moment, these are the nodes which are in the racks that @Gwojda refers to as dll15-dll25 which are being handed over to Decentralized Entities Foundation.

c2dnc-3ozfd-ew52a-yvmrc-mjyss-edoch-k7cki-f7vzk-zqapg-aw44i-mqe
ag3bm-tdrfp-kki7m-yfwop-aoc4g-f4sjz-grd33-7zy3x-xq3tr-hpbuh-zqe
h5hs5-veobj-ft6ms-fr24y-efxzg-fcidc-s2dbn-pcnke-siz2k-bejcm-uqe
dndht-2fce7-aze7e-coa4j-yvyuw-ut4hw-gn5dj-xvxox-whdhg-txikb-yae
7mwzk-chbqh-ydgzb-j3bvh-3l7fh-xc7xm-aud2g-hxyx2-bqcop-st67c-dae
p5h3q-2pght-vje5y-2jmsf-cmdfi-52txk-qkrux-mnvmj-zzira-nugjd-dae
gtjga-mlpu7-5vz4f-knn5w-i2fea-cy3r4-vq245-ip62r-fosvm-7w3ck-2qe
d52j3-6vwb2-ij2ul-sqxhg-wmck4-bh4ce-eabt4-3eqqx-djb6m-n4sd5-xae
kte5g-iwzok-3epfk-lovgf-cylc5-57lmu-olhwg-w4jsn-dquju-5xun6-uae
tybza-gyple-63wq2-qsgwo-w6fqw-6trwu-awukb-skekh-67bqu-qsoeo-aae
t7u3k-tw44d-sewhz-oyy7d-jvial-tci2j-avcj3-3rayz-7jydr-33scr-yqe

3 Likes
151

Thanks @katiep. Is this mapping held in any public records that can be looked up anywhere?

I really appreciate you listing them out. I expect @Gwojda would have shouted if any of these didn’t match up.

Would it be possible to request NPs to be more explicit about the exact nodes they’re referring to in future declarations? (unless there’s a way of establishing which nodes are being referred to that I’m not aware of :slightly_smiling_face:). This would at least safe you some time having to translate what they’re saying.

152

Hello everyone,

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

  1. Self-Declaration Link: Fractal Labs, LLC - Internet Computer Wiki
  2. Node Count: 42 under the new remuneration structure
  3. Data Centers: lj1 / mb1
  4. Node Deployment Confirmation: IPv4 deployed successfully in lj1, mb1 to be done by end of Jan 2025.
  5. Start Date for New Reward Values: Feb 1, 2025
  6. Contact Information: @gorazd_o:matrix.org

We will be selling 14 Nodes in the Data Center mb1 to the node provider BlockFinance, designated rack mb1-dll15 to mb1-dll28
Node IDs:
tm3pc-2bjsx-hhv3v-fsrt7-wotdj-nbu3t-ewloq-uporp-tacou-lupdn-oae
5w5mf-4b2jl-l5vv7-igktn-en2ra-jkwdn-skhc3-6etg7-qmei3-ijb2c-5ae
65a3w-nbftx-ikuvf-6kgta-fxrza-tye5d-qggwc-4orau-6mt2e-xsszw-4ae
bija4-ybnku-fbggc-n3bqj-hardz-4mr5r-prymh-fripb-msk7h-ilh2n-3ae
yttmc-lxazf-6ctyr-aqchl-g5est-gut4i-qltuy-gds2b-7vhfu-43xey-2qe
oxa4d-pajkk-n7fto-dyfxr-z34x3-7zebw-zdqbq-qxzxp-qg7vk-nhcnx-fae
njsmq-lvuj4-fo325-pt3od-f5zqr-j64dp-u5l6n-kdffj-3gvvr-3rbfa-wqe
n74se-c345d-2jd4b-leuu6-jyvim-vcllk-aahj2-vjpvn-pbpks-xtgy2-4qe
nlghu-pupyy-n5oci-hcqvn-5fvdt-h23ta-gueoi-bkpbn-atazo-sfdlp-nae
xzec6-ujfic-zvupf-3cgro-tqgtp-xi5ss-vtxfz-ycecq-n6jsb-t37nk-vqe
jfryc-owgdd-a7pp4-lao2c-anza2-nryvi-gqkmu-m2moj-4hzai-zfdiy-4qe
mp3w3-ut6qr-ef4ax-cwxtg-kkdly-q2xpl-4bisk-vjncp-qcyfy-5t4uz-vqe
djil5-54fkt-55svu-26a7h-ttflx-dqn6u-3w3j6-zyuwg-cfwuo-7oi46-uae
ou5js-fk2zz-pi2ra-jjavx-2ld2m-3l3rh-asgas-tof7u-gxveo-jf3bz-vqe

Let us know if you have any questions.
Best regards,

Fractal Labs

3 Likes
153

Yes, @Gwojda can confirm if you like, but the dll15-25 that he referred to is an old id/label system that we used at Genesis. It’s not public because it’s been replaced by the IDs that are shown on the dashboard. I suspect that he didn’t realize that voters would want to confirm that DFINITY had a valid reason for moving subnets.

There will be only one other NP who is selling off half a DC, and that is @g_fractal who just posted.

@g_fractal Can you please specify which rack you are selling off (since LJ1 and MB1 currently have 4 racks total with 56 nodes) and include the node IDs that are shown in the dashboard for those nodes?

3 Likes
154

Proposal 134925 – LaCosta | CodeGov

Vote: PENDING

As part of the Steps for Gen-1 Node onboarding after 48 months, the Node Provider Bigger Capital is creating the Node Operator ulzfw to hold 28 nodes in the aw1 DC.
All the required steps were followed:

  1. A Forum post by the NP :white_check_mark:
  2. The self-declaration and Proof of Identity documents were uploaded on the IC Wiki :white_check_mark:
  3. The hashes of the Self declaration and Proof of Identity documents don’t match the hashes in the wiki :x:
    image
  4. Matching information in Australian Business Registry :white_check_mark:

Currently the NP has a total of 28 Gen-1 nodes all in the aw1 DC controlled by NO codio-e5e6p-ol6sn-o3mgw-r7v5p-4jmch-a7exl-7pifz-cw4gn-ah47y-6ae which match the proposed number of nodes and the DC mentioned in the proposal.

@kennethwwu please verify why the Self declaration hash doesn’t match the document uploaded.

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
155

Proposal 134929 – LaCosta | CodeGov

Vote: ADOPT

As part of the Steps for Gen-1 Node onboarding after 48 months, the Node Provider Rivonia Holdings LLC is creating the Node Operator stqij to hold 28 nodes in the jv1 DC.
All the required steps were followed:

  1. A Forum post by the NP :white_check_mark:
  2. The self-declaration and Proof of Identity documents were uploaded on the IC Wiki :white_check_mark:
  3. The hashes of the Self declaration and Proof of Identity documents match the hashes in the wiki :white_check_mark:
    image

Currently the NP has a total of 28 Gen-1 nodes from the jv1 DC controlled by NO wmrev-cdq34-iqwdm-oeaak-f6kch-s4axw-ojbhe-yuolf-bazh4-rjdty-oae which match the proposed number of nodes and the DC 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 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
156

Hi all,

Please find the information regarding the excess nodes that will be transferred to the new Node Provider: 100 Count Holdings, LLC

The signed handover statement, containing the same information as below, can be found here.

28 node machines will be transferred from Existing Node Provider (MI Servers, LLC) to the New Node Provider (100 Count Holdings, LLC). The following details outline the specifics of this transfer:

  1. Data Center Location:
    The 28 excess node machines will be operated by the New Node Provider in the following Data Center(s):
  1. Declaration of Independence:
    Both Existing Node Provider and New Node Provider declare that they do not have any majority control in each other’s operations, financial interests, or governance decisions. Each party operates independently, with no undue influence or control over the other’s activities.
  2. Node Deployment Confirmation:
    This has not been completed yet. However, the Existing Node Provider confirms that this will be completed during the process of redeploying the nodes to the new Node Operator record of the new New Node Provider during the transition period, which is approximately between February 12 and March 15, 2025.
  3. Reward Activation Date:
    The above-mentioned nodes will begin earning the new reward values as of February 1st, 2025.

Let me know if you have any questions.

2 Likes
157

Proposal #134925 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • Though this proposal appears to add 28 nodes, the proposer clarified that this is necessary for migrating to the HSM-less deployment method in their statement on the wiki. Once the nodes have transitioned to the new Node Operator (NO) record, the old one will be deprecated. This keeps aligned with the IC target topology.
  • The DC ID in the proposal matches what is displayed on the dashboard.
  • This data center hosts nodes for the node provider Bigger Capital, with the node provider ID 7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe.
  • The previous NO ID (codio-e5e6p-ol6sn-o3mgw-r7v5p-4jmch-a7exl-7pifz-cw4gn-ah47y-6ae) associated with this data center shows 28 nodes, matching the allowance being proposed. The old NO ID also mentions the same NP ID as stated in the previous point.
  • The old NO ID also verifies that these are Gen-1 nodes as indicated by the "type1": 28, meaning that they are in line with motion proposal 132553 for node rewards after 48 months. This proposal is explained at the beginning of this forum thread.
  • For the reasons above, I vote to Adopt

Additional Comments
As noted by @LaCosta , the hashes appear to be incorrect. However, given that this is not a criteria that is usually checked for this proposal type (referring to this post), I would still vote to adopt. @kennethwwu , please make sure to correct the documentation that you have posted on the wiki. You can either find and upload the documents that produce the hash you have published, or, update the hash on 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
158

Proposal #134929 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • Though this proposal appears to add 28 nodes, the proposer clarified that this is necessary for migrating to the HSM-less deployment method in their statement on the wiki. Once the nodes have transitioned to the new Node Operator (NO) record, the old one will be deprecated. This keeps aligned with the IC target topology.
  • The DC ID in the proposal matches what is displayed on the dashboard.
  • This data center hosts nodes for the node provider Rivonia Holdings LLC, with the node provider ID spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe.
  • The previous NO ID (wmrev-cdq34-iqwdm-oeaak-f6kch-s4axw-ojbhe-yuolf-bazh4-rjdty-oae) associated with this data center shows 28 nodes, matching the allowance being proposed. The old NO ID also mentions the same NP ID as stated in the previous point.
  • The old NO ID also verifies that these are Gen-1 nodes as indicated by the "type1": 28, meaning that they are in line with motion proposal 132553 for node rewards after 48 months. This proposal is explained at the beginning of this forum thread.
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
159

Proposal #134936 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • This proposal removes nodes from obsolete node operators ampm3 and ut325
  • All nodes belonging to these node operators are offline on the dashboard :white_check_mark:
  • The total number of nodes being removed (50), matches the sum of the 22 nodes in MR1 (NO ampm3) and 28 nodes in BO1 (NO ut325). :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, 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
160

Proposal #134937 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • This NP (DFINITY Stiftung) is updating the reward configuration for their nodes in SH1
  • The total number of the nodes in the proposal correspond to the nodes visible on that dashboard under the SH1 DC :white_check_mark:
  • All node IDs mentioned in the proposal are visible on the dashboard under SH1 DC as well :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, 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
161

Proposal #134938 Review — Louise | Aviate Labs

Vote: ADOPT
Review:

  • This proposal removes the old NO Record that was associated to the NP 87m Neuron, LLC for the PL1 DC.
  • It can be verified in ic-admin that this NO record has 0 rewardable nodes, indicating it can be safely removed.
  • It can also be verified that most of the nodes have been transferred already, as when looking at PL1 DC on the dashboard, the NP listed there is Uvaca Labs LLC
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
162

https://dashboard.internetcomputer.org/proposal/134925

Hi @LaCosta, thx for pointing out that incorrect hash value for https://mywikis-wiki-media.s3.us-central-1.wasabisys.com/internetcomputer/Bigger_Capital_Self-declaration.pdf, I just updated it on wiki, it is under review now.

3 Likes