View source for Steps for Gen-1 Node onboarding after 48 months

Explanations regarding the reason and timing for these instructions is available in [https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/5 this forum post]

In order for nodes to earn rewards beyond their initial 48 months, each Gen-1 Node Provider will need to follow the below steps. For Gen-1 Node Providers with less than 42 nodes, only steps 1 and 1a are applicable.

This flowchart lays out the steps and include sample dates for Node Providers whose 48 months is ending 31 January 2025. (High resolution PDF [https://wiki.internetcomputer.org/wiki/File:Workflow_Gen1_updated.pdf here].) '''Note that the dates for proposals are when it should PASS by. It takes 4 days for a proposal to pass and we recommend submitting at least 9 days before the deadline so that there is time to correct if a mistake inadvertantly makes it into your first proposal!'''
[[File:Updated workflow chart.jpg|alt=|center|thumb|500x500px]]

===Step 1 - Update of reward configuration of remaining node machines (action holder existing node provider)===
A. On the forum, create a post ([https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months here], and crossposted [https://forum.dfinity.org/t/new-node-provider-proposals/16643/435 here]*) with at least the following information

#A link to your self-declaration on the wiki, to declare that you will act in the best interest of the IC. If not already published, the instruction for publication of the self-declaration can be found [[Node Provider Self-declaration|here]]
# A statement of how many nodes you wish to continue running under the new remuneration (link)
# A statement of which DC(s) those nodes will run in
# A confirmation that you have [[Updating your node's IPv4 and domain name|deployed two nodes with IPv4]] and a domain name in each DC(s)
# The date when these nodes will start earning the [[Node Provider Remuneration|new reward values]] (which should be the day after your original 48 months end)
# The [[Node Provider Matrix channel|Element/Matrix]] alias on which the node provider can be reached

<nowiki>*</nowiki>''Note: If the forum will not permit you to post links, DM Katie on Element or [https://forum.dfinity.org/u/katiep/ in the forum] with your user handle so your permissions can be adjusted.''

<nowiki>*</nowiki> '''Your forum post should be submitted 30 days prior to the date specified Step 1.A.5 to allow the DRE team to submit the subnet membership change proposals, as active excess nodes need to be removed from subnets.'''

B. NNS - '''AFTER you receive the last distribution for your 48 months (Feb 13 for most NPs)''' - Using your existing Node Operator Id, submit an NNS proposal using the template below to submit the new count of nodes into the registry as node type1.1*  ([[Steps for Gen-1 Node onboarding after 48 months#Sample proposal for Step 1.B|sample proposal]])

...

===='''Step 1b'''====
(Optional, but recommended. Action holder existing node provider) 

Reconfigure remaining node machines without HSM-key, to allow for better support by DRE team. 

The following steps need to be followed when reconfiguring the remaining node machines without HSM:

#Get new node operator private keys and node operator principle [[Node Provider Onboarding|using the installation instructions]], without the use of an HSM, i.e. steps 6 and 7.
#NNS - in collaboration with Dfinity DRE team, remove any node machines from active subnets, making node machines “ready to join a subnet”.
#Redeploy the remaining number of nodes (max 42) to the new node operator record following the [[Node Deployment Guide|node deployment instructions]] (keeping the IPv6 for the first two nodes).
#NNS - create a node operator record with the allowance for the remaining number of nodes, following [[Node Provider Onboarding|the installation instruction]], step 10. ([[Steps for Gen-1 Node onboarding after 48 months#Sample proposal.2C Step 1.A.4|sample proposal]])
#NNS - remove the old node operator record ([[Steps for Gen-1 Node onboarding after 48 months#Sample proposal for Step 1.A.5|sample proposal]])
#NNS - Update the new node operator record with the [[Node Provider Reward Configuration Guide|reward configuration]] (same as step 1.6, but with the new NO id) with the nodes that have been redeployed. ([[Steps for Gen-1 Node onboarding after 48 months#Sample proposal for Step 1.A.6|sample propsal]])

=== Step 2 - Handover (action holder - existing node provider) ===
Any excess node machines (above the maximum of 42 nodes) can be sold by the existing node provider to a new (or existing) other node provider that is not in any way controlled by the existing node provider. The following steps need to be followed:

A. A statement, published on the IC wiki, signed by both the existing and the new node provider, of the hand-over of <<xx>> node machines. It should also include:

# In which Data Center these excess node machines will be operated
#Declaration that both NPs do not have any majority control in each other’s operations
#A confirmation that you have deployed two nodes with IPv4 and a domain name in each DC(s)
#The date when these nodes will start earning the new reward values

B. On the forum, a post describing the handover of the excess nodes that links to the above wiki statement and which also includes the same four details. *''Note: If the forum will not permit you to post links, DM Katie on Element or [https://forum.dfinity.org/u/katiep/ in the forum] with your user handle so your permissions can be adjusted.''

After these above steps, the node provider acquiring the excess nodes will commence with officially onboarding as a new node provider following [[Node Provider Onboarding|the regular steps described in the wiki]]. These steps are summarized below:

=== Step 3 - Onboarding of excess Gen1 node machines that are sold to a new or an existing NP (action holder - acquiring node provider) ===
#''(If new NP)'' On IC wiki - Post self-declaration document, as described [[Node Provider Self-declaration|here]].
#''(If new NP)'' On IC wiki - Post proof of identity document, as described [[Node Provider Self-declaration|here]].
#''(If a new NP)'' Follow the [[Node Provider Onboarding|onboarding process]] for a new node provider.
#''(If new NP)'' On Forum [https://forum.dfinity.org/t/new-node-provider-proposals/16643/435 here] - Introduction by the new NP, including the [[Node Provider Matrix channel|Element/Matrix]] alias on which the node provider can be reached.
#''(If new NP)'' NNS - Submit a new NP proposal, as per [[Node Provider Onboarding|step 8 of the NP onboarding instructions]].
#''(New NP or existing NP, if nodes are going into a new DC)'' NNS - submit a new Data Center Record, as per [[Node Provider Onboarding|step 9 of the onboarding process]]. This step can be skipped if the node machines will remain in the current data center where the nodes were hosted by the previous node providers.
#''(New NP or existing NP)'' NNS - submit Node Operator record for node allowance, as per [[Node Provider Onboarding|step 10 of the onboarding process]].
#''(New NP or existing NP)'' NNS - submit Node Operator record for [[Node Provider Onboarding|reward configuration]].

=== Sample Proposals ===
<big>Note that there is a Node '''Operator''' principal that connects each DC to each NP principal. More discussion is [https://forum.dfinity.org/t/subnet-management-uzr34-ii/33981/112 here]. You can find the NO principal '''for each DC''' by looking at one of the node records in the dashboard. It will list ''both'' your Node '''Provider''' principal as well as your Node '''Operator''' principal. Make sure that you put the correct Node '''Operator''' principal in the proposal, or the code will not work in the NNS!</big>

<big>If you have more than one DC, make sure you do a proposal for each one, with its unique NO.</big>

<nowiki>***</nowiki>Make sure that every proposal links to a forum post that thoroughly explains the background information for the proposal! It can be advisable to do the forum post first, ask if anyone has further questions, edit the forum post as needed to answer them, and THEN do the proposal, including in the proposal the details that were requested and also linking to the forum post. That way it is easy for others to understand what is happening and why. Some voters are getting to the point where they will reject any proposal that doesn't have full background information clearly stated and linked to a forum post.
==== '''Sample proposal for Step 1.A.4''' ====
<syntaxhighlight lang="yaml">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL_NEW=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ FORUM_POST_URL="https://forum.dfinity.org/..."
$ WIKI_URL="https://wiki.internetcomputer.org/wiki/..."

$ 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 creating a new Node Operator id for adding $NODE_ALLOWANCE nodes in the $DC_ID data center. This proposal is in line with motion proposal 132553 for node rewards after 48 months, the proposal is clarified in this forum post: $FORUM_POST_URL and this wiki link $WIKI_URL" \
        --proposer $NEURON_ID \
        --node-operator-principal-id $NODE_OPERATOR_PRINCIPAL_NEW \
        --node-allowance $NODE_ALLOWANCE \
        --dc-id $DC_ID
</syntaxhighlight>

==== '''Sample proposal for Step 1.A.5''' ====
<syntaxhighlight lang="yaml">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxx
$ NODE_OPERATOR_PRINCIPAL_OLD=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ FORUM_POST_URL="https://forum.dfinity.org/..."
$ WIKI_URL="https://wiki.internetcomputer.org/wiki/..."

$ ./ic-admin \
        --nns-url https://ic0.app \
        -s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
    propose-to-remove-node-operator \
        $NODE_OPERATOR_PRINCIPAL_OLD \
        --summary "Node provider '$NODE_PROVIDER_NAME' is removing the old Node Operator ID in the $DC_ID data center. This proposal is in line with motion proposal 132553 for node rewards after 48 months, the proposal is clarified in this forum post $FORUM_POST_URL and this wiki link $WIKI_URL" \
        --proposer $NEURON_ID

</syntaxhighlight>

==== '''Sample proposal for Step 1.A.6''' ====
<syntaxhighlight lang="yaml">
$ NEURON_ID = XXXXXXXXXXXXXXXXXXXX
$ NODE_OPERATOR_PRINCIPAL = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ ./ic-admin \
        --nns-url https://ic0.app \
        -s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
    propose-to-update-node-operator-config \
        --proposer $NEURON_ID \
        --summary "In line with motion proposal 132553 for node rewards after 48 months, set rewards for the following nodes:

        * NODE_1_MACHINE_ID
        * NODE_2_MACHINE_ID
        * ...
        * NODE_N_MACHINE_ID
        " \
        --node-operator-id $NODE_OPERATOR_PRINCIPAL \
        --rewardable-nodes '{"type1.1": NODE_COUNT}'

</syntaxhighlight>

==== '''Sample proposal for Step 1.B''' ====
<syntaxhighlight lang="yaml">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ FORUM_POST_URL="https://forum.dfinity.org/..."
$ WIKI_URL="https://wiki.internetcomputer.org/wiki/..."

$ ./ic-admin \
        --nns-url https://ic0.app \
        -s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
    propose-to-update-node-operator-config \
        --proposer $NEURON_ID \
        --summary "In line with motion proposal 132553 for node rewards after 48 months, set rewards for the following nodes:

 * NODE_1_MACHINE_ID
 * NODE_2_MACHINE_ID
 * ...
 * NODE_N_MACHINE_ID

For a detailed clarification of the proposal, please refer to the following forum post $FORUM_POST_URL
" \
        --node-operator-id $NODE_OPERATOR_PRINCIPAL \
        --rewardable-nodes '{"type1.1": NODE_COUNT}'

</syntaxhighlight>