Skip to main content


Nethermind is an Execution layer client developed by the Nethermind team.


Nethermind currently holds the supermajority client position on Gnosis Chain. We suggest considering a switch to Erigon.

Nethermind reference:

There are 2 main options for running Nethermind:

Nethermind can be configured to run different types of nodes:


Ensure the prerequisite steps have been completed in Step 1: Configure Server.

Option 1: Using Docker

1. Folder Structure

Create your folder structure:

mkdir -p /home/$USER/gnosis/execution
mkdir /home/$USER/gnosis/jwtsecret
├── jwtsecret/
└── execution/

2. Docker Compose

Create a docker-compose file with your favorite text editor in /home/$USER/gnosis/docker-compose.yml:

Example Docker Compose file
version: "3"

container_name: execution
image: nethermind/nethermind:latest
restart: always
stop_grace_period: 1m
- gnosis_net
- 30303:30303/tcp # p2p
- 30303:30303/udp # p2p
- 8545 # rpc
- 8551 # engine api
- /home/$USER/gnosis/execution:/data
- /home/$USER/gnosis/jwtsecret/jwt.hex:/jwt.hex
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
command: |
driver: "local"

name: gnosis_net

3. JWT Secret

The JWT secret is a token that allows the EL client to communicate with the CL client, and is required for Nethermind to operate post-merge. We use rand to create a random string, and store the jwt.hex file in /home/$USER/gnosis/jwtsecret/.

Check create JWT section in Step 1: Configure Server.

4. Start Container

Start the Execution layer client listed in the compose file:

cd /home/$USER/gnosis
docker-compose up -d

5. Monitor Logs

Check your logs with:

docker logs -f --tail 500 execution

6. Updating your Node

To update, just pull the new image, then stop and restart your docker-compose file:

cd /home/$USER/gnosis
docker-compose pull
docker-compose stop
docker-compose up -d

Option 2: Running as System Process

Installing Nethermind

Running Nethermind

Nethermind has ‘Nethermind launcher’ an easy GUI where you can configure your node from release.


# Gnosis Mainnet
./nethermind --config gnosis --JsonRpc.JwtSecretFile=<PATH to jwt.hex>

# Chiado Testnet
./nethermind --config chiado --JsonRpc.JwtSecretFile=<PATH to jwt.hex>

Linux and MAC

# Gnosis Mainnet
nethermind --config gnosis --JsonRpc.JwtSecretFile=<PATH to jwt.hex>

# Chiado Testnet
nethermind --config chiado --JsonRpc.JwtSecretFile=<PATH to jwt.hex>

Nethermind Archival Node

An archival node executes a heavy historical sync verifying all the transactions and keeping all of the historical data. Archive sync is the 'heaviest' and slowest sync mode, and can take 2 - 6 weeks depending on the speed of your IO.


Make sure there's enough disk space to accommodate the archive data, the minimum amount of disk required to run the archive node is +2 TB (Feb 2023).

Edit your /home/$USER/gnosis/docker-compose.yml and change the --config from gnosis to gnosis_archive.

    command: |