Cronos POS Chain Docs
  • Getting Started
    • πŸ“‘Cronos POS Chain Introduction
    • πŸ”°Architecture
  • For USERS
    • 🌟New brand and domains
    • πŸ’°Wallets
      • chain-maind
      • Ledger Hardware Wallets with chain-maind
      • Crypto.com DeFi Desktop Wallet
      • Conducting IBC Transfer with Keplr Wallet
      • Using Ledger Device with Keplr Wallet
      • Mainnet Address Generation
      • Mainnet Address Verification
      • Multisig Account
      • Delegation Guide
      • Key Principles for Wallet Security
    • πŸ› οΈToken Migration Web Tool
    • 🚰Croeseid Testnet Faucet
  • For Node Hosts
    • ⛓️Running Nodes
      • Public Node Sync
      • Quicksync
      • Cronos POS Chain Mainnet: Running a Full Node
        • Upgrade Guide
          • The "V5" upgrade guide (v4.* to v5.0.1) :
          • The "V4" upgrade guide (v3.* to v4.2.2) :
          • The "DRACO II" upgrade guide (v2.* to v3.3.2) :
          • The "Canis Major" upgrade guide (v1.* to v2.0.1) at block height 922,363:
          • Running "Canis Major" network upgrade with cosmovisor
      • Cronos POS Chain Mainnet: Running a Validator
      • Cronos POS Chain Mainnet Validator Security Checklist
      • Croeseid Testnet: Running Nodes
      • Mainnet/Testnet: Running Nodes using AWS 1-click Deployment
      • Mainnet/Testnet: Running Nodes using Azure 1-click Deployment
      • Croeseid Testnet: Running Nodes With Nix
      • Devnet: Running Latest Development Node
    • πŸ”„Advanced TMKMS Integration
    • πŸ’«Notes on Performance
    • πŸ”ƒNotes on Production Deployment
  • Block Explorers
    • πŸ“ŠCronos POS Chain Mainnet Explorer
    • πŸ“ŠCroeseid Testnet Explorer
  • Cronos PoS Chain Protocol
    • ⛓️Chain Details
      • Genesis
      • Protocol Documentation
      • Chain ID, Address Format and Signatures
      • Create the IBC-enabled tokens on the Cronos POS Chain with Solo Machine
      • List of parameters
      • Proposal Process
      • Technical glossary
    • πŸŽ›οΈModules
      • module_supply
      • module_slashing
      • module_authz
      • module_bank
      • module_mint
      • module_gov
      • module_staking
      • module_distribution
      • module_nft
  • Cronos PoS Integration
    • πŸ”„Integration documentation
    • πŸ›‚Node Setup and RPC node
    • πŸ”²Blocks and Transactions
Powered by GitBook
On this page
  • Introduction
  • Step 1: Download Public Node Snapshot
  • Step 2: Extract Public Node Snapshot
  • Step 3: Chain-maind Setup
  • Step 4: Extract Data from the Public Node Sync Snapshot
  • Step 5: Run chain-maind
  1. For Node Hosts
  2. Running Nodes

Public Node Sync

PreviousRunning NodesNextQuicksync

Last updated 8 months ago

Introduction

This guide provides step-by-step instructions to perform a faster sync for Chain-maind using Public Node Sync snapshots. Please note that the type of snapshot provided is pruned.

Step 1: Download Public Node Snapshot

Users can visit and download the snapshots for Cronos POS Chain. Make sure to select β€œCronos POS Chain” 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: Chain-maind Setup

Download the latest version of Chain-maind binary from based on your preferred operating system.

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

Follow the step from to initialize and setup chain-maind. The list of the seed is subject to change, you can also find the latest seed to connect . Make sure edit the config.toml under /Users/<username>/.chain-maind/config/config.toml.

Perform , terminate the terminal once chainmaind is able to sync for couple of blocks.

Step 4: Extract Data from the Public Node Sync Snapshot

After you successfully start chain-maind, you should find a new folder named .chain-maind under /Users/<username>. Now add the cronos-pos-pruned-18968897-18968907.tar.lz4 inside .chain-maind. Change the path under .chain-maindand decompress with lz4 and tar by:

lz4 -d /Users/<username>/.chain-maind/ cronos-pos-pruned-18968897-18968907.tar.lz4.tar.lz4 | tar -xv

Note

All of the above files should be extracted to /Users/.chain-maind/data

Step 5: Run chain-maind

Now your chain-maind should be updated to the latest height as the Public Node Sync file, you can run the node now with ./chain-maind start.

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

⛓️
Public Node Page
Cronos POS Chain Github
Step 2-1 Initialize and Step 2-2 Configure Chain-maind
here
Step 3.1 Run Everything