Solo Gnosis staking Validator guide

Run a validator for Gnosis staking

Stakers.space guide works with a concept of validator instances. You are used to have only one validator service from the other staking guides. However, this one service is just a single instance. This guide supports you to set multiple such validator instances on a single machine (if necessary), which has following benefits:

You are able to keep validators separated - e.g. based on used deposit / withdrawal / fee recipient wallet address
Keep logs in smaller size
Remove a limitation of thread perofmance - with more instances you are able to you your CPU and threads in a more efficient way that results in option to run more validators on a single machine.

Under 1 validator instance you can run 1 as well as hundreds of validators. We did numerous tests of efficient number of validators per instances and number of instances on a single machine. We can share this experience under a paid serice.

Validator Keys

Validator keys

To configurate an instance of validator service, you need at least one keystore. 1 keystore represents 1 validator. You can generate keystores on an offline PC with Validator Data generator tool, see the guide.

Get Keystores

Keystores can be generated with validator keys generation guide.

The tool generates a directory deposit_keys with keystore json files and 1 deposit json file.
Generate validator keys
Copy keystores to your machine

Note: If you do not have validator keystores generated yet, follow the Guide to generate keystores.
- Before copying, create following directory for keystores on your staking machine
```
mkdir -p $HOME/keystores
```
- Copy your keystores to $HOME/keystores on your staking machine.
  1. Create a directory for your USB stick (if not created yet)
    sudo mkdir /media/usb
  2. Mount USB stick to /media/usb directory
    sudo mount -t vfat /dev/sda1 /media/usb -o uid=1000
  3. Copy keystores from /media/usb/deposit_keys to $HOME/keystores
    Folder with keystores to copy:
    cp -r /media/usb/deposit_keys ~/keystores
  4. Umount USB stick
    sudo umount /media/usb
  scp can be only used if you have access to your staking machine over ssh, see securing ssh chapter.
  
  on MacOS / Linux Terminal, from the directory with deposit_keys folder, run the following command:
  
  Path into directory with keystores:
```
scp -P SSHport -i ~/.ssh/<SSHprivateKEY> -r deposit_keys myserveruser@<IP>:~/keystores
```

Validator Instance

Configurate & Run Validator instance for Gnosis staking

Instance ID:
Fee Recipient wallet:
Validator Instance service config
- Name:
- User:
- Data:

Do you want to create a new validation instance or extend exisiting instance for more validators?
- Create a directory for validator instance data
```
sudo mkdir -p /var/lib/gnosis/lighthouse/vi1
```
- Load keystores to /var/lib/gnosis/lighthouse/vi1
  Directory with Deposit Data keystores:
```
sudo /usr/local/bin/lighthouse --network gnosis account validator import --reuse-password --directory $HOME/keystores/ddk_i1 --datadir /var/lib/gnosis/lighthouse/vi1
```
  - Insert keystores encryption password (the one used during keystores generation) on request
  - If there are keystores with different encryption password, repeat the process for each encryption password
- Create a service user for the validator instance
```
sudo useradd --system --no-create-home --shell /bin/false gno-lighthouse-vi1
```
- Set ownership of /var/lib/gnosis/lighthouse/vi1 to validators-i1 user
```
sudo chown -R gno-lighthouse-vi1:gno-lighthouse-vi1 /var/lib/gnosis/lighthouse/vi1
```
- Create configuration service file for gno-lighthouse-vi1 service
  1. Open the configuration file
    
    sudo nano /etc/systemd/system/gno-lighthouse-vi1.service
  2. Copy the configuration below into the file.
    
    What's fee recipient wallet?
    
    What's your execution client?
    
    [Unit] Description=Lighthouse Validator Instance (Gnosis Network) Wants=network-online.target After=network-online.target [Service] User=gno-lighthouse-vi1 Group=gno-lighthouse-vi1 Type=simple Restart=always RestartSec=5 ExecStart=/usr/local/bin/lighthouse vc \ --network gnosis \ --datadir /var/lib/gnosis/lighthouse/vi1 \ --suggested-fee-recipient 0xXXXXXXXXXXXXXXXX \ --beacon-nodes http://localhost:5052 \ --graffiti "Nethermind+Lighthouse" [Install] WantedBy=multi-user.target
  3. Press CTRL + X then Y then ENTER to save and exit the config file.
