Validate and sync
Follow the chain from genesis or a trusted snapshot anchor, then synchronize the remaining blocks.
Public 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
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.
Follow the chain from genesis or a trusted snapshot anchor, then synchronize the remaining blocks.
Maintain P2P connections and make your node available to other peers when inbound access is configured.
Use /v1/status to confirm network identity, height, sync state and peer health before any reward-node operation.
Production chain, separate from testnet.
Verify this identity in your node status.
Fetched from the public mainnet API.
Publish it to accept inbound peers.
Requirements
8333 if you want to accept inbound peers127.0.0.1:8080, not exposed publiclyInstall
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
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
The node reports network=mainnet and chain_id=chipcoin-mainnet-1.
The reported chain height increases as new mainnet blocks arrive.
The node discovers and connects to public mainnet peers.
/v1/status returns the canonical mainnet genesis hash, current height and sync state.
Optional Next Steps
Inspect blocks, transactions and addresses on the public explorer. Select mainnet in the explorer.
Open ExplorerUse a mainnet-capable wallet and confirm its selected network before receiving or sending CHC.
Install WalletRead the mainnet Node Rewards requirements before registering an operator identity.
Node RewardsReview mainnet mining prerequisites and keep the miner wallet separate from your node's runtime data.
Developer ReferenceJoin Telegram and share your node_id only after your mainnet node is healthy.
Troubleshooting
Install Docker Engine and Docker Compose for your Linux distribution, then rerun the compose command.
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.
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.
Full sync from genesis is the mainnet default. Allow time for validation; do not import an unverified snapshot just to speed up startup.
Only import a compatible, signed mainnet snapshot after independently verifying the signer, network identity and approved trust anchor.