Certain files will need to be absent or deleted prior to download. A quicksync replaces blockchain data with a custom snapshot. For most use cases a “pruned” version is adequate. Pruned versions will have certain transactions removed from the archive to improve node performance. If you are running a node for archival purposes, you will want an
After choosing the appropriate download type, examine your node and ensure that
.xpla/data is empty.
6:22PM INF Removed all blockchain history dir=/home/ubuntu/.xpla/data
If you are a validator, ensure that you do not remove your private key.
Example of a removed private key:
6:22PM INF Reset private validator file to genesis state keyFile=/home/ubuntu/.xpla/config/priv_validator_key.json stateFile=/home/ubuntu/.xpla/data/priv_validator_state.json
If you have an address book downloaded, you may keep it. Otherwise, you will need to download the appropriate addressbook prior to running
After Joining a public network, your node will begin to sync.
Sync start times
Nodes take at least an hour to start syncing. This wait time is normal. Before troubleshooting a sync, please wait an hour for the sync to start.
Monitor the Sync
Your node is catching up with the network by replaying all the transactions from genesis and recreating the blockchain state locally. You can verify this process by checking the
latest_block_height in the
SyncInfo of the
xplad status response:
"latest_block_height": "42", <-----
"catching_up" : true
You can significantly accelerate the synchronization process by providing
xplad with a recent snapshot of the network state. Snapshots are made publicly available by members of the XPLA Chain community, and not maintained as part of this documentation.
You can tell that your node is in sync with the network when
SyncInfo.catching_up in the
xplad status response returns
false and the
latest_block_height corresponds to the public network blockheight found on the API for either dimension, or cube.
"catching_up" : false
Validators can view the status of the network using XPLA Explorer.
Sync faster during testing
Sometimes you may want to sync faster by foregoing checks.
The following command should only be used by advanced users in non-production environments:
xplad start --x-crisis-skip-assert-invariants
You’ve successfully joined a network as a full node operator. If you are a validator, continue to manage a XPLA Chain validator for the next steps.