New Node Provider Proposals

Roadmap
,
979

Will fix my mistake. Thank you all

980

The problem with your submission is that you just copied what was in the Register your Node Provider principal to the network.
The commands provided are the following:

$ NODE_PROVIDER_NAME="My Company"
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
        --nns-url https://ic0.app \
        -s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
    propose-to-add-or-remove-node-provider add \
        --proposer $NEURON_ID \
        --proposal-title "Register a node provider '${NODE_PROVIDER_NAME}'" \
        --summary "Register a node provider '${NODE_PROVIDER_NAME}', in line with the announcement and discussion at <https://forum.dfinity.org/t/...>. The self-declaration documentation is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>. The proof of identity is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
        --node-provider-pid "$NODE_PROVIDER_PRINCIPAL"

You should customize this to include your links in --sumary.

Since you donā€™t have the required documents yet on the IC Wiki, I would recommend that you start from the Node Provider Roadmap. There you will get all the needed info to register your NP, understand the requirements and finally onboard your nodes.

One important step might be to join the Node Provider matrix channel so you can ask all your questions.

Hopefully this helps.

3 Likes
981

Proposal 136802 - Tim | CodeGov

I have also voted to REJECT this proposal. The proposer has obviously attempted to include all the usual required information for registering a new node provider but the links to supporting documents and forum post and the document hashes are missing, presumably due to a copy-paste error.

982

Thank you @LaCosta. The information helps tremendously. I will start working the paperwork and be active on the Node Provider Matrix Channel

983

Hi Chris,

Itā€™s great to see that youā€™re interested in becoming an IC node provider one day. If youā€™re willing, Iā€™d love to know a little more about you.

How did you come across the IC? Was that recently, or have you been here a while? Have you been interested in crypto long? Whatā€™s your background in (if I may ask)?

Also, out of interest, how many node machines are you planning on registering? What country(s) would you be planning to locate them in? Do you know or have a connection with any of the existing node providers on the IC?

Many thanks,
Alex

1 Like
984

Hello Lorimer

My name is Chris. I have been passively staking ICP over the last few years under identity# 2640671. I have conducted some research on ICP and am very much in support of the ICP roadmap and mission statement. With that being said, I want to play a more active role in the developing ecosystem.

Yesterday, I created Identity 2774606 to submit a proposal to become a Node provider, inadvertently, without following the roadmap line by line, proposal #136802. Thanks to the community here, I plan to submit the required steps Prior to submitting a proposal.

My vision is to set up a single node in the Atos datacenter located in Slovakia. I am an American, My wife is Slovak. I have not seen ICP availability in Slovakia as of yet. I want to be the first. My plan is to initially invest in a single node and grow the number of nodes by reinvesting monthly rewards. I do not havee any connections with existing node providers as of yet. Hence the reason I am here.

4 Likes
985

Sorry. My background is in cyber security. Chris F. (MSc)(Retired) - Booz Allen Hamilton | LinkedIn

1 Like
987

By the way, it is an honor to meet all of you. I look forward to doing all that I can to participate and help achieve the ICP vision.

As far as ICP vision, I believe crypto is a mandatory evolution. Our current approach is so primitive. Look at cybersecurity, for instance. We have spoken about DNSSEC to eliminate race conditions in DNS-based attacks. Yet, we continue to run in circles where CVEā€™s from 1974 continue to devastate infrastructure. Web3 accomplishes all of this via its internal core. AI. How can we trust AI being fed Web2 data? Without AI in the blockchain, nothing is trusted.

Yes, I believe in the ICP mission.

5 Likes
988

Thanks @Chris200712, this is very helpful info. You seem like the sort of person who would make a great node provider and contribute to the network in more ways than one. Itā€™s a pleasure to meet you.

Recently thereā€™s been quite a bit of discussion on the IC about strengthening KYC requirements for node providers, and introducing additional measures to help support decentralisation and verifiability. These discussions are still ongoing, but have already lead to some changes, and thereā€™s also a pilot programme being planned for more major changes (node provider audits).

One of the side effects of these changes is a proposed minimum number of nodes that a node provider should own to be able join the network.

Please donā€™t be disheartened by this. I donā€™t believe itā€™s set in stone, and requirements may evolve as a result of findings from the pilot programme. Iā€™d encourage you to contribute to the discussion in that thread once youā€™ve read up on some of the context - and mention how the planned changes would affect you as a prospective node provider.

One of the ways that you can track and/or participate in these discussions is by attending the periodic node provider working group meetings. Thereā€™s also related discussion on various threads.

Many thanks again, and I hope to see you around on this forum. Iā€™m sure you have a wealth of knowledge and experience that could benefit many discussions.

2 Likes
989

Lorimer

