Skip to main content

Zypher Network

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

Zypher Network — an AI/Agents / ZK / Infra project that positions itself as a “decentralized audit layer for AI agents”: verification of prompt integrity and of execution/results (via ZK proofs), a security browser for auditing, a proof mining network and its own “Zytron Chain” (per the website/docs). Token on BNB Smart Chain: POP.

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/an “audit layer” for AI agents: a protocol and tools that help verify the correctness of prompt/response and record proofs.
  • Who it’s for: AI agent developers and users who need verifiability of interactions; game/agent applications that want ZK verification.
  • Why onchain/token: onchain is needed for public verification and accounting of proofs/state; the token — for the incentive mechanics of proof mining and participation in the economy.

How it works (very briefly)

  1. The user does: launches an AI agent/application or interacts with it.
  2. The system does: records/commits prompts and (per the model) verifies their integrity and results via a ZK pipeline/proofs.
  3. The user gets: verifiability (audit trail), risk labels/anomaly tagging in the security browser, and/or a confirmed result (per the claim).
  4. Where the blockchain is: onchain commits/reports/certificates and accounting of proof verifications; the POP token is on BNB Chain.
  5. Token role (if any): economic incentives for prover/miner nodes and participants (proof mining), as well as DAO governance (in the roadmap).

Quick links: AI thesis fit

Project passport

Field Value
Project name Zypher Network
Also known as (aliases) Zypher, Zypher Games
Logo (logo) ../assets/258_zypher-network_logo.svg
Token symbol (ticker) POP
Category AI/Agents | Infra | ZK
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) — (not found in the extracted Tier‑1)
Project status (status) active
Token (standard) BEP-20
Token contract 0xA3cfB853339b77F385B994799B015cB04b208Fe6
Token model (token_type) utility (governance)
Max supply 10,000,000,000 POP (per BscScan)
Issuance capped (ERC20Capped 10e9) + mint under the owner (per the contract on BscScan)
Tokenomics (tokenomics, brief) POP is a BSC token with a 10B cap; the utility is tied to proof mining and DAO governance (per the roadmap/website).
Governance Zypher DAO (claimed in the roadmap)
Admins/keys owner‑mint is present (per the contract); multisig/timelock details not extracted
Audit there is a link to an audit report (PDF) in this card
Bug bounty — (not found in the extracted Tier‑1)
Team (team) — (not found in the extracted Tier‑1)
Funding (investors/funding) — (not found in the extracted Tier‑1)
AI component (ai_component) prompt/agent audit, security browser
Use‑case (use_case) trustless audit layer for AI agents
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 3 / 1 / 3
Last verified 2026-02-06

General project overview

On its website, Zypher Network describes itself as a “decentralized audit layer for AI agents” and offers a set of components for the verifiability of agent interactions and results: Proof of Prompt (cryptographic verification of prompt integrity with ZK proofs), AI Security Browser (user‑side auditing and risk labels), Proof Mining (decentralized proving infrastructure) and Zytron Chain (an AI rollup/chain for ZK workloads). Separately, the docs describe a proving network for ZK games, where miners generate proofs and receive rewards.

Features/modules

  • Proof of Prompt: a protocol for verifying the integrity of prompts (ZK approach, onchain commits) — per the website.
  • AI Security Browser: auditing of interactions, risk labels, anomaly tagging — per the website.
  • Proof Mining network: a network of prover/miner nodes for generating ZK proofs and rewards — per the website/docs.
  • Zytron Chain: specialized chain/rollup infrastructure for AI/ZK computations — per the website.

Typical scenarios

  • Scenario 1: a developer integrates Proof of Prompt → gets verifiability of the agent’s prompts/responses (per the description).
  • Scenario 2: a user checks agent interactions via the Security Browser → sees risk labels/anomalies (per the description).
  • Scenario 3: a prover/miner generates ZK proofs → receives rewards (per the mining docs).

