Skip to main content

Any Inu

Any Inu (AI) — 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).

Any Inu — a Meme / Interop project: an “omnichain dog coin” with an emphasis on a single supply and multichain operations via Axelar Interchain Token Service (ITS) (claimed in the docs and on Etherscan). The AI token contract is confirmed onchain (ERC‑20 on Ethereum; the docs claim 15 chains “from launch”).

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 “omnichain dog coin” meme token with a claimed single supply across different networks.
  • Who it’s for: holders/traders for whom multichain availability of the token matters.
  • Why onchain/token: onchain is needed as the carrier of the token and of the multichain mechanics via Axelar ITS; there is no separate AI function (the ticker “AI” is the token symbol).

How it works (very briefly)

  1. The user does: interacts with the AI token and moves it between the supported networks (in general terms; a claim in the docs).
  2. The system does: uses Axelar ITS for a “single supply token” and cross‑chain operations (a claim in the docs; Etherscan describes the token as omnichain via ITS).
  3. The user gets: the ability to have one and the same token (by identity) on several networks without “chain wars” (docs).
  4. Where the blockchain is: the AI ERC‑20 contract on Ethereum is confirmed (Etherscan); the docs claim multichain coverage.
  5. Token role (if any): the token itself is the product; utility beyond‑meme in the extracted Tier‑1 is limited to multichain operability and loyalty programs (Diamond Hands — claim).

Quick links: AI thesis fit

Project passport

Field Value
Project name Any Inu
Also known as (aliases) AI, $AI, AnyToshi (founder nickname, docs)
Logo (logo) ../assets/278_any-inu_logo.png
Token symbol (ticker) AI
Category Meme | Interop
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 0x2598c30330D5771AE9F983979209486aE26dE875
Token model (token_type) meme / omnichain token
Max supply 22,067,484,376,314.563194624992699284 AI (Etherscan “Max Total Supply”)
Issuance mint/burn via Axelar ITS (per the source code on Etherscan; cross‑chain mint/burn)
Tokenomics (tokenomics, brief) “single supply token”, “stealth fair launch”, “15 chains from launch” (docs)
Governance community (claim)
Admins/keys —
Audit —
Bug bounty —
Team (team) — (the docs feature the founder nickname AnyToshi without a team/legal entity)
Funding (investors/funding) —
AI component (ai_component) none
Use‑case (use_case) omnichain meme token via Axelar ITS
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 1 / 3
Last verified 2026-02-11

General project overview

Any Inu in its official docs describes the problem of “supply isolated across chains” and states the goal of a single multichain token without intermediate “bridging tokens”. The project explicitly states that it uses Axelar Interchain Token Service (ITS) and that the token “truly breach the network barrier with 15 chains from launch” (docs). The Etherscan token page also states the thesis: “omnichain dog coin powered by Axelar's Interchain Token Service”.

Features/modules

  • Omnichain token (Axelar ITS): claimed unified multichain operability (docs + Etherscan).
  • Single supply token: the thesis “one supply, no bridging tokens” (docs).
  • Diamond Hands (roadmap): a DApp for voluntary token locking with a multiplier and rewards/airdrops (docs).

Typical scenarios

  • Scenario 1: a user interacts with the AI token → checks the contract on Etherscan (explorer).
  • Scenario 2: a user uses the multichain version of the token (claim) → moves the token between networks without “wrapped bridge tokens” (docs).
  • Scenario 3: a user voluntarily locks tokens in the Diamond Hands DApp → gets a multiplier and eligibility for rewards (docs).

Getting started (wallet/network)

  • What you need: an EVM wallet for the ERC‑20 token on Ethereum; for multichain use — the supported networks (the docs claim 15, but per‑network addresses were not extracted).
  • Network/chain: Ethereum mainnet (the network confirmed per Etherscan).
  • Fees: gas on Ethereum (and on the respective networks in multichain use).

Architecture/tech (non‑AI)

  • Components: the AI token ERC‑20 contract on Ethereum (a minimal proxy to InterchainToken) + Axelar ITS infrastructure (per the code/description) + offchain communications/community (docs).
  • Participant roles: holders/traders; participants of the lock program (Diamond Hands).
  • Where logic runs: onchain — the token and the mint/burn interfaces under the control of the interchain token service; offchain — website/social media/announcements.
  • Dependencies: Axelar Interchain Token Service; Ethereum.

