Becoming a ChainOS Validator

Validator Role

Validators are essential participants in the ChainOS network who secure the blockchain, produce blocks, and participate in consensus. In return, validators earn rewards from transaction fees and block rewards.

Validator Overview

The ChainOS network operates with a set of 100 validators who are responsible for maintaining consensus and securing the blockchain. Validators in ChainOS:

Run specialized hardware to ensure high availability and performance
Stake (bond) UOS tokens as collateral
Produce blocks and validate transactions
Participate in governance decisions
Earn rewards proportional to their stake

Requirements

Before becoming a validator, ensure you meet these requirements:

Hardware Requirements

Production Validator Specifications

CPU: 16+ cores / 32+ threads (3.5+ GHz)
RAM: 64GB+ DDR4
Storage: 2TB+ NVMe SSD (enterprise grade)
Network: 1 Gbps symmetric connection with low latency
Redundancy: UPS, backup power, redundant network connections
Security: Hardware security module (HSM) for key storage

Token Requirements

To become a validator, you need:

Minimum Stake: 10,000 UOS tokens
Recommended Stake: 50,000+ UOS tokens for better chances of being in the active set

Important Note on Slashing

Validators who violate protocol rules (double signing, extended downtime) may have a portion of their staked tokens slashed. Ensure your infrastructure is secure and reliable before becoming a validator.

Validator Setup Process

Follow these steps to set up your validator node:

1. Set Up a Full Node

First, you need to set up a full node following our Node Setup Guide. Ensure your node is fully synced with the network before proceeding.

2. Create or Recover a Wallet

# Create a new wallet
chainosd keys add validator-wallet

# Or recover an existing wallet
chainosd keys add validator-wallet --recover

Make sure to securely back up your mnemonic phrase in a safe location.

3. Acquire UOS Tokens

You'll need at least 10,000 UOS tokens to become a validator. These can be acquired through:

Exchanges that list UOS
Direct purchase from existing token holders
Contacting the ChainOS team for validator candidacy

4. Create Your Validator

Once your node is synced and you have the required tokens, you can create your validator:

chainosd tx staking create-validator \
  --amount=10000000000uos \
  --pubkey=$(chainosd tendermint show-validator) \
  --moniker="your-validator-name" \
  --website="https://yourwebsite.com" \
  --details="Description of your validator" \
  --security-contact="security@yourvalidator.com" \
  --chain-id=chainos-1 \
  --commission-rate="0.10" \
  --commission-max-rate="0.20" \
  --commission-max-change-rate="0.01" \
  --min-self-delegation="1" \
  --gas="auto" \
  --from=validator-wallet

Parameter Explanation

amount: Amount of tokens to stake (in uos, where 1 UOS = 1,000,000 uos)
pubkey: Your validator's public key
moniker: A name for your validator (visible on block explorers)
website, details, security-contact: Public information about your validator
commission-rate: Percentage of rewards you take as commission
commission-max-rate: Maximum commission you can charge
commission-max-change-rate: Maximum daily increase in commission

5. Verify Your Validator Status

Check if your validator was successfully created and is in the active set:

# Query your validator info
chainosd query staking validator $(chainosd keys show validator-wallet --bech val -a)

# Check if you're in the active validator set
chainosd query tendermint-validator-set | grep $(chainosd tendermint show-address)

Validator Best Practices

To maintain a reliable validator operation and avoid slashing, follow these best practices:

Security

Security Recommendations

Use a Hardware Security Module (HSM) for key management
Set up a sentry node architecture to protect your validator from DDoS attacks
Implement strict firewall rules to limit access to your validator
Use SSH keys and disable password authentication
Regularly update your server's operating system and security patches
Implement multi-factor authentication for all access points

Monitoring

Set up comprehensive monitoring to ensure your validator is operating correctly:

Monitor server metrics (CPU, RAM, disk, network)
Set up alerts for missed blocks and validator status changes
Monitor your signing performance and uptime
Implement log monitoring for error detection

# Example Prometheus configuration for ChainOS monitoring
scrape_configs:
  - job_name: 'chainos'
    scrape_interval: 15s
    metrics_path: /metrics
    static_configs:
      - targets: ['localhost:26660']

High Availability

To ensure maximum uptime and avoid slashing due to downtime:

Set up a backup validator node that can take over if the primary fails
Implement automatic failover mechanisms
Use redundant power supplies and network connections
Consider using cloud providers with high availability guarantees

Validator Economics

Understanding the economic aspects of running a validator is crucial:

Rewards

Validators earn rewards from two sources:

Block Rewards: New UOS tokens minted with each block
Transaction Fees: Fees paid by users for transactions

Rewards are distributed proportionally to stake, with validators taking a commission.

Commission

Validators set a commission rate, which is the percentage of rewards they keep before distributing the remainder to delegators. Setting the right commission is important:

Too high: May discourage delegations
Too low: May not cover operational costs

Most validators set commissions between 5-20% based on their services and reputation.

Slashing Risks

Validators face slashing penalties for:

Double Signing: 5% of staked tokens
Downtime: 0.01% of staked tokens after missing 10,000 blocks (approximately 6.5 hours)

These penalties affect both the validator's self-bonded tokens and their delegators' tokens.

Validator Application Process

While anyone with sufficient tokens can become a validator, joining the active set requires being among the top 100 validators by stake. To improve your chances:

1. Contact the ChainOS Team

Reach out to the ChainOS team to express your interest in becoming a validator:

Email: validators@opencryptofoundation.com
Discord: discord.gg/opencrypto

2. Prepare a Validator Proposal

Create a proposal document that includes:

Your technical expertise and experience
Infrastructure details and security measures
Contribution plans to the ChainOS ecosystem
Your team and background

3. Engage with the Community

Active participation in the ChainOS community can help you gain visibility and delegations:

Participate in governance discussions
Contribute to development or documentation
Help other community members
Share your validator journey and insights

Ready to Apply?

If you're ready to become a ChainOS validator, contact us through our Discord or email validators@opencryptofoundation.com with your proposal.

Frequently Asked Questions

How much can I earn as a validator?

Earnings depend on your stake, the total staked tokens in the network, and your commission rate. With the current network parameters, validators can expect an annual return of approximately 8-15% before operational costs.

Can I run a validator on a cloud provider?

Yes, many validators use cloud providers like AWS, GCP, or Azure. However, for maximum security and performance, consider using dedicated hardware or a hybrid approach.

What happens if my validator goes offline?

If your validator misses blocks, it will be temporarily removed from the active set (jailed) after missing 10,000 consecutive blocks. You can unjail your validator once it's back online.

Can I change my commission rate after creating my validator?

Yes, you can change your commission rate once per day, up to your commission-max-change-rate parameter set during creation.