METAVERSE / AIPool
METAVERSE / AIPool (METAV) — 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).
METAVERSE — a token/concept that public aggregators describe as an “AI‑driven coin (aICO)” launched by an AI agent; onchain — an SPL token on the Solana network (symbol: METAV). No verifiable Tier‑1 materials about the product were found / confirmed (see Evidence).
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 SPL token on the Solana network (mint:
HCgvbV...3qkeN9), which public descriptions position as “aICO / AI‑agent‑launched”. - Who it’s for: traders/the community around the token; potentially participants in “AI‑governed” mechanics (not confirmed by Tier‑1).
- Why onchain/token: the onchain existence of the token is confirmed by the explorer; useful onchain logic of the product is not confirmed by Tier‑1.
How it works (very briefly)
- The user does: performs operations with the METAV token in the Solana ecosystem.
- The system does: records token transfers onchain.
- The user gets: token balances/transfers on Solana.
- Where the blockchain is: the token and its transactions are onchain (Solana).
- Token role: per Tier‑1 sources, only the fact of the token’s existence is confirmed; the utility role is not verified.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | METAVERSE / AIPool |
| Also known as (aliases) | METAV, aipool_tee (mention in public descriptions) |
| Logo (logo) | — |
| Token symbol (ticker) | METAV |
| Category | AI/Agents |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | 2024 (per public aggregators; no Tier‑1 confirmation of the date found) |
| Project status (status) | active (the token exists onchain) |
| Token (standard) | SPL |
| Token contract | HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9 |
| Token model (token_type) | unknown |
| Max supply | 1,000,000,000 METAV (per public aggregators; no Tier‑1 confirmation of the supply found) |
| Issuance | fixed (not confirmed by Tier‑1) |
| Tokenomics (tokenomics, brief) | No Tier‑1 sources on tokenomics found / not confirmed |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | "AI agent in TEE" |
| Use‑case (use_case) | token / community asset |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | 0 / 1 / 0 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://aipool.tech |
| Docs | https://ai-pool.gitbook.io/docs |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://explorer.solana.com/address/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9?cluster=mainnet |
| X | https://twitter.com/aipool_tee |
| Discord | https://discord.com/invite/ai16z |
| Telegram | — |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/metaverse |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/aipool/ |
General project overview
According to its profile in public aggregators, the token is described as an “AI‑driven coin offering (aICO)” created by an AI agent allegedly running in a Trusted Execution Environment (TEE), with automatic creation of a liquidity pool, etc. However, Tier‑1 sources that would confirm these claims (official website/docs/repository) were not found / unavailable at the time of the check. Therefore, this card below records only what can be confirmed directly: the existence of an SPL token on the Solana network at the specified mint address.
Features/modules
- Onchain asset: an SPL token (mint) on Solana.
- AI/TEE mechanics: claimed in external sources, but there are no Tier‑1 confirmations.
Typical scenarios
- Scenario 1: a user transfers the METAV token → the transfer is recorded onchain on Solana.
- Scenario 2: a user trades the token on DEXs/aggregators → the holder distribution changes (not analyzed; Tier‑1 sources on the DEX mechanics were not collected).
Getting started (wallet/network)
- What you need: a Solana wallet.
- Network/chain: Solana mainnet.
- Fees: Solana fees (SOL) for transactions.
Architecture/tech (non‑AI)
- Components: an SPL token (mint) on the Solana network; the project’s public pages (website/X/Discord). Other components (protocol/smart contracts/client/product backend) are not confirmed by Tier‑1 sources.
- Participant roles: token holders; Solana users performing transfers/swaps of the token.
- Where logic runs: the confirmed logic is onchain accounting of balances/transfers of the SPL token on Solana; the claims about “AI agent / TEE / aICO” remain unverifiable without Tier‑1.
- Dependencies: Solana (wallets/RPC/explorer); DEXs/aggregators (as trading infrastructure, without a Tier‑1 link to the product).
Token/economics (expanded, no forecasts)
- Token utility: not confirmed by Tier‑1 sources.
- Protocol necessity drivers: not established (other than the fact of the token’s existence).
- Who pays fees: Solana fees (SOL) are paid by users performing onchain operations.
- Where fees go: Solana fees go to the validators of the Solana network (as L1 mechanics), not to the “project’s protocol”.
- Issuance/burn: not confirmed by Tier‑1 sources (other than the onchain fact of the SPL mint’s existence).
- Security/incentive mechanisms: not confirmed by Tier‑1 sources.
- Distribution and token issuance schedule: not confirmed by Tier‑1 sources.
- Treasury: not confirmed by Tier‑1 sources.
Governance
- Who makes decisions: not established / not confirmed by Tier‑1.
- How protocol parameters change: not established / not confirmed by Tier‑1.
- Where decisions are discussed/made: public channels (Website/X/Discord), but no formal Tier‑1 governance artifacts were found.
- Keys/multisig: not established / not confirmed by Tier‑1.
Security and incidents
- Audits: no Tier‑1 audit report(s) found.
- Bug bounty: no Tier‑1 bug bounty program found.
- Incidents: no Tier‑1 public post‑mortems/incidents found.
- Threat model: per the current Tier-1 sources, the claims about AI/TEE are not confirmed; the necessity of the token is also not disclosed through Tier-1 utility; in addition, the standard risks of an SPL token remain (phishing/fake tokens/liquidity/DEX risks).
Project status and timeline
- Current status: the token exists on Solana mainnet.
- Key releases/milestones: no Tier‑1 release notes/changelog found.
- Roadmap: no Tier‑1 roadmap found.
Ecosystem/integrations
- Integrations: Solana wallets and DEXs/aggregators (as trading infrastructure for the SPL token).
- Partners: not confirmed by Tier‑1.
- Where it’s actually used: not confirmed by Tier‑1 (other than onchain transfers of the token).
AI component of the project
- What is real AI here? It cannot be confirmed per Tier‑1 sources: the official materials are unavailable/time out.
- What is truly onchain? The fact of an SPL token on Solana at the mint address.
- Why is a token needed? The utility is not confirmed by Tier‑1; at the moment, only the existence of the token is confirmed.
- Red flags (based on the information found): AI‑washing — high risk (AI claims without Tier‑1); token‑washing — possible (no Tier‑1 on utility); double‑check: the website/docs/repository/contract metadata, if they appear.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | low | 0 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): Tier‑1 roadmap/docs with AI claims are not established per the available sources.
- Evidence: Tier‑1 — —
- Evidence (Tier‑3, reference): https://coinmarketcap.com/currencies/aipool/
- Why sufficient / why not (one line): without Tier‑1 this does not count as confirmation.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): the description “AI agent / TEE / aICO” is present in aggregators, but is not confirmed in Tier‑1.
- Evidence: Tier‑3 — https://coinmarketcap.com/currencies/aipool/
- Why sufficient / why not (one line): Tier‑3 does not raise the AI score.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No Tier‑1 demo/repository/proofs of AI logic execution found / confirmed.
- Evidence: Tier‑1 — —
- Evidence (Tier‑3, reference): https://coinmarketcap.com/currencies/aipool/
- Why sufficient / why not (one line): absence of a Tier‑1 demo.
- 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): metrics are not published in Tier‑1 sources (not found).
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a technical description of “TEE/AI agent” is not available/not found in Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without docs/a repository the architecture cannot be verified.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana mainnet
- Addresses/identifiers: HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9
- Evidence: Tier‑1 — https://solscan.io/token/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9
- Why sufficient / why not (one line): solscan is an explorer; it records the token’s mint address.
- Conflict note (if any): the page content is dynamic, but the URL and the token identifier are fixed.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not confirmed (other than the existence of the token).
- Evidence: Tier‑1 — https://solscan.io/token/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9
- Why sufficient / why not (one line): there are no Tier‑1 materials on contracts/the protocol other than the token explorer.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no Tier‑1 justification that onchain is critical for the product was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without Tier‑1 docs the test cannot be performed.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the METAV token exists (SPL mint).
- Evidence: Tier‑1 — https://solscan.io/token/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9
- Why sufficient / why not (one line): the explorer confirms the existence of the token.
- 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): there is no Tier‑1 confirmation that the token is used as payment for a service.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): —
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentives/collateral/penalties with the token are not confirmed by Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): —
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance with the token is not confirmed by Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): —
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): due to the absence of a Tier‑1 description of the utility, the replaceability of the token cannot be assessed.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): —
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://explorer.solana.com/address/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9?cluster=mainnet | Onchain fact: the SPL mint address of the METAV token on Solana mainnet |
| Tier‑1 | — | Tier‑1 sources on the AI claims/product (official website/docs/repository) not found / unavailable |
| Tier‑2 | https://solscan.io/token/HCgvbV9Qcf9TVGPGKMGbVEj8WwwVD6HhTt5E2i3qkeN9 | Navigation through onchain data (third‑party explorer) |
| Tier‑3 | https://coinmarketcap.com/currencies/aipool/ | aggregated description (AI agent/TEE/aICO), the METAV ticker, claimed supply of 1B |
No comments to display
No comments to display