Chipcoin mainnet is live. This guide covers the mainnet node profile. Join Telegram

Public Mainnet Node

Run a Chipcoin mainnet node

Validate the public chain independently and connect to mainnet peers with a dedicated node profile.

Mainnet chain ID: chipcoin-mainnet-1. Keep its data and keys separate from testnet.

Node Overview

What your node does.

A Chipcoin full node validates chain state, synchronizes blocks with peers and exposes a local API for inspection. The setup wizard prepares mainnet runtime paths. Full sync from genesis is the default. Reward-node participation is an additional operator step after the node is healthy.

Validate and sync

Follow the chain from genesis or a trusted snapshot anchor, then synchronize the remaining blocks.

Connect to peers

Maintain P2P connections and make your node available to other peers when inbound access is configured.

Inspect locally

Use /v1/status to confirm network identity, height, sync state and peer health before any reward-node operation.

Network Mainnet

Production chain, separate from testnet.

Chain ID chipcoin-mainnet-1

Verify this identity in your node status.

Current Height Loading

Fetched from the public mainnet API.

P2P port 8333

Publish it to accept inbound peers.

Requirements

Start with a basic Linux machine and Docker.

  • Linux VPS or Linux machine
  • Docker and Docker Compose
  • Git
  • A verified mainnet release image loaded into Docker and its approved snapshot trust key at the path required by the official Compose file
  • Open and publish TCP port 8333 if you want to accept inbound peers
  • Keep the local HTTP API on 127.0.0.1:8080, not exposed publicly

Install

Clone the repository, enter the checkout, and run the setup wizard.

The GitHub repository checks out into a local chipcoin directory. Run the wizard from that directory, choose Mainnet and the node role. Verify the pinned core image and trust-key mount before starting the dedicated mainnet Compose service. The wizard prints the exact command for the environment file it creates.

git clone https://github.com/chipcoin-protocol/chipcoin/
cd chipcoin
python3 scripts/setup/wizard.py
docker compose -f deploy/mainnet-official/compose.yml --env-file .env.mainnet up -d node

The mainnet wizard prepares .env.mainnet and isolated runtime paths under /var/lib/chipcoin-mainnet-official. The official Compose file uses a pinned image with pull_policy: never and a required read-only trust-key mount. Starting it requires those reviewed artifacts to be present locally. The wizard does not start services automatically.

Check Node Status

Confirm Docker, logs, and the local node API.

docker compose -f deploy/mainnet-official/compose.yml --env-file .env.mainnet ps
docker compose -f deploy/mainnet-official/compose.yml --env-file .env.mainnet logs -f node
curl http://127.0.0.1:8080/v1/status

Success Criteria

What success looks like.

Synced node

The node reports network=mainnet and chain_id=chipcoin-mainnet-1.

Increasing height

The reported chain height increases as new mainnet blocks arrive.

Connected peers

The node discovers and connects to public mainnet peers.

API output

/v1/status returns the canonical mainnet genesis hash, current height and sync state.

Optional Next Steps

After your mainnet node is healthy, use the rest of the network.

Explore mainnet

Inspect blocks, transactions and addresses on the public explorer. Select mainnet in the explorer.

Open Explorer

Open the browser wallet

Use a mainnet-capable wallet and confirm its selected network before receiving or sending CHC.

Install Wallet

Register a reward node

Read the mainnet Node Rewards requirements before registering an operator identity.

Node Rewards

Start mining

Review mainnet mining prerequisites and keep the miner wallet separate from your node's runtime data.

Developer Reference

Share your node

Join Telegram and share your node_id only after your mainnet node is healthy.

Join Telegram

Troubleshooting

Common issues are usually environment or connectivity related.

Docker is not installed.

Install Docker Engine and Docker Compose for your Linux distribution, then rerun the compose command.

Port 8333 is closed.

Outbound connections may still work. To accept inbound mainnet peers, publish TCP 8333 on a public interface and allow it through your firewall. The official Compose profile binds it to loopback by default; review NODE_P2P_PUBLISH_HOST before changing that setting.

The node has zero peers.

Check network access, configured mainnet peers and container status. Then inspect docker compose -f deploy/mainnet-official/compose.yml --env-file .env.mainnet logs -f node.

The node is syncing slowly.

Full sync from genesis is the mainnet default. Allow time for validation; do not import an unverified snapshot just to speed up startup.

Snapshot bootstrap.

Only import a compatible, signed mainnet snapshot after independently verifying the signer, network identity and approved trust anchor.