Native Snapshots
Fast, reliable blockchain snapshots for Cronos networks
Introduction
Setting up a new Cronos node traditionally requires synchronizing with the entire blockchain database from the genesis block—a process that can take days or even weeks depending on your hardware and network conditions. To address this challenge and accelerate node deployment, the Cronos team maintains pre-synchronized blockchain snapshots that dramatically reduce setup time.
What Are Snapshots?
Blockchain snapshots are compressed archives containing the complete blockchain state at a specific block height. Instead of downloading and verifying every transaction since genesis, you can restore your node from a recent snapshot and only sync the remaining blocks.
Cronos POS snapshots are available for:
Cronos POS Mainnet with LevelDB backend in default configuration
Default nodes: Standard configuration containing recent state data for typical node operations
Benefits
Using Cronos snapshots provides several key advantages:
Faster deployment: Reduce initial sync time from days to hours
Lower bandwidth usage: Download a single compressed file instead of syncing block-by-block
Quick network participation: Get your node operational and contributing to the network rapidly
Reduced resource consumption: Less CPU and disk I/O during the initial setup phase
Getting Started
All Cronos POS snapshots can be accessed at: https://snapshot.cronos.org/
Installation Guide
Before using snapshots, you'll need to install the Cronos binary. Follow these steps to get started:
Create a new directory and navigate to it:
mkdir cronos-pos-node
cd cronos-pos-nodeDownload the latest Cronos Binary release (Github repo):
curl -LOJ https://github.com/crypto-org-chain/chain-main/releases/tag/v6.0.1Unpack & Install the binary files. This step will create a hidden folder named
.chain-maindin your root directory.
tar -zxvf crypto-org-chain/chain-main/releases/tag/v6.0.1Verify the installation:
# check the version of chain-maind
cd bin
./chain-maind version
6.0.1Once the Cronos binary is installed and verified, you can proceed with downloading and applying the appropriate snapshot for your node configuration.
Download Cronos POS Snapshot
wget https://snapshot.cronos.org/cronos-pos/mainnet-snapshot/leveldb/default/crypto-org-chain-mainnet-1_leveldb-default-20250807.tar.lz4Unpack Cronos POS Snapshot
Copy or Move the snapshot into the hidden .chain-maind directory in the root. Then unpack the file:
mv crypto-org-chain-mainnet-1_leveldb-default-20250807.tar.lz4 ~/.chain.maind
tar -zxvf crypto-org-chain-mainnet-1_leveldb-default-20250807.tar.lz4The original data folder under .chain-maind is overwritten. It takes around a few mins to decompress.
Initialize chain-maind
chain-maindInitialize your Cronos POS node with a unique identifier (moniker):
./chain-maind init [moniker] --chain-id crypto-org-chain-mainnet-1The moniker serves as your node's display name when it appears on the Cronos POS Chain network. Choose a unique, descriptive name for easy identification. Make sure to replace [moniker] with your desired node name without the square brackets.
Configure chain-maind
chain-maindDownload and replace the Cronos POS Chain mainnet
genesis.json:
curl https://raw.githubusercontent.com/crypto-org-chain/mainnet/main/crypto-org-chain-mainnet-1/genesis.json > ~/.chain-maind/config/genesis.jsonVerify sha256sum checksum of the downloaded
genesis.json. You should seeOK!if the sha256sum checksum matches.
$ if [[ $(sha256sum ~/.chain-maind/config/genesis.json | awk '{print $1}') = "d299dcfee6ae29ca280006eaa065799552b88b978e423f9ec3d8ab531873d882" ]]; then echo "OK"; else echo "MISMATCHED"; fi;
OK!In
~/.chain-maind/config/app.toml, update minimum gas price to avoid transaction spamming
sed -i.bak -E 's#^(minimum-gas-prices[[:space:]]+=[[:space:]]+)""$#\1"0.025basecro"#' ~/.chain-maind/config/app.tomlStart the Node
Once the chain-maind has been configured, the node is ready to start synchronization with the blockchain:
./chain-maind startLast updated