Airene
Airene — 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).
Airene — a project/token on the Base network; no verifiable Tier‑1 description of the product/AI component was found.
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 (the contract address — in links_* / Explorer).
- Who it’s for: not established per Tier‑1.
- Why onchain/token: onchain confirms the existence of the token; no Tier‑1 description of useful logic/token utility was found.
How it works (very briefly)
- The user does: interacts with the token on the Base network (for example, transfers).
- The system does: the basic token logic is executed onchain.
- The user gets: not established per Tier‑1.
- Where the blockchain is: the token contract and transactions are visible in the explorer (links_*).
- Token role: not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Airene |
| Also known as (aliases) | — |
| Logo (logo) | — |
| Token symbol (ticker) | — |
| Category | — |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x2eac9B08A4D86F347B9E856fB3EC082e61c76545 |
| 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 | ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://app.virtuals.io/virtuals/2059 |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x2eac9B08A4D86F347B9E856fB3EC082e61c76545 |
| X | https://twitter.com/airene_asianmom |
| Discord | — |
| Telegram | https://t.me/airene_asianmom_virtuals_bot |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/airene |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/airene/ |
General project overview
The available links show that there is a token on the Base network and public accounts/profiles (links_*). No Tier‑1 description of the product, the AI component and the role of the token (utility) was found; therefore, the conclusions and flags below are set conservatively.
Features/modules
- Onchain component: an ERC‑20 token on the Base network (see Explorer).
- Everything else: — (not established per Tier‑1).
Typical scenarios
- Scenario 1: a user performs onchain operations with the token (transfers) → the transactions are visible in the explorer.
Getting started (wallet/network)
- What you need: an EVM wallet.
- Network/chain: Base.
- Fees: Base network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: the token contract on the Base network.
- Where logic runs: basic token operations — onchain; the rest — not established.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
- Issuance/supply: not established per Tier‑1.
Governance
- Who makes decisions: — (not established per Tier‑1).
Security and incidents
- Audits: not found in Tier‑1.
- Bug bounty: not found in Tier‑1.
- Incidents: —.
Project status and timeline
- Current status: not established (other than the fact of the token’s existence onchain).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
AI component of the project
- What is real AI here? No Tier‑1 description of an AI component was found.
- What is truly onchain? The token contract on the Base network (see Explorer).
- Why is a token needed? No Tier‑1 description of the utility/necessity of the token was found.
- Red flags (based on the information found): no Tier‑1 documentation/repository/tech description; the role of the token and of onchain logic other than the token is unclear; the project’s official sources require re‑checking.
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 declaration of AI intent/roadmap was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 source of intent, the flag is set to 0 (conservatively).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): No Tier‑1 description of what exactly the AI does was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of the AI functions, the flag remains 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No Tier‑1 demos/examples of the AI in operation were found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a verifiable Tier‑1 demo, the flag remains 0.
- 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): AI metrics/benchmarks were not found in Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description/architecture/versions of the AI were found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 tech description, the flag remains 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: token contract 0x2eac9B08A4D86F347B9E856fB3EC082e61c76545
- Evidence: Tier‑1 — https://basescan.org/token/0x2eac9B08A4D86F347B9E856fB3EC082e61c76545
- Why sufficient / why not (one line): The existence of the token contract and the explorer confirms the onchain component.
- 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 basic token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of useful onchain logic (access/accounting/rules/DAO), the flag remains 0.
- 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 — —
- Why sufficient / why not (one line): No Tier‑1 justification was found that the product loses its meaning 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 Base network.
- Evidence: Tier‑1 — https://basescan.org/token/0x2eac9B08A4D86F347B9E856fB3EC082e61c76545
- Why sufficient / why not (one line): The onchain explorer confirms the existence 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): No Tier‑1 confirmation of “payment for the service with the token” was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of the payment function, the flag remains 0.
- 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 via the token was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of incentives/security, the flag remains 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of governance use of the token was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of governance, the flag remains 0.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): TK_4 requires explicit argumentation of replaceability; no Tier‑1 found.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://basescan.org/token/0x2eac9B08A4D86F347B9E856fB3EC082e61c76545 | Onchain fact: the token contract on the Base network. |
| Tier‑1 | — | No Tier‑1 source for claim “what exactly the AI does” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “why is a token needed (utility)” was found. |
| Tier‑2 | https://www.coingecko.com/en/coins/airene | Context: token card/metadata (not proof of AI/onchain utility). |
No comments to display
No comments to display