ozonechainWhitepaper ↗Network consensus, economic penalties and contract reviews address different risks. Use the evidence below to understand what each protects—and what still requires your attention.
These mechanisms complement each other. None removes the possibility of software failure, operational disruption or loss.
CometBFT commits a block after validators holding more than two-thirds of voting power sign it. Consensus safety assumes less than one-third of voting power is faulty. Single-block finality is a consensus property, not a guarantee that a contract or transaction is safe.
Validators and delegators commit OZONE to network security. Double-signing or extended downtime can trigger slashing, including penalties affecting delegated stake. Unbonding introduces a waiting period; confirm current parameters before delegating.
Use the explorer to review transactions, balances and published contract verification information. An account balance or directory rank alone does not establish who owns an address, its allocation purpose or whether its code matches an audit.
SolidProof publishes an OZONE CHAIN assessment covering OzoneChain NFTWall smart contracts. Its re-audit summary reports remediation of previously identified critical and high-severity vulnerabilities. Read the individual findings, comments and accepted-risk explanations alongside that summary.
Take time to verify a request before it becomes an on-chain action.
Use the official Ozone Chain links. Mainnet uses OZONE and chain ID 10121. Check the domain, network and destination address; similarly named projects may use different identifiers.
Verify official identity →Read wallet prompts and application terms. Transfers, approvals, mints and burns can have different consequences. On-chain transactions may be irreversible.
Never disclose a private key or recovery phrase to a website, moderator or person claiming to offer support. Lost or compromised keys may be unrecoverable.
Network finality does not validate an application's business logic. Review its contract, audit scope, permissions and operating model. An ecosystem listing is not a security guarantee.
Read the risk disclosure →For general security enquiries, contact info@ozonechain.com. Describe the affected page or service and provide non-sensitive context. Do not send private keys, recovery phrases, passwords or details that would expose user funds.