🤝Joining Network Using State Sync
State sync offers the quickest way to join SEDA network.
The state sync feature allows a new peer to join the network by asking for a snapshot from existing peers. SEDA provides the following RPC nodes to support this feature. Use these addresses in Step 3:
seda-1 (mainnet)
18.133.187.48:26657
https://rpc.seda.xyz
seda-1-testnet (testnet)
52.56.225.178:26657
https://rpc.testnet.seda.xyz
Steps:
Check the version history and download the correct binary version from the SEDA Chain repository.
Initialize your node for
mainnet
ortestnet
:sedad join <moniker> --network mainnet
Query an RPC node to obtain a trusted block height and hash. For example:
curl -s https://rpc.seda.xyz/block | jq -r '.result.block.header.height + "\n" + .result.block_id.hash' 653231 B77528F6A290FCFBF25F730C6D490DE0DA7587EC6B2612AA2547773499CFB47E
Enable state sync and fill out the relevant fields in
config.toml
accordingly:[statesync] enable = true rpc_servers = "https://rpc.seda.xyz,18.133.187.48:26657" trust_height = 653231 trust_hash = "B77528F6A290FCFBF25F730C6D490DE0DA7587EC6B2612AA2547773499CFB47E" trust_period = "168h0m0s"
(Optional) Sometimes a recent snapshot may not be available in the peer-to-peer network, making it difficult to verify its header. SEDA runs a node that broadcasts snapshots taken every 100 blocks to the network. To ensure that a request for snapshots is sent to this node, add the following address to the
persistent_peers
field inconfig.toml
. For mainnet:persistent_peers = "[email protected]:26656"
For testnet:
persistent_peers = "[email protected]:26656"
You may have to disable SEDA signer to start the node. If you are a validator, please read SEDA Keys to set up SEDA signer after you finish the current instructions.
sedad config set app seda.enable-seda-signer false
Start the node.
sedad start
State sync may be unreliable at times. If it fails, please retry the steps after a few hours or consider Joining Network Using Snapshot.
Last updated
Was this helpful?