Skip to main content

OKZOO

OKZOO — 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).

OKZOO — an AI/Data | Infra project on BNB Smart Chain, token (symbol: AIOT).

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: an AIoT/DePIN project that builds a decentralized network of sensor devices (OK‑mini / P‑mini) for collecting environmental data (air quality, noise, CO2, humidity, weather, etc.).
  • Who it’s for: for users (owners of devices and OKZOO V2 “pets”) and for developers/systems that need large‑scale “street‑level” data.
  • Why onchain/token: to validate and store data onchain (transparent verification of origin/integrity) and to account for participation in the network (incentivization is claimed, but the specific token utility is not confirmed in Tier‑1 sources).

How it works (very briefly)

  1. The user does: uses a sensor device (OK‑mini / P‑mini o1) and interacts with a “pet” (OKZOO V2).
  2. The system does: the device measures environmental parameters (air quality / noise / CO2 / humidity / weather, etc.) and forms datasets.
  3. The user gets: a gamified experience (the AI pet reacts to the environment) and claimed incentives for contributing data.
  4. Where the blockchain is: per the Tier‑1 description, data is validated and stored onchain by “validator machines” in the OKZOO network.
  5. Token role (if any): the token exists (AIOT, BEP‑20 on BNB Smart Chain); Tier‑1 sources record the onchain issuance/supply but do not provide a sufficient description of the utility (TK_1..TK_3 remain 0).

Quick links: AI thesis fit

Project passport

Field Value
Project name OKZOO
Also known as (aliases) OKZOO (AIOT)
Logo (logo) ../assets/93_okzoo_logo.svg
Token symbol (ticker) AIOT
Category AI/Data | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2025-04-22
Project status (status) active
Token (standard) BEP-20
Token contract 0x55ad16bd573b3365f43a9daeb0cc66a73821b4a5
Token model (token_type) —
Max supply 1,000,000,000
Issuance fixed (minted at deploy)
Tokenomics (tokenomics, brief) 1B tokens minted in the creation tx; no additional issuance mechanics were found in Tier‑1
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI pets + AIoT environmental data
Use‑case (use_case) decentralized environmental data network
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 3 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

OKZOO positions itself as a decentralized AIoT device network for the mass collection of “street‑level” environmental data and its use in applications. At the center of the idea is moving data collection from the model “a single centralized organization collects/publishes” to a model where many physical sensor devices belong to the community, and the data is validated and stored onchain.

The user “entry point” into the project is OKZOO V2: an app with AI pets (Tamagotchi‑style), which is meant to increase the engagement of device owners and thereby the sustainability of the sensor network. The device (P‑mini/OK‑mini) measures environmental parameters, and the AI pet reacts to them visually/behaviorally.

Features/modules

  • AIoT devices (OK‑mini / P‑mini o1) with micro sensor nodes (air quality, noise, CO2, humidity, weather, etc.).
  • OKZOO V2: AI pets that display emotions/behavior depending on environmental data and user actions.
  • Onchain layer (validators): per the Tier‑1 description, data is validated and stored onchain by “validator machines”.

Typical scenarios

  • Scenario 1 (user/device owner): wears a P‑mini → the device collects environmental data → the AI pet in OKZOO V2 changes its behavior → the user gets a gaming experience and claimed incentives.
  • Scenario 2 (applications/developers): use the aggregated network data as an “environmental oracle” → build services/analytics around local environmental signals.

Getting started (wallet/network)

  • What you need: an account/access to OKZOO V2 and an OK‑mini / P‑mini device (to participate in the physical part).
  • Network/chain: BNB Smart Chain (the AIOT token — BEP‑20).
  • Fees: standard BSC fees for onchain operations (transfers/interaction with contracts), if used.

Architecture/tech (non‑AI)

  • Components: sensor devices (OK‑mini / P‑mini), the OKZOO V2 client app, contracts/accounts on BNB Smart Chain, validator machines (per the Tier‑1 description).
  • Participant roles: device owners/users (data collection), validators (validation and onchain storage), data consumers.
  • Where logic runs: measurements and part of the processing — on the device; the gaming experience — in the app; data validation/accounting — onchain (claimed).
  • Dependencies: BNB Smart Chain as the base L1 for the token/accounting.

Token/economics (expanded, no forecasts)

  • What can be confirmed per Tier‑1 about the token: the AIOT token — BEP‑20 on BNB Smart Chain, with a fixed max supply of 1,000,000,000, which was minted in the creation tx (Apr‑22‑2025) to the deployer/recipient address.
  • Token utility: the Tier‑1 sources used here describe network incentivization and rewards but do not record a specific economic role for the token (payments/staking/DAO). Therefore, in DecAI Fit the token necessity is assessed as low (TK_1..TK_3 = 0).

Governance

  • Who makes decisions: —. No Tier‑1 description of governance mechanics was found.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: no audit report is listed in Tier‑1 (links_*); BscScan states that no audit was submitted via their form.
  • Bug bounty: not found in Tier‑1 sources.
  • Incidents: not found in Tier‑1 sources.
  • Threat model: risks of data quality/forgery from devices and of centralized validation assumptions; token smart contract risks (a standard ERC‑20‑compatible contract).

