Skip to main content

Multiverse

Multiverse — 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).

Multiverse — an AI/Data | Infra project on the Ethereum network, token (symbol: AI).

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 project that describes itself on the website as a decentralized platform for AI (including LLM/RAG/chatbots) and community participation in “knowledge/data”.
  • Who it’s for: developers/teams that want to build AI systems and use the platform’s resources/datasets.
  • Why onchain/token: the confirmed onchain artifact is an ERC‑20 token on Ethereum; the role of the token as a mandatory protocol mechanism is not established per Tier‑1.

How it works (very briefly)

  1. The user does: interacts with the platform (per the description on the website/in the whitepaper).
  2. The system does: provides infrastructure/resources around AI (LLM/RAG/chatbots) and community participation.
  3. The user gets: access to the platform’s resources/capabilities (details are not established per Tier‑1).
  4. Where the blockchain is: the onchain component is confirmed by the existence of an ERC‑20 token on Ethereum.
  5. Token role (if any): AI (ERC‑20); the token utility as a mandatory protocol mechanism is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Multiverse
Also known as (aliases) AI
Logo (logo) ../assets/732_multiverse_logo.svg
Token symbol (ticker) AI
Category AI/Data | 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 0xc91b523a59acc63a64f61fc7bbfb4bfc82dd25f2
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) platform for LLM/RAG/chatbots
Use‑case (use_case) AI platform + community resources
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Multiverse describes itself on the Tier‑1 website as a “decentralized platform for A.I.” and lists areas such as LLM, RAG and chatbots. Within this card, we record verifiable elements: the existence of public Tier‑1 project pages and the existence of an ERC‑20 token on the Ethereum network.

Features/modules

  • Claimed per the Tier‑1 website: an AI platform/resources for building models and community participation.
  • The ERC‑20 contract code is available per the Tier‑1 repository.

Typical scenarios

  • Scenario 1: a developer studies the whitepaper/documentation → evaluates the platform’s approach and capabilities.
  • Scenario 2: a user interacts with the token (transfer/storage) → transactions are observable in the Ethereum explorer.

Getting started (wallet/network)

  • What you need: access to the project’s website/materials; a wallet for EVM networks (for operations with the token).
  • Network/chain: Ethereum (for the token).
  • Fees: Ethereum network fees for token transactions.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token on Ethereum + the offchain part of the platform (details are not established per Tier‑1).
  • Participant roles: platform developers/users and token holders.
  • Where logic runs: the token — onchain (Ethereum); the product/platform — not established (probably offchain).
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (a Tier‑1 description of the mechanics is required).
  • Who pays fees: for token transactions, the sender pays fees (Ethereum gas).
  • Issuance/burn: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: typical token risks and offchain platform risks (details not established).

Project status and timeline

  • Current status: mainnet (the token on Ethereum).
  • Key releases/milestones: see the official repository’s commits (in links_*).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? an AI platform for building/using LLM/RAG/chatbots is claimed on the Tier‑1 website.
  • What is truly onchain? the confirmed onchain artifact is the AI ERC‑20 token on Ethereum.
  • Why is a token needed? the role of the token in the product mechanics is not established per Tier‑1 (a Tier‑1 description is required).
  • Red flags (based on the information found): absence of verifiable metrics/demos of the AI part; mixing marketing wording and Tier‑1 evidence.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described in Tier‑1 as the substance/purpose of the project, not just a “plan/intent”.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): This “intent” item adds no signal when AI is already claimed as an operating goal/positioning.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The website claims that the platform enables building LLM, RAG and chatbots.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): The Tier‑1 source describes the purpose of the AI part, but without metrics/architecture.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A public reproducible demo of the AI part is not recorded per Tier‑1.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): A specific verifiable “what you can touch” scenario is needed.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): No quantitative quality metrics for the AI part were found in the available Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI part is not established per Tier‑1.
  • Evidence: Tier‑1 — https://multiverse.ai/whitepaper
  • Why sufficient / why not (one line): Explicit architectural details/versions are needed; not recorded per Tier‑1 sources.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: token contract 0xc91b523a59acc63a64f61fc7bbfb4bfc82dd25f2
  • Evidence: Tier‑1 — https://etherscan.io/token/0xc91b523a59acc63a64f61fc7bbfb4bfc82dd25f2
  • Why sufficient / why not (one line): The existence of the token and an observable contract in the explorer confirms an onchain artifact.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: Tier‑1 confirmation of onchain logic of the product, other than the token, is not established.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): 1 requires a Tier‑1 description/addresses of protocol/logic contracts, not just a token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that a key property of the product breaks down without onchain.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, AI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xc91b523a59acc63a64f61fc7bbfb4bfc82dd25f2
  • Why sufficient / why not (one line): The token and its contract are observable in the Tier‑1 explorer.
  • 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): The use of the token as a mandatory payment for the service is not established per Tier‑1.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): 1 requires an explicit Tier‑1 payment/access mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Mechanisms of incentives/collateral/penalties with the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): Specific rules/contracts/documentation are needed.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): 1 requires an explicit governance process/documentation.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token without loss of meaning is not established per Tier‑1.
  • Evidence: Tier‑1 — https://multiverse.ai/
  • Why sufficient / why not (one line): There is insufficient data on the role of the token in the product.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://multiverse.ai/ The project’s AI positioning and claimed areas (LLM/RAG/chatbots).
Tier‑1 https://multiverse.ai/whitepaper Whitepaper (context and project claims).
Tier‑1 https://github.com/multiverseai/ERC20 Public ERC‑20 contract repository.
Tier‑1 https://etherscan.io/token/0xc91b523a59acc63a64f61fc7bbfb4bfc82dd25f2 The existence of the AI ERC‑20 token on Ethereum (contract/chain).
Tier‑2 https://www.coingecko.com/en/coins/multiverse Token profile on an aggregator (context; not proof).
Tier‑3 https://coinmarketcap.com/currencies/multiverse/ Token profile on an aggregator (context; not proof).

No comments to display

Back to top