- Stop running validator instance gno-lighthouse-vi1
```
sudo systemctl stop gno-lighthouse-vi1
```
- Extend /var/lib/gnosis/lighthouse/vi1 for new keystores
```
sudo /usr/local/bin/lighthouse --network gnosis account validator import --reuse-password --directory $HOME/keystores/ddk_i1 --datadir /var/lib/gnosis/lighthouse/vi1
```
  - You will be requested to insert keystores encryption password (the one used during keystores generation)
  - If there are keystores with different encryption password, repeat the process for each encryption password
  - Already existing keystores in the directory will be skipped
Load processed changes to the system
```
sudo systemctl daemon-reload
```
Start the validator instance
```
sudo systemctl start gno-lighthouse-vi1
```

Check the running validator instance

systemctl status gno-lighthouse-vi1

journalctl -fu gno-lighthouse-vi1

Activate service to start automatically on system startup
sudo systemctl enable gno-lighthouse-vi1
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

A guide to install the util is attached on the Github.

Open Delayed Start shell
sudo nano /usr/local/bin/delayed-start.sh

Configurate service start inside it

systemctl start gno-lighthouse-vi1.service

Be sure, delayed-start.service service controlling delayed-start.sh is enabled for auto start with system startup
sudo systemctl enable delayed-start.service
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Staking Manager util

A guide to install each util is attached on the Github.
1. Configurate Staking Manager util
  - Open the configuration file
    sudo nano /usr/local/etc/staking/config/clients.conf
    
    If the file is empty, generate it with command sudo /usr/local/bin/staking.sh init
  - Set link to proper service. It should be as follow:
    validatorServices="gno-lighthouse-vi1"
    
    If you place more services to the category, separate them with a space, see validatorServices="service1 service2 service3 ..."
2. Activate service to start automatically on OS startup
  - Open Start with delay util
    sudo nano /usr/local/bin/delayed-start.sh
  - Place or uncomment a command to start the validator client(s)
    /usr/local/bin/staking.sh start validators
  - Verify, that a service `delayed-start.service` exists and is automatically launched on system start.
    sudo systemctl enable delayed-start.service

Guide to exit validator is available at https://stakers.space/lighthouse/exit-validator.

Instance ID:
Fee Recipient wallet:
Validator Instance service config
- Name:
- User:
- Data:

Do you want to create a new validation instance or extend exisiting instance for more validators?
- Create a directory for validator instance data
```
sudo mkdir -p /var/lib/gnosis/lodestar/vi1
```
- Enable accessing /var/lib/gnosis/lodestar/vi1 for server user myserveruser
```
sudo chown -R myserveruser:myserveruser /var/lib/gnosis/lodestar/vi1
```
- Load keystores to /var/lib/gnosis/lodestar/vi1
  Directory with Deposit Data keystores:
  Move to Lodestar client directory
```
cd /usr/local/bin/lodestar
```
```
./lodestar validator import --network gnosis --importKeystores $HOME/keystores/ddk_i1 --dataDir /var/lib/gnosis/lodestar/vi1
```
  - Insert keystores encryption password (the one used during keystores generation) on request
  - If there are keystores with different encryption password, repeat the process for each encryption password
- Create a service user for the validator instance
```
sudo useradd --system --no-create-home --shell /bin/false gno-lodestar-vi1
```
- Set ownership of /var/lib/gnosis/lodestar/vi1 to lodestar-vi1 user
```
sudo chown -R gno-lodestar-vi1:gno-lodestar-vi1 /var/lib/gnosis/lodestar/vi1
```
- Enable access to NodeJs for user lodestar-vi1
  User with NodeJs:
