Node
Run a Clanker Coin node
Running a Clanker Coin node lets you independently verify the blockchain and contribute to the decentralized network, instead of trusting someone else's copy of it.
What it does
What a node does
Validates independently
Checks every block and every transaction against the consensus rules itself, rather than trusting a remote party's answer.
Relays to the network
Forwards valid blocks and transactions to its peers, helping the network stay in sync.
Serves your wallet and miner
Your wallet reads balances and broadcasts payments through it; your miner requests block templates and submits shares to it.
Optional indexes
A transaction index and an address index can be enabled for lookups that would otherwise require scanning the whole chain.
Requirements
A modest machine is enough
Blocks are capped at 128 KiB including witness data, so even a full year of nothing but maximum-size blocks stays under roughly 400 GB of chain data, and real-world usage is far smaller than that ceiling. A node does not need specialized hardware: a small amount of disk space, a modest amount of memory, and a stable internet connection are enough to keep up.
Install
Install per platform
Every release ships a Windows zip, a macOS dmg, and Linux tar.gz archives for x86-64 and ARM64.
Windows
Download the release zip, extract it, and run the node from a terminal in that folder.
clankerd.exe --network mainnetmacOS
Open the release dmg and copy the app to Applications, or run the bundled binary directly from Terminal.
./clankerd --network mainnetLinux
Extract the release archive and run the node.
tar -xzf ClankerCoin-<version>-Linux-x86_64.tar.gz
cd ClankerCoin-<version>-Linux-x86_64
./clankerd --network mainnetContainers
Container images are planned but not yet published. Until they are, install from the release archive for your platform.
Running
Running the node
Each network keeps its own data directory, so one node process corresponds to one directory and one network. Use --datadir to choose a location other than the default, and run separate directories if you ever need more than one network at once.
clankerd --network mainnetCommon flags:
| Flag | Purpose |
|---|---|
--datadir | Use a data directory other than the network default. |
--rpc-bind | Address the JSON-RPC server listens on. Loopback by default. |
--txindex | Build a full transaction index for lookups by transaction id. |
--addressindex | Build an address index for lookups of outputs by address. |
--stratum-enabled | Turn on the solo-mining server used by clanker-miner and Clanker Stratum clients. |
| Network | P2P | RPC | Stratum |
|---|---|---|---|
| Mainnet | 9760 | 9761 | 9762 |
| Testnet | 19760 | 19761 | 19762 |
| Devnet | 29760 | 29761 | 29762 |
| Localdev | 39760 | 39761 | 39762 |
Observability
Health checks and metrics
A running node exposes GET /health, GET /ready, and GET /metrics without a token, so a process manager, load balancer, or monitoring agent can check on it without holding a credential. Logs can be emitted as structured JSON or as plain text, whichever suits your log pipeline.
Security
Keep RPC on loopback
The JSON-RPC interface is bearer-token authenticated using a token written to a local cookie file. Keep it bound to loopback and never expose it to the public internet; anyone who can reach it and read that token can act as your node.
Both peers and RPC input are treated as hostile by design. A node validates everything it is given rather than trusting the source.
Status
No seed nodes are published yet
There is no public Clanker Coin network running today, so no seed node addresses are published. This page will be updated with connection details once a public network launches.