Merge pull request #18 from Alex-ssvlabs/main

Multiple changes + initial cleanup

Author: RaekwonIII

docs/developers/tools/ssv-keys.md

@@ -50,7 +50,7 @@ Using the `ssv-keys` SDK can be simply summarized in 3 steps:
 :::info
 A requirement for splitting the keys of a validator, is to know the validator key owner's nonce (how many times this address has callded the registerValidator() function of the SSV contract) and their address.
 
-These can be obtained via the [SSV Scanner tool](../ssv-scanner/).
+These can be obtained via the [SSV SDK](../SSV-SDK/examples/api-calls/#get-nonce), or the [SSV Subgraph](./ssv-subgraph/subgraph-examples/#account-nonce).
 :::
 
 ## Example
@@ -70,7 +70,7 @@ const keystore = require('./path-to-keystore.json');
 const keystorePassword = 'XYZ';
 
 // The nonce of the owner within the SSV contract (increments after each validator registration), obtained using the ssv-scanner tool
-const TEST_OWNER_NONCE = 1;
+const TEST_OWNER_NONCE = 0;
 // The cluster owner address
 const TEST_OWNER_ADDRESS = '0x81592c3de184a3e2c0dcb5a261bc107bfa91f494';
 

docs/operators/liquidator-bot/README.md

@@ -26,3 +26,4 @@ OWNER                                          OPERATORIDS     BALANCE     BURNR
 2. **Liquidating accounts** \
    Once the potential liquidation block is reached the liquidator bot will call the [liquidate()](../../developers/smart-contracts/ssvnetwork#liquidateowner-operatorids-cluster) function in the network contract, if the bot was the first to successfully pass the transaction the cluster will be liquidated and its SSV collateral will be sent to the wallet address which performed the liquidation  
 
+You can find the [installation instructions here](./installation).

docs/operators/operator-node/README.md

@@ -7,9 +7,9 @@ sidebar_position: 7
 
 Operators provide hardware infrastructure, run the SSV protocol, and are responsible for maintaining the overall health of the SSV network. Operators determine their own fees and are compensated for their integral services to the network by operating and maintaining validators on-behalf of stakers.
 
-To join the network as an operator a user must [install](installation.md) the SSV node software, and [register](../operator-management/registration.md) the operator to the network.
+To join the network as an operator a user must [install](./node-setup) the SSV node software, and [register](../operator-management/registration.md) the operator to the network.
 
-* [Installation Guide](installation.md)
+* [Installation Guide](./node-setup)
 * [Configuring MEV](configuring-mev.md)
 * [Enabling DKG](enabling-dkg.md)
 * [Operator Registration](../operator-management/registration.md)

docs/operators/operator-node/maintenance/README.md

@@ -1,2 +1,8 @@
 # Maintenance
 
+If you are having troubles with your SSV node visit
+* [Troubleshooting section](./troubleshooting.md).
+***
+To migrate your SSV node follow the guides
+* [Node Migration](./node-migration.md)
+* [DKG Migration](./dkg-operator-migration)

docs/operators/operator-node/maintenance/dkg-operator-migration.md

@@ -13,16 +13,16 @@ The recommended migration process could be summarised in the following steps:
 
 * Backup DKG files (if applicable)
 * Shut down DKG operator (if applicable) on the current machine
-* [Start DKG operator on the new machine](../enabling-dkg.md#start-ssv-dkg)
-* [Update operator metadata on the SSV WebApp](enabling-dkg.md#update-operator-metadata)
+* [Start DKG operator on the new machine](../node-setup/enabling-dkg/start-dkg-node/)
+* [Update operator metadata on the SSV WebApp](../node-setup/enabling-dkg/final-steps#update-operator-metadata)
 
 :::info
 Please note: since the DKG node does not have to be on the same machine as the SSV node, one can be migrated without having to migrate the other.
 :::
 
 ### DKG backup (if necessary)
 
-If you have followed [the dedicated guide to enable DKG for your operator](../enabling-dkg), you most likely have (at least) these files in the folder with your node configuration:
+If you have followed [the dedicated guide to enable DKG for your operator](../node-setup/enabling-dkg/start-dkg-node/), you most likely have (at least) these files in the folder with your node configuration:
 
 ```
 ⇒   tree

docs/operators/operator-node/maintenance/node-migration.md

@@ -7,7 +7,7 @@ As a node operator, it may happen that the software stack needs to be migrated t
 
 In such a scenario, it is very important to know what operations must be performed, in which order, and what are the sensitive pieces of data that need to be preserved and copied over to the new hardware. Here is a summary:
 
-### Procedure
+## Procedure
 
 In order to migrate the SSV Node to a different machine, it is necessary to shut down the current setup, **before** launching the new one.
 
@@ -17,19 +17,25 @@ Two nodes with the same public key should never be running at the same time. The
 
 So, for this reason, the migration process could be easily summarised in the following steps:
 
-* Backup node files
-* Shut down SSV Node on the current machine
-* Setup SSV Node on the new machine using backups
-* Wait at least one epoch
-* Start SSV Node service on the new machine
+1. Backup node files
+2. Shut down SSV Node on the current machine
+3. Setup SSV Node on the new machine using backups
+4. Wait at least one epoch
+5. Start SSV Node service on the new machine
 
 :::warning
 Please note: if you are also running a DKG operator node, you may have to [follow the DKG operator migration guide](./dkg-operator-migration), if it is running on the same machine as the SSV node, or if it is running on a different machine, but you need to decommission that machine as well.
 :::
 
-### Node backup
+## Node backup
 
-If you have followed [the dedicated Node setup guide](../installation.md), you most likely have (at least) these files in the folder with your node configuration:
+### SSV Stack setup
+
+If you have followed the [automatic node setup with SSV Stack](../node-setup), your files should be in `/ssv-stack/ssv-node-data` directory.
+
+### Manual Node setup
+
+If you have followed [the Manual Node setup guide](../node-setup/manual-setup), you most likely have (at least) these files in the folder with your node configuration:
 
 ```
 ⇒   tree
@@ -64,7 +70,7 @@ The configuration file (`config.yaml` in the code snippet above), is necessary f
 
 Operator keys are, essentially, the authentication method to identify an SSV node, and link it to an operator ID. As a consequence, whenever a node is moved to a different machine, they **absolutely must** be preserved and copied from the existing setup to the new one.
 
-The files in question are `encrypted_private_key.json` and `password` in the snippet above and if you have followed [the Node setup guide](../installation.md), the filenames should be the same for you.
+The files in question are `encrypted_private_key.json` and `password` in the snippet above and if you have followed [the Manual Node setup guide](../node-setup/manual-setup), the filenames should be the same for you.
 
 #### Node database