# ZooBC Operators

Canonical page: https://zoobc.com/roles/operators/
Audience: Node operators, gateway operators, infrastructure engineers, and network stewards
Symbol: The Elephant, representing memory, continuity, and dependable strength
Last reviewed: 2026-08-18

Operators run distinct network services and must diagnose the correct boundary. A full node validates and accepts transaction POSTs through a mempool. An archival service preserves readable history and is read-only. A gateway routes public traffic to allowed healthy services. A relay has a separate network role.

## Operating duties

- Hash and verify every release before execution.
- Monitor host CPU, memory, disk, and uptime separately from chain height and freshness.
- Test GET history against readable services and transaction POSTs against full nodes.
- Protect the gateway control plane with per-box administrative credentials.
- Keep specific-node proxying constrained by the allowlist so the gateway cannot become an open proxy.

A green machine does not prove a synchronized node. A failed transaction broadcast may be a routing error if it reached archival history instead of a full-node mempool. A missing or stale response must be reported as unavailable, not converted into a zero measurement.

## Readiness test

Record the binary version and fingerprint, service role, network, domain and ports, credential owner, system health, blockchain status, independent height comparison, and the result of a role-specific end-to-end test.

Primary action: Get node software: https://zoobc.com/explorer/#/downloads
Related: https://zoobc.com/gateway/ | https://zoobc.com/developer/#p-ops | https://zoobc.com/admin | https://zoobc.com/explorer/#/network/nodes | https://zoobc.com/coinbase/ | https://zoobc.com/security/