Chain ID: kaiyo-1 | Current Node Version: v0.8.7
State-sync does not take care of the wasm folder on Kujira, so you need to preserve your own current wasm folder, or follow the instruction to download our wasm folder. It is best to just use our Kujira snapshot service since it is more reliable. However, read on if you insist on using state-sync.
app.toml settings related to state-sync is as follows.
This is for you information only. You do not need to follow the same
setup on your node.
# Prune Type pruning = "custom" # Prune Strategy pruning-keep-every = 2000 # State-Sync Snapshot Strategy snapshot-interval = 2000 snapshot-keep-recent = 5
Our state-sync RPC server for Kujira is:
We assume that you use Cosmovisor to manage your node. If you do not use Cosmovisor, you will need to customize the following instruction slightly.
Create a reusable shell script such as
following code. The code will fetch important state-sync information
(such as block height and trust hash) from our server and
config.toml file accordingly.
#!/bin/bash SNAP_RPC="https://kujira-rpc.polkachu.com:443" LATEST_HEIGHT=$(curl -s $SNAP_RPC/block | jq -r .result.block.header.height); \ BLOCK_HEIGHT=$((LATEST_HEIGHT - 2000)); \ 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\"|" $HOME/.kujira/config/config.toml
Grant user the privilege to execute script and then run the script:
chmod 700 state_sync.sh ./state_sync.sh
Stop the node:
sudo service kujira stop
Reset the node:
# On some tendermint chains kujirad unsafe-reset-all # On other tendermint chains kujirad tendermint unsafe-reset-all --home $HOME/.kujira --keep-addr-book
unsafe-reset-allcommand does not reset your
wasmfolder. Now it is time to double-check that you indeed have a
wasmfolder with content under the
.kujirafolder. If so, you can proceed to restart your node right away. If not, you can download our
wasmfolder. Notice that we have taken out the
cachesub-folder to ensure the
wasmfolder is compatible for all CPUs.
# Remove the empty wasm folder if you have an empty one rm -r ~/.kujira/wasm # Get our wasm folder wget -O kujira_wasmonly.tar.lz4 https://snapshots.polkachu.com/wasm/kujira/kujira_wasmonly.tar.lz4 --inet4-only # Extract the wasm folder into the right place lz4 -c -d kujira_wasmonly.tar.lz4 | tar -x -C $HOME/.kujira # Clean up rm kujira_wasmonly.tar.lz4
Restart the node:
sudo service kujira start
If everything goes well, your node should start syncing within 10 minutes.
ALTERNATIVE ROUTE: We also have Kujira Snapshot Service to help you bootstrap a node.
First, visit our state-sync server landing page to ensure it is not down.
Second, add Polkachu's state-sync server as your peer. You can find Polkachu's peer info here.
Make sure that you use the latest version of the chain node when you state-sync.
State-sync can be flaky at times. Join our Discord Server if you have any issues. Happy State-Syncing!