Skip to main content

donotfomoew (MOEW)

donotfomoew (MOEW) — 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).

MOEW — a memecoin/mascot project with a claimed AI agent and tools (meme maker / chatbot), the MOEW token on Base.

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: the MOEW memecoin project, which the documentation describes as having evolved into an AI agent (social media presence + “alpha sharing” + meme maker + chatbot).
  • Who it’s for: the community/users who interact with MOEW in the channels (X/Telegram/website) and use the content tools.
  • Why onchain/token: onchain confirms the existence of the MOEW token on Base; in the extracted Tier‑1 materials, the necessity of the token as “payment/collateral/governance” is not fixed.
  • What you can actually touch (Tier‑1): https://donotfomoew.org/ (the project’s public web page).

How it works (very briefly)

  1. The user does: reads/interacts with MOEW and (claimed) uses the meme maker / chatbot.
  2. The system does: the AI agent generates content/analytics and interacts with users (Tier‑1, claimed).
  3. The user gets: meme content/messages/updates and participation in community activities.
  4. Where the blockchain is: the onchain artifact is the MOEW token (ERC‑20) on the Base network.
  5. Token role (if any): in the extracted Tier‑1 sources, the practical role of the token in the product is not described.

Quick links: AI thesis fit

Project passport

Field Value
Project name donotfomoew (MOEW)
Also known as (aliases) MOEW, Professor MOEW (as claimed)
Logo (logo) —
Token symbol (ticker) MOEW
Category AI/Agents | Meme
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) PoS (Base; Ethereum L2)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x15aC90165f8B45A80534228BdCB124A011F62Fee
Token model (token_type) unknown
Max supply 10 000 000 000 MOEW
Issuance —
Tokenomics (tokenomics, brief) Max total supply 10B (Tier‑1 explorer).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent (content + analytics) + meme maker + chatbot
Use‑case (use_case) meme community mascot + AI content + alpha sharing
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

The Tier‑1 litepaper describes MOEW as a memecoin/mascot that started as a BASE token and then evolved into “Professor MOEW” and further — into an AI agent that publishes insights/Hot Picks and (claimed) supports a meme maker and an interactive chatbot.

Features/modules

  • AI agent / social presence: autonomous presence on X and “alpha sharing” (Tier‑1, claimed).
  • Meme maker and chatbot: functions for meme generation and communication (Tier‑1, claimed).

Typical scenarios

  • Scenario 1: a user follows MOEW updates/analytics.
  • Scenario 2: a user generates memes via the meme maker (claimed).
  • Scenario 3: a user chats with MOEW via the chatbot (claimed).

Getting started (wallet/network)

  • What you need: web access to the website and documentation; community channels (X/Telegram).
  • Network/chain: the MOEW token is on Base (Tier‑1 explorer).
  • Fees: onchain fees depend on transactions on the Base network; not recorded in this card.

Architecture/tech (non‑AI)

  • Components: an AI agent + content tools; the MOEW token contract on Base.
  • Participant roles: users/community; project teams/curators (not disclosed); the AI agent (claimed).
  • Where logic runs: AI and content generation — offchain; onchain — the token.
  • Dependencies: social media platforms and web infrastructure; the Base network for the token.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (in the extracted sources, utility/gov/fees for MOEW are not described).
  • Protocol necessity drivers: —
  • Who pays fees: —
  • Where fees go: —
  • Issuance/burn: —
  • Security/incentive mechanisms: —
  • Distribution and token issuance schedule: —
  • Treasury: —

Governance

  • Who makes decisions: —
  • How protocol parameters change: —
  • Where decisions are discussed/made: —
  • Keys/multisig: —

Security and incidents

  • Audits: — (if many — put a table below)
  • Bug bounty: —
  • Incidents: —
  • Threat model: —

Project status and timeline

  • Current status: the website and documentation are publicly available.
  • Key releases/milestones: the roadmap page highlights the development phases of the AI agent (Tier‑1).
  • Roadmap: available (see links_*).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? the Tier‑1 documentation describes an AI agent and its functions (alpha sharing, meme maker, chatbot) + a high‑level technical architecture (LLM/MCP/RAG, etc.).
  • What is truly onchain? the confirmable artifact is the MOEW token (ERC‑20) on Base.
  • Why is a token needed? per Tier‑1, it is not established how the token is embedded in the product mechanics.
  • Red flags (based on the information found): many items in the architecture/roadmap are at the level of plans/a list of technologies without verifiable metrics/artifacts (AI_3=0); onchain is confirmed only as a token (OC_2=0).

DecAI Fit component summary

  • DecAI Fit: 4/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 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as a working component (an AI agent and functions), not only an intent.
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): Per SSOT, AI_0=1 is set only when AI_1..AI_4 = 0; here there are described functions and a technical context.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Tier‑1 describes the core functions: “alpha sharing”, meme maker and interactive chatbot.
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/what-can-moew-do/quickstart
  • Why sufficient / why not (one line): The Tier‑1 page lists the functions that the AI agent is supposed to perform.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public web page of the project, and Tier‑1 describes that users can generate memes via text prompts (meme maker).
  • Evidence: Tier‑1 — https://donotfomoew.org/ ; https://donotfomoews-organization.gitbook.io/donotfomoew/what-can-moew-do/quickstart
  • Why sufficient / why not (one line): The existence of a public surface + the described meme maker user flow.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): Tier‑1 describes a high‑level technical architecture of the MOEW AI Agent (LLM/MCP/RAG/TEE, etc.).
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/ai-roadmap/technical-architecture
  • Why sufficient / why not (one line): There is a Tier‑1 technical context (albeit at the level of an overview list of components/technologies).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: MOEW token (ERC‑20): 0x15aC90165f8B45A80534228BdCB124A011F62Fee
  • Evidence: Tier‑1 — https://basescan.org/token/0x15aC90165f8B45A80534228BdCB124A011F62Fee
  • Why sufficient / why not (one line): The explorer records the network/address and the max total supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: what breaks without onchain: —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, MOEW, on Base.
  • Evidence: Tier‑1 — https://basescan.org/token/0x15aC90165f8B45A80534228BdCB124A011F62Fee
  • Why sufficient / why not (one line): The explorer confirms the onchain token and its parameters.
  • 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): —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): —
  • Evidence: Tier‑1 — https://donotfomoews-organization.gitbook.io/donotfomoew/
  • Why sufficient / why not (one line): —
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://donotfomoew.org/ Public page of the project; positioning as the “AI agent version of MOEW” (claimed).
Tier‑1 https://donotfomoews-organization.gitbook.io/donotfomoew/ Tier‑1 litepaper: origin and transition to an AI agent (claimed).
Tier‑1 https://donotfomoews-organization.gitbook.io/donotfomoew/what-can-moew-do/quickstart Core functions: alpha sharing, meme maker, chatbot (claimed).
Tier‑1 https://donotfomoews-organization.gitbook.io/donotfomoew/ai-roadmap/technical-architecture High‑level technical architecture of the MOEW AI Agent (claimed).
Tier‑1 https://donotfomoews-organization.gitbook.io/donotfomoew/ai-roadmap/markdown Roadmap by development phases of the AI agent (claimed).
Tier‑1 https://basescan.org/token/0x15aC90165f8B45A80534228BdCB124A011F62Fee Onchain fact: the MOEW token on Base; max total supply 10B; decimals 18.
Tier‑2 https://www.coingecko.com/en/coins/moew Aggregator (context).
Tier‑2 https://coinmarketcap.com/currencies/donotfomoew/ Aggregator (context).

No comments to display

Back to top