```
sudo usermod -aG nodejsusr gno-lodestar-vi1
```
- Create configuration service file for gno-lodestar-vi1 service
  1. Open the configuration file
    
    sudo nano /etc/systemd/system/gno-lodestar-vi1.service
  2. Copy the configuration below into the file.
    
    Installed NodeJs version on the server:
    This can be get with command node -v
    
    What's fee recipient wallet?
    
    What's your execution client?
    
    [Unit] Description=Lodestar Validator Instance (Gnosis Network) Wants=network-online.target After=network-online.target [Service] User=gno-lodestar-vi1 Group=gno-lodestar-vi1 Type=simple Restart=always RestartSec=5 WorkingDirectory=/usr/local/bin/lodestar Environment="PATH=/home/nodejsusr/.nvm/versions/node/v22.16.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ExecStart=/usr/local/bin/lodestar/lodestar validator \ --network gnosis \ --dataDir /var/lib/gnosis/lodestar/validators/i1 \ --suggestedFeeRecipient 0xXXXXXXXXXXXXXXXX \ --beaconNodes http://127.0.0.1:9596 \ --force \ --graffiti "Nethermind+Lodestar" [Install] WantedBy=multi-user.target
    
    Notes
    
    All flags: https://chainsafe.github.io/lodestar/run/validator-management/validator-cli/
  3. Press CTRL + X then Y then ENTER to save and exit the config file.
- Adding validator instance to staking services manager
  
  If you use a staking manager client, add the new instance into it.
- Stop running validator instance gno-lodestar-vi1
```
sudo systemctl stop gno-lodestar-vi1
```
- Extend /var/lib/gnosis/lodestar/validators/i1 for new keystores
```
./lodestar validator import --network gnosis --importKeystores $HOME/keystores/ddk_i1 --dataDir /var/lib/gnosis/lodestar/vi1
```
  - You will be requested to insert keystores encryption password (the one used during keystores generation)
  - If there are keystores with different encryption password, repeat the process for each encryption password
  - Already existing keystores in the directory will be skipped
Load processed changes to the system
```
sudo systemctl daemon-reload
```
Start the validator instance
```
sudo systemctl start gno-lodestar-vi1
```

Check the running validator instance

systemctl status gno-lodestar-vi1

journalctl -fu gno-lodestar-vi1

Other configurations
Activate service to start automatically on OS startup
sudo systemctl enable gno-lodestar-vi1
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

A guide to install the util is attached on the Github.

Open Delayed Start shell
sudo nano /usr/local/bin/delayed-start.sh

Configurate service start inside it

systemctl start gno-lodestar-vi1.service

Be sure, delayed-start.service service controlling delayed-start.sh is enabled for auto start with system startup
sudo systemctl enable delayed-start.service
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Staking Manager util

Lodestar Validator Log Monitor

A guide to install each util is attached on the Github.
1. Configurate Staking Manager util
  - Open the configuration file
    sudo nano /usr/local/etc/staking/config/clients.conf
    
    If the file is empty, generate it with command sudo /usr/local/bin/staking.sh init
  - Set link to proper service. It should be as follow:
    validatorServices="gno-lodestar-vi1"
    
    If you place more services to the category, separate them with a space, see validatorServices="service1 service2 service3 ..."
2. Activate service to start automatically on OS startup
  - Open Start with delay util
    sudo nano /usr/local/bin/delayed-start.sh
  - Place or uncomment a command to start the validator client(s)
    /usr/local/bin/staking.sh start validators
  - Verify, that a service `delayed-start.service` exists and is automatically launched on system start.
    sudo systemctl enable delayed-start.service
Configurate Lodestar validator Log monitor service

Log monitor service monitors the service log and process defined action (fixes) in a case of any issue detected.
1. Check, whether the logmonitor util is installed:
```
/usr/local/bin/logmonitor.sh version
```
  If the util is not installed, install Lodestar validator Log monitor from GitHub.
2. Check defined Errors list for lodestarvalidator service
```
sudo nano /usr/local/etc/lodestarvalidator_tracking_records.txt
```
  If not available, download it from GitHub. You can also modifiy it, if needed.
3. Configurate the validator log monitor for service gno-lodestar-vi1, see guide on Github.
4. Place validator logmonitor service into /usr/local/bin/delayed-start.sh util to start it automatically on system startup
  1. Open delayed-start.sh
    sudo nano /usr/local/bin/delayed-start.sh
  2. Place validator logmonitor service into the file
    systemctl start gno-lodestar-vi1_logmonitor

Guide to exit validator is available at https://stakers.space/lodestar/exit-validator.

Instance ID:
Fee Recipient wallet:
Validator Instance service config
- Name:
- User:
- Data:

Do you want to create a new validation instance or extend exisiting instance for more validators?
- Create a directory for validator instance data
```
sudo mkdir -p /var/lib/gnosis/teku/vi1
```
- If exists, remove deposit_data file from keystores folder
  Directory with Deposit Data keystores:
  - Display files in the directory
    cd $HOME/keystores/ddk_i1 && ls -lh
  - If there is deposit_data-XXX....json file, remove it
    sudo rm deposit_data-XXX....json
