fix(docs): improve validator registration steps (#734)

Author: dineshpinto

docs/2-run-node.mdx

@@ -58,6 +58,12 @@ Once your node is running, proceed with the registration:
   ]}
 />
 
+:::tip[Validator Tracker]
+
+You can track validator status, uptime, and software versions on the [Flare Validator Tracker](https://flare-validators.flare.network).
+
+:::
+
 ## Flare Entity
 
 Runs alongside a Validator to provide crucial data for Flare's FTSO and FDC protocols.
@@ -77,6 +83,6 @@ Requires a running [Validator Node](#validator-node). To set up a Flare Entity:
 
 :::tip[Systems Explorer]
 
-All registered Flare Entities, alongside voting and reward epoch, and finalization data can be viewed on the [Flare Systems Explorer](https://flare-systems-explorer.flare.network/providers).
+You can view Flare Entity data, including reward epochs and finalization, on the [Flare Systems Explorer](https://flare-systems-explorer.flare.network/providers).
 
 :::

docs/network/guides/using-flare-stake-tool.mdx

@@ -410,6 +410,34 @@ If you encounter any issues during this process, refer to the [Troubleshooting](
    - **amount**: Amount must be provided in FLR units.
    - **node ID**, **start time** and **end time**: Use the values noted down from the [setup](#setup).
 
+   If you are adding a validator node, you also need to provide the proof of possession **BLS public key** and **BLS signature**.
+
+   Retrieve these details using the following command:
+
+   ```bash
+   curl -X POST --data '{
+    "jsonrpc":"2.0",
+    "id"     :1,
+    "method" :"info.getNodeID"
+   }' -H 'content-type:application/json;' 127.0.0.1:9650/ext/info | jq
+   ```
+
+   The output will be similar to the following:
+
+   ```plaintext
+   {
+   "jsonrpc": "2.0",
+   "result": {
+      "nodeID": "NodeID-CGeHNYkQJX4qb21x976PEcNt3FqsUZfXL",
+      "nodePOP": {
+         popBLSPublicKey ---> "publicKey": "0xb6a40b905128c010e4d7b0cbd6f7b7912a1da9a6022a8c720887b5183a4f2f109c678027316ae4757f7f987f1fa5addb",
+         popBLSSignature ---> "proofOfPossession": "0xb9394ef2992a77a3b70440c2fdb3b2a53f23fb8579460322b69a290bf3de7fafc2665b155b5300c08a1e7bcb45bb7eaf0ca7f596650b0423f61f329744e37f6908c1d7e4191378d5f0ff7fd7f8abd02d37a2be9dd95635a0b1f744b043cb5d9e"
+      }
+   },
+   "id": 1
+   }
+   ```
+
 3. If you selected **Add a validator node**, you have to set the **delegation fee**. This is the percentage of all rewards that the node owner keeps.
    The rest is split proportionally between the self-bond and all delegators that contributed stake. 10 means 10%, so the maximum value is 100.
 
@@ -420,6 +448,8 @@ If you encounter any issues during this process, refer to the [Troubleshooting](
    ? Enter start time(E.g. 1693185095): ●●●●●●●●
    ? Enter end time(E.g. 1693185095): ●●●●●●●●
    ? Enter delegation fee(E.g. 10): 10
+   ? Please enter the popBLSPublicKey: 0x●●●●●●●●
+   ? Please enter the popBLSSignature: 0x●●●●●●●●
    ```
 
 4. You are then asked to confirm the staking transaction on your hardware wallet.

docs/run-node/2-from-source.mdx

@@ -30,7 +30,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    # 1. Find the latest stable release tag from:
    #    https://github.com/flare-foundation/go-flare/releases
    # 2. Set the tag name in the variable below:
-   LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.10.0
+   LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
    ```
 
 2. Clone and build the binary:
@@ -63,6 +63,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    ```bash
    ./build/avalanchego --network-id=flare \
       --http-host= \
+      --http-allowed-hosts="*" \
       --bootstrap-ips="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeIP"}' -H 'content-type:application/json;' https://flare-bootstrap.flare.network/ext/info  | jq -r '.result.ip')" \
       --bootstrap-ids="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeID"}' -H 'content-type:application/json;' https://flare-bootstrap.flare.network/ext/info | jq -r '.result.nodeID')"
    ```
@@ -74,6 +75,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    ```bash
    ./build/avalanchego --network-id=costwo \
       --http-host= \
+      --http-allowed-hosts="*" \
       --bootstrap-ips="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeIP"}' -H 'content-type:application/json;' https://coston2-bootstrap.flare.network/ext/info  | jq -r '.result.ip')" \
       --bootstrap-ids="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeID"}' -H 'content-type:application/json;' https://coston2-bootstrap.flare.network/ext/info | jq -r '.result.nodeID')"
    ```
@@ -85,6 +87,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    ```bash
    ./build/avalanchego --network-id=songbird \
       --http-host= \
+      --http-allowed-hosts="*" \
       --bootstrap-ips="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeIP"}' -H 'content-type:application/json;' https://songbird-bootstrap.flare.network/ext/info  | jq -r '.result.ip')" \
       --bootstrap-ids="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeID"}' -H 'content-type:application/json;' https://songbird-bootstrap.flare.network/ext/info | jq -r '.result.nodeID')"
    ```
@@ -96,6 +99,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    ```bash
    ./build/avalanchego --network-id=coston \
       --http-host= \
+      --http-allowed-hosts="*" \
       --bootstrap-ips="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeIP"}' -H 'content-type:application/json;' https://coston-bootstrap.flare.network/ext/info  | jq -r '.result.ip')" \
       --bootstrap-ids="$(curl -m 10 -sX POST --data '{"jsonrpc":"2.0", "id":1, "method":"info.getNodeID"}' -H 'content-type:application/json;' https://coston-bootstrap.flare.network/ext/info | jq -r '.result.nodeID')"
    ```
@@ -114,6 +118,62 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
    curl http://127.0.0.1:9650/ext/health | jq
    ```
 
+3. (Optional) If you plan to [register your node as a validator](/run-node/register-validator).
+   Make sure to copy the staking keys to a persistent directory outside the default location.
+   This is important for ensuring that your staking keys are not lost if the node is restarted or updated.
+
+    <Tabs groupId="network" block>
+
+    <TabItem value="flare" label="Flare Mainnet" default>
+
+   ```bash
+   # Create a dedicated directory
+   sudo mkdir -p /opt/flare/staking
+   # Move your keys
+   sudo mv ~/.avalanchego/staking/staker.key /opt/flare/staking/
+   sudo mv ~/.avalanchego/staking/staker.crt /opt/flare/staking/
+   ```
+
+    </TabItem>
+
+    <TabItem value="coston2" label="Flare Testnet Coston2">
+
+   ```bash
+   # Create a dedicated directory
+   sudo mkdir -p /opt/coston2/staking
+   # Move your keys
+   sudo mv ~/.avalanchego/staking/staker.key /opt/coston2/staking/
+   sudo mv ~/.avalanchego/staking/staker.crt /opt/coston2/staking/
+   ```
+
+    </TabItem>
+
+    <TabItem value="songbird" label="Songbird Canary-Network">
+
+   ```bash
+   # Create a dedicated directory
+   sudo mkdir -p /opt/songbird/staking
+   # Move your keys
+   sudo mv ~/.avalanchego/staking/staker.key /opt/songbird/staking/
+   sudo mv ~/.avalanchego/staking/staker.crt /opt/songbird/staking/
+   ```
+
+    </TabItem>
+
+    <TabItem value="coston" label="Songbird Testnet Coston">
+
+   ```bash
+   # Create a dedicated directory
+   sudo mkdir -p /opt/coston/staking
+   # Move your keys
+   sudo mv ~/.avalanchego/staking/staker.key /opt/coston/staking/
+   sudo mv ~/.avalanchego/staking/staker.crt /opt/coston/staking/
+   ```
+
+    </TabItem>
+
+    </Tabs>
+
 :::tip[Node stuck when bootstrapping?]
 
 If the node gets stuck during bootstrap (or it takes far longer than the estimates given above), try adding the parameter `--bootstrap-retry-enabled=false` when running the node.
@@ -125,19 +185,21 @@ If the node gets stuck during bootstrap (or it takes far longer than the estimat
 These are some of the most relevant CLI parameters you can use. Read more about them in the [Avalanche documentation](https://docs.avax.network/nodes/maintain/avalanchego-config-flags).
 
 {/* prettier-ignore */}
-- [`--bootstrap-ips`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--bootstrap-ips-string),
-  [`--bootstrap-ids`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--bootstrap-ids-string):
+- [`--bootstrap-ips`](https://build.avax.network/docs/nodes/configure/configs-flags#--bootstrap-ips-string),
+  [`--bootstrap-ids`](https://build.avax.network/docs/nodes/configure/configs-flags#--bootstrap-ids-string):
   IP address and node ID of the peer used to connect to the rest of the network for bootstrapping. In the run command above, the bootstrap details are programmatically retrieved from the Flare bootstrap nodes upon startup. This is the recommended approach as the bootstrap node's IP and ID can rotate.
 
-- [`--http-host`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--http-host-string): Use `--http-host=` (empty) to allow connections from other machines. Otherwise, only connections from `localhost` are accepted.
+- [`--http-host`](https://build.avax.network/docs/nodes/configure/configs-flags#--http-host-string): Use `--http-host=` (empty) to allow connections from other machines. Otherwise, only connections from `localhost` are accepted.
+
+- [`--http-port`](https://build.avax.network/docs/nodes/configure/configs-flags#--http-port-int): The port through which the node will listen to API requests. The default value is `9650`.
 
-- [`--http-port`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--http-port-int): The port through which the node will listen to API requests. The default value is `9650`.
+- [`--http-allowed-hosts`](https://build.avax.network/docs/nodes/configure/configs-flags#--http-allowed-hosts-string): Use `--http-allowed-hosts="*"` to allow connections from any machine. Otherwise, only connections from `localhost` are accepted.
 
-- [`--staking-port`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--staking-port-int): The port through which the network peers will connect to this node externally. Having this port accessible from the internet is required for correct node operation. The default value is `9651`.
+- [`--staking-port`](https://build.avax.network/docs/nodes/configure/configs-flags#--staking-port-int): The port through which the network peers will connect to this node externally. Having this port accessible from the internet is required for correct node operation. The default value is `9651`.
 
-- [`--db-dir`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--db-dir-string-file-path): Directory where the database is stored, defaults to `~/.avalanchego/db`. Make sure to use a disk with enough space as recommended in the [hardware requirements](/run-node/system-requirements) page. For example, you can use this option to store the database on an external drive.
+- [`--db-dir`](https://build.avax.network/docs/nodes/configure/configs-flags#--db-dir-string-file-path): Directory where the database is stored, defaults to `~/.avalanchego/db`. Make sure to use a disk with enough space as recommended in the [hardware requirements](/run-node/system-requirements) page. For example, you can use this option to store the database on an external drive.
 
-- [`--chain-config-dir`](https://docs.avax.network/nodes/maintain/avalanchego-config-flags#--chain-config-dir-string): Optional JSON configuration file for using non-default values.
+- [`--chain-config-dir`](https://build.avax.network/docs/nodes/configure/configs-flags#--chain-config-dir-string): Optional JSON configuration file for using non-default values.
 
 #### Sample JSON configuration:
 
@@ -185,7 +247,7 @@ To update your node to a newer version of go-flare:
     # 1. Find the latest stable release tag from:
     #    https://github.com/flare-foundation/go-flare/releases
     # 2. Set the tag name in the variable below:
-    LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.10.1
+    LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
     git checkout ${LATEST_TAG}
     ```