Skip to main content

Moonchain

Moonchain (MCH) — 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).

Moonchain — an AI/Other / Infra project: a Layer‑2 (zkEVM) on top of BNB Chain with a focus on IoT/DePIN and AI use cases. The Tier‑1 documentation describes “AI data relaying”, an oracle system, and plans to launch AI models for network optimization; at the same time, a separate public repository/releases of the protocol core as a Tier‑1 artifact are not confirmed in the card (there is a GitHub organization/repositories, but without a specific mapping to the “AI component” per Tier‑1 sources).

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 L2 network (zkEVM) for dApps, with claimed IoT/DePIN scenarios and an “AI value layer”.
  • Who it’s for: developers and users of dApps/DePIN projects; network participants (nodes/staking) in the Moonchain ecosystem.
  • Why onchain/token: the MCH token is used as the network’s native token and, per the documentation, is involved in staking/nodes and the ecosystem economy.

How it works (very briefly)

  1. The user does: connects a wallet to Moonchain (mainnet/testnet) and interacts with dApps/bridges/network components.
  2. The system does: processes transactions in the zkEVM L2 environment and provides infrastructure services (RPC/explorer; planned — oracle/relaying).
  3. The user gets: execution of onchain operations and access to the network’s tools/ecosystem.
  4. Where the blockchain is: state/transactions — onchain on the Moonchain network; part of the “AI/DePIN” logic is described as offchain components that are relayed/verified and recorded onchain.
  5. Token role (if any): MCH — the native token (gas) and, per the documentation, is used in the staking/node mechanics.

Quick links: AI thesis fit

Project passport

Field Value
Project name Moonchain
Also known as (aliases) MCH
Logo (logo) ../assets/415_moonchain_logo.png
Token symbol (ticker) MCH
Category AI/Other | Infra
Primary chain (chain) Moonchain Mainnet
Type EVM
Network status mainnet
Consensus (consensus) L2 (zkEVM on BNB Smart Chain)
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (gas + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) the network’s native token; used for fees and participation in the network mechanics (per docs)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI data relaying + network intelligence
Use‑case (use_case) L2 for DePIN/AI dApps
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 2
Last verified 2026-02-11

General project overview

In its Tier‑1 documentation, Moonchain describes itself as an L2 solution (zkEVM) on top of BNB Chain and a “value layer for ZK & AI”, with an emphasis on scaling IoT/DePIN/AI scenarios. The documentation contains practical guides for connecting to the network (RPC, chain id, explorer), as well as materials on running a node (supernode) and a roadmap that mentions AI components (data relaying, oracle, network intelligence).

Features/modules

  • The Moonchain L2 network (mainnet/testnet) with an RPC/explorer (per docs).
  • Developer guides (network setup, running a node/supernode).
  • Roadmap components: AI data relaying, AI & data oracle system, internal network intelligence (per the roadmap).

Typical scenarios

  • Scenario 1: a developer adds the Moonchain RPC → deploys/tests a smart contract → uses the L2 for a dApp.
  • Scenario 2: an operator runs a supernode → syncs the network → monitors the state via a dashboard (per the guide).

Getting started (wallet/network)

  • What you need: an EVM wallet (for example, MetaMask) and MCH for fees on the Moonchain network.
  • Network/chain: Moonchain Mainnet (Chain ID 999888) or Hudson Testnet (Chain ID 177888) per the official RPC table.
  • Fees: network fees (gas) in MCH on the Moonchain network.

Architecture/tech (non‑AI)

  • Components: the L2 execution engine/nodes, RPC, explorer, bridges/infra (mentioned in the docs), dev guides.
  • Participant roles: dApp users; developers; node/supernode operators.
  • Where logic runs: onchain — L2 transactions/state; offchain — part of the DePIN/AI infrastructure and analytics, which can then be recorded/relayed onchain (per the roadmap description).
  • Dependencies: the base L1 — BNB Chain (as specified in the docs overview); external RPCs/providers and Docker/infrastructure for nodes.

Token/economics (expanded, no forecasts)

  • Token utility: the network’s native token (gas) and, per the node guide, participates in staking/supernode participation (the need for a stake for the proposer is mentioned).
  • Protocol necessity drivers: network fees and the conditions for node/validator participation.
  • Who pays fees: users/developers when transacting on the network.
  • Where fees go: not established per Tier‑1 sources.
  • Issuance/burn: not established per Tier‑1 sources.
  • Security/incentive mechanisms: staking for running a supernode/proposer (mentioned in the guide) and staking mechanics in the roadmap (without parameters).
  • Distribution and token issuance schedule: not established.
  • Treasury: not established.

Governance

  • Who makes decisions: — (not established per Tier‑1 sources; the roadmap mentions “Decentralize Network Governance” as a direction).
  • How protocol parameters change: via network/protocol and documentation updates (the process details are not established per Tier‑1 sources).
  • Where decisions are discussed/made: official channels (Docs/X/Telegram).
  • Keys/multisig: — (not established).

Security and incidents

  • Audits: — (not established per Tier‑1 sources).
  • Bug bounty: — (not established).
  • Incidents: — (not established).
  • Threat model: typical L2/zkEVM and node infrastructure risks (client/configuration errors, bridge/explorer/RPC risks, dependence on the base L1), as well as the risks of the claimed AI/DePIN modules (if data/computation remain offchain).

