This page lists the canonical user-run deployment scripts and peer-list resources referenced by the c8ntinuum docs. These endpoints are intended for downloading scripts and network bootstrap metadata before running them locally.
Canonical resources
| Resource | Purpose | Hosted endpoint | Main docs |
|---|
deploy.sh | Install, state-sync, start, stop, inspect, and reset non-validator ctmd nodes. | https://resources.c8ntinuum.io/deploy.sh | Full Node Installation, State Sync |
local_node.sh | Start the canonical local single-node c8ntinuum developer chain from a source checkout. | Repository-root script, not a hosted metadata artifact | Local Development, Developer Toolkits |
peers.json | Provide seeds, persistent peers, state-sync RPCs, and snapshot peer hosts used by node deployment. | https://resources.c8ntinuum.io/peers.json | Full Node Block Delivery, State Sync |
migrate.js, scripts/deploy.js, arguments.js, npm scripts, make targets, Foundry commands, and ctmd commands.
Deploy script
To install or update ctmd, run the deploy.sh script. You can download and run the script manually:
curl -fsSL https://resources.c8ntinuum.io/deploy.sh -o deploy.sh
chmod +x deploy.sh
sudo ./deploy.sh install --moniker <your-node-moniker>
For production or validator-adjacent infrastructure, prefer the download-first flow so you can inspect the script and keep a local copy for lifecycle commands.
| Command | Purpose |
|---|
install --moniker NAME [--chain-id ID] [-y] | Download the latest metadata-backed release, install it, initialize the node home, download genesis, and patch peers. |
state-sync [-y] [--lag N] [--rpc-1 URL] [--rpc-2 URL] [--p2p-host-1 HOST] [--p2p-host-2 HOST] | Configure state sync, reset local chain data, wait for catch-up, then disable state sync. |
start | Start the managed node. |
stop | Stop the managed node. |
status | Show install, service, local RPC, height, sync, and peer status. |
reset [-y] | Delete the managed install, node home, service, cache, and Linux system user/group. |
help | Show script help. |
deploy.sh install reads release metadata from metadata.json. The script resolves .ctmd.latest_version, selects the platform artifact URL and SHA-256 URL for linux-amd64, linux-arm64, or darwin-arm64, downloads the tarball, verifies SHA-256, and installs the bundled binary and shared libraries.
The script also verifies mainnet genesis against metadata.json field mainnet_genesis_sha256. When install --chain-id uses a non-default chain ID, the script downloads the configured genesis URL but skips the mainnet SHA-256 check.
Peer list
deploy.sh uses the hosted peer list at:
https://resources.c8ntinuum.io/peers.json
| Field family | Used for |
|---|
| Seeds | Initial P2P discovery. |
| Persistent peers | Stable peers for joining and staying connected to the network. |
| State-sync RPCs | Trusted RPC endpoints used to compute state-sync trust height and hash. |
| Snapshot peer hosts | P2P peers that can serve state-sync snapshots. |
deploy.sh selects peer-list entries by chain ID, so node deployers normally do not need to manually copy a peer list into config.toml. Operators using private infrastructure can override RPC and snapshot peer hosts with deploy.sh state-sync flags such as --rpc-1, --rpc-2, --p2p-host-1, and --p2p-host-2.
Local node script
From a checked-out c8ntinuum source repository, start a local developer chain:
