Ika Operatorv1.0.0

An organization sets up a new validator on the Ika mainnet, following the step-by-step guide to generate keys, register as a candidate, stake IKA, and run the node. This scenario covers the entire lifecycle from configuration to verification.

An operator upgrades their validator hardware for better performance or moves to a different data center. They must carefully back up keys, especially the root-seed, and reconfigure the node, minimizing downtime while maintaining committee membership.

A development team deploys an Ika fullnode to access network state for building applications. They use the auto-detection configuration to run a fullnode, which syncs via P2P and provides an interface for transactions without consensus responsibilities.

An entity runs an Ika notifier to submit checkpoints to the Sui network, ensuring cross-chain functionality. They configure the notifier with the necessary key pair and monitor its operations, as it is essential for network integrity.

A node operator experiences connectivity problems, discovering that ports 8080-8084 or 9184 are blocked. They use the guide to verify protocol settings (TCP/UDP) and fix firewall rules, restoring proper communication with peers and metrics scraping.

Offer managed validator services for Ika network, handling deployment, monitoring, and maintenance for clients. Revenue is generated through subscription fees or a percentage of staking rewards.

Operate a staking pool where multiple IKA holders delegate their tokens to the validator, who runs the node. Revenue comes from commission on staking rewards earned by the pool.

Provide consulting services to enterprises setting up their own Ika nodes, offering setup, optimization, and support. Revenue is earned through one-time setup fees and ongoing support contracts.