Skip to main content

Moemate (MATES)

Moemate (MATES) — 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).

Moemate (MATES) — an AI/Agents project on the Solana network, token (symbol: —).

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 application/platform for AI agents (per the Tier‑1 website and repository).
  • Who it’s for: for users who need AI assistants/characters/agents (per the project’s description).
  • Why onchain/token: onchain records ownership and transfers of the token; the necessity of the token for the operation of the application is not established per Tier‑1.
  • What you can actually touch (Tier‑1): https://www.moemate.io/ (web application/entry into the product)

How it works (very briefly)

  1. The user does: chooses/creates an AI agent and gives it tasks (per the project’s description).
  2. The system does: performs the interaction with the agent and services/tools (execution details are partially in the repository/descriptions; quality metrics are not presented).
  3. The user gets: the agent’s responses/actions and the state in the application interface.
  4. Where the blockchain is: the token and its operations — onchain (Solana).
  5. Token role (if any): per Tier‑1, no unambiguous justification of the necessity of the token was found.

Quick links: AI thesis fit

Project passport

Field Value
Project name Moemate (MATES)
Also known as (aliases) Moemate, MATES
Logo (logo) ../assets/527_mates_logo.svg
Token symbol (ticker) —
Category AI/Agents | Consumer
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) —
Token (standard) SPL
Token contract MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX
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) AI agents/assistants in-app
Use‑case (use_case) AI agent creation + use
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Per Tier‑1 sources, the project has a website and a repository describing an application/platform for AI agents. There is also a token on the Solana network with a public mint address. No Tier‑1 justification of the necessity of the token for the operation of the application was found; quality metrics of the AI part are not identified per Tier‑1 sources.

Features/modules

  • AI agents (claimed): the user interacts with agents via the application.
  • Code repository (partially): public modules of the application (per GitHub).
  • Token (Solana): onchain contract (mint) and basic operations.

Typical scenarios

  • Scenario 1: the user opens the application → chooses/creates an agent → interacts with it.
  • Scenario 2: the user checks the token → uses the Solana block explorer.

Getting started (wallet/network)

  • What you need: an account/access to the application; a Solana wallet (for the token).
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: application/client + backend/infrastructure (details are not fully established per Tier‑1); the token — onchain on Solana.
  • Participant roles: application users; token holders.
  • Where logic runs: AI/agents — offchain (per the application model); the token — onchain.
  • Dependencies: Solana infrastructure (for the token) and the application infrastructure (not established).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Protocol necessity drivers: it is not established that the application does not work without the token.
  • Who pays fees: users pay Solana network fees for onchain operations.
  • Where fees go: to the Solana network validators (network level).

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: offchain infrastructure and supply chain risks (client/backend); token/mint risks (onchain).

Project status and timeline

  • Current status: —.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? Per the Tier‑1 website/repository, the project is positioned as a platform/application for AI agents; at the same time, quality metrics of the AI part are not identified per Tier‑1 sources.
  • What is truly onchain? The token on the Solana network (mint address, transactions and metadata via the block explorer).
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags (based on the information found): absence of a Tier‑1 explanation of the necessity of the token; absence of quality metrics; incomplete disclosure of the architecture of the AI part.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
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): Intent is not singled out as a separate signal, because the AI purpose is described as the current product.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): In this card, intent is accounted for via AI_1/AI_4.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Per Tier‑1 sources: a platform/application for AI agents/assistants and interaction with them.
  • Evidence: Tier‑1 — https://moemate.gg/ ; https://github.com/webaverse-studios/moemate-core
  • Why sufficient / why not (one line): There is a Tier‑1 description of the purpose and a repository; quality metrics (AI_3) are not presented.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a product entrypoint (web application) where one can log in and use the product.
  • Evidence: Tier‑1 — https://www.moemate.io/ ; https://github.com/webaverse-studios/moemate-core
  • Why sufficient / why not (one line): There is a Tier‑1 link to the product and a repository that points to the official entrypoint (“head to the Moemate Website”).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): Per Tier‑1 sources, no reproducible quality metrics of the AI part with context were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a Tier‑1 repository with the code of the application modules and official updates/descriptions.
  • Evidence: Tier‑1 — https://github.com/webaverse-studios/moemate-core ; https://www.moemate.io/whatsup
  • Why sufficient / why not (one line): The presence of an official repository and materials is sufficient for the tech context (without quality metrics).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: token mint: MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX
  • Evidence: Tier‑1 — https://solscan.io/token/MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX
  • Why sufficient / why not (one line): The onchain page of the mint address confirms the existence of the token.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 (other than the token).
  • Evidence: Tier‑1 — https://solscan.io/token/MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX
  • Why sufficient / why not (one line): No Tier‑1 confirmation of useful onchain logic beyond the token was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): No Tier‑1 justification was found that the product breaks down without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token on the Solana network (the mint address is in the block explorer).
  • Evidence: Tier‑1 — https://solscan.io/token/MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX
  • Why sufficient / why not (one line): The existence of the token is confirmed by onchain data.
  • 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): No Tier‑1 confirmation of payment for the service with the token was found.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): TK_1=1 requires Tier‑1 terms/tariffs/docs where the token is a mandatory payment.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of incentives/collateral/penalties with the token was found.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): TK_2=1 requires economy/incentive rules.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of the use of the token in governance was found.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): TK_3=1 requires a Tier‑1 governance process and a role of the token in voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability/irreplaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://moemate.gg/
  • Why sufficient / why not (one line): TK_4=1 requires a Tier‑1 explanation that the token is not necessary (it can be replaced with payment/a subscription).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://moemate.gg/ Tier‑1 source: description of the product/platform for AI agents.
Tier‑1 https://www.moemate.io/ Product entrypoint/web application (AI_2).
Tier‑1 https://github.com/webaverse-studios/moemate-core Tier‑1 artifact: public repository with the code of the application modules.
Tier‑1 https://solscan.io/token/MAtesZXcU38mgPuteRFo9ApCauYRRuwn3xf1cs5y7ZX Onchain fact: the token on the Solana network (mint address, transactions and metadata).
Tier‑1 — No Tier‑1 source for claim “why is a token needed” was found.
Tier‑2 https://coinmarketcap.com/currencies/mates/ Reference token profile (not proof of the necessity of the token/AI component).

No comments to display

Back to top