State sync
With our state sync services you will be able to catch up latest chain block in matter of minutes

Instructions
Stop the service and reset the data
sudo systemctl stop pylonsd
cp $HOME/.pylons/data/priv_validator_state.json $HOME/.pylons/priv_validator_state.json.backup
pylonsd tendermint unsafe-reset-all --home $HOME/.pylons
Get and configure the state sync information
STATE_SYNC_RPC=https://pylons.rpc.takeshi.team:443
STATE_SYNC_PEER=d9bfa29e0cf9c4ce0cc9c26d98e5d97228f93b0b@pylons.rpc.takeshi.team:21656
LATEST_HEIGHT=$(curl -s $STATE_SYNC_RPC/block | jq -r .result.block.header.height)
SYNC_BLOCK_HEIGHT=$(($LATEST_HEIGHT - 2000))
SYNC_BLOCK_HASH=$(curl -s "$STATE_SYNC_RPC/block?height=$SYNC_BLOCK_HEIGHT" | jq -r .result.block_id.hash)
sed -i \
-e "s|^enable *=.*|enable = true|" \
-e "s|^rpc_servers *=.*|rpc_servers = \"$STATE_SYNC_RPC,$STATE_SYNC_RPC\"|" \
-e "s|^trust_height *=.*|trust_height = $SYNC_BLOCK_HEIGHT|" \
-e "s|^trust_hash *=.*|trust_hash = \"$SYNC_BLOCK_HASH\"|" \
-e "s|^persistent_peers *=.*|persistent_peers = \"$STATE_SYNC_PEER\"|" \
$HOME/.pylons/config/config.toml
mv $HOME/.pylons/priv_validator_state.json.backup $HOME/.pylons/data/priv_validator_state.json
Restart the service and check the log
sudo systemctl start pylonsd && sudo journalctl -u pylonsd -f --no-hostname -o cat
Last updated