Skip to main content

AIOZ Network

AIOZ Network (AIOZ) — 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).

AIOZ Network describes itself as web3 infrastructure for “storage + streaming + decentralized AI computation”, “powered by people” (edge nodes). In Tier‑1 sources, the project also has its own blockchain (EVM x Cosmos) and the AIOZ token (including an ERC‑20 on Ethereum).

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: infrastructure for web3 storage (S3‑like), IPFS services and web3 streaming; plus claimed infrastructure for decentralized AI computation.
  • Who it’s for: dApp developers and projects that need content storage/delivery; users who run edge nodes.
  • Why onchain/token: the network uses a blockchain/smart contracts for accounting/transactions and incentives; the AIOZ token is used for staking, rewards and payments in the ecosystem (per the docs).

How it works (very briefly)

  1. The user does: runs an edge node or uses the products (storage/streaming/AI compute).
  2. The system does: distributes tasks across P2P nodes (storage/delivery/transcoding; for AI — execution of tasks on nodes, as claimed) and keeps onchain accounting/incentives.
  3. The user gets: an infrastructure service (content/data/computation) and/or rewards for contributing resources.
  4. Where the blockchain is: the whitepaper describes a blockchain layer and dBFT consensus for microtransactions; the docs describe the mainnet and tokenomics.
  5. Token role: staking for security, rewards to participants and a means of payment in dApps/infrastructure (per the tokenomics).

Quick links: AI thesis fit

Project passport

Field Value
Project name AIOZ Network
Also known as (aliases) AIOZ
Logo (logo) ../assets/aioz_logo.svg
Token symbol (ticker) AIOZ
Category AI/Compute | Infra
Primary chain (chain) AIOZ
Type Appchain
Network status mainnet
Consensus (consensus) dBFT (Tendermint-based; 21 validators)
Launch date (launch_date) 2021-12
Project status (status) active
Token (standard) ERC-20
Token contract 0x626e8036deb333b408be468f951bdb42433cbf18
Token model (token_type) utility (payments + staking + rewards)
Max supply 549612265
Issuance inflationary + burn (onchain); ERC‑20 capped
Tokenomics (tokenomics, brief) inflation decreasing 8%→5% (2023–2026); 50% to validators/delegators, 50% treasury; burn 50% tx fees
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized AI compute + marketplace
Use‑case (use_case) storage/streaming + AI compute infra
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

In its “Vision Paper”, AIOZ positions itself as a set of infrastructure “pillars”: web3 storage, IPFS infrastructure, web3 streaming and AI compute. The basic thesis is the use of global edge nodes, run by users, for distributed storage/delivery of content and computation.

In the whitepaper (2021), the main focus is dCDN/streaming (transcoding/storage/delivery) with the roles of HUB nodes and Edge nodes, as well as the “dBFT” (delegated BFT) consensus for the blockchain.

Features/modules

  • dCDN / streaming: P2P delivery, transcoding and storage, where edge nodes receive tasks and rewards (whitepaper).
  • Web3 Storage (W3S) and IPFS (W3IPFS): S3‑compatible object storage and IPFS pinning/gateways (vision paper).
  • AIOZ AI (W3AI): claimed AI infrastructure (local execution of tasks on nodes, a marketplace of models/datasets, AI‑as‑a‑service) (vision paper + roadmap).

Typical scenarios

  • Scenario 1 (storage): a dApp stores/serves files via W3S/W3IPFS → pays for usage.
  • Scenario 2 (streaming): a platform serves video/live streams via the dCDN → uses edge nodes for delivery/transcoding.
  • Scenario 3 (AI intent): a developer wants to execute AI tasks/models in the distributed network and/or publish models/datasets in the marketplace (as claimed).
  • Scenario 4 (node operator): a user runs an edge node → provides resources → receives rewards.

Getting started (wallet/network)

  • What you need: for the onchain part — a wallet; for a node — a PC/internet (vision paper).
  • Network/chain: AIOZ mainnet (there is a dedicated explorer in the docs), plus the ERC‑20 token contract on Ethereum.
  • Fees: onchain fees + payments/fees in the ecosystem products.

Architecture/tech (non‑AI)

  • Roles: HUB nodes (indexing/control/payouts) and Edge nodes (transcoding/storage/delivery) — per the whitepaper.
  • Onchain vs offchain: execution of tasks — offchain on nodes; accounting/incentives/contracts — onchain (whitepaper; tokenomics docs).

Token/economics (expanded, no forecasts)

  • Token utility: the tokenomics describe staking for security, rewards to participants and transactions/payments in the ecosystem.
  • Inflation: from 25 Dec 2023, inflation decreases 8%→5% by 1%/year until 2026; 50% to validators/delegators and 50% to the treasury (docs).
  • Burn: 50% of all blockchain transactions, as well as additional burn mechanics (docs).
  • ERC‑20 supply: Etherscan indicates a Max Total Supply of 549,612,265 AIOZ for the ERC‑20 contract.

Governance

The vision paper claims “community governance” for the AI marketplace; the tokenomics docs mention a treasury and incentives, but the governance mechanics lack a specific process/contracts in the available Tier‑1 sources.

Security and incidents

  • Security advisories: there are GitHub advisories for aioz-node.
  • Audits/bug bounty: not found in Tier‑1 sources.

Project status and timeline

  • Mainnet: the tokenomics docs say the mainnet launched in Dec 2021.
  • Roadmap: a separate docs page with AI/Stream/Storage items.

Ecosystem/integrations

  • EVM x Cosmos: the vision paper describes the blockchain’s compatibility with EVM and Cosmos.
  • Explorers: the docs list AIOZ Blockchain explorers (mainnet/testnet).

AI component of the project

  • What is real AI here? The vision paper describes the “W3AI” product block with local execution of AI tasks on nodes, an AI marketplace and AI‑as‑a‑service (Tier‑1 as the project’s claim).
  • What is truly onchain? There is a blockchain/smart contracts and a token; the ERC‑20 address on Ethereum is confirmed by Etherscan.
  • Why is a token needed? Incentives (rewards), security (staking) and payments within the ecosystem (tokenomics).
  • Red flags (based on the information found): AI‑washing (part of the AI functionality may be roadmap/not launched); onchain‑washing (addresses of specific AI marketplace contracts and the payment flow are needed).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the vision paper describes W3AI as infrastructure for executing AI tasks on nodes and a marketplace of models/datasets.
  • Evidence: Tier‑1 — https://blog.aioz.network/aioz-network-vision-paper/
  • Why sufficient / why not (one line): there is a description of the AI block’s functions (although without signs of production metrics).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo of “working AI models/agents” in the form of reproducible examples/endpoints was found.
  • Evidence: Tier‑1 — https://blog.aioz.network/aioz-network-vision-paper/
  • Why sufficient / why not (one line): there is a description of use cases, but no demos/interfaces.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://blog.aioz.network/aioz-network-vision-paper/
  • Why sufficient / why not (one line): AI performance/quality metrics are not provided.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the AI block is described conceptually; specifications of architecture/versions/interfaces are insufficient.
  • Evidence: Tier‑1 — https://blog.aioz.network/aioz-network-vision-paper/
  • Why sufficient / why not (one line): there are no detailed implementation parameters.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: AIOZ mainnet; ERC‑20 token on Ethereum
  • Addresses/identifiers: AIOZ ERC‑20: 0x626E8036dEB333b408Be468F951bdB42433cBF18
  • Evidence: Tier‑1 — https://etherscan.io/token/0x626E8036dEB333b408Be468F951bdB42433cBF18
  • Why sufficient / why not (one line): Etherscan confirms the address, supply and metadata.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the whitepaper describes a blockchain layer and microtransactions/payouts in the network (dBFT).
  • Evidence: Tier‑1 — https://aioz.network/210121_AIOZ_Whitepaper.pdf
  • Why sufficient / why not (one line): a separate blockchain and consensus for network operations are described.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: Tier‑1 contains no strict proof that the entire infrastructure is impossible without the onchain layer (part of the functions could be centralized).
  • Evidence: Tier‑1 — https://aioz.network/210121_AIOZ_Whitepaper.pdf
  • Why sufficient / why not (one line): there is a design with onchain incentives, but criticality is not formalized by a test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the AIOZ token exists (including an ERC‑20 on Ethereum).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x626E8036dEB333b408Be468F951bdB42433cBF18
  • Why sufficient / why not (one line): Etherscan shows the contract and supply.
  • 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 docs describe that AIOZ tokens are used for transactions/payments in dApps and infrastructure products.
  • Evidence: Tier‑1 — https://docs.aioz.network/overview/aioz-tokenomics
  • Why sufficient / why not (one line): it is explicitly stated: “means of payment within dApps built on the AIOZ Network”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the token is used for staking (security) and reward mechanics (validators/delegators, DePIN and others).
  • Evidence: Tier‑1 — https://docs.aioz.network/overview/aioz-tokenomics
  • Why sufficient / why not (one line): staking and the distribution of inflation/rewards are described.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance mechanics are claimed in the vision paper for individual components, but the Tier‑1 docs contain no governance process/contracts.
  • Evidence: Tier‑1 — https://blog.aioz.network/aioz-network-vision-paper/
  • Why sufficient / why not (one line): there is a declaration of “community governance”, but without onchain details.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): in Tier‑1 the token is described as a utility for payments/rewards/security, without a statement that it is “optional”.
  • Evidence: Tier‑1 — https://docs.aioz.network/overview/aioz-tokenomics
  • Why sufficient / why not (one line): the token is built into the network economy.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.aioz.network/overview/aioz-tokenomics inflation/distribution/burn and token utility (staking/payments/rewards)
Tier‑1 https://docs.aioz.network/overview/roadmap roadmap for AIOZ AI (agents/LLM/GenAI and more)
Tier‑1 https://blog.aioz.network/aioz-network-vision-paper/ positioning of the pillars (storage/streaming/AI compute) and description of W3AI
Tier‑1 https://aioz.network/210121_AIOZ_Whitepaper.pdf dCDN architecture and description of dBFT on Tendermint
Tier‑1 https://etherscan.io/token/0x626E8036dEB333b408Be468F951bdB42433cBF18 the AIOZ ERC‑20 token contract and max total supply

No comments to display

Back to top