Chain ID: seda-1-testnet | Current Node Version: v0.0.7
Our Seda Snapshot Server Setup
| Size | Timestamp |
|---|---|
| 0.73 GB | Sun, 24 Nov 2024 06:18:39 GMT |
We take one node snapshot every day. We then delete all the previous snapshots to free up the space on the file server.
The snapshot is designed for node opeartors to run an efficient node on Seda chain. To make the snapshot as small as possible while still viable as a validator, we use the following setting to save on the disk space. It might be helpful for you to sync with our snapshot periodically because Tendermint chain storage grows over time regardless of the pruning. Since we periodically state-sync our snapshot nodes, you might notice that sometimes the size of our snapshot is surprisingly small.
# Prune Type
pruning = "custom"
# Prune Strategy
pruning-keep-recent = "100"
pruning-keep-every = "0"
pruning-interval = "10"
indexer = "null"
How To Process Seda Snapshot
sudo apt update
sudo apt install snapd -y
sudo snap install lz4
Stop your node
sudo systemctl stop sedad
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 command. The command does not wipe the file. However, you should have a backup of it already in a safe location.
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.
# Back up priv_validator_state.json if needed
cp ~/.sedad/data/priv_validator_state.json ~/.sedad/priv_validator_state.json
cd $HOME
sudo rm -rf ~/.sedad/data
sudo rm -rf ~/.sedad/wasm
Decompress the snapshot to your database location. You database location will be something to the effect of ~/.sedad depending on your node implemention.
The above solution requires you to download the compressed file, uncompressed it and then delete the original file. This requires extra storage space on your server. You can run the following combo command to stream the snapshot into your database location. For advanced users only:
Data
curl -o - -L https://config-t.noders.services/seda/data.tar.lz4 | lz4 -d | tar -x -C ~/.sedad
Wasm
curl -o - -L https://config-t.noders.services/seda/wasm.tar.lz4 | lz4 -d | tar -x -C ~/.sedad
If you run a validator node and the chain is in halt, it is time to replace the priv_validator_state.json file that you have backed up.
# Replace with the backed-up priv_validator_state.json
cp ~/.sedad/priv_validator_state.json ~/.sedad/data/priv_validator_state.json
If everything is good, now restart your node Make sure that your node is running
sudo systemctl restart sedad
sudo journalctl -fu sedad --no-hostname -o cat
We also have Seda state-sync service to help you bootstrap a node.