Skip to main content

Mind Network

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

Mind Network — an AI/Other | Infra project that positions itself as FHE infrastructure for the “Fully Encrypted Web” and encrypted computation for AI/agents. Token: FHE (ERC‑20).

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: FHE‑based privacy infrastructure (computation over encrypted data), oriented toward AI/agents and web3 payments/compliance without disclosing data.
  • Who it’s for: developers of AI agents/protocols who need private data processing and confidential settlement/payments.
  • Why onchain/token: onchain records settlement/state and makes it possible to “verify without disclosure”; the $FHE token is used for staking/agent activation, governance and payment for computation/utility (per docs).
  • What you can actually touch (Tier‑1): x402z.mindnetwork.xyz (testnet flow “prepare confidential assets”) and dapp.mindnetwork.xyz (delegation/voting/vFHE).

How it works (very briefly)

  1. The user/agent does: initiates an action where confidentiality matters (payment/computation/verification) or connects to Mind Network products.
  2. The system does: uses FHE to process/validate values in encrypted form (including for x402z A2A payments based on ERC‑7984).
  3. The user gets: a verifiable result without disclosing amounts/balances/strategy (as claimed).
  4. Where the blockchain is: the token contract and protocol states/settlement onchain (EVM); products such as x402z/dapp interact with the onchain layer.
  5. Token role: staking/activation and reward cycles, governance, payment for computation and access to utility (per docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Mind Network
Also known as (aliases) MindNetwork | $FHE
Logo (logo) ../assets/47_mind-network_logo.svg
Token symbol (ticker) FHE
Category AI/Other | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xd55C9fB62E176a8Eb6968f32958FeFDD0962727E
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance fixed cap
Tokenomics (tokenomics, brief) Initial circulating supply 24.9% (per tokenomics)
Governance DAO (MindDAO; per docs)
Admins/keys multisig + timelock (per docs)
Audit yes (audit restake; per docs)
Bug bounty —
Team (team) —
Funding (investors/funding) $12.5M funding (per docs)
AI component (ai_component) FHE encrypted AI computation + HTTPZ
Use‑case (use_case) confidential A2A payments + encrypted compute
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

In its documentation, Mind Network describes itself as Fully Homomorphic Encryption (FHE) infrastructure for the “Fully Encrypted Web”: the idea is that data remains encrypted not only in transit (as in HTTPS) but also during computation/validation (the HTTPZ/zero‑trust paradigm). This is presented as a base privacy layer for AI/agents, DeFi and other web3 scenarios.

The product layer includes:

  • x402z — a “privacy‑first payment protocol” for agent‑to‑agent payments, which attempts to combine blockchain verification with confidentiality (FHE + ERC‑7984).
  • dApp for participation in the ecosystem (delegation/voting/vFHE, CitizenZ flows).
  • a set of SDKs/repositories and “MindChain / AgenticWorld” as a direction for “FHE protected agents” and encrypted computation.

Features/modules

  • HTTPZ (Tier‑1 docs): a zero‑trust approach to the internet protocol with computation over encrypted data.
  • x402z (Tier‑1 docs + dApp): confidential A2A payments (402 gateway → encrypted instruction → FHE validation → settlement) based on FHE and ERC‑7984.
  • FHE / confidential token standard (Tier‑1): mention of collaboration with Zama and the ERC‑7984 standard for “confidential settlement”.
  • FHEBridge / Restake / governance tools (Tier‑1 docs): security blocks (audits), multisig/timelock and tokenomics.
  • Open‑source ecosystem (Tier‑1 GitHub): a set of repositories/SDKs for FHE and integrations.

Typical scenarios

  • Scenario 1 (A2A payments): an agent receives “402 Payment Required” → forms an encrypted payment instruction → the network validates/executes the transfer without disclosing the amount/balance (per x402z docs).
  • Scenario 2 (developer integration): a developer uses the x402z/HTTPZ SDK/documentation → adds private settlement/payments to an agent service.
  • Scenario 3 (staking/governance): a participant stakes/delegates $FHE/vFHE → participates in hub votes/ecosystem activities.

Getting started (wallet/network)

  • What you need: an EVM wallet; for the x402z demo flow — test assets (Sepolia ETH + TestUSDC) and the x402z interface; for the dApp — a wallet connection and participation in vFHE/votes.
  • Network/chain: Ethereum (per the contract explorer); BNB Smart Chain and MindChain are also mentioned in the tokenomics.
  • Fees: gas of EVM networks; the x402z flow includes “encrypt/convert” actions and interaction with contracts (per the UI).

Architecture/tech (non‑AI)

  • Components: the $FHE token (ERC‑20), web dApps (x402z, dapp), the FHE validation network/infrastructure, SDKs/repositories, the governance layer (multisig/timelock per docs).
  • Participant roles: users/developers, AI agents, validators/operators of the FHE infrastructure, stakers/delegators.
  • Where logic runs: cryptography/FHE computation and validation — part of the offchain/infrastructure; settlement/contracts/accounting — onchain (EVM).
  • Dependencies: the Zama FHE stack (as a partner/compatibility), EVM networks (Ethereum/BNB are mentioned), web interfaces and the open‑source ecosystem.

Token/economics (expanded, no forecasts)

  • Token utility: staking (agent activation), governance (MindDAO), payment for private computation, rewards and access to utility (per the $FHE docs).
  • Protocol necessity drivers: the docs directly list what $FHE “powers” (activate agents, pay for computation, governance, cross‑chain value flow).
  • Who pays fees: users/agents who perform onchain actions and/or pay for computation; market participants — gas in the respective networks.
  • Where fees go: — (not explicitly extracted as Tier‑1).
  • Issuance/burn: total supply 1B; no inflation model is specified (fixed cap).
  • Security/incentive mechanisms: staking/reward cycles and distribution by category (per tokenomics).
  • Distribution and token issuance schedule: an allocation table + vesting (airdrop/community/investors/team/treasury, etc.), initial circulating supply 24.9% (Tier‑1).
  • Treasury: Treasury 10% (per tokenomics); control details — via governance/multisig/timelock (links in the docs).

Governance

  • Who makes decisions: MindDAO (per the $FHE docs); some critical operations — via multisig/timelock (per the Security & Privacy docs).
  • How protocol parameters change: via governance processes/proposals and onchain governance (within the dApp/hubs).
  • Where decisions are discussed/made: the dApp “Vote to Earn / Vote On Hubs” as the entry point (Tier‑1); other venues — not recorded.
  • Keys/multisig: the docs have a Multi‑Sig & Timelock section (Tier‑1).

Security and incidents

  • Audits: audits of the Restaking contracts have been published (Offside/CertiK; links to PDFs on GitHub) — Tier‑1.
  • Bug bounty: — (no Tier‑1 found).
  • Incidents: — (not established).
  • Threat model: correctness of the FHE cryptography/implementations, trust in the validation network infrastructure, governance key risks (multisig/timelock), bridge/interoperability risks.

Project status and timeline

  • Current status: the website and docs are public; x402z and the dApp are available; the $FHE token is deployed on EVM (Tier‑1).
  • Key releases/milestones: x402z announced as a product (there is a docs page; January 2026 in the website news).
  • Roadmap: — (not listed in links_*; not extracted as Tier‑1).

Ecosystem/integrations

  • Integrations: Zama (FHE), ERC‑7984 (confidential token standard), the x402z/dApp/bridge products; open‑source repositories/SDKs (Tier‑1).
  • Partners: the docs/website list investors/credits (Binance/Chainlink and others); partnership details require separate verification.
  • Where it’s actually used: private agent payments (x402z) and ecosystem voting/staking flows (dApp).

AI component of the project

  • What is real AI here? Mind Network positions itself as FHE infrastructure for AI computation on encrypted data and AI agent scenarios (agent economy). This is more of an AI‑security/compute infra than an “own model”.
  • What is truly onchain? The $FHE token contract (ERC‑20), as well as onchain accounting/settlement for the products (x402z/dApp) — per the Tier‑1 description.
  • Why is a token needed? Per the docs, $FHE is needed for staking (agent activation), governance (MindDAO), rewards and payment/utility for private computation.
  • Red flags (based on the information found): the difficulty of verifying the “FHE validation network” for an external observer (what exactly is executed and where), bridge/interop risks, governance key risks (multisig/timelock), mixing the “AI‑agents economy” with the fact that there are no AI quality metrics.

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity high 3
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 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Mind Network describes itself as infrastructure that enables AI computation on encrypted data (FHE) and private agent computation/payments.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs, https://www.mindnetwork.xyz/
  • Why sufficient / why not (one line): Tier‑1 directly points to AI computation as the target application area of FHE.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there are public interfaces of x402z (testnet flow for preparing ConfUSDC) and the dApp (vFHE/delegate/vote) that demonstrate the product flows.
  • Evidence: Tier‑1 — https://x402z.mindnetwork.xyz, https://dapp.mindnetwork.xyz, https://docs.mindnetwork.xyz/minddocs/product/x402z
  • Why sufficient / why not (one line): these are reproducible “what you can touch” artifacts related to the AI/agent economy.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs
  • Why sufficient / why not (one line): Tier‑1 has no formal benchmarks of the “quality of AI solutions/models” as part of the protocol.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the docs describe the x402z stack (402 gateway → encrypted instruction → FHE validation → settlement) and the basic HTTPZ architecture; there are open‑source repositories/SDKs.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/product/x402z, https://docs.mindnetwork.xyz/minddocs/background/httpz, https://github.com/mind-network
  • Why sufficient / why not (one line): there is a technical description and code artifacts, albeit without AI metrics.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: token FHE (ERC‑20): 0xd55C9fB62E176a8Eb6968f32958FeFDD0962727E
  • Evidence: Tier‑1 — https://etherscan.io/token/0xd55C9fB62E176a8Eb6968f32958FeFDD0962727E
  • Why sufficient / why not (one line): the onchain fact of the token/contract is verifiable in the explorer.
  • Conflict note (if any): the tokenomics lists the same address also for BNB Smart Chain and MindChain.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: x402z settlement/accounting via the confidential token standard (ERC‑7984) and the dApp staking/delegate/voting flows (vFHE).
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/product/x402z, https://dapp.mindnetwork.xyz
  • Why sufficient / why not (one line): this describes an onchain function beyond simply “there is a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain settlement/verification, the claimed “verifiable privacy” (validation of a transfer/values without disclosure) and the public audit trail are lost.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/product/x402z, https://www.mindnetwork.xyz/
  • Why sufficient / why not (one line): the value of x402z is tied to verifiable onchain settlement while preserving confidentiality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, $FHE (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xd55C9fB62E176a8Eb6968f32958FeFDD0962727E
  • Why sufficient / why not (one line): the onchain fact of the token is verifiable.
  • 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 indicate payment for computation/utility in the ecosystem via $FHE (“paying for computation secured by FHE”).
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/governance/usdfhe
  • Why sufficient / why not (one line): Tier‑1 explicitly lists the payment function of the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): staking $FHE is used to activate AI agents and for reward cycles; the tokenomics describes distribution and incentives.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/governance/usdfhe, https://docs.mindnetwork.xyz/minddocs/governance/tokenomics
  • Why sufficient / why not (one line): Tier‑1 records staking and reward logic at the level of the token’s purpose.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the tokenomics describes $FHE as a “native utility and governance token”, and the $FHE docs mention participation in MindDAO/Hub proposals.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/governance/tokenomics, https://docs.mindnetwork.xyz/minddocs/governance/usdfhe
  • Why sufficient / why not (one line): Tier‑1 explicitly links the token to governance.
  • 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; there is no strict comparison with alternatives.
  • Evidence: Tier‑1 — https://docs.mindnetwork.xyz/minddocs/governance/tokenomics
  • Why sufficient / why not (one line): the presence of utility is not equal to proof of irreplaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.mindnetwork.xyz/minddocs Definition of the project: FHE infra for the fully encrypted web and AI computation; HTTPZ as a concept.
Tier‑1 https://www.mindnetwork.xyz/ Product positioning: confidential payment infra for the AI agent economy, x402z overview, links to dApps.
Tier‑1 https://docs.mindnetwork.xyz/minddocs/product/x402z x402z: FHE + ERC‑7984, workflow “402 → encrypted instruction → FHE validation → settlement”.
Tier‑1 https://x402z.mindnetwork.xyz Public x402z interface (testnet flow for preparing ConfUSDC).
Tier‑1 https://dapp.mindnetwork.xyz Public dApp (delegate/vote/vFHE) as a reproducible product flow.
Tier‑1 https://docs.mindnetwork.xyz/minddocs/governance/tokenomics Tokenomics: supply 1B, allocation, vesting, governance/utility purpose, contracts by network.
Tier‑1 https://docs.mindnetwork.xyz/minddocs/governance/usdfhe $FHE: what the token “powers” (staking/compute/governance/cross-chain).
Tier‑1 https://etherscan.io/token/0xd55C9fB62E176a8Eb6968f32958FeFDD0962727E Onchain facts of the FHE ERC‑20 token (contract, max supply).
Tier‑1 https://docs.mindnetwork.xyz/minddocs/security-and-privacy/audit-restake Tier‑1: links to audit PDFs (Offside/CertiK) for the restaking contracts.
Tier‑1 https://github.com/mind-network Tier‑1: open‑source repositories/SDKs and development activity.
Tier‑2 https://mindnetwork.medium.com/ Context/publications (not evidence).
Tier‑3 — —

No comments to display

Back to top