Thank you for the information. I plan on joining the working group on the 23rd. A threshold of 10, whew, not a deal killer, but a huge initial investment.

Thank you again!

1 Like
990

Proposal 136802 ā€” Louise | Aviate Labs
Vote: REJECT
Review
This proposal registers a new NP ML_MIST.

Rejecting because there is no forum post and the links in the proposal summary do not point to valid documentation.

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.

1 Like
991

Hi Chris!

Welcome to the Internet Computer forum!

Iā€™ve rejected the wiki edit you did because of the formatting issues and added a placeholder page for you here: ML MIST - Internet Computer Wiki

Feel free to add your docs to it. Please be aware that we are going to ask our existing and future node providers to go through a stricter KYC / UBO audit in the future. See Enhancing Network Decentralization - Proposals for Identity Verification and Subnet Allocation thread for details, and make sure you are comfortable with it!

3 Likes
992

Hey everyone,

The hardware issues with two of the nodes have now been resolved. The following two are now online and ready to join the network:

  • clto5-apr2m-kchli-74da2-eg5md-lnmya-blvu3-nxsgw-mygx6-ashjr-dqe
  • oxfpl-mnall-x64st-zzj56-r2c6n-6lcyo-lvlth-yycxr-ct54w-fio3c-la

As a result, proposal#136809 raises the rewardable nodes count for Blue Ant LLC from 40 to 42.

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

  • Self-Declaration Link: Blue Ant LLC
  • Node Count: 40 under the new remuneration structure
  • Data Center: im1
  • Node Deployment Confirmation: Two nodes have been deployed with IPv4 addresses and domain names.
  • Contact Information: Element/Matrix - @enzo.blueant:matrix.org
  • All nodes have been installed following the node provider documentation. A forum post outlining the setup process and key learnings will follow.
  • Reward type is 1.1, consistent with Proposal 136036 and further discussed in this forum post.
  • Previous proposal#136504, to set Gen-1.1 rewards for the first 40 nodes.
6 Likes
993

Proposal 136809 Review | Krzysztof Żelazko - ICP Hub Poland

This proposal updates the rewardable node count for an already registered Node Operator of Node Provider Blue Ant LLC, by adding two nodes that were previously omitted due to hardware issues:

  1. clto5-apr2m-kchli-74da2-eg5md-lnmya-blvu3-nxsgw-mygx6-ashjr-dqe
  2. oxfpl-mnall-x64st-zzj56-r2c6n-6lcyo-lvlth-yycxr-ct54w-fio3c-lae

I voted to Adopt this proposal because it satisfies the current requirements for updating node rewards and demonstrates transparency and alignment with past standards:

  1. The two affected nodes have now been resolved and confirmed as online in this forum post.
  2. The self-declaration and proof of identity documents for Blue Ant LLC are available on the Internet Computer Wiki.
  3. The proposed reward type (1.1) is consistent with previous proposal 136036, as explained in this forum post.
  4. The proposer confirmed that all nodes follow the official deployment guidelines and are now fully operational.

While itā€™s important to rigorously assess all reward updates, this proposal includes sufficient evidence, context, and consistency.

About Krzysztof Żelazko Independent reviewer and Governance Lead at ICP Hub Poland. Votes manually on NNS proposals related to decentralization, node operations, and governance integrity. Aims to support transparency and the long-term health of the Internet Computer ecosystem by making fair and well-reasoned decisions.
2 Likes
994

Fantastic to hear! I think you would make an excellent NP. The group could do with more people that have a technical background for sure!

1 Like
995

Thanks a lot! I will be submitting my documentation shortly!

1 Like
996

Proposal 136809 | Tim - CodeGov

Vote: Adopt

This proposal sets rewardable_nodes to 42 for node operator 4isre, corresponding to the number of nodes now deployed under this node operator ID by node provider Blue Ant LLC.

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, API Boundary Node 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
997

Proposal 136809 ā€” Louise | Aviate Labs
Vote: ADOPT
Review:

This proposal increases the rewardable nodes for Node Operator 4isre from 40 to 42 nodes.

  • At the time of this review, the node IDs mentioned in the proposal are in a healthy state on the public dashoard. :white_check_mark:
  • ic-admin shows that node_allowance <= 0 :white_check_mark:
  • type1.1 rewards configuration was 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.

1 Like
998

Setting up the LLC at this time.

2 Likes
999

Proposal #136809 ā€” Zack | CodeGov

Vote: Adopted

Reason:
NP Blue Ant LLC adds the remaining two nodes to NO 4isre rewardable_nodes for a total of 42 to the IM1 DC in Douglas, Isle of Man. The proposal is correct and has all requirements linked.
Looking forward to any updated setup process and key learnings, that the NP will share. Also at the time of the proposal all nodes were up and running unassigned with Status Awaiting.

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