Difference between revisions of "Node Provider Documentation"

From Internet Computer Wiki
Jump to: navigation, search
(Added page for moving a node)
 
(54 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
 +
The Internet Computer is a decentralized network of nodes running the Internet Computer protocol. These nodes are owned by Node Providers who receive rewards for their nodes' [[Proof of Useful Work|useful work]]. Individuals or organizations can become Node Providers through submitting a proposal to the Network Nervous System (NNS), the Decentralized Autonomous Organization (DAO) that governs the Internet Computer. The ICP community then votes on whether to include the Node Provider.
  
ICP runs on a [[Sovereign Network]] that is a governed by a DAO using [[Deterministic Decentralization | deterministic decentralization]] to maximize its [[Decentralization in ICP: Infrastructure Governance | decentralization]]. Node providers invest in and operate the node hardware which powers the Internet Computer. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.
+
Node Providers invest in and operate the node hardware that powers the Internet Computer. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer.  
  
To be part of the ICP infrastructure, any potential node providers can submit NNS proposals to the DAO controlling the ICP blockchain. ICP community then votes on whether to include the node provider.
+
The more diverse the set of Node Providers who supply node machines, the more resilient the Internet Computer is. You can support the Internet Computer and the IC community by becoming a Node Provider and increasing its decentralization.
  
This article is the hub for hub for ICP node provider documentation.
+
This article is the hub for ICP Node Provider documentation.
  
==Node Provider Tokenomics & Remuneration==
+
== Roadmap ==
Node providers receive rewards (remuneration) for operating node machines that run the IC network. The single source of truth for node provider rewards is the NNS, where changes can only be made through NNS proposals adopted by the IC community.
+
To become a Node Provider, follow the [[Node Provider Roadmap]], which explain the costs, rewards, responsibilities, and steps required to become a Node Provider.
  
This page summarizes the current node provider rewards and serves to discuss proposals for future reward models: [[Node Provider Remuneration]]
+
== Target topology reached - no new node machines being onboarded ==
 +
Last year, the community has voted on an IC target topology with a maximum number of node machines, as well as on an optimization model to validate candidate node machines against this IC target topology. The IC target topology has been reached by December of 23, see for more information [https://forum.dfinity.org/t/new-node-provider-proposals/16643/322?u=svenf this forum post.]. This means that the '''IC network currently does not require any additional node machine'''s in order to reach its decentralization targets. Therefore, DFINITY will not vote to adopt any proposals for new node machines being added to the IC network. Once the subnets are reaching capacity and more subnets are required to run all applications, the community may decide to increase the target topology again and allow additional node machines to the network.
  
==Submitting Proposal to Join the Network==
+
== Resources ==
 
+
*Node deployment guides:
As part of the process to become a node provider, a candidate node provider has to declare their intent and self-identify so the ICP DAO can make an informed decision. Please see [[Node Provider Self-declaration]] for more info.
+
**[[Node Deployment Guide (with an HSM)|Legacy (Gen-1) Node Deployment Guide (with an HSM)]]
 
+
**[[Node Deployment Guide|Current (Gen-2) Node Deployment Guide (without an HSM)]]
==Onboarding for accepted Node Providers==
+
*Node Provider onboarding
* [[Node Provider Onboarding]]
+
**[[Node Provider Onboarding]]
 
+
**[[Node Provider Self-declaration]]
===Gen-2 Documentation (new node providers start here)===
+
**[[Validation of Candidate Node Machines]]
* [[Gen-2 Network Requirements]]
+
**[[Node Provider Reward Configuration Guide]]
* [[Gen-2 Data Center runbook|Example Gen-2 Data Center runbook]]
+
**[[Troubleshooting Failed NNS proposals]]
* [[IC OS Installation Runbook]] for Gen-2
+
*Troubleshooting and maintenance:
 
+
**[[Node Provider Troubleshooting|Node Provider Troubleshooting guides]]
===Node Provider Troubleshooting===
+
**[[Troubleshooting Node Deployment Errors]]
* [[Node Provider Troubleshooting]]
+
**[[Node Provider Matrix channel]]
** [[Possible Node Onboarding Errors]]
+
**[[Node Provider Maintenance Guide]]
** [[Unhealthy Nodes]]
+
**[[Node Provider NNS proposals]]
** [[Updating Firmware]]
+
**[[Removing a Node From the Registry]]
** [[iDRAC access and TSR logs]]
+
**[[Changing Your Data Center Principal]]
 
+
**[[Adding additional node machines to existing Node Allowance]]
===Gen-1 Documentation===
+
**[[Updating your node's IPv4 and domain name]]
The first batch of ICP node providers joined under Gen-1. These documents are for those legacy node providers.
+
**[[Moving a node from one DC to another]]
 
+
*Guides and resources
* [[IC OS Installation Runbook - Dell Poweredge]] for Gen-1
+
**[[Node Provider Machine Hardware Guide]]
* [[IC OS Installation Runbook - Supermicro]] for Gen-1
+
**[[Node Provider Networking Guide]]
* [[Storage Runbook]] for Gen-1
+
**[[Node Provider Alerting Options]]
 +
**[[Node Provider Data Center and ISP Guide]]
 +
**[[Node Provider Decentralization and Security Guide]]
 +
**[[Node Provider Legal Guide]]
 +
**[[Node Provider Remuneration]]
 +
**[[Node Provider Domain Name Guide]]
 +
**[[BMC Password Reset Guide]]
 +
**[[Gen1 Node Provider onboarding Gen2 node machines]]
 +
**[[RMU build Gen-1.5|Guide for Gen-1 to Gen-1.5 RMU build]]
 +
*Other resources:
 +
**[[Node Provider FAQ]]

Latest revision as of 17:39, 15 April 2024

Introduction

The Internet Computer is a decentralized network of nodes running the Internet Computer protocol. These nodes are owned by Node Providers who receive rewards for their nodes' useful work. Individuals or organizations can become Node Providers through submitting a proposal to the Network Nervous System (NNS), the Decentralized Autonomous Organization (DAO) that governs the Internet Computer. The ICP community then votes on whether to include the Node Provider.

Node Providers invest in and operate the node hardware that powers the Internet Computer. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer.

The more diverse the set of Node Providers who supply node machines, the more resilient the Internet Computer is. You can support the Internet Computer and the IC community by becoming a Node Provider and increasing its decentralization.

This article is the hub for ICP Node Provider documentation.

Roadmap

To become a Node Provider, follow the Node Provider Roadmap, which explain the costs, rewards, responsibilities, and steps required to become a Node Provider.

Target topology reached - no new node machines being onboarded

Last year, the community has voted on an IC target topology with a maximum number of node machines, as well as on an optimization model to validate candidate node machines against this IC target topology. The IC target topology has been reached by December of 23, see for more information this forum post.. This means that the IC network currently does not require any additional node machines in order to reach its decentralization targets. Therefore, DFINITY will not vote to adopt any proposals for new node machines being added to the IC network. Once the subnets are reaching capacity and more subnets are required to run all applications, the community may decide to increase the target topology again and allow additional node machines to the network.

Resources