- Copy keystores dedicated for instance into /var/lib/gnosis/teku/vi1/keystores folder
```
sudo mkdir /var/lib/gnosis/teku/vi1/keystores
```
```
sudo cp -a $HOME/keystores/ddk_i1/* /var/lib/gnosis/teku/vi1/keystores && cd /var/lib/gnosis/teku/vi1/keystores
```
- Teku requires a .txt file with encryption password for each .json validator file.
  1. Display all keystores in the directory
    ls -lh
  2. Whats's the first keystore name? .json
    
    Create a new .txt file for the keystore-m_12381_3600_X_0_0-XXXXXXXXXX.json keystore file
    
    sudo nano keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
    
    Insert an encryption password for the validator key (the one used during keystores generation) into that file.
    
    Press ctrl + x, then y to save and exit
  3. Set readonly permission for that file
    sudo chmod 400 keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
  Now, you can either repeate the process for all other keystores in the folder, or use an automated solution to duplicate the created password file (with modified name) for all remaining keystores, see Shell Script to generate password files for Teku.
  
  With automated process, to generate .txt file with a content of /var/lib/gnosis/teku/vi1/keystores/keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt for all remaining keystores in the /var/lib/gnosis/teku/vi1/keystores/ directory, use command
```
sudo /opt/teku-create-validator-psw-files.sh /var/lib/gnosis/teku/vi1/keystores/keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
```
- Create a service user for the validator instance
```
sudo useradd --system --no-create-home --shell /bin/false gno-teku-vi1
```
- Set ownership of validator instance data directory to validator-instance user
```
sudo chown -R gno-teku-vi1:gno-teku-vi1 /var/lib/gnosis/teku/vi1
```
- Create configuration service file for gno-teku-vi1 service
  1. Open the configuration file
    sudo nano /etc/systemd/system/gno-teku-vi1.service
  2. Copy the configuration below into the file.
    
    What's fee recipient wallet?
    
    What's your execution client?
    
    [Unit] Description=Teku Validator Instance (Gnosis Network) Wants=network-online.target After=network-online.target [Service] User=gno-teku-vi1 Group=gno-teku-vi1 Type=simple Restart=always RestartSec=5 Environment="JAVA_OPTS=-Xmx4g" Environment="TEKU_OPTS=-XX:-HeapDumpOnOutOfMemoryError" ExecStart=/usr/local/bin/teku/bin/teku validator-client \ --network gnosis \ --beacon-node-api-endpoint http://127.0.0.1:5051 \ #--beacon-node-api-endpoint http://127.0.0.1:5051,http://192.10.10.101:5051,http://192.140.110.44:5051 \ --data-path /var/lib/gnosis/teku/vi1 \ --validator-keys /var/lib/gnosis/teku/vi1/keystores:/var/lib/gnosis/teku/vi1/keystores \ --validators-proposer-default-fee-recipient 0xXXXXXXXXXXXXXXXX \ --validators-graffiti "Nethermind+Teku" [Install] WantedBy=multi-user.target
- Stop running validator instance gno-teku-vi1
```
sudo systemctl stop gno-teku-vi1
```
- If exists, remove deposit_data file from keystores folder
  Directory with Deposit Data keystores:
  - Display files in the directory
    cd $HOME/keystores/ddk_i1 && ls -lh
  - If there is deposit_data-XXX....json file, remove it
    rm deposit_data-XXX....json
- Copy keystores dedicated for instance into /var/lib/gnosis/teku/vi1/keystores folder
```
sudo mkdir /var/lib/gnosis/teku/vi1/keystores
```
```
sudo cp -a $HOME/keystores/ddk_i1/* /var/lib/gnosis/teku/vi1/keystores/keystores  && cd /var/lib/gnosis/teku/vi1/keystores
```
- Teku requires a .txt file with encryption password for each .json validator file.
  1. Display all keystores in the directory
    ls -lh
  2. Whats's the first keystore name? .json
    
    Vreate a new .txt file for the keystore-m_12381_3600_X_0_0-XXXXXXXXXX.json keystore file
    
    nano keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
    
    Insert an encryption password for the validator key (the one used during keystores generation) into that file.
    
    Press ctrl + x, then y to save and exit
  3. Set readonly permission for that file
    sudo chmod 400 keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
  Now, you can either repeate the process for all other keystores in the folder, or use an automated solution to duplicate the created password file (with modified name) for all remaining keystores, see Shell Script to generate password files for Teku.
  
  With automated process, to generate .txt file with a content of /var/lib/gnosis/teku/vi1/keystores/keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt for all remaining keystores in the /var/lib/gnosis/teku-vi1/keystores/ directory, use command
