FAQ
Pull the latest version of Nethermind using the
latest
tag. You can find specific tag at Docker Hub.docker pull nethermind/nethermind:latest
or pull with docker-compose if the
nethermind/nethermind:latest
base image is specifieddocker-compose pull
Simply download the latest Nethermind package either from https://downloads.nethermind.io or https://github.com/NethermindEth/nethermind/releases and make sure that the package is extracted in the
WorkingDirectory
path defined in your systemd
service. Make sure to stop the service before the upgrade and start it after.WorkingDirectory=/home/nethermind/nethermind
Download the latest Nethermind package either from https://downloads.nethermind.io or https://github.com/NethermindEth/nethermind/releases and extract the package in the folder you currently use for running Nethermind. Make sure the service is down before the update. Make sure to stop the service before the upgrade and start it after.
This config downloads a minimal amount of bodies and receipts to be able to serve ETH2 validator requests since the deposit contract deployment. It also enables JSON RPC (important - make sure that you do not open firewall to the outside world!)
nethermind --config mainnet --Init.BaseDbPath /your/db/path
Try changing the config to a lower number (
--Network.ActivePeersMaxCount 25
)Your node is synced when it shows log lines starting with:
Processed ...
And the block numbers shown are at the head of the chain.
In blockchain, any node can never be 100% sure it is synced because there is no central source of truth - so your node is generally not able to tell you that it is synced but, it is able to tell you that it believes it is synced based on what it knows from the peers that it talks to).
You have to configure a few ports used by Nethermind.
Settings | Default Value | Comment |
---|---|---|
JsonRpc.EnginePort | 8551 | Remember to change it on your Consensus client. |
JsonRpc.Port | 8545 | Only needed if you are using standard JsonRpc |
JsonRpc.WebSocketsPort | 8545 | By default same as the JsonRpc port. Only relevant when you use WebSockets |
Network.P2PPort | 30303 | |
Network.DiscoveryPort | 30303 | |
The example of parameters that you have to pass to your second node when the first has been running with default settings:
--JsonRpc.EnginePort 8552 --JsonRpc.Port 8546 --Network.P2PPort 30304 --Network.DiscoveryPort 30304
Last modified 2mo ago