Internet Computer Wiki - User contributions [en]

Yannick Endrion

2024-12-05T08:36:37Z

Sven.fischer:

=== Self Declaration ===
[[File:Self Declaration Node.pdf|center|thumb|1035x1035px|Self Declaration Yannick Endrion]]

SHA 256 Hash e2599e672ac53a6a823f33176592014a416af805bd7bef159bd2b655a8be443a

=== Proof of Identity ===
[[File:Identity Proof Yannick Endrion.pdf|alt=Identity Proof Yannick Endrion|thumb|800x800px|Identity Proof Yannick Endrion|center]]

SHA256 hash 208f4b388cde546486a926ce1c02cefd59933a765d49b9691fb300751754f0ec

Yannick Endrion

2024-12-05T08:35:57Z

Sven.fischer: Created page with "=== Self Declaration === Self Declaration Yannick Endrion SHA 256 Hash e2599e672ac53a6a823f33176592014a416af805bd..."

=== Self Declaration ===
[[File:Self Declaration Node.pdf|center|thumb|1035x1035px|Self Declaration Yannick Endrion]]

SHA 256 Hash e2599e672ac53a6a823f33176592014a416af805bd7bef159bd2b655a8be443a

=== Proof of Identity ===
[[File:Identity Proof Yannick Endrion.pdf|alt=Identity Proof Yannick Endrion|thumb|800x800px|Identity Proof Yannick Endrion]]

SHA256 hash 208f4b388cde546486a926ce1c02cefd59933a765d49b9691fb300751754f0ec

Node Provider Self Declarations

2024-12-05T08:24:32Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[87m Neuron, LLC]]

[[9Yards Capital]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ALLUSION BV]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitapp]]

[[Bitmoon]]

[[Blockchain Development Labs Inc]]

[[Blockchain Literacy Foundation]]

[[Blocktech Ventures LLC]]

[[BLP22, LLC]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[CocoMango LLC]]

[[Conic Ventures]]

[[Decentralized Entities Foundation]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Ferndale International]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[Giant Leaf, LLC]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Iancu-Aurel|Iancu Aurel]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Louise Velayo]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[MI Servers]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[NODAL CAPITAL]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[Nikola Nikov]]

[[OneSixtyTwo Digital Capital]]

[[User:Soekawat|Origin Game]]

[[Paul Creasey]]

[[User:Protocol16|Philip Hur]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Quantum Node Ltd.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Serenity lotus limited]]

[[Starbase]]

[[Technical University of Munich]]

[[Tenderloin Ventures AG|Tenderloin Ventures AG (Tomahawk.vc)]]

[[Timur Rakhimzhan]]

[[Uvaca Labs LLC]]

[[VirtualHiveLtd|Virtual Hive Ltd]]

[[Vladyslav Popov]]

[[Wolkboer (Pty) Ltd]]

[[WMA Investments Limited]]

[[Yannick Endrion]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Node Provider Self-declaration

2024-11-07T12:07:08Z

Sven.fischer: Replace "Signature or representatives" with "Name and Signature of representatives" in self declaration, avoiding havign self declarations without a name of signatory on it

This page describes the Node Provider self-declaration process and provides templates. This process and templates are currently in a draft state and discussed by the community (see [https://forum.dfinity.org/t/proposal-for-node-provider-self-declaration/16501 forum post]). Once the NNS has decided on the expected format, the post and this page will be updated to reflect the NNS decision.

== Motivation ==

In a fully decentralized network, the onboarding of a Node Provider is managed entirely by the Network Nervous Systems (NNS). This means that anybody who wants to become a Node Provider needs to submit a proposal that will be voted upon by the community. The main question for the community is: how to decide whether to accept or reject a new Node Provider into the network?

Ultimately, it’s the Node Provider's responsibility to convince the community to adopt their proposal to be added as a new Node Provider. With the self-declaration, the Node Provider shall:

* Establish their identity.
* Make a statement of good intent.

This way, the community will have sufficient information to vote on the Node Provider's onboarding proposal.

== Documents and Templates ==

Before submitting a proposal to become a new Node Provider, the Node Provider shall prepare two kinds of documents. The documents should be delivered as a PDF file that is digitally signed.

=== (1) Self-declaration ===

(A) Statement of identity

Entity name: __________________________________________________

Representative name: __________________________________________

Position within entity: ___________________________________________

Entity address and location: ______________________________________

Country: ______________________________________________________

Chamber of Commerce Nr: _______________________________________

(B) Statement of provision of node machines

I hereby guarantee that I shall provide node machines in accordance with the required Hardware Configuration for running the IC Network, as described on the IC wiki (see [[Node Provider Machine Hardware Guide]]).

(C) Statement of good intent

I guarantee to the world that I shall honestly operate the node machines I provide, and that should I behave dishonestly, for example by deliberately interfering with my node machine(s) to prevent them correctly processing ICP protocol messages, in collusion with others or alone, that I will be liable to users of the network, and to other node providers, for any damages caused.

I further declare I am aware that any deliberate interference with a node machine, which causes it to incorrectly process ICP protocol messages, represents a misuse of that hardware, and of any hardware it interacts with, and that in some jurisdictions, that may constitute a crime.

Name and Signature of representatives

___________________

___________________

___________________

=== (2) Identity Proof ===

The Node Provider shall provide proof that the identity(ies) listed in the self-declaration exist in the real world. The proof can be any document that sufficiently proves the identity of the signers of the self-declaration to the community.

== Process ==

Initially, the process is quite manual. Over time, it shall be automated and for convenience be incorporated into dApps running on the IC. For now:

# '''Preparation:''' The Node Provider prepares:
## The two kinds of documents listed above in a format that is widely available, e.g. PDF. .zip files are not recommended.
### Compute the sha256 hash of each document. (Can be done online [https://www.fileformat.info/tool/hash.htm here])
# '''Publication:''' The Node Provider uploads the documents including the sha256 hashes to the wiki page [[Node Provider Self Declarations|Node Provider Self Declarations.]]
# '''Proposal submission:''' The Node Provider submits a proposal to the NNS asking to be accepted to the network.
## The technical instructions are provided on the [[Node Provider Onboarding]] page.
## The summary of the proposal shall point to the published file (step 2) and list the hash (step 1).
# '''NNS vote:''' It’s now up to the NNS community to check whether the provided information matches the community’s expectations and to vote on the proposal.

Philip Hur

2024-09-30T06:38:34Z

Sven.fischer: Created page with "=== Self Declaration === ICP NP Self Declaration PH SHA256 hash <code>d433497932de39..."

=== Self Declaration ===
[[File:ICP NP Self Declaration PH.pdf|alt=ICP NP Self Declaration PH|thumb|1456x1456px|ICP NP Self Declaration PH]]

SHA256 hash <code>d433497932de39d880974dc0e50ae34cf4227ae53d0eaf3f364c83c16eff06e6</code>.

=== Identity Document ===
[[File:Proof of Identity PH.pdf|alt=Proof of Identity PH.pdf|thumb|1491x1491px|Proof of Identity PH.pdf]]

SHA256 hash <code>ba5d2bead0ad9dd5777287257607ad79678d8638a76bb6af2c46b3eb855daf8b</code>.

Node Provider Self Declarations

2024-09-30T06:29:56Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ALLUSION BV]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitapp]]

[[Bitmoon]]

[[Blockchain Development Labs Inc]]

[[Blockchain Literacy Foundation]]

[[Blocktech Ventures LLC]]

[[BLP22, LLC]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[CocoMango LLC]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Ferndale International]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[Giant Leaf, LLC]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Louise Velayo]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[NODAL CAPITAL]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[Nikola Nikov]]

[[OneSixtyTwo Digital Capital]]

