Persistence Snapshots

Persistence is a Layer-1 network that leverages Tendermint and is designed to support a DeFi ecosystem focused on unlocking the liquidity of staked assets. This network enables the creation and utilization of liquid-staked stkASSETs, allowing users to earn staking rewards while participating in various DeFi activities like lending, borrowing, and providing liquidity on decentralized exchanges (DEXs). The primary objective of Persistence is to offer a seamless staking and DeFi experience for Proof-of-Stake (PoS) users and empower developers to build innovative applications centered around stkASSETs

persistence testnet Snapshot

Versionv11.12.0-rc0
Creation Date
Last Updated
Block Number5607943
Pruning modePruned
Size16G
Download Persistence testnet Snapshot

How to use

Download the snapshot

wget https://snapshots.bwarelabs.com/persistence/testnet/persistence20240527.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-node

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>

Make sure your Persistence data directory is clean (let us assume <PERSISTENCE_HOME> is your root Persistence directory)

rm -rf <PERSISTENCE_HOME>/data/*

Make sure you have lz4 installed

sudo apt-get install lz4

Decompress the archive

lz4 -c -d persistence20240527.tar.lz4 | tar -x -C <PERSISTENCE_HOME>/data

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!

persistence mainnet Snapshot

Versionv11.11.0
Creation Date
Last Updated
Block Number16851000
Pruning modePruned
Size50G
Download Persistence mainnet Snapshot

How to use

Download the snapshot

wget https://snapshots.bwarelabs.com/persistence/mainnet/persistence20240528.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-node

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>

Make sure your Persistence data directory is clean (let us assume <PERSISTENCE_HOME> is your root Persistence directory)

rm -rf <PERSISTENCE_HOME>/data/*

Make sure you have lz4 installed

sudo apt-get install lz4

Decompress the archive

lz4 -c -d persistence20240528.tar.lz4 | tar -x -C <PERSISTENCE_HOME>/data

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!

What is Persistence snapshot?

Our Persistence snapshot can be particularly valuable when syncing a new node to the testnet or mainnet network. Instead of downloading and validating the entire blockchain from scratch, a new node can use a snapshot to quickly synchronize within the network.

Why use our Persistence snapshot?

Using our snapshots during the setup of full Persistence chain nodes can significantly speed up the syncing process by skipping the validation of all data. This can greatly enhance the speed of the setup. Instead of syncing from scratch with other nodes, you can utilize our Persistence snapshot to sync faster.

What is the block number of Persistence Snapshot?

A node snapshot is a snapshot of the blockchain at a specific point in time, and it includes data and state of the blockchain up until that block number. The block number determines the specific point in the blockchain's history that the snapshot represents.

The current block number of Persistence testnet snapshot is 5607943

The current block number of Persistence mainnet snapshot is 16851000

How often is the Persistence snapshot updated?

Regular updates are made to ensure accurate and up-to-date information. The frequency of the updates depends on the specific data being captured. We regularly update our snapshots to reflect the most recent and accurate state of the Persistence chain.

The most recent update to the Persistence testnet was on

The most recent update to the Persistence mainnet was on

How long does it take to restore a node using Persistence Snapshot?

The time it takes to restore a node using a snapshot can vary depending on several factors, including the size of the snapshot file and the performance of the underlying hardware. In general, the process involves transferring the snapshot data to the node's storage and then initializing the node from that snapshot. For smaller snapshots, the restoration process can be relatively quick and may take just a few minutes. However, for larger snapshots or in cases where the network or storage infrastructure is slower, the restoration process can take longer, potentially several hours.

The Persistence testnet size is 16G.

The Persistence mainnet size is 50G.

What does it mean if a snapshot is pruned?

The pruning of a node snapshot refers to the process of removing unnecessary data from the blockchain database to optimize storage space while keeping the integrity of the data. Pruning allows nodes to store only the most essential information needed for the blockchain's operation while discarding older and less relevant data.

The Persistence testnet snapshot is pruned.

The Persistence mainnet snapshot is pruned.

What is the main difference between pruned and archival nodes?

Pruned and archival node snapshots are two different approaches to storing blockchain data in a more efficient manner. Pruned node snapshots prioritize storage efficiency by discarding older transaction data, while archival node snapshots prioritize preserving the complete blockchain state.

Subscribe to our newsletter and never skip a beat!

Get updates on our latest news and product releases.

Get your API Endpoint from Blast

If you are in need of blockchain access through some of the fastest and most reliable infrastructure services, try out our API platform and get your project started in just a couple of clicks.

Learn more about Blast API