BlastL2 Snapshots
BlastL2 testnet Snapshot
| Version | 0.1.0 |
| Creation Date | |
| Last Updated | |
| Block Number | 14723856 |
| Pruning mode | Pruned |
| Size | 869G |
How to use
Download the snapshot
wget https://snapshots.bwarelabs.com/blast/testnet/blast20241214.tar.lz4
If Blast L2 was already on your machine, stop your Blast L2 service
sudo systemctl stop <BLAST_GETH_SERVICE>
sudo systemctl stop <BLAST_OP_NODE_SERVICE>
OR containers if you are using the recommended docker compose setup
docker compose down
AND make sure there is no process running that might try to write to the database
ps -ef | grep blastl2-node
make sure your blast data directory is clean (let us assume <BLAST_HOME> is your root Blast L2 directory)
rm -rf <BLAST_HOME>/geth/geth/*
Make sure you have lz4 installed
sudo apt-get install lz4
Decompress the archive
lz4 -c -d https://snapshots.bwarelabs.com/blast/testnet/blast20241214.tar.lz4 | tar -x -C <BLASTL2_HOME>/geth/geth
Start the BlastL2 service OR container!
BlastL2 mainnet Snapshot
| Version | 0.1.0 |
| Creation Date | |
| Last Updated | |
| Block Number | 12359893 |
| Pruning mode | Pruned |
| Size | 3.4T |
How to use
Download the snapshot
wget https://snapshots.bwarelabs.com/blast/mainnet/blast20241207.tar.lz4
If Blast L2 was already on your machine, stop your Blast L2 service
sudo systemctl stop <BLAST_GETH_SERVICE>
sudo systemctl stop <BLAST_OP_NODE_SERVICE>
OR containers if you are using the recommended docker compose setup
docker compose down
AND make sure there is no process running that might try to write to the database
ps -ef | grep blastl2-node
make sure your blast data directory is clean (let us assume <BLAST_HOME> is your root Blast L2 directory)
rm -rf <BLAST_HOME>/geth/geth/*
Make sure you have lz4 installed
sudo apt-get install lz4
Decompress the archive
lz4 -c -d https://snapshots.bwarelabs.com/blast/mainnet/blast20241207.tar.lz4 | tar -x -C <BLASTL2_HOME>/geth/geth
Start the BlastL2 service OR container!
What is BlastL2 snapshot?
Our BlastL2 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 BlastL2 snapshot?
Using our snapshots during the setup of full BlastL2 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 BlastL2 snapshot to sync faster.
What is the block number of BlastL2 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 BlastL2 testnet snapshot is 14723856
The current block number of BlastL2 mainnet snapshot is 12359893
How often is the BlastL2 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 BlastL2 chain.
The most recent update to the BlastL2 testnet was on
The most recent update to the BlastL2 mainnet was on
How long does it take to restore a node using BlastL2 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 BlastL2 testnet size is 869G.
The BlastL2 mainnet size is 3.4T.
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 BlastL2 testnet snapshot is pruned.
The BlastL2 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