[[User:Soekawat|Origin Game]]

[[Paul Creasey]]

[[Philip Hur]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Serenity lotus limited]]

[[Technical University of Munich]]

[[Tenderloin Ventures AG]]

[[Timur Rakhimzhan]]

[[Wolkboer (Pty) Ltd]]

[[WMA Investments Limited]]

[[VirtualHiveLtd|Virtual Hive Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Mariano Stoll

2024-08-15T13:16:30Z

Sven.fischer:

Mariano Stoll

2024-08-15T13:15:43Z

Sven.fischer: Stoll Mariano Identity Document

Mariano Stoll

2024-08-15T13:15:15Z

Sven.fischer:

Mariano Stoll

2024-08-15T13:13:42Z

Sven.fischer:

Mariano Stoll

2024-08-15T13:09:35Z

Sven.fischer:

Node Provider Remuneration

2024-07-11T13:18:14Z

Sven.fischer:

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. (See [[How the 30-Day Moving Average Is Calculated]].) Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
An [[Proposed Gen-1 Remuneration Model|Interim Gen-1 Remuneration Model]] has been approved for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
If a Node Provider has nodes in more than one type or geography but within the same country, the NNS knows that they are in the same country and counts the combined total of nodes, each according to their own type and geography.

The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Israel
|49500
|2
|2063
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|New Zealand
|47000
|2
|1958
|0.95
|-
|Panama
|51774
|2
|2158
|0.95
|-
|Costa Rica
|51774
|2
|2158
|0.95
|-
|Colombia
|57455
|2
|2394
|0.95
|-
|Argentina (proposed)
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

== Trustworthy Node Metrics ==
In February 2024, Trustworthy Node Metrics were introduced on the IC, in an attempt to provide greater visibility into node performance, stability, and reliability. These metrics could potentially be used to influence node rewards in the future.

There is a forum post here https://forum.dfinity.org/t/trustworthy-node-metrics-for-useful-work/22989, then

Blog post on Medium here: https://medium.com/dfinity/dont-trust-verify-new-node-metrics-on-the-internet-computer-367cc154a572

And technical documentation and instructions here: https://dfinity.github.io/dre/trustworthy-metrics/trustworthy-metrics.html

Node Provider Remuneration

2024-07-11T13:11:12Z

Sven.fischer: Added Argentina to the Gen2.1 reward table as additional South American country, to support reward payout for Gen2 node machines as part of approved target topology.

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. (See [[How the 30-Day Moving Average Is Calculated]].) Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
An [[Proposed Gen-1 Remuneration Model|Interim Gen-1 Remuneration Model]] has been approved for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
If a Node Provider has nodes in more than one type or geography but within the same country, the NNS knows that they are in the same country and counts the combined total of nodes, each according to their own type and geography.

The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Israel
|49500
|2
|2063
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|New Zealand
|47000
|2
|1958
|0.95
|-
|Panama
|51774
|2
|2158
|0.95
|-
|Costa Rica
|51774
|2
|2158
|0.95
|-
|Colombia
|57455
|2
|2394
|0.95
|-
|Argentina
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

== Trustworthy Node Metrics ==
In February 2024, Trustworthy Node Metrics were introduced on the IC, in an attempt to provide greater visibility into node performance, stability, and reliability. These metrics could potentially be used to influence node rewards in the future.

There is a forum post here https://forum.dfinity.org/t/trustworthy-node-metrics-for-useful-work/22989, then

Blog post on Medium here: https://medium.com/dfinity/dont-trust-verify-new-node-metrics-on-the-internet-computer-367cc154a572

And technical documentation and instructions here: https://dfinity.github.io/dre/trustworthy-metrics/trustworthy-metrics.html

Node Provider Onboarding

2024-07-03T09:45:28Z

Sven.fischer: Added a comment under paragraph 8 to present node provider name in single quotes in the NP proposal, for the dashboard to pick this up automatically

Learn how to be accepted by the NNS as a Node Provider and onboard your nodes to the IC.

Please allocate up to a week to complete this guide, as it may take several days for a proposal to be accepted by the NNS, and you may have to submit multiple NNS proposals.

'''Note that the following steps do not need to be performed on the node machine itself.''' You can complete them on your personal laptop.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

For regular operations after onboarding, please refer to [[Node Provider Maintenance Guide]]

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

'''''<big>Requirements</big>'''''
* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [https://www.ledger.com/ Hardware wallet]
* [https://shop.nitrokey.com/shop/product/nkhs2-nitrokey-hsm-2-7/ NitroKey HSM] (Optional, legacy—not recommended)
* 11 ICP (10 of which are to be staked for the NNS proposal deposit)
* Basic understanding of [[Neurons 101|neurons]], [https://internetcomputer.org/docs/current/tokenomics/nns/nns-staking-voting-rewards staking], and [[Governance of the Internet Computer|governance]] proposals. For instance, understanding what it means to stake a neuron for 8 years.

== 1. Install the required tools ==
===''' A. Install ic-admin '''===

<code>ic-admin</code> is the tool used to create and submit NNS proposals.

==== MacOS ====
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/246d0ce0784d9990c06904809722ce5c2c816269/binaries/x86_64-darwin/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo e3b2964d959509a2c3347503d02211a205b719d06c771d6bab4025d9e63d0605) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/246d0ce0784d9990c06904809722ce5c2c816269/binaries/x86_64-linux/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo 1b9795f752c9854ad070fcc4b4ec0673978731d0c7e0d875db0c4872217f443d) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

===''' B. Install dfx '''===

#<code>dfx</code> is used to generate neuron hotkeys, among other things <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"

</syntaxhighlight>
#Verify that dfx is up to date. <syntaxhighlight lang="shell">
$ export PATH=$HOME/bin:$PATH
$ dfx upgrade
$ dfx --version
</syntaxhighlight>

==2. Create Node Provider hotkey ==

#Create an identity for the Node Provider '''Hotkey''' <syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node-provider-hotkey

Created identity: "node-provider-hotkey".

$ dfx --identity node-provider-hotkey identity get-principal

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# example node-provider-hotkey: wuyst-x5tpn-g5wri-mp3ps-vjtba-de3xs-w5xgb-crvek-tucbe-o5rqi-mae

</syntaxhighlight>'''You will need the Node Provider hotkey in the next steps.''' Note: you may be prompted to enter a passphrase when creating your identity and accessing your identity principal. Take note of the passphrase you choose.

'''Note:''' The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

==3. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity==

#Send at least 11 ICPs to your hardware wallet address.
#Navigate to Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP works as well, but 10 is the minimum to stake a neuron, and you must have a little more for transaction fees.
#IMPORTANT! Confirm the transaction on your hardware wallet.
#:[[File:-docs-stake_neuron_1.png|1024px|stake neuron]]
#After the Neuron has been created successfully, confirm to "Add NNS Dapp as hotkey" in the dialogue and on your hardware wallet, and close the dialog after the action completes.
#:[[File:-docs-stake_neuron_2.png|1024px|neuron id]]
#Set the dissolve delay to at least 6 months, and confirm the choice in the dialogue and on your hardware wallet. After the action completes, you can close the "Follow Neurons".
#:[[File:dissolve_delay.png|480px|neuron id]]
#You will now see a Neuron listed with its ID. Copy the Neuron ID, since you will need it in the next steps to place the necessary proposals.
#:[[File:Neuron id.png|1024px]]

==4. Add hotkeys==

#Select the Neuron you just created to open Neuron management view and press “Add hotkey” button.
#:[[File:Hotkey 1.png|873x873px]]
# A dialog will pop up where you can enter the hotkey you generated in step 2.1 (output from command <code>dfx --identity node-provider-hotkey identity get-principal</code>). This will allow you to submit NNS proposals using <code>ic-admin</code> and will not be used for anything else. 
#:Press the '''confirm''' button and confirm the transactions on your hardware wallet. 
#:[[File:Hotkey 2.png|899x899px]]
#Get the Ledger Hardware Wallet Principal Id: Navigate back to ICP page and select your Ledger hardware wallet account. You will need to use this Ledger Hardware Wallet principal as the Node Provider principal in order to get the rewards directly into the secure hardware wallet.
#:[[File:Node provider principal 1.png|1024px]]
#:[[File:Node provider principal 2.png|800px]]
#Copy and save this Node Provider principal by clicking on the copy icon after the principal id. You'll need it in the next steps. <syntaxhighlight lang="shell">
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# Input ledger Hardware Wallet principal, from the NNS FrontEnd dapp https://nns.ic0.app/

# example: $ NODE_PROVIDER_PRINCIPAL=fharn-5vyi2-4xb4a-64yyi-3jpmj-pga23-mxy25-d5uim-fqcro-eoefh-tae
</syntaxhighlight>

==5. Choose onboarding path (HSM vs no HSM)==
Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' a NitroKey HSM, continue to the next step.

If the legacy procedure is necessary, follow the [[NitroKey HSM onboarding instructions]] and '''return to step 8.'''

==6. Setup the Node Operator keys ==
#'''''Ensure dfx is at least version 0.14.''''' Node Operator keys created with older versions of dfx '''will fail to join the IC'''. Run:<syntaxhighlight lang="bash">
$ dfxvm update
$ dfx --version
</syntaxhighlight>
#Create a new principal with dfx:<syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node_operator
</syntaxhighlight>
#Confirm <code>node_operator</code> identity was created successfully:<syntaxhighlight lang="shell">
$ dfx identity list
</syntaxhighlight>This list ''should'' contain <code>node_operator</code>.
#Copy new key to a known location:<syntaxhighlight lang="shell">
$ cp ~/.config/dfx/identity/node_operator/identity.pem ./node_operator_private_key.pem
</syntaxhighlight>
#Check the contents of the <code>node_operator_private_key.pem</code> file and double check that it contains the following contents. It is imperative that the first line has <code>-----BEGIN EC PRIVATE KEY-----</code>. If it does not, make sure you use the latest <code>dfx</code> version and that you followed the instructions precisely.<syntaxhighlight lang="shell">
❯ cat ./node_operator_private_key.pem
-----BEGIN EC PRIVATE KEY-----
[3 lines of base64 encoded private key, e.g. n2Nhp68YcQpuS0u96r...]
-----END EC PRIVATE KEY-----
</syntaxhighlight>Note: you must retain access to the <code>node_operator_private_key.pem</code> file for when you onboard nodes in '''[https://wiki.internetcomputer.org/wiki/Node_Provider_Roadmap#Milestone_Five:_Node_Machine_Onboarding roadmap milestone five.]'''

==7. Get the node operator principal==

#Get the principal:<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(dfx --identity node_operator identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>
'''You will need the node operator principal in the next steps.'''

==8. Register your Node Provider principal to the network==
In the next codeblock:
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4)
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)

*'''''IMPORTANT:''''' Please make sure that you also update the <code>--summary</code> and include a link to the forum discussion, your company's web page, and/or to another place that can convince the voting community that you are making a legitimate request. You must also include the file hash for the [[Node Provider Self-declaration|self declaration and proof of identity documents]], or the proposal will be rejected. This way you will avoid the community voting NO to your proposal and you losing your staked ICPs.

##Create the Proposal <syntaxhighlight lang="shell">
$ 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"
</syntaxhighlight>Note: make sure <code>${NODE_PROVIDER_NAME}</code> is presented in single quotes, so the IC dashboard can pick up and display the correct Node Provider name.
#Find the proposal on https://dashboard.internetcomputer.org/governance and '''wait until it is executed before proceeding to next step.'''
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==9. Register your datacenter to the network (if necessary)==
#Search for your data center on https://dashboard.internetcomputer.org/centers.
#*If you found the datacenter that is hosting your nodes, remember its ID, and skip the following section. Otherwise, proceed with the registration of a new DC record.
#:[[File:dc_id.png|1041x1041px|alt=]]
===Create a data center record for a new DC===
In the next block of code:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)
*Replace the JSON fields from the <code>–data-centers-to-add</code> argument and their corresponding values in <code>--summary</code>:
**<code>"id"</code> represents the city that your datacenter is in and is formulated as a combination of two letters representing the city and an incrementing number. Search data center IDs on https://dashboard.internetcomputer.org, and find a combination of two letters and a number that’s not yet registered. Examples:
***dl1 (Dallas, no IDs with “dl” prefix)
***zh10 (Zurich, numbers 0-9 are already registered)
**:[[File:dc_id.png|1024px]]
**<code>"region"</code> represents the local region of a datacenter and is formulated as a three-part string divided by commas. The three parts making the string are continent, country code, and region, in the given order. Examples:
***North America,US,Florida
***Europe,DE,Bavaria
***Asia,SG,Singapore
**:[[File:datacenter_region.png|1024px]]
**<code>"owner"</code> The entity that provides your datacenter facilities.
***Search https://dashboard.internetcomputer.org for existing data center providers.
*** If there’s match, make sure you use the same exact some name for your datacenter.
***Otherwise, name the data center owner to your best knowledge.
**:[[File:datacenter_owner.png|1024px]]
**<code>"gps"</code> GPS coordinates.
***Find your datacenter on https://www.google.com/maps/.
***Right click on location, and select the GPS coordinates (first item in the menu) in order to copy them.
**:[[File:maps.png|310x310px|alt=Getting GPS coordinates|Getting GPS coordinates]]

#Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-data-centers \
--summary "Register a Flexential datacenter as dl1 in North America,US,Texas" \
--skip-confirmation \
--proposer $NEURON_ID \
--data-centers-to-add '{
"id": "dl1",
"region": "North America,US,Texas",
"owner": "Flexential",
"gps": [
33.00803, -96.66614
]
}'
</syntaxhighlight>'''Remember to replace all the values of both the arguments <code>–data-centers-to-add</code> and <code>--summary</code>'''
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==10. Create a node operator record==
'''''IMPORTANT''':'' Before submitting the Node Operator record, please go through the description of [[Validation of Candidate Node Machines]] to validate whether additional node machines are needed for decentralization of the IC-network.

* Create a pdf with the outcome of running the optimization model and the steps that allow the community to reproduce the validation check.
* Include the pdf in the wiki page that includes the NP documents (self-declaration and proof-of-identity document)
* Include a link to the pdf as well as the hash of the document in the Node Operator record proosal.

In the next codeblock:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6).
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 7.1). '''Important''': if you are adding an additional node operator record because you will deploy nodes in another data center, please make sure to create a new node operator principal first (steps 6 and 7). A node operator principal can only be tied to 1 data center.
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_ALLOWANCE</code> variable value with number of nodes you are providing.
* Replace the <code>DC_ID</code> variable value with id of your datacenter.

# Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ DC_ID=dl1

$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-node-operator \
$NODE_PROVIDER_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adding $NODE_ALLOWANCE nodes in the $DC_ID data center. The result of the canidate node machine validation and exact configuration run is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--proposer $NEURON_ID \
--node-operator-principal-id $NODE_OPERATOR_PRINCIPAL \
--node-allowance $NODE_ALLOWANCE \
--dc-id $DC_ID
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

''See guide for [[Troubleshooting Failed NNS proposals]]''

Node Provider Self Declarations

2024-05-23T12:47:28Z

Sven.fischer: Removed Marc Johnson as he is not a NP anymore. Nodes have been moved to CarbonTwelve

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ALLUSION BV]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitapp]]