Getting started (wallet/network)

  • What you need: an EVM wallet for BNB Chain (if POP is needed); to participate in proof mining — launching a prover/miner per the documentation.
  • Network/chain: BNB Smart Chain (POP token).
  • Fees: BNB Chain fees for onchain operations; the computational load of proof generation is offchain, on the prover/miner side.

Architecture/tech (non‑AI)

  • Components: onchain contracts/modules for commits/accounting, the prover/miner network (offchain proof generation), web interfaces (security browser), the POP token (BSC).
  • Participant roles: users/developers, prover/miner operators, governance participants (DAO — in the roadmap).
  • Where logic runs: ZK proof generation — offchain; verification/accounting/publication — onchain + applications on top.
  • Dependencies: BNB Chain; ZK provers and integrations (external provers are mentioned in the roadmap).

Token/economics (expanded, no forecasts)

  • Token utility: incentivizing participants in proof mining and onchain programs; DAO governance is described in the roadmap as a future component.
  • Protocol necessity drivers: for the coordination/incentives of the prover/miner ecosystem (proof generation and verification).
  • Who pays fees: users/participants pay network gas (BNB) for onchain transactions.
  • Where fees go: network fees — to the BNB Chain validators; the protocol‑level distribution of rewards/fees is not disclosed in the extracted Tier‑1.
  • Issuance/burn: the token is capped at 10B and has a mint function held by the owner (per the contract on BscScan); burn is available (ERC20Burnable).
  • Security/incentive mechanisms: proof mining is described as the reward mechanics for prover/miner; details of slashing/penalties are not disclosed.
  • Distribution and token issuance schedule: — (not found in the extracted Tier‑1)
  • Treasury: — (not found in the extracted Tier‑1)

Governance

  • Who makes decisions: Zypher DAO is claimed in the roadmap (Q4 2025), but details are not given in the extracted fragments.
  • How protocol parameters change: via releases and updates (GitHub/docs/whitepaper/roadmap).
  • Where decisions are discussed/made: public channels (X/Discord/Telegram) and the documentation.
  • Keys/multisig: the token contract contains an owner‑mint; key management details are not disclosed.

Security and incidents

Project status and timeline

  • Current status: the product is active (website/docs); the roadmap publishes plans for 2025–2026.
  • Key releases/milestones: roadmap: AI Security Browser beta (2025 Q3), DAO launch (2025 Q4), expansion of mining nodes/verifications (2026 Q1).
  • Roadmap: https://wiki.zypher.network/general-introduction/zypher-101-roadmap

Ecosystem/integrations

  • Integrations: proof mining/prover tools; “Featured DAIpps” are listed on the website as example applications.
  • Partners: — (backers are listed on the website without details, not extracted in the text fragment)
  • Where it’s actually used: examples on the website (z2048, Crypto Rumble, Zypher Girl, Alpha Girl, etc.) — as a showcase of the ecosystem.

