Mainnet

• Official Docs

• Github Repository

The snapshot service for Persistence Mainnet (chain-id core-1) is available here.

Whether you need to bootstrap your full node or you are in need of a snapshot to ease the migration or kick-start of your validator, you can use our daily snapshot service to speed up the process.

Note: the nodes used for snapshotting are using the pruning values from below, they have state-sync & indexer disabled and are hosted as Docker containers on machines using Ubuntu 22.04.

# in app.toml
pruning = "custom"
pruning-keep-recent = "100"
pruning-keep-every = "0"
pruning-interval = "10"

...

[state-sync]

snapshot-interval = 0

# in config.toml

...

[tx_index]

indexer = "null"

How to use

You simply go to our snapshot service, select the "Persistence Snapshots" section and you can download the latest available snapshot! In order to use it, simply decompress the archive as per the following instructions and start your node.

# download the snapshot
wget https://snapshots.bwarelabs.com/persistence/mainnet/persistence20221208.tar.lz4

# if Persistence was already on your machine, stop your Persistence service
sudo systemctl stop persistence.service
# OR container
docker stop <PERSISTENCE_CONTAINER_NAME>
# AND make sure there is no process running that might try to write to the database
ps -ef | grep persistence

# make sure your persistence data directory is clean (let us assume <PERSISTENCE_HOME> is your root Persistence directory)
# make sure to backup your priv_validator_state.json file before deleting the contents of the data directory
mv <PERSISTENCE_HOME>/data/priv_validator_state.json <PERSISTENCE_HOME>
rm -rf <PERSISTENCE_HOME>/data/

# make sure you have lz4 installed
sudo apt-get install lz4

# decompress the archive
lz4 -c -d persistence20221208.tar.lz4  | tar -x -C <PERSISTENCE_HOME>

# copy back the priv_validator_state.json file
rm <PERSISTENCE_HOME>/data/priv_validator_state.json
mv <PERSISTENCE_HOME>/priv_validator_state.json <PERSISTENCE_HOME>/data/

# start the Persistence service OR container

You should be in-sync with the network in minutes after starting the node.

Please make sure to also check the Official Documentation and the Github Repository posted above in order to correctly deploy the node of your choice, be it a full node or validator.