Public Testnet Node

Run a Chipcoin testnet node in 5 minutes

Join the Chipcoin public testnet by running your own node.

View GitHub Join Telegram

Help us reach 100 independent nodes before mainnet.

Active Nodes 24h Join the count

Public daily active-node reporting is being prepared.

Reward Nodes Passed Testnet live

Reward-node flow is active on the public testnet.

Current Height Loading

Fetched from the public testnet API.

Goal 100 nodes

Before mainnet.

Requirements

Start with a basic Linux machine and Docker.

Linux VPS or Linux machine
Docker and Docker Compose
Git
Open port 28444 if you want to accept inbound peers

Install

Clone the repository and start the node.

git clone https://github.com/chipcoin-project/Chipcoin-v2
cd Chipcoin-v2
docker compose up -d

Check Node Status

Confirm Docker, logs, and the local node API.

docker compose ps
docker compose logs -f node

curl http://127.0.0.1:28081/v1/status

Success Criteria

What success looks like.

Synced node

The node reports the testnet network and the local API responds.

Increasing height

The reported chain height increases as new testnet blocks arrive.

Connected peers

The node discovers and connects to public testnet peers.

API output

/v1/status returns network=testnet and current height data.

Optional Next Steps

After your node is running, test the rest of the network path.

Claim testnet coins

Use the faucet after you have a valid CHC address.

Open Faucet

Open the browser wallet

Install the browser wallet and verify balances through the public testnet path.

Install Wallet

Register a reward node

Use the Node Rewards docs when you are ready to test reward-node participation.

Node Rewards

Start mining

Use the developer and docs pages to understand local APIs and operator commands.

Developer Reference

Share your node

Join Telegram and share your node_id after your 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 28444 is closed.

The node can still make outbound connections, but inbound peers need TCP port 28444 open on your firewall or VPS security group.

The node has zero peers.

Check network access, DNS, bootstrap peer discovery, and whether your container is running. Then inspect docker compose logs -f node.

The node is syncing slowly.

Let the node continue syncing and check whether snapshot bootstrap is enabled in the current package.

Snapshot bootstrap.

Snapshot bootstrap imports a trusted chainstate anchor and syncs only the newer delta, which makes new testnet nodes faster to bring online.