RP1 operations differ from a standard Cosmos deployment because the daemon starts custom DAG consensus around the SDK application. Use the operator pages as a map, then follow the versioned runbook for the exact release and network.
Operations map
- Join the testnet as a validator — partner binary/image install, bootstrap join, and live admission into the validator group.
- Validator — active-validator role, startup, peer reachability, and shutdown expectations.
- Observer — read-only node role for RPC, indexing, and integration checks.
- Monitoring — status, canonical headers, metrics, and evidence.
- State sync and recovery — durable state movement and retained-data boundaries.
- Upgrades — named migrations, app/consensus coordination, and rollback thinking.
- Testnet — local and public testnet workflows.
Core operator rule
Keep consensus, application, RPC, API, gRPC, EVM, and validator configuration aligned. A node can be process-live while not being ready to accept work, connected to the expected consensus set, or exposing a complete retained header.
Partners evaluating the public testnet should start with Getting started for client connectivity, then use the join guide only when they intend to run consensus infrastructure.