Injective Snapshots
Injective is a finance-focused blockchain that offers developers a wide range of pre-built modules for creating advanced applications. It features a decentralized orderbook, allowing developers to build sophisticated applications easily. Furthermore, Injective is an open and interoperable smart contracts platform.
Built on the Cosmos SDK, Injective achieves instant transaction finality through the Tendermint proof-of-stake consensus framework. It also enables fast cross-chain transactions across major layer one networks like Ethereum and Cosmos Hub
Injective mainnet Snapshot
| Version | v1.12.1 |
| Creation Date | |
| Last Updated | |
| Block Number | 68452001 |
| Pruning mode | Pruned |
| Size | 12G |
How to use
Download the snapshot
wget https://snapshots.bwarelabs.com/injective/mainnet/injective20240504.tar.lz4
If Injective was already on your machine, stop your Injective service
sudo systemctl stop injective.service
OR container
docker stop <INJECTIVE_CONTAINER_NAME>
AND make sure there is no process running that might try to write to the database
ps -ef | grep injective-node
Make sure your Injective data directory is clean (let us assume <INJECTIVE_HOME> is your root Injective directory)
Make sure to backup your priv_validator_state.json file before deleting the contents of the data directory
mv <INJECTIVE_HOME>/data/priv_validator_state.json <INJECTIVE_HOME>
Make sure your injective data directory is clean (let us assume <INJECTIVE_HOME> is your root Injective directory)
rm -rf <INJECTIVE_HOME>/data/*
Make sure you have lz4 installed
sudo apt-get install lz4
Decompress the archive
lz4 -c -d injective20240504.tar.lz4 | tar -x -C <INJECTIVE_HOME>/data
Copy back the priv_validator_state.json file
rm <INJECTIVE_HOME>/data/priv_validator_state.json
mv <INJECTIVE_HOME>/priv_validator_state.json <INJECTIVE_HOME>/data/
Start the Injective service OR container!
What is Injective snapshot?
Our Injective snapshot can be particularly valuable when syncing a new node to the 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 Injective snapshot?
Using our snapshots during the setup of full Injective 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 Injective snapshot to sync faster.
What is the block number of Injective 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 Injective mainnet snapshot is 68452001
How often is the Injective 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 Injective chain.
The most recent update to the Injective mainnet was on
How long does it take to restore a node using Injective 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 Injective mainnet size is 12G.
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 Injective 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