Lava Snapshots
Lava testnet Snapshot
| Version | v3.2.0 |
| Creation Date | |
| Last Updated | |
| Block Number | 2390229 |
| Pruning mode | Pruned |
| Size | 2.1G |
How to use
Download the snapshot
wget https://snapshots.bwarelabs.com/lava/testnet/lava20241220.tar.lz4
If Lava was already on your machine, stop your Lava service
sudo systemctl stop lava.service
OR container
docker stop <LAVA_CONTAINER_NAME>
AND make sure there is no process running that might try to write to the database
ps -ef | grep lava
Make sure to backup your priv_validator_state.json file before deleting the contents of the data directory
mv <LAVA_HOME>/data/priv_validator_state.json <LAVA_HOME>
Make sure your lava data directory is clean (let us assume <LAVA_HOME> is your root Lava directory)
rm -rf <LAVA_HOME>/data/
Make sure you have lz4 installed
sudo apt-get install lz4
Decompress the archive
lz4 -c -d lava20241220.tar.lz4 | tar -x -C <LAVA_HOME>
Copy back the priv_validator_state.json file
rm <LAVA_HOME>/data/priv_validator_state.json
mv <LAVA_HOME>/data/priv_validator_state.json <LAVA_HOME>/data/
Start the Lava service OR container!
Lava mainnet Snapshot
| Version | v3.1.0 |
| Creation Date | |
| Last Updated | |
| Block Number | |
| Pruning mode | Pruned |
| Size | 435M |
How to use
Download the snapshot
wget https://snapshots.bwarelabs.com/lava/mainnet/lava20241220.tar.lz4
If Lava was already on your machine, stop your Lava service
sudo systemctl stop lava.service
OR container
docker stop <LAVA_CONTAINER_NAME>
AND make sure there is no process running that might try to write to the database
ps -ef | grep lava
Make sure to backup your priv_validator_state.json file before deleting the contents of the data directory
mv <LAVA_HOME>/data/priv_validator_state.json <LAVA_HOME>
Make sure your lava data directory is clean (let us assume <LAVA_HOME> is your root Lava directory)
rm -rf <LAVA_HOME>/data/
Make sure you have lz4 installed
sudo apt-get install lz4
Decompress the archive
lz4 -c -d lava20241220.tar.lz4 | tar -x -C <LAVA_HOME>
Copy back the priv_validator_state.json file
rm <LAVA_HOME>/data/priv_validator_state.json
mv <LAVA_HOME>/data/priv_validator_state.json <LAVA_HOME>/data/
Start the Lava service OR container!
What is Lava snapshot?
Our Lava 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 Lava snapshot?
Using our snapshots during the setup of full Lava 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 Lava snapshot to sync faster.
What is the block number of Lava 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 Lava testnet snapshot is 2390229
The current block number of Lava mainnet snapshot is
How often is the Lava 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 Lava chain.
The most recent update to the Lava testnet was on
The most recent update to the Lava mainnet was on
How long does it take to restore a node using Lava 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 Lava testnet size is 2.1G.
The Lava mainnet size is 435M.
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 Lava testnet snapshot is pruned.
The Lava 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