CommunityCoins Deployment (cc-deploy)

cc-deploy is the canonical orchestration layer for running CommunityCoins infrastructure.

It provides production-ready Docker Compose configurations for:

• Legacy Bitcoin-era core forks
• The CommunityCoins Ring-of-Trust (ROT) layer

This repository does not contain protocol software. It defines how protocol software is deployed.

---

Philosophy

CommunityCoins preserves legacy core forks unmodified.

To achieve reproducible and decentralized infrastructure, we separate concerns:

Layer	Responsibility
Core repositories	Protocol software + Docker image
cc-deploy	Deterministic orchestration
rot	Trust & verification layer

cc-deploy ensures that operators can deploy an up to date full core + optional ROT environment with minimal friction and maximum determinism.

---

Requirements

• Docker Engine
• Docker Compose v2 or newer

Sovereign Local Build Mode

CommunityCoins uses a self-contained, source-built deployment model.

All images are built locally from source. No registry pulls. No hidden dependencies.

First-time bootstrap (one-time per machine)

git clone https://git.communitycoins.org/Communitycoins.Rooty/cc-deploy
cd cc-deploy/orchest

# Build canonical builder base (Berkeley DB + toolchain)
docker compose -p berkeley build bdb

This creates the deterministic builder image cc_bdb:24.04.

It only needs to be built once per host.

Deploying a coin

docker compose -p <coin> --env-file <coin>.env up -d --build

What happens

• The cc_bdb:24.04 image must exist (see above)
• The coin core image is built from source (Dockerfile.[coin])
• The ROT image is build
• Containers start

For additional coins:

docker compose -p <coin2> --env-file <coin2>.env up -d --build

• cc_bdb is reused.
• Only the new coin image is built.
• Services start

Operational commands

Each coin is isolated by project name (-p)

docker compose -p <coin> stop
docker compose -p <coin> start
docker compose -p <coin> ps
docker compose -p <coin> logs -f

Lifecycle semantics

• --build creates images.
• up -d creates and starts containers.
• stop halts containers but preserves state.
• down removes containers but keeps blockchain data.
• down -v removes containers and volumes (destructive). Blockchain state lives in volumes and is never lost unless explicitly removed.

Design guarantees

-Fully sovereign: builds from source -No registry dependency -Deterministic builder base -Coin-level isolation via project name -No wrapper scripts required -Explicit operator control