```
$HOME/bashscripts/create-teku-pswfiles.sh /var/lib/gnosis/teku/vi1/keystores/keystore-m_12381_3600_X_0_0-XXXXXXXXXX.txt
```
Load changes made in config files to the system
```
sudo systemctl daemon-reload
```
Start the validator instance
```
sudo systemctl start gno-teku-vi1
```

Check the running validator instance

systemctl status gno-teku-vi1

journalctl -fu gno-teku-vi1

Activate service to start automatically
sudo systemctl enable gno-teku-vi1
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Remove Lock files util.

A guide to install the util is attached on the Github.

Open Delayed Start shell
sudo nano /usr/local/bin/delayed-start.sh

Attach command to remove lock files (to prevent start the validator in a case of existing lock fiels after a power failure). This must be processed before starting the validator service.

/opt/remove-teku-validator-lock-files.sh '/var/lib/gnosis/teku/vi1/keystores'

Configurate service start inside it

systemctl start gno-teku-vi1.service

Be sure, delayed-start.service service controlling delayed-start.sh is enabled for auto start with system startup
sudo systemctl enable delayed-start.service
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Staking Manager util

Remove Lock files util.

A guide to install each util is attached on the Github.
1. Configurate Staking Manager util
  - Open the configuration file
    sudo nano /usr/local/etc/staking/config/clients.conf
    
    If the file is empty, generate it with command sudo /usr/local/bin/staking.sh init
  - Set link to proper service. It should be as follow:
    validatorServices="gno-teku-vi1"
    
    If you place more services to the category, separate them with a space, see validatorServices="service1 service2 service3 ..."
2. Activate service to start automatically on OS startup
  - Open Start with delay util
    sudo nano /usr/local/bin/delayed-start.sh
  - Attach command to remove lock files (to prevent start the validator in a case of existing lock fiels after a power failure). This must be processed before starting the validator service.
    
    /opt/remove-teku-validator-lock-files.sh '/var/lib/gnosis/teku/vi1/keystores'
  - Place or uncomment a command to start the validator client(s)
    /usr/local/bin/staking.sh start validators
  - Verify, that a service `delayed-start.service` exists and is automatically launched on system start.
    sudo systemctl enable delayed-start.service

Guide to exit validator is available at https://stakers.space/teku/exit-validator.

Instance ID:
Fee Recipient wallet:
Validator Instance service config
- Name:
- User:
- Data:

Do you want to create a new validation instance or extend exisiting instance for more validators?
- Create a directory for validator instance data
```
sudo mkdir -p /var/lib/gnosis/prysm/vi1
```
- Load keystores to /var/lib/gnosis/prysm/vi1
  Directory with Deposit Data keystores: Gnosis chain is not supported by Prysm client
  - Accept Terms of Use
  - Set a wallet password. This is different to the validator password you set during keys generation. Prysm will use this to decrypt the validator wallet. Back it up somewhere safe. You will need this later in this section and when configuring the validator.
  - Provide the validator keys password. This is the password you set when you created the keys during keys generation
  NOTE: If you have used different passwords for each of your validators you will get an error. Run the process multiple times, providing each of the different passwords until they are all imported. Use the accounts list command to verify.
- Create a Wallet Password File
  
  Create a file to store the wallet password so the Prysm validator service can access the wallet without you having to supply the password.
```
sudo nano /var/lib/gnosis/prysm/vi1/password.txt
```
  Press CTRL + X then Y then ENTER to save and exit the config file.
