Stop cudos-noded and reset database
Copy sudo systemctl stop cudos-noded
cp $HOME /cudos-data/data/priv_validator_state.json $HOME /cudos-data/priv_validator_state.json.backup
cudos-noded tendermint unsafe-reset-all --home $HOME /cudos-data --keep-addr-book
Copy STATE_SYNC_RPC = https://rpc.cosmos.directory:443/cudos
BACKUP_RPC = https://cudos-rpc.lavenderfive.com:443
LATEST_HEIGHT = $( curl -s $STATE_SYNC_RPC /block | jq -r .result.block.header.height )
BLOCK_HEIGHT = $( echo LATEST_HEIGHT | awk '{print $1 - ($1 % 6000)}' ); \
TRUST_HASH = $( curl -s "$STATE_SYNC_RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash )
SEEDS="ff3f0f7b1eecc6844e6512428ef4c7a9448452a8@cluster-1-seed-1.hosts.cudos.org:26656,6d9beb4d44a530a4a10ebe78ed7717f6083d0c4b@cluster-2-seed-1.hosts.cudos.org:26656,e0f3bcc574ef66ae4561fad0772a4fd1959969af@cluster-3-seed-1.hosts.cudos.org:26656,ebc272824924ea1a27ea3183dd0b9ba713494f83@cudos-mainnet-seed.autostake.com:27256,20e1000e88125698264454a884812746c2eb4807@seeds.lavenderfive.com:12356,8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:26656"
echo -e "Modifying $HOME/cudos-data/config/config.toml based on the following values:"
echo -e "RPC Address: $STATE_SYNC_RPC"
echo -e "Latest Block Height: $LATEST_HEIGHT"
echo -e "Sync Block Height: $BLOCK_HEIGHT"
echo -e "Trust Hash: $TRUST_HASH"
sed -i \
-e "s|^enable *=.*|enable = true|" \
-e "s|^rpc_servers *=.*|rpc_servers = \"$STATE_SYNC_RPC,$BACKUP_RPC\"|" \
-e "s|^trust_height *=.*|trust_height = $BLOCK_HEIGHT|" \
-e "s|^trust_hash *=.*|trust_hash = \"$TRUST_HASH\"|" \
-e "s|^seeds *=.*|seeds = \"$SEEDS\"|" \
$HOME /cudos-data/config/config.toml
mv $HOME /cudos-data/priv_validator_state.json.backup $HOME /cudos-data/data/priv_validator_state.json
Copy curl -L https://snapshots.lavenderfive.com/wasm/$HOME/cudos-data/wasmonly.tar.lz4 | lz4 -dc - | tar -xf - -C $HOME/cudos-data
Restart cudos-noded and check the log
Copy sudo systemctl restart cudos-noded && sudo journalctl -u cudos-noded -f --no-hostname -o cat