AI component of the project

  • What is real AI here? the focus is on AI agents and their interactions; the project does not claim its own LLM/model as the core, but builds a trust/audit layer for agent systems (prompts/outputs).
  • What is truly onchain? commits/reports/certificates and the POP token on BNB Chain; validation/accounting of proofs.
  • Why is a token needed? the incentive mechanics of proof mining and future governance (DAO) per the roadmap.
  • Red flags (based on the information found): AI‑washing — it is important to distinguish “auditing AI agents” from “creating AI models”; token‑washing — owner‑mint and undisclosed tokenomics; onchain‑washing — part of the ZK computations is inevitably offchain.

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 medium 1
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 project builds an audit layer for AI agents (prompt integrity / verification / security browser), not its own model; the AI object is agent applications.
  • Evidence: Tier‑1 — https://zypher.network/
  • Why sufficient / why not (one line): this describes the role of AI agents and the purpose of the system, but without technical details of the “agent brain”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): the extracted Tier‑1 contain no replicable demo that shows an end‑to‑end check of the prompts/outputs of a specific agent.
  • Evidence: Tier‑1 — https://zypher.network/ ; https://wiki.zypher.network/general-introduction/zypher-101-roadmap
  • Why sufficient / why not (one line): the website/roadmap describe the product, but without a step‑by‑step demo in the extracted content.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: — (not found)
  • Context (version/date/how measured): — (not found)
  • Evidence: Tier‑1 — https://zypher.network/
  • Why sufficient / why not (one line): the extracted Tier‑1 contain no accuracy/quality metrics for the audit layer or “security scoring” indicators.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the extracted material contains a high‑level description of PoP/the audit layer, but no technical specifications (architecture, versions, limitations).
  • Evidence: Tier‑1 — https://zypher.network/ ; https://wiki.zypher.network/general-introduction/zypher-101-roadmap
  • Why sufficient / why not (one line): the description is insufficient for technical confirmation.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: 0xA3cfB853339b77F385B994799B015cB04b208Fe6
  • Evidence: Tier‑1 — https://bscscan.com/token/0xA3cfB853339b77F385B994799B015cB04b208Fe6
  • Why sufficient / why not (one line): BscScan confirms the contract, the name/ticker and the max total supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the roadmap describes “on-chain reports & certifications” and a marketplace of certificates, i.e. onchain artifacts other than the token.
  • Evidence: Tier‑1 — https://wiki.zypher.network/general-introduction/zypher-101-roadmap
  • Why sufficient / why not (one line): the existence of planned/claimed onchain artifacts is confirmed by the roadmap.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the public verifiability and immutability of the audit reports/certificates and verifications are lost; trust shifts to a centralized service.
  • Evidence: Tier‑1 — https://wiki.zypher.network/general-introduction/zypher-101-roadmap ; https://zypher.network/
  • Why sufficient / why not (one line): the design claims onchain reports/certificates and large‑scale verifications, where public verifiability is the core property.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, POP, on BNB Smart Chain.
  • Evidence: Tier‑1 — https://bscscan.com/token/0xA3cfB853339b77F385B994799B015cB04b208Fe6
  • Why sufficient / why not (one line): BscScan shows the token and its parameters.
  • 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): mandatory payment for services in POP is not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://zypher.network/
  • Why sufficient / why not (one line): the extracted text of the website contains no specific payment rules/fee model.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the token economy is claimed around proof mining (incentives for prover/miner nodes).
  • Evidence: Tier‑1 — https://zypher.network/ ; https://wiki.zypher.network/general-introduction/zypher-101-roadmap
  • Why sufficient / why not (one line): the sources describe mining/nodes and the scale of verifications, implying an incentive layer, although specific formulas are not given.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the roadmap claims the launch of Zypher DAO and governance for PoP mining/certifications.
  • Evidence: Tier‑1 — https://wiki.zypher.network/general-introduction/zypher-101-roadmap
  • Why sufficient / why not (one line): this confirms the governance intent, but does not show implemented onchain governance today.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): in the absence of detailed tokenomics and a fee model, the token looks potentially replaceable for part of the functions (audit/verifications), although incentives for mining are the expected use-case.
  • Evidence: Tier‑1 — https://zypher.network/
  • Why sufficient / why not (one line): the extracted Tier‑1 contain no strict proof that “without the token the system does not work”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://zypher.network/ the “audit layer for AI agents” positioning and the description of the modules (PoP, Security Browser, Proof Mining, Zytron).
Tier‑1 https://wiki.zypher.network/general-introduction/zypher-101-roadmap plans for the AI security browser/certificates/DAO/scale of verifications.
Tier‑1 https://bscscan.com/token/0xA3cfB853339b77F385B994799B015cB04b208Fe6 confirmation of the POP token, the contract and the 10B cap.
Tier‑1 https://scalebit.xyz/reports/20250813-Zypher-Network-Token-Final-Audit-Report.pdf the existence of an audit report (token) via the link in this card.

No comments to display

Back to top