- Create a service user for the validator instance
```
sudo useradd --system --no-create-home --shell /bin/false gno-prysm-vi1
```
- Set ownership of /var/lib/gnosis/prysm/vi1 to validators-i1 user
```
sudo chown -R gno-prysm-vi1:gno-prysm-vi1 /var/lib/gnosis/prysm/vi1
```
- Create configuration service file for gno-prysm-vi1 service
  1. Open the configuration file
    
    sudo nano /etc/systemd/system/gno-prysm-vi1.service
  2. Copy the configuration below into the file.
    
    What's fee recipient wallet?
    
    What's your execution client?
    
    Gnosis chain is not supported
  3. Press CTRL + X then Y then ENTER to save and exit the config file.
- Stop running validator instance gno-prysm-vi1
```
sudo systemctl stop gno-prysm-vi1
```
- Extend /var/lib/gnosis/prysm/vi1 for new keystores
  Gnosis chain is not supported by Prysm client
  - Accept Terms of Use
  - Set a wallet password. This is different to the validator password you set during keys generation. Prysm will use this to decrypt the validator wallet. Back it up somewhere safe. You will need this later in this section and when configuring the validator.
  - Provide the validator keys password. This is the password you set when you created the keys during keys generation
  NOTE: If you have used different passwords for each of your validators you will get an error. Run the process multiple times, providing each of the different passwords until they are all imported. Use the accounts list command to verify.
Load processed changes to the system
```
sudo systemctl daemon-reload
```
Start the validator instance
```
sudo systemctl start gno-prysm-vi1
```

Check the running validator instance

systemctl status gno-prysm-vi1

journalctl -fu gno-prysm-vi1

Activate service to start automatically
sudo systemctl enable gno-prysm-vi1
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

A guide to install the util is attached on the Github.

Open Delayed Start shell
sudo nano /usr/local/bin/delayed-start.sh

Configurate service start inside it

systemctl start gno-prysm-vi1.service

Be sure, delayed-start.service service controlling delayed-start.sh is enabled for auto start with system startup
sudo systemctl enable delayed-start.service
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Staking Manager util

A guide to install each util is attached on the Github.
1. Configurate Staking Manager util
  - Open the configuration file
    sudo nano /usr/local/etc/staking/config/clients.conf
    
    If the file is empty, generate it with command sudo /usr/local/bin/staking.sh init
  - Set link to proper service. It should be as follow:
    validatorServices="gno-prysm-vi1"
    
    If you place more services to the category, separate them with a space, see validatorServices="service1 service2 service3 ..."
2. Activate service to start automatically on OS startup
  - Open Start with delay util
    sudo nano /usr/local/bin/delayed-start.sh
  - Place or uncomment a command to start the validator client(s)
    /usr/local/bin/staking.sh start validators
  - Verify, that a service `delayed-start.service` exists and is automatically launched on system start.
    sudo systemctl enable delayed-start.service

Guide to exit validator is available at https://stakers.space/prysm/exit-validator.

Instance ID:
Fee Recipient wallet:
Validator Instance service config
- Name:
- User:
- Data:

Do you want to create a new validation instance or extend exisiting instance for more validators?
- Create a directory for validator instance data
```
sudo mkdir -p /var/lib/gnosis/nimbus/vi1
```
- Load keystores to /var/lib/gnosis/nimbus/vi1
  Directory with Deposit Data keystores:
```
sudo /usr/local/bin/nimbus-validator import data-dir=/var/lib/gnosis/nimbus/vi1 $HOME/keystores/ddk_i1
```
  NOTE: If you have used different passwords for each of your validators you will get an error. Run the process multiple times, providing each of the different passwords until they are all imported. Use the accounts list command to verify.
- Create a service user for the validator instance
```
sudo useradd --system --no-create-home --shell /bin/false gno-nimbus-vi1
```
- Set ownership of /var/lib/gnosis/nimbus/vi1 to validators-i1 user
```
sudo chown -R gno-nimbus-vi1:gno-nimbus-vi1 /var/lib/gnosis/nimbus/vi1
```
- Create configuration service file for gno-nimbus-vi1 service
  1. Open the configuration file
    
    sudo nano /etc/systemd/system/gno-nimbus-vi1.service
  2. Copy the configuration below into the file.
    
    What's fee recipient wallet?
    
    What's your execution client?
    
    [Unit] Description=Nimbus Validator Instance (Gnosis Network) Wants=network-online.target After=network-online.target [Service] User=gno-nimbus-vi1 Group=gno-nimbus-vi1 Type=simple Restart=always RestartSec=5 ExecStart=/usr/local/bin/nimbus/nimbus_validator_client \ --network=gnosis \ --data-dir=/var/lib/gnosis/nimbus/vi1 \ --beacon-node=http://127.0.0.1:5052 \ --suggested-fee-recipient=0xXXXXXXXXXXXXXXXX \ --graffiti="Nethermind+Nimbus" [Install] WantedBy=multi-user.target
    
    See more flags at https://nimbus.guide/options.html
  3. Press CTRL + X then Y then ENTER to save and exit the config file.