Token/economics (expanded, no forecasts)

  • Token utility: a single multichain token for holding/trading; the Diamond Hands lock program for eligibility/multipliers (docs).
  • Protocol necessity drivers: multichain availability and a “single supply token” are the core claim of the project (docs).
  • Who pays fees: users pay gas on the respective networks.
  • Where fees go: to the validators/sequencers of the networks (network fees).
  • Issuance/burn: the contract contains mint/burn functions (Etherscan source code) within the interchain token standard; Etherscan shows the Max Total Supply.
  • Security/incentive mechanisms: Diamond Hands lock with a 1x–5x multiplier (docs).
  • Distribution and token issuance schedule: — (in the extracted Tier‑1 there is no distribution/vesting table).
  • Treasury: —.

Governance

  • Who makes decisions: — (the docs say “community focused”, but the governance process/venues were not extracted).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the risks depend on the Axelar ITS infrastructure (cross‑chain mint/burn); absence in the extracted Tier‑1 of a list of contracts for all claimed networks; token focus without additional protocol guarantees.

Project status and timeline

  • Current status: the AI token exists on Ethereum; the docs are available.
  • Key releases/milestones: the Diamond Hands DApp is described as a future/roadmap element (docs).
  • Roadmap: — (in the extracted Tier‑1 there is no separate roadmap page, apart from fragments of the community roadmap).

Ecosystem/integrations

  • Integrations: Axelar ITS (claim); EVM wallets for ERC‑20.
  • Partners: —.
  • Where it’s actually used: — (apart from trading/holding the token; no other integrations are indicated in the extracted Tier‑1).

AI component of the project

  • What is real AI here? there is no AI component; “AI” is the token ticker.
  • What is truly onchain? the AI token ERC‑20 contract on Ethereum is confirmed; the contract implements interchain token interfaces (mint/burn) for ITS (Etherscan).
  • Why is a token needed? the token is the product: an omnichain meme token; the docs also describe the Diamond Hands lock mechanism for rewards/airdrops.
  • Red flags (based on the information found): AI‑washing (the “AI” symbol may be misleading); limited verification of multichain coverage (no list of contracts per network in the extracted Tier‑1); dependence on external cross‑chain infrastructure (Axelar).

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality absent 0
Onchain necessity medium 2
Token necessity medium 1
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): in the extracted Tier‑1 there is no statement about developing an AI product/agents; AI is the ticker.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): AI as a product is not claimed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): no AI functions/models/agents are described.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): the docs focus on the token and cross‑chain interoperability.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): there is no demo of an AI product.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): there is no AI component.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): not applicable (there is no AI component).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no technical description of AI.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): not applicable.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: AI token: 0x2598c30330D5771AE9F983979209486aE26dE875
  • Evidence: Tier‑1 — https://etherscan.io/token/0x2598c30330D5771AE9F983979209486aE26dE875
  • Why sufficient / why not (one line): the address is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the contract implements interchain token functions (init/mint/burn) and references the interchain token service (Axelar ITS), which supports the “omnichain token” mechanics.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x2598c30330D5771AE9F983979209486aE26dE875
  • Why sufficient / why not (one line): the source code on Etherscan shows interchain token interfaces (not just a basic ERC‑20).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: an “omnichain token” is by definition about blockchains, but in the extracted Tier‑1 it is not proven that the onchain architecture specifically is necessary (rather than a centralized bridge/ledger).
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): there is no detailed comparison/proof of the necessity of the onchain approach.
  • 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.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x2598c30330D5771AE9F983979209486aE26dE875
  • Why sufficient / why not (one line): the token is confirmed onchain.
  • 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): payment for a service/protocol with the AI token is not described in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): there is no product with payment — mainly the token/multichain narrative.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the Diamond Hands DApp implies voluntary token locking for a multiplier and eligibility for rewards (airdrops/whitelists).
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/community/roadmap/diamond-hands
  • Why sufficient / why not (one line): an incentive mechanism is described (lock → multiplier → rewards).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): token governance (voting/DAO mechanics) is not described in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/
  • Why sufficient / why not (one line): there is no description of a governance module.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is the central object of the project (omnichain dog coin); replacing it would mean changing the identity/supply across networks.
  • Evidence: Tier‑1 — https://docs.anyinu.xyz/ ; https://etherscan.io/token/0x2598c30330D5771AE9F983979209486aE26dE875
  • Why sufficient / why not (one line): the token is described as a “single supply token” and as the core of the product.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.anyinu.xyz/ Description of the “omnichain dog coin”, the principles of single supply/15 chains/Axelar ITS.
Tier‑1 https://docs.anyinu.xyz/community/roadmap/diamond-hands The Diamond Hands lock mechanics and its purpose (rewards/airdrops).
Tier‑1 https://etherscan.io/token/0x2598c30330D5771AE9F983979209486aE26dE875 The AI token contract on Ethereum (ITS proxy), supply, source code.

No comments to display

Back to top