Public Node Sync

Introduction

Note

As of v0.9.0, we have merged the binary to support both levelDB and rocksDB. Therefore, make sure to select the rightapp-db-backendin yourapp.toml.

This guide provides step-by-step instructions to perform a faster sync for Cronosd using Public Node Sync snapshots. Please note that the type of snapshot provided is pruned. If you require more complete data or run a full node, consider using Quicksync.

Step 1: Download Public Node Snapshot

Users can visit Public Node Page and download the snapshots for Cronos. Make sure to select “Cronos” and download the lz4 file.

Step 2: Extract Public Node Snapshot

To start with Public Node Sync, run brew install lz4 in a new terminal.

Step 3: Cronosd Setup

Download the latest version of Cronosd from Cronos Chain Github based on your preferred operating system.

Extract the downloaded file (Cronos_1.3.0_Darwin_arm64.tar.gz is used as an example). After you download and unzip the cronosd to the location you desire. In terminal, change directory to the bin folder, where cronosd is located.

Follow the step from Step 2-1 Initialize and Step 2-2 Configure cronosd to initialize and setup cronosd.

Make sure you also implement the changes from Step 0 : Notes on Network Upgrade, and add these config items from v0.7.0 into app.toml before upgrade:

### JSON RPC Configuration ###
[json-rpc]
feehistory-cap = 100
logs-cap = 10000
block-range-cap = 10000
http-timeout="30s"
http-idle-timeout="120s"

### EVM Configuration ###
[evm]
max-tx-gas-wanted=500000

Perform Run Everything, Cronosd should be able to sync.

Step 4: Extract Data from the Public Node Sync Snapshot

After you successfully start cronosd, you should find a new folder named .cronos under /Users/<username>. Move the .lz4 snapshot file (e.g., Cronos-pruned-15250257-15250267.tar.lz4) into the .cronos directory. Decompress with lz4 and tar by:

lz4 -d Users/<username>/.cronos/Cronos-pruned-15250257-15250267.tar.lz4 | tar -xv

Note

All of the above files should be extracted to /Users/<username>/.cronos/data

Step 5: Run Cronosd

Now your cronosd is updated to the latest height as the Public Node Sync file, you can run the node now with cronosd start.

That's it! You are now running a synced node on Cronos mainnet.