New Node Provider Proposals

1 Like

If my proposal is wrong can you help me on the mistake ?

Proposal 134603

Vote: REJECT

The proposal aims to increase the rewardable nodes of a NO under the Node Provider Bitmoon. However from the two nodes provided in the proposal only one belongs to this node provider while the other is not registered in the Dashboard.

@bitmoon don’t know if you are already in talks with DFINITY to solve the issue and if so great, but you can check this wiki page to check for deployment errors of your node. If even with that you can’t fix the problem then I think going over to the Node Provider Matrix channel might be your best resource.

3 Likes

Proposal #134603 Review — Roald | Aviate Labs

Vote: REJECT
Review:

As mentioned by others but for completion:

  • The first Node is properly registered: 6hqi5-ctyoo-qijwz-dtvwo-g5puo-yaftz-dmaid-rambc-li5dx-q46y2-sae
  • The second Node is not present on the dashboard: z4avz-jczt7-2ozqw-7esmh-ynrgc-p4dgh-fdqel-ixub6-fi3bo-im4hi-xae
  • This second Node should be properly registered first before rewards can be set. It appears Bitmoon is in talks with Dfinity for help on this issue.
1 Like

Hi, understood. I will create a new proposal updating the node allowance by 2 (step 10) and after I will update the rewards.

Did you manage to deploy the missing node ? Am AFK on mobile but you still seem to have only 2 nodes https://dashboard.internetcomputer.org/provider/mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
Do not submit any new proposal until the “Registration Failed” for node z4avz-jczt7-2ozqw-7esmh-ynrgc-p4dgh-fdqel-ixub6-fi3bo-im4hi-xae is fixed.

I think you’ve already done that. As Zack mentioned, you would first need to make sure that the new node has been successfully registered. I’m not a node provider, however, so please double-check this information in case I’ve overlooked anything.

Yes you are right I have done the update of node allowance and though that I need to update the rewards only. Now I’m checking with the DC because Sven told me that they didn’t find the public key.

2 Likes

Let us know when it’s done, not sure about that Node keys are not setup: PublicKeyNotFound error, maybe some in Matrix can help ?


Will then check it so that you can go ahead with the proposal. The timing is a bit difficult but tomorrow is Monday someone should be able to help.

Thank you so much for your help.

1 Like

Proposal 134660 Review | Louise - Aviate Labs

Vote: ADOPT
Review:

  • Though this proposal appears to add 28 nodes, the proposer clarified that this is necessary for migrating the nodes in PL1 from the old NO record associated with the previous NP (87M Neuron LLC) to the new NO record, associated to the new NP (Uvaca Labs LLC).
  • The hash of the handover document matches what is published on the wiki.

  • This DC being transitioned matches what was announced on the forum via the pervious NP.
  • The Datacenter ID (PL1) matches what is shown on the dashboard.
  • The previous Node Operator ID (lz4fy-gca6y-aodk3-ncdrw-ouoqb-kgvjj-h4nul-eybyu-puwev-hkogp-fqe) associated with this data center 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 in the image above, meaning that they are in line with motion proposal 132553 for node rewards after 48 months.
  • This actions are also inline with the steps outlined by DFINITY.
  • For the reasons above, I vote to Adopt
1 Like

Proposal 134660 Review | Quint - Aviate Labs

Vote: ADOPT
Review:

Context:
Migration of 28 nodes in PL1 from the old NO record associated with the previous NP (87M Neuron LLC) to the new NO record, associated to the new NP (Uvaca Labs LLC).

  • Hash matches Handover Document.
  • DC ID (PL1) matches.
  • The previous NO ID (lz4fy-gca6y-aodk3-ncdrw-ouoqb-kgvjj-h4nul-eybyu-puwev-hkogp-fqe) associated with this data center has 28 (type1) nodes.

More info about the steps outlined by DFINITY here.

1 Like

Proposal 134660 | Tim - CodeGov

Vote: Adopt

The proposal adds a new node operator ID for node provider Uvaca Labs LLC. The addition of the new node operator ID is consistent with the processes outlined in the current thread for reconfiguring existing Gen-1 nodes under the new remuneration structure, and with the statement of intent here and node handover statement in the Wiki.

2 Likes

Proposal 134660 – LaCosta | CodeGov

Vote: ADOPT

As part of the Steps for Gen-1 Node onboarding after 48 months, the Node Provider 87m Neuron LLC is handing over excess nodes to Node Provider Uvaca Labs LLC.
All the required steps were made in order for this handover:

  1. A statement on the IC Wiki signed by the previous NP and the new NP file :white_check_mark:
  2. A forum post that complies with this statement :white_check_mark:
  3. The new NP has currenly 0 nodes which means it’s able to add the proposed 28 nodes. :white_check_mark:
  4. Although the DC pl1 has only 18 nodes differing from the 28 proposed, using the ic-admin tool we can verify that the Node Operator that currently operatores nodes in the pl1 DC currently has 28 Gen-1 rewardable nodes.
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.

2 Likes

Proposal 134660 Review | Roald - Aviate Labs

Vote: ADOPT
Review:

This proposal facilitates the migration of 28 nodes in PL1 from the old Node Operator (NO) record, “87M Neuron LLC” to the new NO record under the Node Provider “Uvaca Labs LLC”.

Supporting points:

  1. The hash matches the Handover Document. Also checked proof of identity and self-declaration.

  2. The DC ID (PL1) has an allocation of 28 rewardable nodes.

  3. The previous NO ID (lz4fy-gca6y-aodk3-ncdrw-ouoqb-kgvjj-h4nul-eybyu-puwev-hkogp-fqe) associated with this data center confirms 28 “type1” nodes, ensuring consistency with the proposed migration.

For the reasons stated, I vote to Adopt.

2 Likes

Hi all,
Please find the information regarding the excess nodes that will be transferred to the new Node Provider: Aksinia Stavskaya
The signed handover statement, containing the same information as below, can be found here. Starbase - Internet Computer Wiki
28 node machines from Starbase will be transferred to Aksinia Stavskaya. The following details outline the specifics of this transfer:

  1. Data Center Location: TY2 (Equinix TY6)
  2. Node Count: 28 under the new remuneration structure
  3. 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.
  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. Onboarding Start Date: Feb 1, 2025
  6. Contact Information for the New Node Provider: Element/Matrix alias aka_stava
    Let us know if you have any questions.
    Thanks,
    Starbase
3 Likes

Hi everyone,

Please find the necessary information regarding the nodes that I will be taking over from Starbase (@Tomoaki).

  1. Statement and Self-Declaration Link: Aksinia Stavskaya - Internet Computer Wiki
  2. Node Count: 28 under the new remuneration structure
  3. Data Centers: TY2 (Equinix TY6)
  4. Onboarding Start Date: Feb 1, 2025
  5. Contact Information: Element/Matrix alias aka_stava

Let me know if you have any questions.

Thanks,

Aksinia

3 Likes

Hello everyone,

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,

Brian Porter

2 Likes

Hi everyone,

Cross posting this information here for your visibility and as instructed:

(Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #5 by katiep).

Let me know if you have any questions.

Kind regards,

Brian Porter

1 Like

Hello, we installed again and it works now.
https://dashboard.internetcomputer.org/node/lh2af-66zso-76kqu-d57ag-jca5d-yvmfo-rcabh-ptlvj-ltfdf-kyg6q-lqe

Can you confirm that I can run the proposal to update the rewards ?

Thx

2 Likes