[[Bitmoon]]

[[Blockchain Development Labs Inc]]

[[Blocktech Ventures LLC]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[CocoMango LLC]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Ferndale International]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Louise Velayo]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[NODAL CAPITAL]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[Nikola Nikov]]

[[OneSixtyTwo Digital Capital]]

[[User:Soekawat|Origin Game]]

[[Paul Creasey]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Serenity lotus limited]]

[[Technical University of Munich]]

[[Timur Rakhimzhan]]

[[Wolkboer (Pty) Ltd]]

[[WMA Investments Limited]]

[[VirtualHiveLtd|Virtual Hive Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Marc Johnson

2024-05-23T12:46:49Z

Sven.fischer: Blanked the page

Node Provider Onboarding

2024-03-02T09:17:53Z

Sven.fischer:

Learn how to be accepted by the NNS as a Node Provider and onboard your nodes to the IC.

Please allocate up to a week to complete this guide, as it may take several days for a proposal to be accepted by the NNS, and you may have to submit multiple NNS proposals.

'''Note that the following steps do not need to be performed on the node machine itself.''' You can complete them on your personal laptop.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

For regular operations after onboarding, please refer to [[Node Provider Maintenance Guide]]

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

'''''<big>Requirements</big>'''''
* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [https://www.ledger.com/ Hardware wallet]
* [https://shop.nitrokey.com/shop/product/nkhs2-nitrokey-hsm-2-7/ NitroKey HSM] (Optional, legacy—not recommended)
* 11 ICP (10 of which are to be staked for the NNS proposal deposit)
* Basic understanding of [[Neurons 101|neurons]], [https://internetcomputer.org/docs/current/tokenomics/nns/nns-staking-voting-rewards staking], and [[Governance of the Internet Computer|governance]] proposals. For instance, understanding what it means to stake a neuron for 8 years.

== 1. Install the required tools ==
===''' A. Install ic-admin '''===

<code>ic-admin</code> is the tool used to create and submit NNS proposals.

==== MacOS ====
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-darwin/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo 3f75026d2f28f171068e332a42c82a2795c93fbf5ab351baef30b30eb901cdba) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-linux/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo e29bb9cc462e800b8b960ad49c412e5f5fdbb5ae2ae9fde0c13058422ba32802) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

===''' B. Install dfx '''===

#<code>dfx</code> is used to generate neuron hotkeys, among other things <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://smartcontracts.org/install.sh)"

</syntaxhighlight>
#Verify that dfx is up to date. <syntaxhighlight lang="shell">
$ export PATH=$HOME/bin:$PATH
$ dfx upgrade
$ dfx --version
</syntaxhighlight>

==2. Create Node Provider hotkey ==

#Create an identity for the Node Provider '''Hotkey''' <syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node-provider-hotkey

Created identity: "node-provider-hotkey".

$ dfx --identity node-provider-hotkey identity get-principal

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# example node-provider-hotkey: wuyst-x5tpn-g5wri-mp3ps-vjtba-de3xs-w5xgb-crvek-tucbe-o5rqi-mae

</syntaxhighlight>'''You will need the Node Provider hotkey in the next steps.''' Note: you may be prompted to enter a passphrase when creating your identity and accessing your identity principal. Take note of the passphrase you choose.

'''Note:''' The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

==3. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity==

#Send at least 11 ICPs to your hardware wallet address.
#Navigate to Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP works as well, but 10 is the minimum to stake a neuron, and you must have a little more for transaction fees.
#IMPORTANT! Confirm the transaction on your hardware wallet.
#:[[File:-docs-stake_neuron_1.png|1024px|stake neuron]]
#After the Neuron has been created successfully, confirm to "Add NNS Dapp as hotkey" in the dialogue and on your hardware wallet, and close the dialog after the action completes.
#:[[File:-docs-stake_neuron_2.png|1024px|neuron id]]
#Set the dissolve delay to at least 6 months, and confirm the choice in the dialogue and on your hardware wallet. After the action completes, you can close the "Follow Neurons".
#:[[File:dissolve_delay.png|480px|neuron id]]
#You will now see a Neuron listed with its ID. Copy the Neuron ID, since you will need it in the next steps to place the necessary proposals.
#:[[File:Neuron id.png|1024px]]

==4. Add hotkeys==

#Select the Neuron you just created to open Neuron management view and press “Add hotkey” button.
#:[[File:Hotkey 1.png|873x873px]]
# A dialog will pop up where you can enter the hotkey you generated in step 2.1 (output from command <code>dfx --identity node-provider-hotkey identity get-principal</code>). This will allow you to submit NNS proposals using <code>ic-admin</code> and will not be used for anything else. 
#:Press the '''confirm''' button and confirm the transactions on your hardware wallet. 
#:[[File:Hotkey 2.png|899x899px]]
#Get the Ledger Hardware Wallet Principal Id: Navigate back to ICP page and select your Ledger hardware wallet account. You will need to use this Ledger Hardware Wallet principal as the Node Provider principal in order to get the rewards directly into the secure hardware wallet.
#:[[File:Node provider principal 1.png|1024px]]
#:[[File:Node provider principal 2.png|800px]]
#Copy and save this Node Provider principal by clicking on the copy icon after the principal id. You'll need it in the next steps. <syntaxhighlight lang="shell">
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# Input ledger Hardware Wallet principal, from the NNS FrontEnd dapp https://nns.ic0.app/

# example: $ NODE_PROVIDER_PRINCIPAL=fharn-5vyi2-4xb4a-64yyi-3jpmj-pga23-mxy25-d5uim-fqcro-eoefh-tae
</syntaxhighlight>

==5. Choose onboarding path (HSM vs no HSM)==
Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. If you will not be using a NitroKey HSM, continue to the next step.

If the legacy procedure is necessary, follow the [[NitroKey HSM onboarding instructions]] and '''return to step 8.'''

==6. Setup the Node Operator keys ==
#'''''Ensure dfx is at least version 0.14.''''' Node Operator keys created with older versions of dfx '''will fail to join the IC'''. Run:<syntaxhighlight lang="bash">
$ dfx upgrade
$ dfx --version
</syntaxhighlight>
#Create a new principal with dfx:<syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node_operator
</syntaxhighlight>
#Confirm <code>node_operator</code> identity was created successfully:<syntaxhighlight lang="shell">
$ dfx identity list
</syntaxhighlight>This list ''should'' contain <code>node_operator</code>.
#Copy new key to a known location:<syntaxhighlight lang="shell">
$ cp ~/.config/dfx/identity/node_operator/identity.pem ./node_operator_private_key.pem
</syntaxhighlight>
#Check the contents of the <code>node_operator_private_key.pem</code> file and double check that it contains the following contents. It is imperative that the first line has <code>-----BEGIN EC PRIVATE KEY-----</code>. If it does not, make sure you use the latest <code>dfx</code> version and that you followed the instructions precisely.<syntaxhighlight lang="shell">
❯ cat ./node_operator_private_key.pem
-----BEGIN EC PRIVATE KEY-----
[3 lines of base64 encoded private key, e.g. n2Nhp68YcQpuS0u96r...]
-----END EC PRIVATE KEY-----
</syntaxhighlight>Note: you must retain access to the <code>node_operator_private_key.pem</code> file for when you onboard nodes in '''[https://wiki.internetcomputer.org/wiki/Node_Provider_Roadmap#Milestone_Five:_Node_Machine_Onboarding roadmap milestone five.]'''

==7. Get the node operator principal==

#Get the principal:<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(dfx --identity node_operator identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>
'''You will need the node operator principal in the next steps.'''

==8. Register your Node Provider principal to the network==
In the next codeblock:
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4)
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)

*'''''IMPORTANT:''''' Please make sure that you also update the <code>--summary</code> and include a link to the forum discussion, your company's web page, and/or to another place that can convince the voting community that you are making a legitimate request. You must also include the file hash for the [[Node Provider Self-declaration|self declaration and proof of identity documents]], or the proposal will be rejected. This way you will avoid the community voting NO to your proposal and you losing your staked ICPs.

#Create the Proposal <syntaxhighlight lang="shell">
$ 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"
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and '''wait until it is executed before proceeding to next step.'''
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.
==9. Register your datacenter to the network (if necessary)==
#Search for your data center on https://dashboard.internetcomputer.org/centers.
#*If you found the datacenter that is hosting your nodes, remember its ID, and skip the following section. Otherwise, proceed with the registration of a new DC record.
#:[[File:dc_id.png|1041x1041px|alt=]]
===Create a data center record for a new DC===
In the next block of code:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)
*Replace the JSON fields from the <code>–data-centers-to-add</code> argument and their corresponding values in <code>--summary</code>:
**<code>"id"</code> represents the city that your datacenter is in and is formulated as a combination of two letters representing the city and an incrementing number. Search data center IDs on https://dashboard.internetcomputer.org, and find a combination of two letters and a number that’s not yet registered. Examples:
***dl1 (Dallas, no IDs with “dl” prefix)
***zh10 (Zurich, numbers 0-9 are already registered)
**:[[File:dc_id.png|1024px]]
**<code>"region"</code> represents the local region of a datacenter and is formulated as a three-part string divided by commas. The three parts making the string are continent, country code, and region, in the given order. Examples:
***North America,US,Florida
***Europe,DE,Bavaria
***Asia,SG,Singapore
**:[[File:datacenter_region.png|1024px]]
**<code>"owner"</code> The entity that provides your datacenter facilities.
***Search https://dashboard.internetcomputer.org for existing data center providers.
*** If there’s match, make sure you use the same exact some name for your datacenter.
***Otherwise, name the data center owner to your best knowledge.
**:[[File:datacenter_owner.png|1024px]]
**<code>"gps"</code> GPS coordinates.
***Find your datacenter on https://www.google.com/maps/.
***Right click on location, and select the GPS coordinates (first item in the menu) in order to copy them.
**:[[File:maps.png|310x310px|alt=Getting GPS coordinates|Getting GPS coordinates]]

#Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-data-centers \
--summary "Register a Flexential datacenter as dl1 in North America,US,Texas" \
--skip-confirmation \
--proposer $NEURON_ID \
--data-centers-to-add '{
"id": "dl1",
"region": "North America,US,Texas",
"owner": "Flexential",
"gps": [
33.00803, -96.66614
]
}'
</syntaxhighlight>'''Remember to replace all the values of both the arguments <code>–data-centers-to-add</code> and <code>--summary</code>'''
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

==10. Create a node operator record==
'''''IMPORTANT''':'' Before submitting the Node Operator record, please go through the description of [[Validation of Candidate Node Machines]] to validate whether additional node machines are needed for decentralization of the IC-network.

* Create a pdf with the outcome of running the optimization model and the steps that allow the community to reproduce the validation check.
* Include the pdf in the wiki page that includes the NP documents (self-declaration and proof-of-identity document)
* Include a link to the pdf as well as the hash of the document in the Node Operator record proosal.

In the next codeblock:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6).
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 7.1). '''Important''': if you are adding an additional node operator record because you will deploy nodes in another data center, please make sure to create a new node operator principal first (steps 6 and 7). A node operator principal can only be tied to 1 data center.
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_ALLOWANCE</code> variable value with number of nodes you are providing.
* Replace the <code>DC_ID</code> variable value with id of your datacenter.

# Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ DC_ID=dl1

$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-node-operator \
$NODE_PROVIDER_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adding $NODE_ALLOWANCE nodes in the $DC_ID data center. The result of the canidate node machine validation and exact configuration run is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--proposer $NEURON_ID \
--node-operator-principal-id $NODE_OPERATOR_PRINCIPAL \
--node-allowance $NODE_ALLOWANCE \
--dc-id $DC_ID
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

Node Provider Documentation

2024-02-29T22:37:44Z

Sven.fischer:

