Skip to main content

AI69SAKURA

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

AI69SAKURA — a Meme project on Base, token (symbol: SAKURA).

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 token on the Base network (per the explorer).
  • Who it’s for: for token participants/holders (detailed scenarios are not established per Tier‑1).
  • Why onchain/token: the onchain token contract is confirmed; the AI component and token utility are not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: receives the token/transfers the token.
  2. The system does: transactions are recorded on the Base network.
  3. The user gets: ownership/transfers of the token (onchain).
  4. Where the blockchain is: the token and transactions are onchain (Base).
  5. Token role (if any): not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name AI69SAKURA
Also known as (aliases) AI69 Sakura
Logo (logo) —
Token symbol (ticker) SAKURA
Category 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 0x00EF403ECb9FC75811d6869c6ca676770100da8d
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) —
Use‑case (use_case) —
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 1 / 0 / 1
Last verified 2026-02-11

General project overview

Per the available data, this is an ERC‑20 token on the Base network. No Tier‑1 confirmation of the AI component and token utility was found.

Features/modules

  • Onchain token: an ERC‑20 contract on the Base network (confirmed in the explorer).
  • AI/product features: not established per Tier‑1.

Typical scenarios

  • Scenario 1: a holder transfers the token → the transaction is visible on Base.

Getting started (wallet/network)

  • What you need: an EVM wallet.
  • Network/chain: Base.
  • Fees: gas on the Base network.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract.
  • Where logic runs: onchain (Base) — token transfers.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Tokenomics parameters: not established per Tier‑1 sources.

Governance

  • Who makes decisions: not established.

Security and incidents

  • Audits: not found per Tier‑1.
  • Bug bounty: not found per Tier‑1.
  • Incidents: not found per Tier‑1.

Project status and timeline

  • Current status: active (the token exists onchain).
  • Roadmap: not found per Tier‑1.

Ecosystem/integrations

  • Integrations/cases: not established per Tier‑1 sources.

AI component of the project

  • What is real AI here? Not established: no Tier‑1 sources explaining the AI component were found.
  • What is truly onchain? An ERC‑20 token on the Base network (address in the explorer).
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags and what to double‑check:
    • AI‑washing: no Tier‑1 description of the AI component (AI_0..AI_4=0).
    • onchain‑washing: no confirmation of useful onchain logic other than the token (OC_2=0).
    • token‑washing: no Tier‑1 description of the token utility was found.

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 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 “AI intent/roadmap” was found.
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 source where AI is explicitly claimed as intent/roadmap.
  • 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 not established.
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 description of AI features.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No demo/app for AI features was found per Tier‑1.
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 “what you can touch”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1
  • Context (version/date/how measured): not found per Tier‑1
  • Evidence: —
  • Why sufficient / why not (one line): No Tier‑1 quality metrics were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): No tech description of an AI component was found per Tier‑1.
  • Evidence: —
  • Why sufficient / why not (one line): There are no Tier‑1 technical docs/architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: 0x00EF403ECb9FC75811d6869c6ca676770100da8d
  • Evidence: Tier‑1 — https://basescan.org/token/0x00EF403ECb9FC75811d6869c6ca676770100da8d
  • Why sufficient / why not (one line): There is an onchain fact in the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (other than the token)
  • Evidence: —
  • Why sufficient / why not (one line): No Tier‑1 confirmation of onchain logic other than 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 (other than the token).
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 argument for blockchain 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 (ERC‑20).
  • Evidence: Tier‑1 — https://basescan.org/token/0x00EF403ECb9FC75811d6869c6ca676770100da8d
  • Why sufficient / why not (one line): There is onchain confirmation 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): Utility as “payment for the service” is not established.
  • Evidence: —
  • Why sufficient / why not (one line): No Tier‑1 sources about the token utility were found.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Token‑based incentives/collateral/penalties are not established.
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 description of incentive mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The governance mechanics of the token are not established.
  • Evidence: —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance.
  • 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.
  • Evidence: —
  • Why sufficient / why not (one line): Insufficient Tier‑1 data.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://basescan.org/token/0x00EF403ECb9FC75811d6869c6ca676770100da8d Onchain fact: the token (contract) on Base
Tier‑1 — No Tier‑1 source for claim “the project contains an AI component” was found.
Tier‑1 — No Tier‑1 source for claim “why is a token needed (utility)” was found.
Tier‑2 https://coinmarketcap.com/currencies/ai69sakura/ Reference token page (not proof of technology)

No comments to display

Back to top