CLRTY-1 Mainnet → Validators and Systems → Validator Guides

Validator guides index Moniversive operator paths: registry, heartbeat, genesis verification, and failover rehearsal.

On This Page

Overview

Validator guides index Moniversive operator paths: registry, heartbeat, genesis verification, and failover rehearsal.

<aside> <img src="g" alt="g" width="40px" />

Where validators exist (read first): Where Validators Exist

On Proof-of-Stake chains (primary use case): validators replace miners — they stake tokens instead of using compute power. CLRTY-1 has no miners; security is PoC bonding of CLRTY.

</aside>

Core Principle / Logic

Rehearse on Devnet/Testnet before Mainnet. Full stake invent CLIs remain Roadmap. Operators bond / stake CLRTY (not burn electricity like PoW miners).

Architecture / Commands

Operators and developers interact through the clrty control plane; Systems (clarityd) and RPC (clrty-api) remain distinct roles.

Live CLI

clrty node status --plain
clrty node registry --plain
clrty node register --dry-run
clrty node heartbeat --node-id test --dry-run
clrty node genesis-verify --plain
clrty producer deadman --dry-run