From 87faeb98e1e58e536baefedc9f584df1f12d0818 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kamil=20Chodo=C5=82a?= <43241881+kamilchodola@users.noreply.github.com> Date: Fri, 26 Jan 2024 13:00:04 +0100 Subject: [PATCH] Add info about p2p and discovery same port --- docs/get-started/migrating-from-geth.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/get-started/migrating-from-geth.md b/docs/get-started/migrating-from-geth.md index 0a3186a5e..349febc77 100644 --- a/docs/get-started/migrating-from-geth.md +++ b/docs/get-started/migrating-from-geth.md @@ -23,6 +23,7 @@ First, [install Nethermind](./installing-nethermind.md) and a [consensus client] - `--JsonRpc.EnginePort ` - `--Network.DiscoveryPort ` - `--Network.P2PPort ` +- **DiscoveryPort and P2PPort should use same value** ::: Once you fulfill the above requirements, you can start syncing Nethermind. To check the sync status, use the [`eth_syncing`](../interacting/json-rpc-ns/eth.md#eth_syncing) JSON-RPC method. When it returns `false`, Nethermind is considered fully synced with all block bodies and receipts needed to work properly as a validator. Another option to monitor the sync is a [health check](../monitoring/health-check.md).