🏟️ BUIDL where legends play. Join our Hackathon at Parc des Princes, Paris – July 2025 β€’
Register Now
Chiliz Chain Developer Docs
Chiliz ChainBlock ExplorerCommunitySocios.com
English
English
  • Chiliz Chain developer docs
  • Quick Start
    • Chiliz Chain in a nutshell
    • Connect to Mainnet and Testnet
    • Deploy and verify a contract
      • Deploy with Remix IDE
      • Deploy with thirdweb
      • Verify with Chiliscan
      • Verify with Chiliz Block Explorer
    • Run a Chiliz Chain Node
    • Free online courses
    • Inflation Supply Allocation Addresses
    • Smart Contract Addresses
  • Learn
    • About Chiliz Chain
      • Tokenomics
      • Security Audits
      • Chiliz Labs
    • About Wallets
      • How to use MetaMask
        • Install MetaMask
        • Link Chiliz Chain to MetaMask
      • How to use a multisig wallet (Safe)
    • About Bridging
      • Using Dcentralab's Chainport
      • Using Chiliz Bridge
      • Bridging stablecoins
      • Making your project token bridgeable
    • About Staking
      • Stake your CHZ
      • Unstake your CHZ
      • Staking Rewards
      • Stake CHZ from your Ledger
      • Chiliz Staking FAQ
    • About Validators
      • Defining Validators and Delegators
      • Why Become a Validator
      • How to Become a Validator
      • Running a Validator node
      • How to Stop Being a Validator
      • About Validator slashing
    • About Fan Tokens
      • 2023 Migration of Fan Tokens to Chiliz Chain
    • About Stablecoins
      • Stablecoins on Chiliz Chain
    • Glossary
      • Blockchain
      • Consensus mechanisms
      • Governance
      • Validator
      • Staking
      • Wallet
      • CAP-20
      • Wrapped CHZ (wCHZ)
  • Develop
    • Basics
      • Connect to Chiliz Chain
        • Connect using RPC
        • Run a Chiliz Chain Node
        • Use a hardware wallet
      • Block Explorers
      • Testnet Faucet
        • Obtain testCHZs with Tatum Faucet
      • Use Wrapped CHZ
      • How-Tos
        • How to get the balance of a wallet
        • How to get the history of a wallet
        • How to get the metadata of a specific NFT
      • Tips & Tricks
    • Advanced
      • How to integrate Socios Wallet in your dApp
      • How to use Account Abstraction
      • How to get the USD price of Fan Tokens
      • How to generate random numbers
      • How to follow transfers of a Fan Token
      • How to create Telegram notifications for Fan Token transfers
      • How to estimate gas fees
    • Chiliz Chain API
    • Developers FAQ
  • Community
    • Chiliz Chain Ecosystem
      • Developer Tools
        • Ankr
        • Azuro
        • Biconomy
        • Blocknative
        • Hyperlane
        • Lumx
        • Moralis
        • Pyth
        • Reown
        • Rarible
        • Tatum
        • The Graph
        • Thirdweb
        • Web3Auth
      • Custody solutions
        • Cobo
        • Fireblocks
      • Wallets
        • Magic
        • Privy
    • Developers events
      • Chiliz Sports Hackathon - July 2024
        • Setting The Stage
        • Getting Started
        • Mission Brief & Key Dates
        • The Prize Money
        • Theme & Intro
        • Tracks, Requirements, Regulations & Scoring Criteria
        • The Process
        • Disclaimers
        • Useful information
      • ETHGlobal Bangkok Hackathon 2024
      • ETHGlobal Istanbul Hackathon 2023
      • ETHGlobal London Hackathon 2024
      • ETHGlobal Online Hackathon Summer 2024
      • Hacking Poland 2025
      • Lumx Hack powered by ETH Rio
  • Chiliz Chain Changelog
    • Governance Proposals & Decisions
      • February 2025: New validator proposals
      • December 2024: Governance Update Proposals
      • May 2024: Dragon 8 (Tokenomics 2.0) Proposal
      • 2024 Dragon8 hard fork announcement
    • Blockchain code changes
    • Outage reports
      • Details on the May 21st outage
  • Doc Updates
Powered by GitBook
On this page
  • Prerequisites
  • Pre-built Docker images
  • Launch a node and start the sync
  • Step 1: Create a directory
  • Step 2: Connect Client
  • Node maintenance information
  • Change verbosity when debugging
  • Stop the node and clean up
  • Delete the directory
  • Updating your node
  • Running an archive node
  • Running a Chiliz Chain Node from a Snapshot or Backup
  • Available Snapshots
  • Cleaning Existing Data
  • Steps to Run a Node from a Snapshot:
  • Additional Geth information

Was this helpful?

  1. Develop
  2. Basics
  3. Connect to Chiliz Chain

Run a Chiliz Chain Node

Launch, create, connect, and debug a node to sync with Chiliz Chain

Last updated 3 months ago

Was this helpful?

Running your own Chiliz Chain node offers enhanced control, privacy, and reliability, but requires more technical expertise and resources compared to using an existing RPC endpoint.

It allows you to transact and communicate with smart contracts on the Chiliz Chain

Note that there's a Validator-specific node-running documentation page: Running a Validator node

Prerequisites

To run the Chiliz Chain node, you must have installed, either on your machine or your server. Therefore, please complete the before you proceed.

Pre-built Docker images

