Skip to main content

Ozone Metaverse

Ozone Metaverse (OZONE) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Ozone Metaverse — an AI/Other | Metaverse project on BNB Smart Chain, token (symbol: OZONE).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a platform/studio for creating 3D content and game/online worlds with Web3 integration; “AI services” are claimed as part of the future utility.
  • Who it’s for: developers/content creators and teams that build games/virtual worlds and want Web3 integration.
  • Why onchain/token: the OZONE token is described as the currency/utility for in‑game transactions, the asset marketplace and future “software/AI services”.
  • What you can actually touch (Tier‑1): Arena (an application/surface of the ecosystem, mentioned in the whitepaper).

How it works (very briefly)

  1. The user does: uses Ozone products/services and interacts with the Web3 part (assets/marketplace; claimed).
  2. The system does: provides 3D/gaming infrastructure and Web3 integration (claimed).
  3. The user gets: content/experience (games/worlds) and digital assets; in some scenarios — via the OZONE token (claimed).
  4. Where the blockchain is: the OZONE token and Web3 assets/transactions are onchain; the rest of the platform logic — offchain.
  5. Token role (if any): the currency/utility of the ecosystem (in‑game transactions, marketplace, rewards; governance — as a plan).

Quick links: AI thesis fit

Project passport

Field Value
Project name Ozone Metaverse
Also known as (aliases) Ozone | OZONE
Logo (logo) ../assets/554_ozone-metaverse_logo.svg
Token symbol (ticker) OZONE
Category AI/Other | Metaverse | Gaming
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0xbf8bab33600d5bca18e4464e34c2a8d532031f5c
Token model (token_type) utility (payments)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The token is used as the currency/utility for in‑game transactions and the marketplace; governance/AI services are mentioned as future directions.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) Ozone Technologies
Funding (investors/funding) —
AI component (ai_component) AI services
Use‑case (use_case) 3D/game platform + Web3
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 2 / evidence_score 2
Last verified 2026-02-11

General project overview

Ozone Metaverse describes itself as a platform/studio for developing 3D content and game/online worlds, with “Web3 & AI” integrations. Within this card, we record only what is confirmed by Tier‑1 sources: the existence of a public whitepaper (GitBook), the description of the token utility and the link to Arena.

Features/modules

  • 3D/gaming platform: a “3D graphics engine” and cloud infrastructure (claimed).
  • Web3 integration: the token and digital ownership/marketplace scenarios (claimed).
  • AI direction: “AI services” are mentioned as part of the future utility (intent).

Typical scenarios

  • Scenario 1: a user/player buys/sells digital assets → uses the token for transactions (claimed).
  • Scenario 2: a user interacts with Arena → gets access to the ecosystem surface (Tier‑1 link).

Getting started (wallet/network)

  • What you need: an EVM wallet and assets for fees on BNB Smart Chain.
  • Network/chain: BNB Smart Chain.
  • Fees: BNB Smart Chain fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: the OZONE token (BEP‑20), web products/portals of the ecosystem (Arena/website/whitepaper), the platform’s offchain infrastructure.
  • Participant roles: users/players; content creators/developers.
  • Where logic runs: onchain — the token and Web3 transactions; offchain — the main functionality of the platform/services.
  • Dependencies: BNB Smart Chain RPC; web infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): in‑game transactions and metaverse services; support for marketplace/virtual asset trading; rewards; governance as a plan.
  • Protocol necessity drivers: the token is claimed as the “primary currency” of the ecosystem and as an element of the Web3 integration (claimed).
  • Issuance/burn: — (not established per Tier‑1).

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: typical smart contract risks of the token and web infrastructure risks.

Project status and timeline

  • Current status: active (based on the presence of a public website/whitepaper).
  • Key releases/milestones: —.
  • Roadmap: see links_* (Tier‑1).

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? Tier‑1 sources mention “AI‑driven/AI services”, but without a tech description/metrics — we treat it as intent.
  • What is truly onchain? Onchain — the OZONE token (BEP‑20) and the related Web3 transactions.
  • Why is a token needed? The token is described as the currency/utility for in‑game transactions, marketplace and rewards; governance — as a plan.
  • Red flags (based on the information found): “AI services” without verifiable artifacts/metrics; it is important to separate intent from a real AI component.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity medium 2
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 1
  • Claim (one line): In Tier‑1 sources, AI is mentioned as a direction/services for the platform.
  • Evidence: Tier‑1 — https://ozonemetaverse.io/ ; https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token
  • Why sufficient / why not (one line): This records intent, but does not prove a specific AI module/quality.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): What exactly the AI part does (task/model/metric) is not established per Tier‑1.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/
  • Why sufficient / why not (one line): 1 requires specifics about the AI component, not general mentions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo that shows the operation of the AI part specifically was found.
  • Evidence: Tier‑1 — https://ozonemetaverse.io/
  • Why sufficient / why not (one line): The existence of a product/website does not prove an AI demo.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/
  • Why sufficient / why not (one line): In Tier‑1, no reproducible quality metrics for the AI part were found.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): No tech description of the AI module (model/versions/architecture) was found per Tier‑1.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/
  • Why sufficient / why not (one line): A general description of the platform is not enough to record AI_4=1.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: OZONE contract: 0xbf8bab33600d5bca18e4464e34c2a8d532031f5c
  • Evidence: Tier‑1 — https://bscscan.com/token/0xbf8bab33600d5bca18e4464e34c2a8d532031f5c
  • Why sufficient / why not (one line): The token contract is observable in a public explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: per Tier‑1, the existence of protocol onchain logic other than the token/assets is not established.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/
  • Why sufficient / why not (one line): 1 requires specific contracts and their role (not found).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/
  • Why sufficient / why not (one line): No proof was found that a key property of the product breaks down without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, OZONE (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0xbf8bab33600d5bca18e4464e34c2a8d532031f5c
  • Why sufficient / why not (one line): The token contract is observable in the explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): The token is described as a digital currency for in‑game transactions, smart contracts and metaverse services.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token
  • Why sufficient / why not (one line): Tier‑1 directly describes the token’s use scenarios as currency/utility.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): Rewards and the token’s role in the ecosystem’s engagement/rewards are mentioned.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token
  • Why sufficient / why not (one line): Tier‑1 lists rewards as part of the token utility.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance is described as a future activity/experiments, not a working mechanism.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token
  • Why sufficient / why not (one line): 1 requires a launched/described governance process (not found).
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token
  • Why sufficient / why not (one line): 1 requires an explicit argument “possible without the token” (not found).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://ozone-metaverse.gitbook.io/whitepaper/2025-livepaper/technology/web3/usdozone-token Tier‑1 description of the token utility (currency for in‑game and metaverse services, marketplace, rewards; governance as a plan).
Tier‑1 https://ozonemetaverse.io/ozone-token Token page on the official website (context and a link to the whitepaper).
Tier‑1 https://bscscan.com/token/0xbf8bab33600d5bca18e4464e34c2a8d532031f5c Onchain fact: the OZONE token contract on BNB Smart Chain.
Tier‑1 https://arena.ozonemetaverse.io/ The “Arena” ecosystem surface (mentioned as usable at).

No comments to display

Back to top