==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.

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 [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.

== Resources ==
*Node deployment guides:
**[[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)]]
*Node Provider onboarding
**[[Node Provider Onboarding]]
**[[Node Provider Self-declaration]]
**[[Validation of Candidate Node Machines]]
**[[Node Provider Reward Configuration Guide]]
**[[Failed NNS proposals - finding the cause]]
*Troubleshooting and maintenance:
**[[Node Provider Matrix channel]]
**[[Node Provider Troubleshooting|Node Provider Troubleshooting guides]]
**[[Node Provider Maintenance Guide]]
**[[Node Provider NNS proposals]]
**[[Removing a Node From the Registry]]
**[[Changing Your Data Center Principal]]
**[[Adding additional node machines to existing Node Allowance]]
**[[Updating your node's IPv4 and domain name]]
*Guides and resources
**[[Node Provider Machine Hardware Guide]]
**[[Node Provider Networking Guide]]
**[[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]]
*Other resources:
**[[Node Provider FAQ]]

Node Provider Remuneration

2024-02-29T11:23:55Z

Sven.fischer:

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. (See [[How the 30-Day Moving Average Is Calculated]].) Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
An [[Proposed Gen-1 Remuneration Model|Interim Gen-1 Remuneration Model]] has been approved for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Israel
|49500
|2
|2063
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|New Zealand
|47000
|2
|1958
|0.95
|-
|Panama
|51774
|2
|2158
|0.95
|-
|Costa Rica
|51774
|2
|2158
|0.95
|-
|Colombia
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

== Trustworthy Node Metrics ==
In February 2024, Trustworthy Node Metrics were introduced on the IC, in an attempt to provide greater visibility into node performance, stability, and reliability. These metrics could potentially be used to influence node rewards in the future.

There is a forum post here https://forum.dfinity.org/t/trustworthy-node-metrics-for-useful-work/22989, then

Blog post on Medium here: https://medium.com/dfinity/dont-trust-verify-new-node-metrics-on-the-internet-computer-367cc154a572

And technical documentation and instructions here: https://dfinity.github.io/dre/trustworthy-metrics/trustworthy-metrics.html

Node Provider Documentation

2024-02-26T10:12:24Z

Sven.fischer:

==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.

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 ==
Please note that currently, the '''IC has reached target topology''', see also [https://forum.dfinity.org/t/new-node-provider-proposals/16643/322?u=svenf this forum post.]. It means that '''no new node machines will be accepted to the IC network''' for the time being. Once the subnets are reaching capacity and more subnets are required to run all applications, the community can decide to increase the target topology again and allow additional node machines to the network.

== Resources ==
*Node deployment guides:
**[[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)]]
*Node Provider onboarding
**[[Node Provider Onboarding]]
**[[Node Provider Self-declaration]]
**[[Validation of Candidate Node Machines]]
**[[Node Provider Reward Configuration Guide]]
**[[Failed NNS proposals - finding the cause]]
*Troubleshooting and maintenance:
**[[Node Provider Matrix channel]]
**[[Node Provider Troubleshooting|Node Provider Troubleshooting guides]]
**[[Node Provider Maintenance Guide]]
**[[Node Provider NNS proposals]]
**[[Removing a Node From the Registry]]
**[[Changing Your Data Center Principal]]
**[[Adding additional node machines to existing Node Allowance]]
**[[Updating your node's IPv4 and domain name]]
*Guides and resources
**[[Node Provider Machine Hardware Guide]]
**[[Node Provider Networking Guide]]
**[[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]]
*Other resources:
**[[Node Provider FAQ]]

NODAL CAPITAL

2024-02-14T08:52:35Z

Sven.fischer:

==Self-Declaration==
The self-declaration document can be found here:

File: NODAL CAPITAL Self-declaration.pdf

[[File:NODAL CAPITAL Self-declaration.pdf|thumb|1510x1510px|NODAL CAPITAL Self Declaration]]

The SHA256 hash of the linked PDF is: ''0af318f022d942aacd55b2bca683437b8787bee7fbd88dee0eefefde073d3bef'' .

==Company Authenticity Proof==
All information about the company and its legal status can be found by entering the registration number (CNPJ): '''49.773.067/0001-58''' on the Brazilian Federal Revenue Service website.

Here is the link to the website: [https://solucoes.receita.fazenda.gov.br/Servicos/cnpjreva/cnpjreva_Solicitacao.asp gov.br]

Attached Copy : FIle: NODAL CAPITAL Certificate.pdf

[[File:NODAL CAPITAL Certificate.pdf|thumb|1490x1490px|NODAL Capital Certificate]]

The SHA256 hash of the linked PDF is: ''9c0ff8a4bd195b0dc76b0c4bdd4e46d33b7e7484b07696bdbfe5f57594c8c6ad'' .

==Identity Proof==
The document proving the real identity of NODAL CAPITAL's founder can be found below.

You can verify the authenticity of the document at https://meu.inss.gov.br/central/#/autenticidade with the code ''240207SPDHLRXX457QU400''.

Attached Copy : File: INSS_CNIS Registration Data.pdf
[[File:INSS CNIS Registration Data.pdf|thumb|1479x1479px|NODAL CAPITAL INSS CNIS Registration]]

The SHA256 hash of the linked PDF is: ''b65f280cac3a916f56022f492acdbfffaacbfacfd44f9e1152bc3be5701d5176'' .

NODAL CAPITAL

2024-02-14T08:50:55Z

Sven.fischer:

==Self-Declaration==
The self-declaration document can be found here:

File: NODAL CAPITAL Self-declaration.pdf

[[File:NODAL CAPITAL Self-declaration.pdf|thumb|1510x1510px|NODAL CAPITAL Self Declaration]]

The SHA256 hash of the linked PDF is: ''0af318f022d942aacd55b2bca683437b8787bee7fbd88dee0eefefde073d3bef'' .

==Company Authenticity Proof==
All information about the company and its legal status can be found by entering the registration number (CNPJ): '''49.773.067/0001-58''' on the Brazilian Federal Revenue Service website.

Here is the link to the website: [https://solucoes.receita.fazenda.gov.br/Servicos/cnpjreva/cnpjreva_Solicitacao.asp gov.br]

Attached Copy : FIle: NODAL CAPITAL Certificate.pdf

[[File:NODAL CAPITAL Certificate.pdf|thumb|1490x1490px|NODAL Capital Certificate]]

The SHA256 hash of the linked PDF is: ''9c0ff8a4bd195b0dc76b0c4bdd4e46d33b7e7484b07696bdbfe5f57594c8c6ad'' .

==Identity Proof==
The document proving the real identity of NODAL CAPITAL's founder can be found below.

You can verify the authenticity of the document at https://meu.inss.gov.br/central/#/autenticidade with the code ''240207SPDHLRXX457QU400''.

Attached Copy : File: INSS_CNIS Registration Data.pdf

The SHA256 hash of the linked PDF is: ''b65f280cac3a916f56022f492acdbfffaacbfacfd44f9e1152bc3be5701d5176'' .

Node Provider Self Declarations

2024-02-13T12:08:11Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitmoon]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[https://dos.sunbiz.org/scripts/ficidet.exe?action=DETREG&docnum=G24000011592&rdocnum=G24000011592 Legra-Neurons]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[User:Soekawat|Origin Game]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Technical University of Munich]]

[[Wolkboer (Pty) Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Node Provider Onboarding

2024-02-05T19:05:15Z

Sven.fischer:

Learn how to be accepted by the NNS as a Node Provider and onboard your nodes to the IC.

Please allocate up to a week to complete this guide, as it may take several days for a proposal to be accepted by the NNS, and you may have to submit multiple NNS proposals.

'''Note that the following steps do not need to be performed on the node machine itself.''' You can complete them on your personal laptop.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

For regular operations after onboarding, please refer to [[Node Provider Maintenance Guide]]

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

'''''<big>Requirements</big>'''''
* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [https://www.ledger.com/ Hardware wallet]
* [https://shop.nitrokey.com/shop/product/nkhs2-nitrokey-hsm-2-7/ NitroKey HSM] (Optional, legacy—not recommended)
* 11 ICP (10 of which are to be staked for the NNS proposal deposit)
* Basic understanding of [[Neurons 101|neurons]], [https://internetcomputer.org/docs/current/tokenomics/nns/nns-staking-voting-rewards staking], and [[Governance of the Internet Computer|governance]] proposals. For instance, understanding what it means to stake a neuron for 8 years.

== 1. Install the required tools ==
===''' A. Install ic-admin '''===

<code>ic-admin</code> is the tool used to create and submit NNS proposals.

==== MacOS ====
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-darwin/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo 3f75026d2f28f171068e332a42c82a2795c93fbf5ab351baef30b30eb901cdba) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-linux/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo e29bb9cc462e800b8b960ad49c412e5f5fdbb5ae2ae9fde0c13058422ba32802) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

===''' B. Install dfx '''===

#<code>dfx</code> is used to generate neuron hotkeys, among other things <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://smartcontracts.org/install.sh)"

</syntaxhighlight>
#Verify that dfx is up to date. <syntaxhighlight lang="shell">
$ export PATH=$HOME/bin:$PATH
$ dfx upgrade
$ dfx --version
</syntaxhighlight>

==2. Create Node Provider hotkey ==

#Create an identity for the Node Provider '''Hotkey''' <syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node-provider-hotkey

Created identity: "node-provider-hotkey".

$ dfx --identity node-provider-hotkey identity get-principal

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# example node-provider-hotkey: wuyst-x5tpn-g5wri-mp3ps-vjtba-de3xs-w5xgb-crvek-tucbe-o5rqi-mae

</syntaxhighlight>'''You will need the Node Provider hotkey in the next steps.''' Note: you may be prompted to enter a passphrase when creating your identity and accessing your identity principal. Take note of the passphrase you choose.

'''Note:''' The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

==3. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity==

#Send at least 11 ICPs to your hardware wallet address.
#Navigate to Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP works as well, but 10 is the minimum.
#IMPORTANT! Confirm the transaction on your hardware wallet.
#:[[File:-docs-stake_neuron_1.png|1024px|stake neuron]]
#After the Neuron has been created successfully, confirm to "Add NNS Dapp as hotkey" in the dialogue and on your hardware wallet, and close the dialog after the action completes.
#:[[File:-docs-stake_neuron_2.png|1024px|neuron id]]
#Set the dissolve delay to at least 6 months, and confirm the choice in the dialogue and on your hardware wallet. After the action completes, you can close the "Follow Neurons".
#:[[File:dissolve_delay.png|480px|neuron id]]
#You will now see a Neuron listed with its ID. Copy the Neuron ID, since you will need it in the next steps to place the necessary proposals.
#:[[File:Neuron id.png|1024px]]

==4. Add hotkeys==

#Select the Neuron you just created to open Neuron management view and press “Add hotkey” button.
#:[[File:Hotkey 1.png|873x873px]]
# A dialog will pop up where you can enter the hotkey you generated in step 2.1 (output from command <code>dfx --identity node-provider-hotkey identity get-principal</code>). This will allow you to submit NNS proposals using <code>ic-admin</code> and will not be used for anything else. 
#:Press the '''confirm''' button and confirm the transactions on your hardware wallet. 
#:[[File:Hotkey 2.png|899x899px]]
#Get the Ledger Hardware Wallet Principal Id: Navigate back to ICP page and select your Ledger hardware wallet account. You will need to use this Ledger Hardware Wallet principal as the Node Provider principal in order to get the rewards directly into the secure hardware wallet.
#:[[File:Node provider principal 1.png|1024px]]
#:[[File:Node provider principal 2.png|800px]]
#Copy and save this Node Provider principal by clicking on the copy icon after the principal id. You'll need it in the next steps. <syntaxhighlight lang="shell">
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# Input ledger Hardware Wallet principal, from the NNS FrontEnd dapp https://nns.ic0.app/

# example: $ NODE_PROVIDER_PRINCIPAL=fharn-5vyi2-4xb4a-64yyi-3jpmj-pga23-mxy25-d5uim-fqcro-eoefh-tae
</syntaxhighlight>

==5. Choose onboarding path (HSM vs no HSM)==
Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. If you will not be using a NitroKey HSM, continue to the next step.

If the legacy procedure is necessary, follow the [[NitroKey HSM onboarding instructions]] and '''return to step 8.'''

==6. Setup the Node Operator keys ==
#'''''Ensure dfx is at least version 0.14.''''' Node Operator keys created with older versions of dfx '''will fail to join the IC'''. Run:<syntaxhighlight lang="bash">
$ dfx upgrade
$ dfx --version
</syntaxhighlight>
#Create a new principal with dfx:<syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node_operator
</syntaxhighlight>
#Confirm <code>node_operator</code> identity was created successfully:<syntaxhighlight lang="shell">
$ dfx identity list
</syntaxhighlight>This list ''should'' contain <code>node_operator</code>.
#Copy new key to a known location:<syntaxhighlight lang="shell">
$ cp ~/.config/dfx/identity/node_operator/identity.pem ./node_operator_private_key.pem
</syntaxhighlight>
#Check the contents of the <code>node_operator_private_key.pem</code> file and double check that it contains the following contents. It is imperative that the first line has <code>-----BEGIN EC PRIVATE KEY-----</code>. If it does not, make sure you use the latest <code>dfx</code> version and that you followed the instructions precisely.<syntaxhighlight lang="shell">
❯ cat ./node_operator_private_key.pem
-----BEGIN EC PRIVATE KEY-----
[3 lines of base64 encoded private key, e.g. n2Nhp68YcQpuS0u96r...]
-----END EC PRIVATE KEY-----
</syntaxhighlight>Note: you must retain access to the <code>node_operator_private_key.pem</code> file for when you onboard nodes in '''[https://wiki.internetcomputer.org/wiki/Node_Provider_Roadmap#Milestone_Five:_Node_Machine_Onboarding roadmap milestone five.]'''

==7. Get the node operator principal==

#Get the principal:<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(dfx --identity node_operator identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>
'''You will need the node operator principal in the next steps.'''

==8. Register your Node Provider principal to the network==
In the next codeblock:
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4)
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)

*'''''IMPORTANT:''''' Please make sure that you also update the <code>--summary</code> and include a link to the forum discussion, your company's web page, and/or to another place that can convince the voting community that you are making a legitimate request. You must also include the file hash for the [[Node Provider Self-declaration|self declaration and proof of identity documents]], or the proposal will be rejected. This way you will avoid the community voting NO to your proposal and you losing your staked ICPs.

#Create the Proposal <syntaxhighlight lang="shell">
$ 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>." \
--node-provider-pid "$NODE_PROVIDER_PRINCIPAL"
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and '''wait until it is executed before proceeding to next step.'''
#You are encouraged to
* In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.

==9. Register your datacenter to the network (if necessary)==
#Search for your data center on https://dashboard.internetcomputer.org/centers.
#*If you found the datacenter that is hosting your nodes, remember its ID, and skip the following section. Otherwise, proceed with the registration of a new DC record.
#:[[File:dc_id.png|1041x1041px|alt=]]
===Create a data center record for a new DC===
In the next block of code:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)
*Replace the JSON fields from the <code>–data-centers-to-add</code> argument and their corresponding values in <code>--summary</code>:
**<code>"id"</code> represents the city that your datacenter is in and is formulated as a combination of two letters representing the city and an incrementing number. Search data center IDs on https://dashboard.internetcomputer.org, and find a combination of two letters and a number that’s not yet registered. Examples:
***dl1 (Dallas, no IDs with “dl” prefix)
***zh10 (Zurich, numbers 0-9 are already registered)
**:[[File:dc_id.png|1024px]]
**<code>"region"</code> represents the local region of a datacenter and is formulated as a three-part string divided by commas. The three parts making the string are continent, country code, and region, in the given order. Examples:
***North America,US,Florida
***Europe,DE,Bavaria
***Asia,SG,Singapore
**:[[File:datacenter_region.png|1024px]]
**<code>"owner"</code> The entity that provides your datacenter facilities.
***Search https://dashboard.internetcomputer.org for existing data center providers.
*** If there’s match, make sure you use the same exact some name for your datacenter.
***Otherwise, name the data center owner to your best knowledge.
**:[[File:datacenter_owner.png|1024px]]
**<code>"gps"</code> GPS coordinates.
***Find your datacenter on https://www.google.com/maps/.
***Right click on location, and select the GPS coordinates (first item in the menu) in order to copy them.
**:[[File:maps.png|310x310px|alt=Getting GPS coordinates|Getting GPS coordinates]]

#Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-data-centers \
--summary "Register a Flexential datacenter as dl1 in North America,US,Texas" \
--skip-confirmation \
--proposer $NEURON_ID \
--data-centers-to-add '{
"id": "dl1",
"region": "North America,US,Texas",
"owner": "Flexential",
"gps": [
33.00803, -96.66614
]
}'
</syntaxhighlight>'''Remember to replace all the values of both the arguments <code>–data-centers-to-add</code> and <code>--summary</code>'''
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

==10. Create a node operator record==
'''''IMPORTANT''':'' Before submitting the Node Operator record, please go through the description of [[Validation of Candidate Node Machines]] to validate whether additional node machines are needed for decentralization of the IC-network.

* Create a pdf with the outcome of running the optimization model and the steps that allow the community to reproduce the validation check.
* Include the pdf in the wiki page that includes the NP documents (self-declaration and proof-of-identity document)
* Include a link to the pdf as well as the hash of the document in the Node Operator record proosal.

In the next codeblock:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6).
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 7.1). '''Important''': if you are adding an additional node operator record because you will deploy nodes in another data center, please make sure to create a new node operator principal first (steps 6 and 7). A node operator principal can only be tied to 1 data center.
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_ALLOWANCE</code> variable value with number of nodes you are providing.
* Replace the <code>DC_ID</code> variable value with id of your datacenter.

# Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ DC_ID=dl1

$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-node-operator \
$NODE_PROVIDER_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adding $NODE_ALLOWANCE nodes in the $DC_ID data center. The result of the canidate node machine validation and exact configuration run is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--proposer $NEURON_ID \
--node-operator-principal-id $NODE_OPERATOR_PRINCIPAL \
--node-allowance $NODE_ALLOWANCE \
--dc-id $DC_ID
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

Node Provider Self Declarations

2024-01-24T12:54:57Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitmoon]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd]]

