Native Snapshots

Fast, reliable blockchain snapshots for Cronos networks

Introduction

These snapshots are available for both Cronos EVM Mainnet and Testnet networks, supporting multiple database backends including LevelDB, RocksDB, and VersionDB. Additionally, snapshots are provided for different node types to match your specific use case:

• Archive nodes: store complete blockchain history and state

• Default nodes: standard configuration with recent state data

• Pruned nodes: optimized storage with minimal historical data

All Cronos EVM snapshots can be accessed at: https://snapshot.cronos.org/

Using these snapshots significantly reduces the time required to get your Cronos node operational, allowing you to quickly join the network without waiting for a full synchronization from the genesis block.

Step 1: Installation Guide

Before using snapshots, you'll need to install the Cronos binary. Follow these steps to get started:

1. Create a new directory and navigate to it:

mkdir cronos-node
cd cronos-node

1. Download the latest Cronos Binary release:

curl -LOJ https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9_Darwin_arm64.tar.gz

1. Unpack & Install the binary files:

tar -zxvf cronos_1.4.9_Darwin_arm64.tar.gz

1. Verify the installation:

cd bin
./cronosd version
Expected output:
1.4.9

Once the Cronos binary is installed and verified, you can proceed with downloading and applying the appropriate snapshot for your node configuration.

Step 2: Download Cronos EVM Snapshot

wget https://snapshot.cronos.org/cronos/mainnet-snapshot/leveldb/pruned/cronosmainnet_25-1_leveldb-pruned-20250819.tar.lz4

Step 3: Unpack Cronos EVM Snapshot

First copy or move the snapshot to the hidden .cronos/ directory in the root. Then unpack the file:

tar -zxvf cronosmainnet_25-1_leveldb-pruned-20250819.tar.lz4

Note: Pre-requisite: gnu-tar and lz4 brew install gnu-tar lz4

Step 4: Initialize cronosd

Initialize your Cronos node with a unique identifier (moniker):

./cronosd init [moniker] --chain-id cronosmainnet_25-1

The moniker will be the displayed name of your node when connected to the Cronos network. Make sure to replace [moniker] with your desired node name without the square brackets.

Step 4: Configure cronosd

Now you'll need to download the genesis file and configure your node settings:

1. Download and replace the Cronos Mainnet genesis file:

curl https://raw.githubusercontent.com/crypto-org-chain/cronos-mainnet/master/cronosmainnet_25-1/genesis.json > ~/.cronos/config/genesis.json

1. Verify the genesis file checksum:

if [[ $(sha256sum ~/.cronos/config/genesis.json | awk '{print $1}') = "58f17545056267f57a2d95f4c9c00ac1d689a580e220c5d4de96570fbbc832e1" ]]; then echo "OK"; else echo "MISMATCHED"; fi;

Expected output:

OK

1. Configure network settings:

Update the configuration file with the required seed nodes and timing parameters:

sed -i.bak -E 's#^(seeds[[:space:]]+=[[:space:]]+).*$#\1"[e-mail]:26656,[e-mail]:26656,[e-mail]:26656,[e-mail]:26656"#' ~/.cronos/config/config.toml

sed -i.bak -E 's#^(create_empty_blocks_interval[[:space:]]+=[[:space:]]+).*$#\1"5s"#' ~/.cronos/config/config.toml

sed -i.bak -E 's#^(timeout_commit[[:space:]]+=[[:space:]]+).*$#\1"5s"#' ~/.cronos/config/config.toml

1. Update the minimum-gas-prices in the app.toml file:

minimum-gas-prices = "10000000000000basetcro"

Step 5: Start the Node

  $ ./cronosd start