Story Protocol Testnet Node Snapshot

Our Story Protocol Testnet Snapshot Server Setup

We take node snapshot periodically on a needed basis for testnet.

How To Process Story Protocol Testnet Snapshot

Install lz4 if needed

sudo apt install lz4

Download the snapshot

wget -O story_4340821.tar.lz4 https://snapshots.polkachu.com/testnet-snapshots/story/story_4340821.tar.lz4 --inet4-only

Stop your node

sudo service story stop
sudo service story_geth stop

Reset your node. This will erase your node database. If you are already running validator, be sure you backed up your priv_validator_key.json prior to running the the command. The command does not wipe the file. However, you should have a backup of it already in a safe location.

WARNING: If you use this snapshot on a validator node during a chain halt, make sure you back up priv_validator_state.json and then replace it after the snapshot is extracted but before you start the node process. This is very important in order to avoid double-sign. When in doubt, reach out to the project team.

# Reset cometbft data
cp ~/.story/story/data/priv_validator_state.json  ~/.story/story/priv_validator_state.json
rm ~/.story/story/data -rf
cp ~/.story/story/priv_validator_state.json  ~/.story/story/data/priv_validator_state.json

# Reset geth data
rm ~/.story/geth/story/geth/chaindata -rf

Decompress the snapshot to your database root location. You database location will be something to the effect of ~/.story depending on your node implementation.

lz4 -c -d story_4340821.tar.lz4  | tar -x -C ~/.story

If everything is good, now restart your node

sudo service story start
sudo service story_geth start

Remove downloaded snapshot to free up space

rm -v story_4340821.tar.lz4

Make sure that your node is running

sudo service story status
sudo service story_geth status
sudo journalctl -u story -f
sudo journalctl -u story_geth -f