Here is a quick start example for Goerli testnet Nethermind sync.
Setup a VM¶
If you are not launching on your laptop/desktop then you will probably want to setup a cloud VM. You cand more info about setting up everything with selected cloud providers. Make sure that you configure firewall properly. You can check supported operating systems and architectures and hardware requirements
After launching Nethermind via ./Nethermind.Launcher you need to choose the Node to start first
Then select Goerli testnet
Then select fast sync mode
Then ensure that JSON RPC is enabled
Then skip the ethstats registration (you may need to press ENTER twice after that)
After the node starts you will see some initial info about the node and then the sync will start. Goerli fast sync uses a ‘fast blocks’ sync mode initially. The fast blocks sync picks some known pivot block from the past and downloads headers, bodies, and receipts downwards all the way to genesis block. The console display shows the number growing from 0 to pivot but this is just to make the display more user-friendly.
You will see some information about the sync progress, like below:
- Shows the number of already downloaded headers, bodies and receipts out of all to be downloaded in the fast blocks stage.
- Shows the current queue of already downloaded blocks, headers and receipts waiting for being saved to the database.
- Shows the current download speed (blocks per second - bps).
- Shows the average download speed (blocks per second - bps).
When the fast blocks stage finishes there will be some period of downloading blocks between the pivot and the latest blocks which will have some additional info:
- Shows the last entry from the fast blocks stage.
- Shows the mode transition moment.
- Displays the speed (in blocks per second) of all headers, bodies and receipts at the same time.
- Additional info will appear every 30000 blocks with information about the Goerli epoch being stored.
After the fast sync part finished the node will transition to the state sync stage when the state trie is being downloaded. Much information is displayed about the progress as this process may take a long time on mainnet (a few hours).
- Total elapsed time in state sync is displayed.
- Total downloaded DB size is displayed (on mainnet the sync finishes around 34GB in March 2020, on Goerli around 800MB).
- Download speed in kilobytes per second is displayed.
- Occasionally a queue review message may appear (you can ignore it).
- ‘P’ stands for the number of current parallel requests that the node is waiting for.
- ‘acc’ stands for the number of accounts data downloaded already.
- ‘nodes’ stands for the number of Patricia trie nodes downloaded by the sync process.
- ‘db_delay’ shows the time spent in the DB write / read access. The higher the value the worse. It may get much worse if you restart the node during the sync process as we need to recreate some caches then by reading data from the DB.
- Occasionally we display additional info about the health of requests and caches that you may ignore unless you need to report any issues.
When the state sync is nearing completion you may see a series of branch sync information realoading many times from 0% to nearly 100%. This is the node trying to retrieve the few remaining state nodes and progressing with the head block rapidly:
At some point the entire state is downloaded and the node enters the full sync mode and will allow you to issue CLI / Web3 queries and send / receive transactions.
- The root is saved at the moment when the entire Patricia trie is downloaded.
- We also clearly state that the node transitions to the full sync.
- When you see the block being processed then you are in the full sync and the newly arrived block is being calculated.
- Every two minutes you will see a summary of connected peers with their client version, IP address, highest synced block, and data download speeds.
Now you can launch CLI in the separate process (launching Nethermind.Launcher again and selecting CLI instead of Node). You can read more about CLI here.)
You can also connect to the node from Metamask by selecting localhost:8545 from the Metamask network list.