[[Exaion]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital]]

[[Icaria_Systems_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Neptune Partners]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[User:Soekawat|Origin Game]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Technical University of Munich]]

[[Wolkboer (Pty) Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Bitmoon

2024-01-24T12:53:30Z

Sven.fischer:

BITMOON SARL

Self-Declaration

The self-declaration document can be found here: [[File:Self-Declaration.pdf]]

The SHA256 hash of the linked PDF is 6217297B57728231E6DACD52E68787539B8A07494854E303DEF508B0B9967800

Identity Proof

Company information can be verified on the following website: https://zefix.ch/fr/search/entity/list/firm/1603106

Attached Copy : [[File:Bitmoon_extract_CHE-151.622.046.pdf]]

The SHA256 hash of the linked PDF is 0B2764C306DD0D46B67DDE4F35AAE7BCFCA3446E3940884EA384B8F6EE97105D

The proof of purchase of the node machines can be found here:
[[File:Invoice Dell Bitmoon.pdf|center|thumb|1132x1132px|Invoice Dell Bitmoon]]

File:Invoice Dell Bitmoon.pdf

2024-01-24T12:52:52Z

Sven.fischer:

Invoice Dell Bitmoon

Node Provider Remuneration

2024-01-12T14:57:25Z

Sven.fischer:

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
A [[Proposed Gen-1 Remuneration Model]] is currently under discussion for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Proposed Israel
|49500
|2
|2063
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|Proposed New Zealand
|47000
|2
|1958
|0.95
|-
|Proposed Panama
|51774
|2
|2158
|0.95
|-
|Proposed Costa Rica
|51774
|2
|2158
|0.95
|-
|Proposed Colombia
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

Node Provider Remuneration

2024-01-12T14:56:09Z

Sven.fischer:

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
A [[Proposed Gen-1 Remuneration Model]] is currently under discussion for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Proposed Israel
|49500
|2
|2063
|0.7
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|Proposed New Zealand
|47000
|2
|1958
|0.95
|-
|Proposed Panama
|51774
|2
|2158
|0.95
|-
|Proposed Costa Rica
|51774
|2
|2158
|0.95
|-
|Proposed Colombia
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

Krishna Enterprises

2023-12-27T13:11:06Z

Sven.fischer:

== Self declaration and Identity Proof ==
Self Declaration and Identity Proof in one combined file is given ( 2 pages)
[[File:Krishna Enterprises.pdf|thumb|Self Declaration and Identity proof |alt=|center|1035x1035px]]Zip File with Hash - [[:File:KE.zip|File:KE.zip]]

Hash is 3c7e429077f0ab5ead92c7a0ac84a6af

== Hardware order ==
Evidence that these machines have been ordered before 1st December and are actually in the process of being onboarded and SHA is as below:

SHA 256 is 0f2bcc09b09654650958308911fc46ec014d847c45e48f7c053edeb3817c7957

[[File:Proof of Hardware Order Krishna Enterprises.jpg|center|thumb|986x986px]]

File:Proof of Hardware Order Krishna Enterprises.jpg

2023-12-27T13:09:50Z

Sven.fischer:

Proof of Hardware Order Krishna Enterprises

Neptune Partners

2023-12-19T16:04:26Z

Sven.fischer:

==Self-Declaration==
The self-declaration document can be found here:
[[File:Self Declaration Neptune.pdf|thumb|alt=|center]]
The SHA256 hash of the linked PDF is 212c43503bbbe421e213a7b46da2c91c70c80ae7326b91d2ddedc29f4e26a984.
==Identity Proof==
Company information can be verified by entering UEN number : ''201813417G on the following website.''

https://www.uen.gov.sg/ueninternet/faces/pages/uenSrch.jspx

Attached Copy :
[[File:Certificate of Incorporate.pdf|center|thumb]]

The SHA256 hash of the linked PDF is 78588307b8273d3b9ac7f4e26194c76da7a5c74aea91b4246def566ab97cd568.

== Proof of hardware order ==

SHA256 hash of linked PDF is 35712cda62bf07210b3851365dfec40d356265caa549e2b69b899e96f6849102
[[File:Dell Invoice Neptune Partners.pdf|center|thumb|1133x1133px]]

File:Dell Invoice Neptune Partners.pdf

2023-12-19T16:03:14Z

Sven.fischer:

Dell Invoice Neptune Partners

Node Provider Self Declarations

2023-12-15T13:39:32Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''</blockquote>

[[ACCUSET SOLUTIONS]]

[[Altimist Ltd]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bohatyrov Volodymyr]]

[[CarbonTwelve]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd]]