You can use the pre-built Docker images from the .

Launch a node and start the sync

The recommended starting point to run a Chiliz Chain node is with the mounted data volume. If this method is used to recreate a Docker container, the data gets stored in the directory and can easily be reused or cloned to another node.

Step 1: Create a directory

Create a directory and point to it in the -v parameter in the following command:

docker run \
-v $(pwd)/my-datadir:/datadir \
--name ccv2-node \
-p 8545:8545 \
-p 8546:8546 \
chilizchain/ccv2-geth:latest \
--chiliz # for Chiliz Mainnet. Use --spicy for Spicy Testnet.
--datadir=/datadir \
--ipcdisable

Step 2: Connect Client

To connect a client with a node, you must enable RPC HTTP and/or the WebSocket servers by specifying --http and/or --ws parameter groups respectively.

For example:

docker run \
-v $(pwd)/my-datadir:/datadir \
--name ccv2-node \
-p 8545:8545 \
-p 8546:8546 \
chilizchain/ccv2-geth:latest \
--chiliz \ # for Chiliz Mainnet. Use --spicy for Spicy Testnet.
--datadir=/datadir \
--ipcdisable \
--http \
--http.addr=0.0.0.0 \
--http.api=eth,net,web3,debug,txpool \
--http.port=8545 \
--http.corsdomain="*" \
--http.vhosts="*" \
--ws \
--ws.addr=0.0.0.0 \
--ws.api=eth,net,web3,debug,txpool \
--ws.port=8546 \
--ws.origins="*" \

CAUTION

For security reasons, ensure you set appropriate values for the following parameters:

--http.corsdomain

--http.vhosts

--ws.origins

Node maintenance information

Change verbosity when debugging

​In some cases, you may want to increase the verbosity of the node, i.e. when you must debug either the node or the connecting client itself.

To do that, you can define a --verbosity parameter. It can accept the following options (default is 3):

  • 0=silent

  • 1=error

  • 2=warn

  • 3=info

  • 4=debug

  • 5=detail

Stop the node and clean up

If you have launched the node using one of the above commands then your node process continues to run in the foreground. To stop this process, press CTRL+C.

Run the following command to remove the Docker container:

docker rm ccv2-node

Delete the directory

Run the following command to delete a directory:

rm my-datadir

Updating your node

The Chiliz Chain team strives to keep Chiliz Chain secure and modern, and we will therefore make hard fork now and then every year, such as the Dragon8 hard fork.

In the event of a hard fork, your node will be out of sync with the network. It is therefore important to follow our announcements, and update your node.

To keep your node updated, you can follow the following steps.

If you use Docker:

  1. Ensure you stop and delete your existing Docker container while preserving the volumes that contain your database.

If you use your own binary:

  1. Build from there with your toolset.

Running an archive node

To run an archive node, you should add the following 2 params into the ccv2-geth call presented above:

--syncmode=full \
--gcmode=archive \

Running a Chiliz Chain Node from a Snapshot or Backup

To speed up the synchronization process of your Chiliz Chain node, you can rely on a snapshot β€” a recent copy (or archive/backup) of the blockchain data directory (datadir). This method allows your node to become operational more quickly compared to syncing from scratch.

It recommend to keep snapshots for new node setups. Overwriting an existing datadir with a snapshot may lead to inconsistencies.

Available Snapshots

Each network has a dedicated snapshot:

Cleaning Existing Data

If you intend to apply a snapshot to an existing node, ensure you delete the following directories and files within your datadir before restarting the node:

rm -rf blobpool transactions.rlp LOCK lightchaindata triecache

This step helps prevent potential conflicts arising from residual data.

Steps to Run a Node from a Snapshot:

  1. Create a Data Directory:

mkdir -p ~/chiliz-node/my-datadir
  1. Download the Snapshot:

Replace the URL with the Mainnet snapshot URL if needed.

cd ~/chiliz-node/my-datadir
nohup curl -L --retry 5 -o chaindata.tar.gz https://s3.eu-west-3.amazonaws.com/spicy-snapshots.chiliz.com/chaindata_snapshot.tar.gz > download.log 2>&1 &

To monitor the download progress, use: tail -f download.log

  1. Extract the Snapshot:

tar -xzf chaindata.tar.gz
  1. Run the Chiliz Chain Node:

docker run \
  -v ~/chiliz-node/my-datadir:/datadir \
  --name ccv2-node \
  -p 8545:8545 \
  -p 8546:8546 \
  chilizchain/ccv2-geth:latest \
  --spicy \  # Use --chiliz for Mainnet
  --datadir=/datadir \
  --ipcdisable \
  --http \
  --http.addr=0.0.0.0 \
  --http.api=eth,net,web3,debug,txpool \
  --http.port=8545 \
  --http.corsdomain="*" \
  --http.vhosts="*" \
  --ws \
  --ws.addr=0.0.0.0 \
  --ws.api=eth,net,web3,debug,txpool \
  --ws.port=8546 \
  --ws.origins="*"

Additional Geth information

Launch your node using .

.

Spicy Testnet:

Mainnet:

Visit Geth's to view the full list of available Geth parameters.

Docker
Docker installation
Chiliz Chain 2.0 public repository on the Docker hub for Chiliz Chain 2.0
the latest pre-built Docker image available
Download the latest release from our GitHub repository
chaindata_snapshot.tar.gz
chaindata_snapshot.tar.gz
command-line options