Skip to main content

HeyAnon

HeyAnon (ANON) — 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).

HeyAnon — an AI/Agents | DeFi project on Ethereum, token (symbol: ANON).

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 AI‑DeFi assistant/“copilot” that accepts natural‑language requests and helps execute DeFi operations and gather project/market information.
  • Who it’s for: DeFi users and traders who need a quick “chat interface” for actions and research (swap/bridge/stake/borrow + monitoring of project channels).
  • Why onchain/token: onchain is needed to execute DeFi operations on networks; the ANON token is used for DAO governance and claimed benefits (free/discounted access) for holders.
  • What you can actually touch (Tier‑1): the web product heyanon.ai + the public Chrome extension Anon HUD (a HUD/overlay for trading).

How it works (very briefly)

  1. The user does: connects an account/wallet and formulates a natural‑language request (assets, network, conditions/triggers).
  2. The system does: interprets the request (NLP), selects integrations and forms/launches onchain actions (bridge/swap/borrow/stake) and/or produces a summary based on data from social channels/docs/development.
  3. The user gets: transactions/operations in DeFi protocols and/or near‑real‑time “insights” (prices/sentiment/development activity/updates).
  4. Where the blockchain is: actions are executed on onchain networks and protocols; the ANON token contract is deployed (as OFT_V2) on several networks (including Ethereum).
  5. Token role (if any): governance (Anon DAO) + claimed benefits (free/discounted access) for holders; the necessity of paying for the service with the token is not established in the Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name HeyAnon
Also known as (aliases) HeyAnon.ai; Anon
Logo (logo) ../assets/112_hey-anon_logo.ico
Token symbol (ticker) ANON
Category AI/Agents | DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2024-12-14
Project status (status) active
Token (standard) ERC-20
Token contract 0x79bbF4508B1391af3A0F4B30bb5FC4aa9ab0E07C
Token model (token_type) utility (access + discounts + governance)
Max supply 21,000,000 ANON (per the tokenomics; there is a conflict with Etherscan)
Issuance fixed (per the tokenomics; see the conflict below)
Tokenomics (tokenomics, brief) Total Supply 21,000,000; distribution: ICO 10.5M, Team 6.1M, Foundation/Treasury 4.2M; the docs list vesting streams (Sablier)
Governance DAO (Anon DAO; token voting)
Admins/keys owner (Ownable; delegate/owner set at deployment; OApp/OFT admin)
Audit —
Bug bounty —
Team (team) Founder: t.me/danielesesta; Co‑founder: t.me/georgiiyvl; BD: t.me/crypto_anita
Funding (investors/funding) —
AI component (ai_component) conversational AI for DeFi tasks + research
Use‑case (use_case) DeFi copilot (NL execution + info mining)
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

HeyAnon is positioned as an AI DeFi protocol that combines two scenarios:

  • DeFi actions via chat: the user writes a natural‑language request (swap/bridge/borrow/stake + conditions/triggers), and the system helps execute it via integrated protocols.
  • “Information mining”: aggregation of near‑real‑time data on projects from several channels (X/Twitter, Telegram, Discord, GitBook, GitHub) and delivery of summaries (updates, development activity, sentiment, price changes, etc.).

A separate part of the product is the HUD browser extension (an overlay on trading/analytics platforms) with data export/search and claimed AI analytics.

Features/modules

  • HeyAnon Web App: login/account, execution of DeFi tasks and “info mining” requests.
  • DeFi integrations (from the docs): bridging (LayerZero / deBridge), swaps (0x, Odos, OpenOcean, KyberNetwork, Magpie, Hypersonic, OKX dex), borrow/earn (Aave, Spark, Venus, Kamino, Jito, Marinade), price feeds (Pyth).
  • Automation & Triggers: time‑based / gas‑based / price‑based triggers.
  • Data aggregation: monitoring of social channels and dev artifacts (GitHub, GitBook) + counts/summaries.
  • Anon HUD (Chrome extension): an overlay/buttons on supported platforms, data export and claimed AI analytics.

Typical scenarios

  • Scenario 1 (DeFi action): the user writes “Swap 100 USDT to WBTC on Arbitrum when price < …” → the system forms a sequence of actions and helps execute the transactions via the supported integrations.
  • Scenario 2 (Info mining): the user asks “Show the latest GitHub commits/Telegram sentiment for Project X over the last 24 hours” → the system aggregates the data and produces a summary.
  • Scenario 3 (HUD): the user opens TradingView/Dexscreener/Hyperliquid, etc. → the extension adds an overlay/controls for searching/exporting and analyzing the selected asset/data.

Getting started (wallet/network)

  • What you need: an account in heyanon.ai; for onchain actions — a connected wallet and funds for fees/operations.
  • Network/chain: depends on the operation (the project describes multichain actions; the ANON token is published as OFT_V2 on several networks).
  • Fees: network fees (gas) of the respective networks + fees/spreads of the integrations (DEX/bridge), where applicable.