- Stop running validator instance gno-nimbus-vi1
```
sudo systemctl stop gno-nimbus-vi1
```
- Extend /var/lib/gnosis/nimbus/vi1 for new keystores
```
sudo /usr/local/bin/nimbus-validator import data-dir=/var/lib/gnosis/nimbus/vi1 $HOME/keystores/ddk_i1
```
  NOTE: If you have used different passwords for each of your validators you will get an error. Run the process multiple times, providing each of the different passwords until they are all imported. Use the accounts list command to verify.
Load processed changes to the system
```
sudo systemctl daemon-reload
```
Start the validator instance
```
sudo systemctl start gno-nimbus-vi1
```

Check the running validator instance

systemctl status gno-nimbus-vi1

journalctl -fu gno-nimbus-vi1

Activate service to start automatically
sudo systemctl enable gno-nimbus-vi1
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

A guide to install the util is attached on the Github.

Open Delayed Start shell
sudo nano /usr/local/bin/delayed-start.sh

Configurate service start inside it

systemctl start gno-nimbus-vi1.service

Be sure, delayed-start.service service controlling delayed-start.sh is enabled for auto start with system startup
sudo systemctl enable delayed-start.service
Note

This option requires the following installed utils:

Start with Delay util with delayed-start.service

Staking Manager util

A guide to install each util is attached on the Github.
1. Configurate Staking Manager util
  - Open the configuration file
    sudo nano /usr/local/etc/staking/config/clients.conf
    
    If the file is empty, generate it with command sudo /usr/local/bin/staking.sh init
  - Set link to proper service. It should be as follow:
    validatorServices="gno-nimbus-vi1"
    
    If you place more services to the category, separate them with a space, see validatorServices="service1 service2 service3 ..."
2. Activate service to start automatically on OS startup
  - Open Start with delay util
    sudo nano /usr/local/bin/delayed-start.sh
  - Place or uncomment a command to start the validator client(s)
    /usr/local/bin/staking.sh start validators
  - Verify, that a service `delayed-start.service` exists and is automatically launched on system start.
    sudo systemctl enable delayed-start.service

Guide to exit validator is available at https://stakers.space/nimbus/exit-validator.

Keys Deposit

Fund validator keys for Gnosis staking

If everything works smoothly, you can deposit the validator keys now.

Deposit validator keys

Client Maintenance

Regular maintenance

As a regular member securying the network and processing blockchain operations on it, you need to keep your software up to date to avoid penalties and earning rewards for the work.

Guides for regular maintenance

Validator Exit

Exiting validators

You can exit the validator and withdraw the funds anytime.

Exit validator

Validator Duties

Other Validator actions

You can perform additional actions with your validator.

See Validator actions

Staking Emergency

Staking emergency

Does anything go wrong with your validator?

Check emergency guide

Interactive Solo Gnosis staking guide for Ubuntu OS

Disclaimer

Prerequisites for Gnosis staking

Installed and synced Execution and Consensus client

Sufficient capital

Run a validator for Gnosis staking

Validator keys

Get Keystores

Copy keystores to your machine

Configurate & Run Validator instance for Gnosis staking

Create a directory for validator instance data

Load keystores to /var/lib/gnosis/lighthouse/vi1

Create a service user for the validator instance

Set ownership of /var/lib/gnosis/lighthouse/vi1 to validators-i1 user

Create configuration service file for gno-lighthouse-vi1 service

Stop running validator instance gno-lighthouse-vi1

Extend /var/lib/gnosis/lighthouse/vi1 for new keystores

Load processed changes to the system

Start the validator instance

Check the running validator instance

Configurate Staking Manager util

Activate service to start automatically on OS startup

Create a directory for validator instance data

Enable accessing /var/lib/gnosis/lodestar/vi1 for server user myserveruser

Load keystores to /var/lib/gnosis/lodestar/vi1

