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
Use `kwild` to create your initial configuration file:
23
32
@@ -30,7 +39,7 @@ kwild setup init \
30
39
31
40
For detailed instructions on configuration options more relevant to a production setup, refer to our [Configuration Guide](docs/creating-config.md).
32
41
33
-
### 2. Enable State Sync
42
+
### 3. Enable State Sync
34
43
35
44
Edit the `config.toml` file in your node configuration directory to enable state sync. The following example assumes you used `./my-node-config` as your root directory in the previous step. Adjust the path if you used a different directory:
This will configure your node to use state sync for faster synchronization with the network.
44
53
45
-
### 3. Set Up PostgreSQL
54
+
### 4. Set Up PostgreSQL
46
55
47
56
For a quick setup, run Kwil's pre-configured PostgreSQL Docker image:
48
57
@@ -89,7 +98,7 @@ If you prefer a custom PostgreSQL setup, ensure it meets the requirements specif
89
98
90
99
**Security Warning**: It is recommended to not expose port 5432 publicly in production environments.
91
100
92
-
### 4. Deploy TN Node
101
+
### 5. Deploy TN Node
93
102
94
103
Run the kwild binary to deploy your node:
95
104
@@ -111,7 +120,7 @@ Ensure your firewall allows incoming connections on:
111
120
112
121
The `--statesync.enable` and `--statesync.trusted_providers` flags are optional and will help your node sync faster with the network using snapshots provided by the RPC servers.
113
122
114
-
### 5. Verify Node Synchronization
123
+
### 6. Verify Node Synchronization
115
124
116
125
Before proceeding to become a validator, ensure your node is fully synced with the network:
117
126
@@ -121,7 +130,7 @@ kwild admin status
121
130
122
131
Look for the `syncing: false` in the output, and check that your `best_block_height` is close to the current network height.
123
132
124
-
### 6. Become a Validator (Optional)
133
+
### 7. Become a Validator (Optional)
125
134
126
135
To upgrade your node to a validator:
127
136
@@ -160,7 +169,7 @@ This will show your node's public key and key type, which you'll need for valida
160
169
161
170
You can always reach out to the community for help with the validator process.
162
171
163
-
### 7. Submit Your Node to Available Node List (Optional)
172
+
### 8. Submit Your Node to Available Node List (Optional)
0 commit comments