Merge pull request #160 from gnosischain/ne-archive-update

Update info on how to run archive nodes

docs/node/execution-layer-validator.md

@@ -17,11 +17,11 @@ GC Nodes can be run with Nethermind client and the following recommended minimum
 ## Setup on Nethermind
 
 :::caution
-A majority of Gnosis validators are now running the Nethermind client. The latest version 1.12.7 includes support for the latest Gnosis HF.
+A majority of Gnosis validators are now running the Nethermind client. The latest version 1.14.1 includes support for the latest Gnosis HF.
 
-Version [https://github.com/NethermindEth/nethermind/releases/tag/1.12.7](https://github.com/NethermindEth/nethermind/releases/tag/1.12.7)
+Version [https://github.com/NethermindEth/nethermind/releases/tag/1.14.1](https://github.com/NethermindEth/nethermind/releases/tag/1.14.1)
 
-Ethstats: [https://dai-netstat.poa.network/](https://dai-netstat.poa.network)
+Ethstats: [https://ethstats.gnosischain.com/](https://ethstats.gnosischain.com/)
 :::
 
 Nethermind Launcher is a self-contained app - you do not need to install .NET separately to run it.
@@ -53,7 +53,7 @@ When you start the Launcher choose the following options to sync a node:
 
 *Replace `<user>` with your username on your device*
 ```bash
-    cd 
+    cd
     mkdir /home/<user>/nethermind
     mkdir /home/<user>/nethermind/nethermind_db
     mkdir /home/<user>/nethermind/keystore
@@ -90,7 +90,7 @@ services:
       - NETHERMIND_CONFIG=xdai
     logging:
       driver: "local"
- 
+
 networks:
   net:
     ipam:
@@ -111,7 +111,7 @@ docker-compose up
 To check logs:
 ```bash
 sudo docker ps -a
-sudo docker-compose logs -f <container name> 
+sudo docker-compose logs -f <container name>
 ```
 Container name should in this case be 'nethermind'
 
@@ -123,6 +123,10 @@ This can take 1-3 days to sync, so in the meantime you can connect your Beacon c
 
 A Gnosis archive node execute heavy historical sync verifying all the transactions and keeping all the historical state. In Nethermind, the default configuration activates the pruning functionality.
 
+:::caution
+Make sure there's enough disk space to accommodate the archive data, the minimum amount of disk required to run the archive node is as of today ~1.9 TB.
+:::
+
 To start a node as an archive node you will need to disable pruning in the config file when running an archive node.
 
 Set the following variable:
@@ -160,7 +164,7 @@ services:
       - NETHERMIND_CONFIG=xdai_archive
     logging:
       driver: "local"
- 
+
 networks:
   net:
     ipam:
@@ -174,7 +178,7 @@ Read more about the [Nethermind Sync Modes](https://docs.nethermind.io/nethermin
 
 ## Node Maintenance
 
-Once Nethermind has fully synced, you can point your validator nodes to it to use as an RPC to increase decentralization of the network. To do this or any other maintenence, you will have to take down your nodes, so make sure you closely follow the restart procedure closely to avoid slashing. 
+Once Nethermind has fully synced, you can point your validator nodes to it to use as an RPC to increase decentralization of the network. To do this or any other maintenence, you will have to take down your nodes, so make sure you closely follow the restart procedure closely to avoid slashing.
 
 ### Restart Procedure
 
@@ -196,4 +200,4 @@ Restart the containers using `docker-compose up` as you did initially when setti
 
 As was mentioned on the doc page for running a beacon chain node, if you decide to run a Gnosis client (Nethermind) and a Gnosis Beacon Chain client (Lighthouse, Teku, Nimbus or Prysm) on the same machine, we recommend [running both in the same docker-compose.yml](https://docs.docker.com/compose/extends/) file to enable RPC access by container name.
 
-If you have questions about config details for this type of setup, please [ask in our discord.](https://discord.gg/VQb3WzsywU)
+If you have questions about config details for this type of setup, please [ask in our discord.](https://discord.gg/VQb3WzsywU)