From fe30d426df7d6c385ca78b6aa6e408b61a578330 Mon Sep 17 00:00:00 2001 From: Vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Mon, 29 Apr 2024 13:56:30 -0700 Subject: [PATCH] Adjusting the machine account creation instructions in the node bootstrap guide (#755) * removing instructions for existing node operators to create a machine account * adding a line for new SL and LN NO to take note of the machine account when staking --- docs/networks/flow-port/staking-guide.md | 12 ------------ .../node-ops/node-operation/node-bootstrap.md | 2 ++ docs/networks/staking/11-machine-account.md | 4 +--- 3 files changed, 3 insertions(+), 15 deletions(-) diff --git a/docs/networks/flow-port/staking-guide.md b/docs/networks/flow-port/staking-guide.md index 161221d4d6..726a7c7ce9 100644 --- a/docs/networks/flow-port/staking-guide.md +++ b/docs/networks/flow-port/staking-guide.md @@ -62,18 +62,6 @@ If you return to the home screen, you'll be able to see your staking request in ![Flow Port Staking](port-stake-4.png) -### Existing Node Operators - -If you are already a node operator with a staked node, you will first need to upgrade your account to a Staking Collection. On the Stake & Delegate page you will see a card which will walk you through submitting the transaction to upgrade your account to Staking Collection. - -![Flow Port Staking](staking-collection.png) - -Once this is done, you can now create a [Machine Account](../../networks/node-ops/node-operation/machine-existing-operator.md) by clicking the "Upgrade Node" button on the Stake & Delegate page. - -![Flow Port Staking](machine-account.png) - -You can follow the guide [here](../../networks/node-ops/node-operation/machine-existing-operator.md) to create your Machine Account. - ## Delegating Delegating is the process of staking your locked FLOW to nodes which are being run by another party. diff --git a/docs/networks/node-ops/node-operation/node-bootstrap.md b/docs/networks/node-ops/node-operation/node-bootstrap.md index a6fd8e15fe..2218f95e0e 100644 --- a/docs/networks/node-ops/node-operation/node-bootstrap.md +++ b/docs/networks/node-ops/node-operation/node-bootstrap.md @@ -178,6 +178,8 @@ $cat ./bootstrap/public-root-information/node-info.pub.39fa54984b8eaa463e1299194 If you are running a collection or consensus node, you will need to provide an additional field `Machine Account Public Key`. This value is found in the output of the `bootstrap key` command from Step 1. +Staking a collection or consensus node will also create a machine account for the node. The machine account will be mentioned in the output of the staking transaction displayed by Flow Port. Please save the machine account for the next step. + Please let us know your node id via discord or email. diff --git a/docs/networks/staking/11-machine-account.md b/docs/networks/staking/11-machine-account.md index 3313a7ff67..577203bdaa 100644 --- a/docs/networks/staking/11-machine-account.md +++ b/docs/networks/staking/11-machine-account.md @@ -23,9 +23,7 @@ Currently Machine Accounts are required only for `collection` and `consensus` no #### Creation -For new node operators, Machine Accounts are created during the [staking process](../../networks/flow-port/staking-guide.md) in Flow Port. -For node operators who initially staked prior to the introduction of Machine Accounts, Machine Accounts can be -created for your staked nodes by following [this guide](../node-ops/node-operation/machine-existing-operator.md). +Machine Accounts are created during the [staking process](../../networks/flow-port/staking-guide.md) in Flow Port. #### Funding