OZONE CHAIN / WHITEPAPER V3.0A clearer view of the network ↗
HOME / VALIDATORS
SECURITY THROUGH PARTICIPATION

The operators behind
every committed block.

Validators propose and sign blocks. Delegators support the operators they choose with staked OZONE. Explore the network, understand the responsibilities and choose your next step.

01 / CHOOSE WITH CONTEXT

Look beyond
a single number.

Review the current directory and operating history before delegating. Past performance and voting power provide context, not a promise of future results.

REVIEW

Validator information

Check the operator details, commission and current staking status in Ozone Hub. Commission affects the fees a delegator receives.

OBSERVE

Operating performance

Use uptime and consensus views to inspect network operation. Availability and participation can change over time.

UNDERSTAND

Your delegation risk

Delegated OZONE remains owned by the delegator, but it is exposed to validator penalties. Confirm commission, slashing and unbonding rules before signing.

02 / OPERATE RESPONSIBLY

Start with the source.
Prepare for the duty.

A validator is an ongoing network operation. Review the project repository and confirm the current network requirements before provisioning infrastructure or committing stake.

  1. 01

    Confirm the network

    Use the maintained project instructions to confirm software releases, chain configuration and genesis information. The EVM mainnet chain ID is 10121.

  2. 02

    Verify operating requirements

    Confirm hardware, connectivity and minimum self-bond requirements in current operator documentation. Whitepaper v3.0 does not specify a numerical minimum self-bond.

  3. 03

    Plan monitoring and key security

    Prepare monitoring, recovery procedures and secure signing-key handling. Avoid configurations that could lead to double-signing or extended downtime.

  4. 04

    Review the economic exposure

    Understand fees, commission, slashing and the unbonding period. No fixed validator income or reward rate is promised.

03 / THE AGREEMENT LAYER

Voting power
follows stake.

A validator’s voting power combines its own stake with OZONE delegated to it. CometBFT commits a block when validators holding more than two-thirds of voting power sign it.

Read the assumptions with the finality.

Consensus safety relies on less than one-third of voting power being faulty. Committed blocks have single-block finality under those assumptions.

Double-signing can result in slashing and removal. Extended downtime can result in a smaller penalty and jailing. Penalties also affect delegations.

Mechanics summarised from Ozone Chain whitepaper v3.0, section 4, October 2026. External directory and performance tools are maintained separately. Counts of bonded validators and validators producing blocks over a particular window measure different things; consult the source and measurement period.