[[Exaion]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital]]

[[Icaria_Systems_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Neptune Partners]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[User:Soekawat|Origin Game]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Wolkboer (Pty) Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

CarbonTwelve

2023-12-15T13:38:15Z

Sven.fischer:

File:C12 Node Topology.pdf

2023-12-15T13:37:42Z

Sven.fischer:

C12 Node Topology

Geeta Kalwani

2023-12-15T12:44:47Z

Sven.fischer:

== Self declaration document ==
[[File:Geeta Kalwani Self declaration.pdf|center|thumb|1131x1131px|Geeta Kalwani Self Declaration]]

Self-declaration SHA256: 454e41ea6b63fc2fc6c25f5353c3138da6d84ff49d92fd422c1db06706355bec

== Proof of identity document ==
[[File:Geeta Kalwani Identity Proof.pdf|center|thumb|1133x1133px]]

Proof of identity SHA256: 06d21b40f5d1739418e661cd489aebcc147b41b7e1fc387e3cf3fd13cb960072

==Optimisation Model==
[[File:Optimization Model Colombia-FINAL.pdf|center|thumb|1132x1132px|Optimization Model Colombia-FINAL]]

File:Optimization Model Colombia-FINAL.pdf

2023-12-15T12:44:13Z

Sven.fischer:

Optimization Model Colombia-FINAL

GeoNodes LLC

2023-12-13T08:11:16Z

Sven.fischer:

File:CostaRica Final.pdf

2023-12-13T08:10:49Z

Sven.fischer:

CostaRica Final

File:Israel Final.pdf

2023-12-13T08:10:06Z

Sven.fischer:

Israel Final

GeoNodes LLC

2023-12-13T08:09:24Z

Sven.fischer:

Geeta Kalwani

2023-12-11T21:24:13Z

Sven.fischer: Created page with "== Self declaration document == Geeta Kalwani Self Declaration == Proof of identity document == File:Ge..."

File:Geeta Kalwani Identity Proof.pdf

2023-12-11T21:23:40Z

Sven.fischer:

Geeta Kalwani Identity Proof

File:Geeta Kalwani Self declaration.pdf

2023-12-11T21:22:40Z

Sven.fischer:

Geeta Kalwani Self declaration

Node Provider Self Declarations

2023-12-11T21:21:11Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''</blockquote>

[[ACCUSET SOLUTIONS]]

[[Altimist Ltd]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bohatyrov Volodymyr]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd]]

[[Exaion]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital]]

[[Icaria_Systems_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Neptune Partners]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[User:Soekawat|Origin Game]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Wolkboer (Pty) Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Bianca-Martina Rohner

2023-12-11T19:36:40Z

Sven.fischer:

Bianca-Martina Rohrer

2023-12-08T15:17:40Z

Sven.fischer: Blanked the page

Bianca-Martina Rohner

2023-12-08T15:16:42Z

Sven.fischer: Created page with "== Self-declaration == SHA256 hash: ca3973712c4d7947b0b835368ca0648696d52ff6e7ed69a7c92766c1da51e0ce == Identit..."

Node Provider Self Declarations

2023-12-08T15:13:18Z

Sven.fischer:

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''</blockquote>

[[ACCUSET SOLUTIONS]]

[[Altimist Ltd]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bohatyrov Volodymyr]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd]]

[[Exaion]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital]]

[[Icaria_Systems_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Neptune Partners]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[User:Soekawat|Origin Game]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Wolkboer (Pty) Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />