Skip to main content

Züs

Züs (0chain) — 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).

Züs — an AI/Data | Infra project positioning itself as a blockchain‑based storage system (BOSS) with a token economy and a claimed AI direction (AI data platform / AI agents); token (symbol: ZCN).

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 decentralized data storage system (S3‑compatible) where the blockchain observes/validates storage and incentivizes providers.
  • Who it’s for: users and teams that need storage/backups/exchange of encrypted files; storage providers (blobbers) and staking participants.
  • Why onchain/token: the token is used to pay for storage/reads, for staking/delegation and for reward/penalty mechanics; the blockchain records the rules and the validation (challenge flow).

How it works (very briefly)

  1. The user does: creates an allocation (a storage contract) and selects a set of blobber providers to host the data.
  2. The system does: blobbers store the data, validators run integrity checks (challenges) and confirm correct storage.
  3. The user gets: storage/access to data; the ability to share encrypted files (per the project’s description).
  4. Where the blockchain is: onchain — the network’s transactions/smart contracts that manage allocations, challenges and the storage economy.
  5. Token role: payment for operations (write/read pools), staking on blobbers and distribution of rewards/penalties.

Quick links: AI thesis fit

Project passport

Field Value
Project name Züs
Also known as (aliases) 0chain, Zus Network, ZCN
Logo (logo) ../assets/516_0chain_logo.svg
Token symbol (ticker) ZCN
Category AI/Data | Infra
Primary chain (chain) Züs Network
Type Appchain
Network status mainnet
Consensus (consensus) PoS
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xb9ef770b6a5e12e45983c5d80545258aa38f3b78
Token model (token_type) utility (payments + staking + governance)
Max supply 400,000,000 ZCN
Issuance —
Tokenomics (tokenomics, brief) Clients lock tokens in write/read pools; there is staking/delegation and slashing/burn upon failed challenges (per the tokenomics).
Governance —
Admins/keys —
Audit —
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI data platform / AI agents
Use‑case (use_case) decentralized storage (S3-compatible) + data integrity
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 3 / evidence_score 2
Last verified 2026-02-11

General project overview

Züs positions itself as a blockchain‑based decentralized data storage system. In the documentation, the project describes an architecture where the blockchain subsystem (miners/sharders and smart contracts) observes the storage subsystem (blobbers/validators) and incentivizes correct storage via challenge mechanics and a token economy.

On the AI side, the project describes itself as a “secure AI data platform” and mentions “AI agents” as part of its high‑level positioning. Within this card, this is counted as AI intent (AI_0=1) until Tier‑1 artifacts appear that show a working AI component/demo/metrics.

Features/modules

  • Storage allocation model: the client selects a set of blobbers (k+m for erasure coding) and pays for storage for a term (per the tokenomics).
  • Challenge flow: validators check blobbers; failures lead to a penalty (slashing/burn) per the tokenomics description.
  • Züs Apps (interfaces): the documentation lists web applications as an interface to the system.

Typical scenarios

  • Scenario 1: a user creates an allocation → uploads data → gets storage/access to the files.
  • Scenario 2: a blobber provider stakes tokens → provides storage → receives a reward for correct storage.
  • Scenario 3: a validator participates in challenges → confirms the correctness of storage → receives validation rewards.

Getting started (wallet/network)

  • What you need: a wallet/keys to interact with the network and applications; a choice of blobbers for the allocation.
  • Network/chain: Züs Network (the storage system) + an ERC‑20 token on Ethereum (for part of the token layer).
  • Fees: depend on write/read operations and the selected providers (per the tokenomics).

Architecture/tech (non‑AI)

  • Components: blockchain subsystem (miners/sharders, smart contracts), storage subsystem (blobbers/validators), supporting nodes (0DNS/0Box etc.), SDK/CLI/webapps.
  • Participant roles: clients (storage/reads), blobbers (storage providers), validators (checks), miners/sharders (the blockchain layer).
  • Where logic runs: file storage — at the blobbers; checks/accounting/incentive rules — via the system with an onchain component (described in the docs).
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: payment for storage/reads via write/read pools; staking/delegation on blobbers; rewards and penalties.
  • Protocol necessity drivers: the token economy is used to align the incentives of providers and clients and for security mechanics (penalty/slashing).
  • Security/incentive mechanisms: challenge mechanics; upon failed challenges, part of the stake is slashed and burned (per the tokenomics).

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: yes (see links_*).
  • Incidents: —.
  • Threat model: risks of provider storage/availability; risks of errors in the incentive model; risks of bridges/the token layer (if used).

Project status and timeline

  • Current status: mainnet (per the description in the release documentation).
  • Key releases/milestones: —.
  • Roadmap: see links_*.

Ecosystem/integrations

  • Integrations: SDK/CLI/webapps (described in the docs).
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? in the Tier‑1 documentation Züs is described as a platform for AI data and mentions AI agents; no Tier‑1 demo/metrics/tech description of AI agents was found → we count it as AI intent.
  • What is truly onchain? the onchain component is described in Tier‑1 (miners/sharders, storage smart contract, challenge validation).
  • Why is a token needed? the token is used to pay for storage/reads and for staking/delegation with reward/penalty mechanics.
  • Red flags (based on the information found): if AI is mentioned only as marketing without a reproducible demo/metrics (AI_2/AI_3=0); it is important to separate the storage architecture (Tier‑1) from the claims about “AI agents”.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): The project positions itself as a secure AI data platform and mentions AI agents.
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs
  • Why sufficient / why not (one line): This is Tier‑1 intent/positioning; without a demo/metrics/architecture of AI agents we do not raise AI_1..AI_4.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): Not established (no specific Tier‑1 description of the tasks/behavior of AI agents and their role in the product).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The general phrase “AI agents” without specifics does not pass as AI_1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): AI demos/examples of AI agents at work are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No Tier‑1 “app surface” or tutorial specifically on AI agents was found.
  • 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): Quality metrics of the AI part were not found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of AI agents/model versions is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The system overview describes the storage architecture, but not an AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Züs Network
  • Addresses/identifiers: —
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/system-overview
  • Why sufficient / why not (one line): The Tier‑1 system overview describes the blockchain layer (miners/sharders) and the storage layer (blobbers/validators) as part of the network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: allocation contracts, challenge flow, reward/penalty (as part of the observed storage system).
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/system-overview ; https://docs.zus.network/zus-docs/tokenomics
  • Why sufficient / why not (one line): The documentation describes that the blockchain manages the rules and incentivizes/validates the storage subsystem.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without blockchain observation and challenge validation, the trustless verification of storage correctness and the network’s incentive mechanics break down.
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/system-overview ; https://docs.zus.network/zus-docs/tokenomics
  • Why sufficient / why not (one line): The BOSS architecture is tied to observing storage via the blockchain and to reward/penalty rules.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ZCN.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xb9ef770b6a5e12e45983c5d80545258aa38f3b78
  • Why sufficient / why not (one line): The Tier‑1 explorer confirms the token and max total 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): Clients pay with tokens for storage/operations via write/read pools.
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/tokenomics
  • Why sufficient / why not (one line): The tokenomics describes the cost model and write/read pools as the payment mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): There is staking/delegation; failed challenges lead to slashing and burning of part of the stake.
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/tokenomics
  • Why sufficient / why not (one line): The tokenomics describes staking/delegation and penalty/slashing/burn upon failures.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): The token is used for voting/governance (as a demand driver per the tokenomics).
  • Evidence: Tier‑1 — https://docs.zus.network/zus-docs/tokenomics
  • Why sufficient / why not (one line): The tokenomics states “Governance & Staking: Tokens are used for voting and securing the network”.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): Not established (no Tier‑1 analysis of the replaceability of the token with alternatives).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a separate analysis of replaceability we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.zus.network/zus-docs/system-overview BOSS architecture: blockchain subsystem + storage subsystem, the roles of miners/sharders/blobbers/validators and challenge validation.
Tier‑1 https://docs.zus.network/zus-docs/tokenomics Token economy: allocations, write/read pools, staking/delegation, challenge rewards and penalty (slashing/burn).
Tier‑1 https://docs.zus.network/zus-docs Tier‑1 AI intent: positioning as an AI data platform and a mention of AI agents.
Tier‑1 https://etherscan.io/token/0xb9ef770b6a5e12e45983c5d80545258aa38f3b78 Onchain fact: the Zus (ZCN) ERC‑20 token, max total supply 400,000,000.
Tier‑1 — No Tier‑1 source for claim “demos/examples of AI agents or a reproducible AI workflow” was found.

No comments to display

Back to top