Architecture/tech (non‑AI)

  • Components: the web application heyanon.ai; integrations with DeFi protocols/aggregators; the Chrome extension Anon HUD; the onchain artifact — the ANON token contract (LayerZero OFT).
  • Participant roles: users (DeFi actions/research); token holders (governance); the team/DAO (development and deployment).
  • Where logic runs: DeFi operations — onchain on the target networks/protocols; orchestration/interpretation of requests and data aggregation — offchain.
  • Dependencies: LayerZero/deBridge (bridging); DEX aggregators (0x/Odos/…); price feeds (Pyth); social channels and dev sources (X/Telegram/Discord/GitBook/GitHub).

Token/economics (expanded, no forecasts)

  • Token utility: governance (Anon DAO) + claimed benefits for holders (free/discounted access to AI agent services).
  • Protocol necessity drivers: Tier‑1 describes governance/benefits; at the same time, no Tier‑1 proof that the service must be paid for with the ANON token was found.
  • Who pays fees: users pay network fees (gas) for onchain operations on the selected networks/protocols.
  • Issuance/burn: the tokenomics claim a Total Supply of 21,000,000; (see the conflict with Etherscan below).
  • Distribution and token issuance schedule: the tokenomics list shares (ICO/Team/Foundation) and provide the issuance schedule for the team + links to Sablier vesting streams.
  • Treasury: the tokenomics describe the areas of treasury spending (access subsidies, hiring, infrastructure, grants).

Governance

  • Who makes decisions: Anon DAO (token holders receive voting rights).
  • How protocol parameters/development change: in Tier‑1 this is formulated as “voting rights to direct development and deployment”; details of the voting procedures/modules are not established in this card.
  • Keys/multisig: the ANON token contract is Ownable (owner/delegate set at deployment).

Security and incidents

  • Audits: — (no public Tier‑1 reports found).
  • Bug bounty: — (no Tier‑1 program was found).
  • Incidents: — (no Tier‑1 postmortems found).
  • Threat model: the risk of centralized admin powers in the token contract (Ownable/OApp configuration); operational risks of executing onchain actions via integrations (bridge/DEX/borrow protocols).

Project status and timeline

  • Current status: an active product + the onchain ANON token (mainnet).
  • Key milestones: creation of the ANON token contract on Ethereum — 2024-12-14 (Etherscan tx).
  • Roadmap: — (a separate roadmap is not recorded in Tier‑1; the token docs describe general directions of development via the DAO).

Ecosystem/integrations

  • Integrations: LayerZero, deBridge; DEX aggregators (0x/Odos/OpenOcean/…); borrow/earn protocols (Aave/Spark/Venus/…); Pyth price feeds; X/Telegram/Discord/GitBook/GitHub channels for data aggregation.
  • Where it’s actually used: reproducible “Getting started” scenarios in the docs + the public Anon HUD extension (Chrome Web Store).

AI component of the project

  • What is real AI here? the Tier‑1 docs describe “conversational AI + NLP” for interpreting requests and aggregating data from various sources; the product is positioned as an AI‑DeFi assistant.
  • What is truly onchain? DeFi operations (swap/bridge/borrow/stake, etc.) are executed in onchain protocols; the ANON token is an onchain contract (LayerZero OFT) on Ethereum and other networks.
  • Why is a token needed? governance (Anon DAO) + claimed benefits (free/discounted access) for holders; payment for the service with the token is not confirmed in Tier‑1.
  • Red flags (based on the information found): token‑washing risk (if the token is not a mandatory access/payment primitive), onchain‑washing risk (if “onchain” boils down to third‑party protocols without HeyAnon’s own onchain components), a conflict in the supply metric (tokenomics vs Etherscan). What to double‑check: which “AI agent service” exactly is meant and how it is priced; whether HeyAnon has its own onchain contracts besides the token; how DAO voting is organized (where/with what it is implemented).

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
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): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is a Tier‑1 description of working AI interaction (AI_1=1) and a demo/onboarding (AI_2=1), so AI_0 as “intent only” does not apply.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): conversational AI (NLP) interprets requests and aggregates project/market data from various sources.
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai
  • Why sufficient / why not (one line): the Tier‑1 introduction directly describes NLP/conversational AI and the “DeFi actions + data aggregation” scenarios.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there are public entry points: the web app + Getting started instructions + the HUD extension.
  • Evidence: Tier‑1 — https://heyanon.ai/ ; https://docs.heyanon.ai/heyanon.ai/hey-anon/getting-started ; https://chromewebstore.google.com/detail/anon-hud/oimcinaflljpjficmfbibjjcaailecnk
  • Why sufficient / why not (one line): there are reproducible onboarding steps + a public extension with a version/update date.
  • 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): there are no reproducible quality/accuracy metrics/benchmarks for the AI part in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no Tier‑1 description of specific AI models/versions/architecture (apart from the general description of NLP/aggregation).
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai
  • Why sufficient / why not (one line): the docs describe the functionality but do not disclose model details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the ANON token (OFT / ERC‑20): 0x79bbF4508B1391af3A0F4B30bb5FC4aa9ab0E07C
  • Evidence: Tier‑1 — https://etherscan.io/token/0x79bbf4508b1391af3a0f4b30bb5fc4aa9ab0e07c ; https://etherscan.io/tx/0xf7d11ce0cccab62714084156fd93fafb4716edb87dcbfa155b5d0f7caa11d18f
  • Why sufficient / why not (one line): the explorer records the contract address and the creation transaction with its date.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (the token is confirmed in Tier‑1; separate HeyAnon onchain contracts for product logic are not listed).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the Tier‑1 docs describe DeFi actions via integrations but do not provide addresses/artifacts of HeyAnon’s own onchain modules besides the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the blockchain the target scenario (swap/bridge/borrow/stake) does not exist — the product loses its meaning as a DeFi tool.
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai/hey-anon/features
  • Why sufficient / why not (one line): Tier‑1 lists onchain actions (bridge/swap/borrow/stake) as key functionality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, ANON (LayerZero OFT / ERC‑20).
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai/general-information/contracts ; https://etherscan.io/token/0x79bbf4508b1391af3a0f4b30bb5fc4aa9ab0e07c
  • Why sufficient / why not (one line): the token address and the multichain contracts are listed in Tier‑1.
  • 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): Tier‑1 does not confirm mandatory payment for the service with the ANON token.
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai ; https://docs.heyanon.ai/heyanon.ai/general-information/anon-token
  • Why sufficient / why not (one line): Tier‑1 describes governance/benefits, but “pay‑in‑ANON” is not described as a mandatory access mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Tier‑1 contains no description of mandatory token incentives/collateral/penalties as part of protocol security.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the tokenomics describe the distribution/treasury usage but do not record mandatory incentives/penalties in the protocol.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): ANON is the governance token of Anon DAO (voting rights).
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai/general-information/anon-token
  • Why sufficient / why not (one line): Tier‑1 directly describes governance and voting rights for holders.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): Tier‑1 does not prove the irreplaceability of ANON (governance/benefits are potentially implementable alternatively).
  • Evidence: Tier‑1 — https://docs.heyanon.ai/heyanon.ai/general-information/anon-token
  • Why sufficient / why not (one line): rights/benefits are described, but there is no strict “without the token the product breaks” test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.heyanon.ai/heyanon.ai positioning: AI DeFi protocol; conversational AI (NLP) + data aggregation
Tier‑1 https://docs.heyanon.ai/heyanon.ai/hey-anon/getting-started reproducible steps: how to formulate prompts and execute DeFi actions / info mining
Tier‑1 https://docs.heyanon.ai/heyanon.ai/hey-anon/features the list of onchain scenarios (bridge/swap/borrow/stake) + automation/triggers + data aggregation sources
Tier‑1 https://heyanon.ai/ the public entry point of the product + links to staking/HUD
Tier‑1 https://docs.heyanon.ai/heyanon.ai/hud/installation-of-the-hud Tier‑1 HUD installation instructions + requirements (account connection)
Tier‑1 https://chromewebstore.google.com/detail/anon-hud/oimcinaflljpjficmfbibjjcaailecnk the public Anon HUD extension (description, version, update date, developer email @heyanon.ai)
Tier‑1 https://docs.heyanon.ai/heyanon.ai/general-information/anon-token governance token + benefits; tokenomics (Total Supply 21,000,000 + allocations/vesting)
Tier‑1 https://docs.heyanon.ai/heyanon.ai/general-information/contracts multichain ANON contracts (OFT_V2) + Solana programId/mint
Tier‑1 https://etherscan.io/token/0x79bbf4508b1391af3a0f4b30bb5fc4aa9ab0e07c onchain fact: the ANON token contract on Ethereum + Max Total Supply (95,950.751458)
Tier‑1 https://etherscan.io/tx/0xf7d11ce0cccab62714084156fd93fafb4716edb87dcbfa155b5d0f7caa11d18f creation of the ANON contract: 2024‑12‑14; owner/delegate at deployment
Tier‑1 https://docs.heyanon.ai/heyanon.ai/general-information/team-telegram-contacts Tier‑1 team contacts (Founder/Co‑founder/BD)
Tier‑1 — Supply conflict: the tokenomics claim a Total Supply of 21,000,000, but Etherscan shows a Max Total Supply of 95,950.751458 (possible reason: specifics of multichain/OFT accounting or incomplete information in the explorer).

No comments to display

Back to top