Project status and timeline

  • Current status: the mainnet and the Hudson testnet are described in the official RPC tables.
  • Key releases/milestones: — (not established per Tier‑1 sources).
  • Roadmap: see links_* (Roadmap 2025).

Ecosystem/integrations

  • Integrations: connection via RPC (MetaMask, etc.), explorer, guides for running nodes/supernodes.
  • Partners: the docs list ecosystem partners (the list is mostly marketing; requires selective double‑checking).
  • Where it’s actually used: development/testing of dApps on the Moonchain network and node operation (per the docs guides).

AI component of the project

  • What is real AI here? The documentation and roadmap describe AI scenarios (AI data relaying, AI & data oracle, internal AI models for network optimization), but without public metrics/versions/model architecture per Tier‑1 sources.
  • What is truly onchain? the Moonchain network (RPC/explorer) and transactions on the L2; the native MCH token as gas.
  • Why is a token needed? the network’s native token for fees and participation in the node/staking mechanics (per docs).
  • Red flags (based on the information found): AI‑washing — the absence of technical artifacts for the AI models; what to double‑check — open repositories/releases, staking/governance contract addresses, provable AI artifacts.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the docs/roadmap claim AI components and an AI direction for the network’s development.
  • Evidence: Tier‑1 — https://docs.mchain.ai/ ; https://docs.mchain.ai/resources/roadmap/
  • Why sufficient / why not (one line): this is Tier‑1 intent, but without proof of a specific working AI component/metrics.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): “what exactly the AI does” is described at the level of directions (relaying/oracle/optimization), but without verifiable implementation details.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/roadmap/
  • Why sufficient / why not (one line): not enough Tier‑1 detail to confidently assign 1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a demo of the AI component specifically is not established; there are documentation and network tools (RPC/explorer/guides).
  • Evidence: Tier‑1 — https://docs.mchain.ai/
  • Why sufficient / why not (one line): the presence of the network/guides does not prove a working AI demo artifact.
  • 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.mchain.ai/resources/roadmap/
  • Why sufficient / why not (one line): no quantitative AI quality metrics/benchmarks were found in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech description of the AI architecture/model versions is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/roadmap/
  • Why sufficient / why not (one line): the roadmap lists directions, but contains no technical specifications of the models.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Moonchain Mainnet (Chain ID 999888)
  • Addresses/identifiers: RPC https://rpc.mchain.ai ; Explorer https://explorer.mchain.ai/
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/rpc-configuration/
  • Why sufficient / why not (one line): there is a Tier‑1 RPC/Chain ID/Explorer table for the network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the L2 network (zkEVM) for executing transactions/smart contracts and ecosystem dApps.
  • Evidence: Tier‑1 — https://docs.mchain.ai/moonchain-design/chains-and-testnets/
  • Why sufficient / why not (one line): the docs describe the L2 network and its use by developers/users.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: as an L2 network, Moonchain uses the blockchain for execution and verifiability, but the “criticality” for a unique AI property is not proven by Tier‑1.
  • Evidence: Tier‑1 — https://docs.mchain.ai/
  • Why sufficient / why not (one line): Tier‑1 contains no formulation of the “replace the blockchain” test as a mandatory property of the product.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the network uses the native MCH token.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/rpc-configuration/
  • Why sufficient / why not (one line): the RPC table specifies Symbol = MCH for mainnet/testnet.
  • 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): MCH is used as the network’s native token (gas) for transactions.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/rpc-configuration/
  • Why sufficient / why not (one line): the presence of the MCH Symbol and the description of connecting to the network imply the use of MCH as the network currency.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): for running a supernode as a proposer, the need for a stake of 5,000 MCH is mentioned (and having MCH “as a fee”).
  • Evidence: Tier‑1 — https://docs.mchain.ai/testnet-tutorials/run-moonchain-supernode/
  • Why sufficient / why not (one line): the guide explicitly specifies a stake requirement for the node role.
  • Conflict note (if any): staking contracts/parameters are not given as addresses.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/roadmap/
  • Why sufficient / why not (one line): the roadmap mentions governance as a direction, but without clear token mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): no statement about the full replaceability of MCH without loss of functions was found in Tier‑1.
  • Evidence: Tier‑1 — https://docs.mchain.ai/resources/rpc-configuration/
  • Why sufficient / why not (one line): a conclusion about replaceability requires separate justification; the current Tier‑1 does not provide it.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.mchain.ai/ the basic description of Moonchain and the documentation sections
Tier‑1 https://docs.mchain.ai/resources/rpc-configuration/ RPC/Chain ID/Explorer for the Moonchain mainnet/testnet; the MCH symbol
Tier‑1 https://docs.mchain.ai/moonchain-design/chains-and-testnets/ Moonchain as an L2 on top of BNB Chain and instructions for connecting to the networks
Tier‑1 https://docs.mchain.ai/resources/roadmap/ the roadmap with AI data relaying / oracle / internal network intelligence
Tier‑1 https://docs.mchain.ai/testnet-tutorials/run-moonchain-supernode/ running a supernode and mentions of the stake requirement (5,000 MCH)
Tier‑2 https://www.coingecko.com/en/coins/moonchain aggregator (context/for reference)
Tier‑2 https://coinmarketcap.com/currencies/moonchain/ aggregator (context/for reference)

No comments to display

Back to top