Our State-Sync Server Setup

For your reference, the following are the state-sync-related settings in our app.toml configuration file. Please note that this is provided for informational purposes only, and you are not required to replicate the same setup on your node.

# Prune Type
pruning = "custom"

# Prune Strategy
pruning-keep-every = 1000

# State-Sync Snapshot Strategy
snapshot-interval = 2000
snapshot-keep-recent = 2

Our state-sync RPC server for Humans is:


One line script

wget && chmod +x && ./

Stop the node

sudo systemctl stop persistence

Reset the node

persistenceCore tendermint unsafe-reset-all --keep-addr-book

Change config file

LATEST_HEIGHT=$(curl -s $SNAP_RPC/block | jq -r .result.block.header.height); \
TRUST_HASH=$(curl -s "$SNAP_RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash)
sed -i.bak -E "s|^(enable[[:space:]]+=[[:space:]]+).*$|\1true| ; \
s|^(rpc_servers[[:space:]]+=[[:space:]]+).*$|\1\"$SNAP_RPC,$SNAP_RPC\"| ; \
s|^(trust_height[[:space:]]+=[[:space:]]+).*$|\1$BLOCK_HEIGHT| ; \
s|^(trust_hash[[:space:]]+=[[:space:]]+).*$|\1\"$TRUST_HASH\"| ; \
s|^(seeds[[:space:]]+=[[:space:]]+).*$|\1\"\"|" $HOME/.persistenceCore/config/config.toml

Start the node

sudo systemctl restart persistence

And check logs

sudo journalctl -fu persistence -o cat

If everything goes well, your node should start syncing within 10 minutes.


If you are experiencing difficulty connecting to the state-sync server, please check the status of our RPC node to rule out any downtimes.

In case you are able to connect, but encountering AppHash errors, ensure that you are using the most recent version of the chain node during state-sync.

If you continue to experience issues, please do not hesitate to reach out to us in our Telegram chat for further assistance. Keep in mind that occasional unavailability of state-sync is a possibility

Persistence tendermint Chain Services