Move to Lodestar client directory

Create a service user for the validator instance

Set ownership of /var/lib/gnosis/lodestar/vi1 to lodestar-vi1 user

Enable access to NodeJs for user lodestar-vi1

Create configuration service file for gno-lodestar-vi1 service

Notes

Adding validator instance to staking services manager

Stop running validator instance gno-lodestar-vi1

Extend /var/lib/gnosis/lodestar/validators/i1 for new keystores

Load processed changes to the system

Start the validator instance

Check the running validator instance

Other configurations

Activate service to start automatically on OS startup

Configurate Staking Manager util

Activate service to start automatically on OS startup

Configurate Lodestar validator Log monitor service

Create a directory for validator instance data

If exists, remove deposit_data file from keystores folder

Copy keystores dedicated for instance into /var/lib/gnosis/teku/vi1/keystores folder

Create a service user for the validator instance

Create configuration service file for gno-teku-vi1 service

Stop running validator instance gno-teku-vi1

If exists, remove deposit_data file from keystores folder

Copy keystores dedicated for instance into /var/lib/gnosis/teku/vi1/keystores folder

Load changes made in config files to the system

Start the validator instance

Check the running validator instance

Activate service to start automatically

Configurate Staking Manager util

Activate service to start automatically on OS startup

Create a directory for validator instance data

Load keystores to /var/lib/gnosis/prysm/vi1

Create a Wallet Password File

Create a service user for the validator instance

Set ownership of /var/lib/gnosis/prysm/vi1 to validators-i1 user

Create configuration service file for gno-prysm-vi1 service

Stop running validator instance gno-prysm-vi1

Extend /var/lib/gnosis/prysm/vi1 for new keystores

Load processed changes to the system

Start the validator instance

Check the running validator instance

Activate service to start automatically

Configurate Staking Manager util

Activate service to start automatically on OS startup

Create a directory for validator instance data

Load keystores to /var/lib/gnosis/nimbus/vi1

Create a service user for the validator instance

Set ownership of /var/lib/gnosis/nimbus/vi1 to validators-i1 user

Create configuration service file for gno-nimbus-vi1 service

Stop running validator instance gno-nimbus-vi1

Extend /var/lib/gnosis/nimbus/vi1 for new keystores

Load processed changes to the system

Start the validator instance

Check the running validator instance

Load keystores to `/var/lib/gnosis/lighthouse/vi1`

Set ownership of `/var/lib/gnosis/lighthouse/vi1` to `validators-i1` user

Create configuration service file for `gno-lighthouse-vi1` service

Stop running validator instance `gno-lighthouse-vi1`

Extend `/var/lib/gnosis/lighthouse/vi1` for new keystores

Enable accessing `/var/lib/gnosis/lodestar/vi1` for server user `myserveruser`

Load keystores to `/var/lib/gnosis/lodestar/vi1`

Set ownership of `/var/lib/gnosis/lodestar/vi1` to `lodestar-vi1` user

Enable access to `NodeJs` for user `lodestar-vi1`

Create configuration service file for `gno-lodestar-vi1` service

Stop running validator instance `gno-lodestar-vi1`

Extend `/var/lib/gnosis/lodestar/validators/i1` for new keystores

If exists, remove `deposit_data` file from keystores folder

Copy keystores dedicated for instance into `/var/lib/gnosis/teku/vi1/keystores` folder

Create configuration service file for `gno-teku-vi1` service

Stop running validator instance `gno-teku-vi1`

If exists, remove `deposit_data` file from keystores folder

Copy keystores dedicated for instance into `/var/lib/gnosis/teku/vi1/keystores` folder

Load keystores to `/var/lib/gnosis/prysm/vi1`

Set ownership of `/var/lib/gnosis/prysm/vi1` to `validators-i1` user

Create configuration service file for `gno-prysm-vi1` service

Stop running validator instance `gno-prysm-vi1`

Extend `/var/lib/gnosis/prysm/vi1` for new keystores

Load keystores to `/var/lib/gnosis/nimbus/vi1`

Set ownership of `/var/lib/gnosis/nimbus/vi1` to `validators-i1` user

Create configuration service file for `gno-nimbus-vi1` service

Stop running validator instance `gno-nimbus-vi1`

Extend `/var/lib/gnosis/nimbus/vi1` for new keystores