You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user/staking/switch-clients.md
+36-44Lines changed: 36 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
This guide explains how to switch execution and consensus clients on Dappnode for Ethereum, Gnosis, and Lukso networks. It includes detailed information about the switching process and expected waiting times for resynchronization and attestation.
4
4
5
5
## General Information
6
+
6
7
Important considerations before switching clients:
7
8
8
9
-**Downtime:** Switching clients will result in temporary downtime and missed attestations.
@@ -11,111 +12,101 @@ Important considerations before switching clients:
11
12
-**Backup:** Always backup your validator keys and wallet information before making any changes.
12
13
13
14
**Basic Switching Process Overview**
14
-
The following switching process applies to Ethereum, Gnosis and Lukso.
15
-
- Install new client.
16
-
- Go to the stakers tab in the left menu.
15
+
The following switching process applies to Ethereum, Gnosis and Lukso.
16
+
17
+
- Install new client.
18
+
- Go to the stakers tab in the left menu.
17
19
- Select the new client.
18
20
- Click on the Apply changes button.
19
-
20
-
21
21
22
-
- Wait for synchronization. You can view the sync process in the dashboard tab or inside the client package in the logs section.
23
-
22
+
24
23
24
+
- Wait for synchronization. You can view the sync process in the dashboard tab or inside the client package in the logs section.
25
+
25
26
26
27
**What's happening during Sync?**
28
+
27
29
- Connecting to peers on the network
28
30
- Downloading block headers and bodies
29
31
- Processing and validating transactions
30
32
- Building the state trie and other database structures
31
33
- Executing all historical transactions
32
34
33
-
34
-
**Verify correct operation**
35
-
Go to the new client package in the packages tab and check the logs section (Technical knowledge is needed to read the logs)
36
-
Go to Beaconcha.in dashboard and check if your validators are active and attesting.
37
-
35
+
**Verify correct operation**
36
+
Go to the new client package in the packages tab and check the logs section (Technical knowledge is needed to read the logs)
37
+
Go to Beaconcha.in dashboard and check if your validators are active and attesting.
38
38
39
39
## Execution client switch
40
40
41
-
The current execution clients supported in Dappnode are the following:
41
+
The current execution clients supported in Dappnode are the following:
42
42
43
43
- Ethereum execution clients: Reth, Geth, Nethermind, Erigon and Besu
44
44
- Gnosis execution clients: Nethermind and Erigon
45
45
- Lukso execution client: Geth
46
46
47
-
Switching execution clients is a **critical operation that can substantially impact attestation performance** due to the extensive sync time required. Additionally, it is important to consider that installing a new execution client demands significant disk space.
48
-
49
-
47
+
Switching execution clients is a **critical operation that can substantially impact attestation performance** due to the extensive sync time required. Additionally, it is important to consider that installing a new execution client demands significant disk space.
50
48
51
49
| Sync time | Attestattion impact | Disk space required |
If the client was not downloaded and sync previously, an initial sync is needed. It typically takes from 12 to 48 hours depending on the client. All times mentioned here assume standard Solid State Disk storage and reasonable network conditions. Actual times may vary based on hardware, network conditions, and chain state. Attestation impact directly correlates with sync time plus small overhead for client initialization.
57
54
58
-
:::info
59
-
The sync process might **require high resources of your hardware**, do not worry if your CPU temperature reaches 100ºC or your CPU usage is +90%, it is normal during the sync process. It would be problematic only if it stays at these levels for several days. In this case check maintenance practices in this documentation.
55
+
:::info
56
+
The sync process might **require high resources of your hardware**, do not worry if your CPU temperature reaches 100ºC or your CPU usage is +90%, it is normal during the sync process. It would be problematic only if it stays at these levels for several days. In this case check maintenance practices in this documentation.
60
57
:::
61
58
62
59
## Consensus client switch
63
60
64
-
The current consensus clients supported in Dappnode are the following:
61
+
The current consensus clients supported in Dappnode are the following:
65
62
Ethereum consensus clients: Lighthouse, Teku, Lodestar Nimbus and Prysm.
66
-
Gnosis consensus clients: Lighthouse, Teku, Lodestar and Nimbus
63
+
Gnosis consensus clients: Lighthouse, Teku, Lodestar and Nimbus
67
64
Lukso consensus clients: Teku and Prysm
68
65
69
-
Switching consensus clients is a **quick action and the attestation impact is limited**. Consensus clients do not require a lot of space to run properly.
66
+
Switching consensus clients is a **quick action and the attestation impact is limited**. Consensus clients do not require a lot of space to run properly.
70
67
71
68
| Sync time | Attestattion impact | Disk space required |
All consensus clients have a **sync time of 5-10 minutes** max thanks to checkpoint sync.
76
-
Checkpoint sync helps to connect to the current state of the blockchain getting the data from an external node, so it does not need to start from scratch, reducing the time of synchronization significantly.
73
+
Checkpoint sync helps to connect to the current state of the blockchain getting the data from an external node, so it does not need to start from scratch, reducing the time of synchronization significantly.
77
74
78
-
It is always advisable to switch to a new consensus client from scratch (without existent volumes) to trigger the checkpoint sync. Otherwise, if you have a client with previous blockchain data, it will require more time to sync.
75
+
It is always advisable to switch to a new consensus client from scratch (without existent volumes) to trigger the checkpoint sync. Otherwise, if you have a client with previous blockchain data, it will require more time to sync.
79
76
80
-
:::info
77
+
:::info
81
78
After sync time completes, it has an extra downtime of 1-3 epochs (6 - 18 minutes). This is the “doppelganger” check, an extra protection measure to avoid slashing.
82
79
:::
83
80
84
81
## Blockchains sync time & recommended disk space
85
-
The sync time varies depending on the blockchain selected to run your validators.
82
+
83
+
The sync time varies depending on the blockchain selected to run your validators.
86
84
87
85
| Blockchain | Sync time | Disk space recommended |
**Plan Your Switch**: Choose a time with low network activity for switching to minimize the impact of missed attestations.
98
95
99
-
100
-
**Don't Delete Old Client Data Immediately:** Keep the data from your old client for a few days in case you need to switch back. If you want to keep the new client in the long term, we recommend deleting the previous client before installing the new one to ensure enough disk space
101
-
96
+
**Don't Delete Old Client Data Immediately:** Keep the data from your old client for a few days in case you need to switch back. If you want to keep the new client in the long term, we recommend deleting the previous client before installing the new one to ensure enough disk space
102
97
103
98
**Monitor Synchronization:** Use Dappnode's dashboard to monitor the synchronization progress of your new client.
104
99
105
-
106
-
**Verify Client Health:** After switching, verify that your new client is properly connected to the network and producing attestations in the package logs.
107
-
100
+
**Verify Client Health:** After switching, verify that your new client is properly connected to the network and producing attestations in the package logs.
108
101
109
102
**Check Logs:** Regularly check the logs of your new client to ensure there are no errors or issues.
110
103
111
-
112
104
**Update API Connections:** If you have any external tools connecting to your node, update their connection settings to point to the new client.
113
105
114
-
115
-
**Enable Dappnode notifications:** Push notifications can help to track the status of your validators and clients.
116
-
106
+
**Enable Dappnode notifications:** Push notifications can help to track the status of your validators and clients.
117
107
118
108
## Troubleshooting
109
+
119
110
Common Issues and Solutions
120
111
121
112
<details>
@@ -160,5 +151,6 @@ Common Issues and Solutions
160
151
</details>
161
152
162
153
If you are experiencing a different problem, you can:
154
+
163
155
- Ask the community in the support channel in Discord.
164
-
- Subscribe to **Dappnode Premium** to be guided by a Dappnode team member personally.
156
+
- Subscribe to **Dappnode Premium** to be guided by a Dappnode team member personally.
0 commit comments