Run a Congrid Verifier

Install a full Congrid node and verifier stack, or attach the verifier components to an existing node, with one interactive command. The official installer supports Linux and macOS, uses native binaries, and does not require Docker.

Step 1 — Install the native verifier stack

Run this as a normal login user with sudo access on Linux. On macOS, run it as your normal user without sudo. The installer downloads checksum-verified binaries, asks for the required settings through your terminal, and fetches the seed list in full-stack mode.

curl -fsSL https://congrid.net/downloads/install.sh | bash

If content-grid-d is already running on this machine, install only Chroma, indexerd, and verifierd with the existing-node mode:

curl -fsSL https://congrid.net/downloads/install.sh | bash -s -- --components-only

This mode verifies the existing RPC and gRPC endpoints, then uses isolated component state. It does not replace, configure, stop, start, or restart the existing chain node.

You can also download and inspect the installer before running it. Re-running the same command safely updates the software and service definitions while preserving chain data, keys, verifier state, and Chroma data.

Step 2 — Fund and bond the verifier

The installer prints the verifier address when it finishes. Send enough ucongrid to that address for the bond and ongoing transaction fees, then submit the bond from the same host. The examples use the default key name verifier-key; replace it if you chose another name.

Linux

sudo -u congrid /usr/local/bin/content-grid-d verifier bond 1000000 \
  --denom ucongrid \
  --from verifier-key \
  --home /var/lib/congrid \
  --keyring-backend file \
  --keyring-dir /var/lib/congrid/keyrings/verifier \
  --chain-id congrid-main \
  --node tcp://127.0.0.1:26657 \
  --gas-prices 0.001ucongrid \
  -y

With --components-only, use /usr/local/libexec/congrid/content-grid-d-client as the Linux binary and /var/lib/congrid-components for both --home and the keyring path prefix.

macOS

~/.local/bin/content-grid-d verifier bond 1000000 \
  --denom ucongrid \
  --from verifier-key \
  --home "$HOME/.content-grid" \
  --keyring-backend file \
  --keyring-dir "$HOME/.content-grid/keyrings/verifier" \
  --chain-id congrid-main \
  --node tcp://127.0.0.1:26657 \
  --gas-prices 0.001ucongrid \
  -y

With --components-only, use ~/.local/share/congrid/libexec/content-grid-d-client as the macOS binary and ~/.content-grid-components as the home and keyring path prefix.

Step 3 — Monitor the verifier stack

On Linux, inspect all four systemd services and follow verifier logs. Existing-node mode manages only congrid-chroma, congrid-indexer, and congrid-verifier.

sudo systemctl status congrid-node congrid-chroma congrid-indexer congrid-verifier
sudo journalctl -u congrid-verifier -f

On macOS, inspect the launchd job and its log:

launchctl print "gui/$(id -u)/net.congrid.verifier"
tail -f "$HOME/.content-grid/logs/verifier.log"

Health endpoints and assignment queries are available locally on either platform:

curl -fsS http://127.0.0.1:8000/healthz
curl -fsS http://127.0.0.1:9100/healthz
curl -fsS http://127.0.0.1:9200/healthz

# Linux binary path; use ~/.local/bin/content-grid-d on macOS
/usr/local/bin/content-grid-d verifier assignments <verifier-address> \
  --node tcp://127.0.0.1:26657 \
  --grpc-addr 127.0.0.1:9090 \
  --grpc-insecure \
  --include-finalized -o json

• When this installer manages the full node, allow inbound TCP/26656 for P2P connectivity.
• Alert on service exit, RPC disconnect, failed checks, and assignment backlog.
• Keep enough balance available for verifier transaction fees.
• Re-run the installer periodically to deploy published software updates.