Skip to content

Commit 6edffc8

Browse files
committed
feat: add fairground and validators testnet to restart data-node from network history
1 parent f3083cb commit 6edffc8

File tree

1 file changed

+88
-1
lines changed

1 file changed

+88
-1
lines changed

docs/node-operators/how-to/restart-data-node-from-network-history.md

Lines changed: 88 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ title: How to restart data-node from the network history
44
sidebar_label: Restart data-node from the network history
55
hide_title: false
66
---
7+
import Tabs from '@theme/Tabs';
8+
import TabItem from '@theme/TabItem';
79

810

911
## Why would you start/restart your data node from network history?
@@ -64,6 +66,11 @@ vega tm unsafe_reset_all --home <tendermint-home>
6466

6567
The config is located in the `<vega_home>/config/data-node/config.toml`. Update the following parameters in your `config.toml` file for the data node:
6668

69+
70+
<Tabs groupId="network">
71+
<TabItem value="mainnet" label="Mainnet">
72+
73+
6774
```toml
6875
AutoInitialiseFromNetworkHistory = true
6976

@@ -80,10 +87,31 @@ AutoInitialiseFromNetworkHistory = true
8087
TimeOut = "4h"
8188
```
8289

90+
</TabItem>
91+
92+
<TabItem value="fairground" label="Fairground">
93+
94+
TBD for fairground
95+
96+
</TabItem>
97+
98+
<TabItem value="validators-testnet" label="Validator testnet">
99+
100+
TBD for validators-testnet
101+
102+
</TabItem>
103+
104+
</Tabs>
105+
83106
#### b. The vega core config
84107

85108
The config is located in the `<vega_home>/config/node/config.toml`. Update the following parameters in your `config.toml` file for the vega core:
86109

110+
<Tabs groupId="network">
111+
112+
<TabItem value="mainnet" label="Mainnet">
113+
114+
87115
```toml
88116
[Snapshot]
89117
StartHeight = -1
@@ -93,6 +121,22 @@ The config is located in the `<vega_home>/config/node/config.toml`. Update the f
93121
DialTimeout = "4h"
94122
```
95123

124+
</TabItem>
125+
126+
<TabItem value="fairground" label="Fairground">
127+
128+
TBD for fairground
129+
130+
</TabItem>
131+
132+
<TabItem value="validators-testnet" label="Validator testnet">
133+
134+
TBD for validators-testnet
135+
136+
</TabItem>
137+
138+
</Tabs>
139+
96140
#### c. Tendermint config
97141

98142
To update tendermint, you have to know the trust block and height. To collect the above information, please visit one of the following link:
@@ -106,6 +150,11 @@ Then select one of the latest pair for block height and hash
106150

107151
Once you have thrusted block, you can update the following parameters in the `<tendermint_home>/config/config.toml` file:
108152

153+
<Tabs groupId="network">
154+
155+
<TabItem value="mainnet" label="Mainnet">
156+
157+
109158
```toml
110159
[statesync]
111160
enable = true
@@ -128,6 +177,44 @@ trust_height = 3040600
128177
trust_hash = "b4b500d8fc84cce3a42b141193db7ba23ff03cc80b70cc817f6536582ebd5eda"
129178
```
130179

180+
</TabItem>
181+
182+
<TabItem value="fairground" label="Fairground">
183+
184+
```toml
185+
[statesync]
186+
enable = true
187+
rpc_servers = "n00.testnet.vega.rocks:26657,n06.testnet.vega.rocks:26657,n07.testnet.vega.rocks:26657"
188+
trust_height = &lt;height for collected block&gt;
189+
trust_hash = "&lt;hash for collected block&gt;"
190+
```
191+
192+
Example config:
193+
194+
:::warning
195+
Do not use below block. Please select newer block!
196+
:::
197+
198+
```toml
199+
[statesync]
200+
enable = true
201+
rpc_servers = "api0.vega.community:26657,api1.vega.community:26657,api2.vega.community:26657,api7.vega.community:26657"
202+
trust_height = 3040600
203+
trust_hash = "b4b500d8fc84cce3a42b141193db7ba23ff03cc80b70cc817f6536582ebd5eda"
204+
```
205+
206+
207+
208+
</TabItem>
209+
210+
<TabItem value="validators-testnet" label="Validator testnet">
211+
212+
TBD for validators-testnet
213+
214+
</TabItem>
215+
216+
</Tabs>
217+
131218
### 4. Start your node
132219

133220
:::warning
@@ -181,4 +268,4 @@ Open the `<vega_home>/config/data-node/config.toml` file and update the followin
181268

182269
:::info
183270
Do not restart your node. Just update config to avoid issues in the future restarts.
184-
:::
271+
:::

0 commit comments

Comments
 (0)