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
3. Edit `$IOTEX_HOME/etc/config.yaml`, look for `externalHost` and `producerPrivKey`, uncomment the lines and fill in your external IP and private key. If you leave `producerPrivKey` empty, your node will be assgined with a random key.
56
56
57
57
4. Start from a **baseline snapshot** (rather than sync from the genesis block), run the following commands:
> mainnet-data-with-idx-latest.tar.gz will be update on Monday every week
77
+
If you need to run your node in archive mode to provide full historical data, please go to [Archive Node](./archive-node.md).
106
78
107
79
- Optional 2: If you only want to sync chain data from 0 height without relaying on legacy delegate election data from Ethereum, you can setup legacy delegate election data with following command:
- Optional 3: If you want to sync the chain from 0 height and also fetching legacy delegate election data from Ethereum, please change the `gravityChainAPIs` in config.yaml to use your infura key with Ethereum archive mode supported or change the API endpoint to an Ethereum archive node which you can access.
6. Ensure that TCP ports `4689` and `8080` are open on your firewall and load balancer (if applicable). Additionally, if you intend to use the node as a gateway, make sure the following ports are open:
124
+
7. Ensure that TCP ports `4689` and `8080` are open on your firewall and load balancer (if applicable). Additionally, if you intend to use the node as a gateway, make sure the following ports are open:
153
125
-`14014` for the IoTeX native gRPC API
154
126
-`15014` for the Ethereum JSON API
155
127
-`16014` for the Ethereum WebSocket
@@ -166,7 +138,7 @@ Same as [Join MainNet](#mainnet) step 2
0 commit comments