Project status and timeline

  • Current status: mainnet (the token and the onchain part on BNB Smart Chain are available; the roadmap describes upcoming device/version releases).
  • Key milestones: deployment of the AIOT token (2025-04-22, BNB Smart Chain).
  • Roadmap: P‑mini o1 launch, AI Engine upgrade, OKZOO V3 expansion, P‑mini o2, OKZOO World, Collective Learning.

Ecosystem/integrations

  • Integrations: BNB Smart Chain (the AIOT token), GitHub (smart‑contract repo), docs/roadmap.
  • Partners: —. No Tier‑1 confirmed partners were found.
  • Where it’s actually used: OKZOO V2 as a consumer app; P‑mini/OK‑mini as the physical data source.

AI component of the project

  • What is real AI here? Tier‑1 describes AI pets in OKZOO V2: adaptive personality modeling, real‑time behavior adaptation, an AI assistant to guide the player; the P‑mini device is also described with an “AIoT learning capability” for adapting to interactions.
  • What is truly onchain? the Tier‑1 primer states that the collected data is validated and stored onchain by “validator machines”; the issuance of the AIOT token on BNB Smart Chain is also confirmed onchain.
  • Why is a token needed? Tier‑1 records the issuance and supply of the token but does not disclose a specific utility (payments/staking/governance) → in the scoring, token necessity is low.
  • Red flags (based on the information found): token‑washing — the token exists, but its role in the protocol is not described in Tier‑1; AI‑washing — many descriptions of AI features, but without metrics/benchmarks and without a reproducible demo of the AI component.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): The AI component is confirmed as existing (AI_1=1), so “intent only” does not apply.
  • Evidence: Tier‑1 — https://docs.okzoo.app/okzoo-v2
  • Why sufficient / why not (one line): By definition, AI_0 is set only when AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): OKZOO V2 describes AI pets (adaptive personality modeling / real‑time behavior adaptation / AI assistant).
  • Evidence: Tier‑1 — https://docs.okzoo.app/okzoo-v2
  • Why sufficient / why not (one line): Tier‑1 directly describes what exactly the AI does in the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No reproducible Tier‑1 demo/quickstart showing the AI module in operation was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is a description of features, but no “how‑to/demo” by which the AI can be verified in practice.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No benchmarks/quality metrics for the AI part were found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The documentation describes the mechanics of the AI part (behavior/gamification/assistant systems; the EXP formula) and the device’s “AIoT learning capability”.
  • Evidence: Tier‑1 — https://docs.okzoo.app/okzoo-v2, https://docs.okzoo.app/p-mini-o1
  • Why sufficient / why not (one line): There is a technical description of how the AI features manifest and some of the parameters/formulas.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: AIOT (BEP‑20) 0x55ad16bd573b3365f43a9daeb0cc66a73821b4a5
  • Evidence: Tier‑1 — https://bscscan.com/token/0x55ad16bd573b3365f43a9daeb0cc66a73821b4a5
  • Why sufficient / why not (one line): There is an onchain token contract in the network explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Tier‑1 describes that the collected data is validated and stored onchain by the OKZOO network’s validator machines.
  • Evidence: Tier‑1 — https://docs.okzoo.app/primer
  • Why sufficient / why not (one line): Tier‑1 directly states onchain storage/validation of data (not just a token).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain validation/storage, the claimed verifiability of data origin is lost and the “single point of failure” returns to the data distribution system.
  • Evidence: Tier‑1 — https://docs.okzoo.app/primer
  • Why sufficient / why not (one line): The problem of a centralized provider and the solution via decentralized onchain validation are described as the core of the concept.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The token exists: AIOT (BEP‑20) on BNB Smart Chain.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x55ad16bd573b3365f43a9daeb0cc66a73821b4a5
  • Why sufficient / why not (one line): The existence of the token is confirmed onchain.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Tier‑1 does not describe payments with the token for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 artifact “pay with AIOT for X”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentivization is claimed, but the link to the AIOT token (rewards/collateral/penalties) is not recorded in Tier‑1.
  • Evidence: Tier‑1 — https://docs.okzoo.app/primer
  • Why sufficient / why not (one line): Tier‑1 talks about incentives but does not link them to token mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not described in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 artifact (Snapshot/DAO/voting) for AIOT.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token cannot be assessed without a Tier‑1 description of its role (TK_1..TK_3).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Insufficient data.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.okzoo.app/primer OKZOO as a decentralized AIoT network; sensor devices; the problem of centralized collection; the statement “validated and stored on-chain by validator machines”.
Tier‑1 https://docs.okzoo.app/okzoo-v2 What the AI part does in OKZOO V2 (AI pets, adaptive personality modeling, AI assistant, etc.).
Tier‑1 https://docs.okzoo.app/p-mini-o1 P‑mini o1 as a physical sensor device; AIoT learning capability; interactions/sensors.
Tier‑1 https://docs.okzoo.app/roadmap Roadmap: device launches (P‑mini o1/o2), AI engine upgrade, collective learning (plans/product evolution).
Tier‑1 https://bscscan.com/tx/0xd6ffdfe243fe35f21aa3999978c40a906239b33e82b287aa5e9c2ee2a5aa8460 Creation tx of the AIOT token: timestamp (launch/creation date) and mint of 1,000,000,000 (max supply).
Tier‑1 https://github.com/okzoo-app/okzoo-v2-smart-contract/security/advisories Security advisories: no advisories published (at the time of the check).

No comments to display

Back to top