Skip to main content

Lush AI

Lush 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).

Lush AI — an AI/Agents \| Consumer project on the Ethereum network, token (symbol: LUSH).

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 product/ecosystem for creating and managing AI models/agents for content scenarios (including “AI influencers”, claimed on the Tier‑1 website).
  • Who it’s for: content creators and teams that need AI content and management of AI agents on social media (claimed).
  • Why onchain/token: onchain, the LUSH token is observable; the necessity of the token for the key features of the product is not established per Tier‑1 sources.
  • What you can actually touch (Tier‑1): Lush Agents (see App / Demo in links_*).

How it works (very briefly)

  1. The user does: selects an AI model/agent and sets a scenario/prompt.
  2. The system does: generates content and/or manages the agent for publications (offchain).
  3. The user gets: finished content/the result of the interaction.
  4. Where the blockchain is: onchain, the LUSH token is observable (Explorer); the functionality of the product is described as offchain services.
  5. Token role: per Tier‑1 sources, it is not confirmed that the token is mandatory for the operation of the key features.

Quick links: AI thesis fit

Project passport

Field Value
Project name Lush AI
Also known as (aliases) LUSH
Logo (logo) ../assets/575_lush-ai_logo.svg
Token symbol (ticker) LUSH
Category AI/Agents | Consumer
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 0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0
Token model (token_type) —
Max supply 20,000,000,000 LUSH (max total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Max total supply in the Explorer; the necessity of the token for the key features of the product is not established per Tier‑1 sources.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI models + social agents for content workflows
Use‑case (use_case) AI content generation + social media agents
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Lush AI positions itself as an ecosystem around generative AI models and AI agents for content scenarios. The Tier‑1 website describes the directions: “AI models”, “Agents” for working on social media, as well as separate products/interfaces (Agents/Exchange/Chat).

Features/modules

  • AI models: content generation based on AI models (claimed).
  • Lush Agents: autonomous agents for working on social media (claimed; a separate product/interface).
  • Exchange / tokenization: a product/interface for the “tokenization of AI influencers” (claimed).

Typical scenarios

  • Scenario 1: a user selects a model and generates content from a prompt → receives a finished result.
  • Scenario 2: a user configures an agent → the agent performs actions on social media according to the set rules (claimed).
  • Scenario 3: a user uses the ecosystem interfaces (Agents/Exchange/Chat) → gets access to the corresponding features.

Getting started (wallet/network)

  • What you need: open the product/interfaces (see links_*).
  • Network/chain: Ethereum (the LUSH token is observable via the Explorer).
  • Fees: Ethereum fees (gas) for operations with the token; the fee model inside the products is not established per Tier‑1 sources.

Architecture/tech (non‑AI)

  • Components: offchain services/interfaces of the ecosystem; the onchain part (at minimum) — the LUSH token.
  • Participant roles: users; product operators.
  • Where logic runs: generation/agents — offchain; the token/transactions — onchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Protocol necessity drivers: not established per Tier‑1 sources.
  • Who pays fees: not established per Tier‑1 sources.
  • Where fees go: not established per Tier‑1 sources.
  • Issuance/burn: fixed supply (see max total supply in the Explorer).
  • Security/incentive mechanisms: not established per Tier‑1 sources.
  • Distribution and token issuance schedule: not established per Tier‑1 sources.
  • Treasury: not established per Tier‑1 sources.

Governance

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

Security and incidents

  • Audits: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: not found per Tier‑1 sources.
  • Threat model: risks of a centralized offchain service and risks of the token contract/DeFi integrations.

Project status and timeline

  • Current status: mainnet (in terms of the token on Ethereum).
  • Key releases/milestones: not established per Tier‑1 sources.
  • Roadmap: see links_* Roadmap.

Ecosystem/integrations

  • Integrations: Agents/Exchange/Chat (see Website and the ecosystem links).
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 sources.

AI component of the project

  • What is real AI here? Generative AI models and AI agents for content scenarios (Tier‑1: website/docs).
  • What is truly onchain? Onchain, the LUSH token is observable; the AI part is described as offchain products/interfaces.
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags (based on the information found): a gap between the offchain product and the onchain part (only the token); Tier‑1 model quality metrics were not found (AI_3=0).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
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_0 (intent) does not apply, since Tier‑1 already describes the AI features of the product (see AI_1/AI_2).
  • Evidence: Tier‑1 — https://lushai.net/
  • Why sufficient / why not (one line): AI_0 is used when there is only intent without a confirmed feature; here there is already a described feature and a demo.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): content generation and the operation of AI agents (claimed as the core features of the product).
  • Evidence: Tier‑1 — https://lushai.net/
  • Why sufficient / why not (one line): The Tier‑1 source describes the AI features as part of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the Lush Agents interface for interacting with the agents/model is available.
  • Evidence: Tier‑1 — https://agents.lushai.net
  • Why sufficient / why not (one line): the demo is publicly available and demonstrates the claimed AI functionality.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1 sources.
  • Context (version/date/how measured): not established.
  • Evidence: Tier‑1 — https://lushai.net/
  • Why sufficient / why not (one line): Tier‑1 quality metrics/benchmarks are not published.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a detailed tech description of the AI component (models/datasets/pipeline) was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://lushai.gitbook.io/lushai
  • Why sufficient / why not (one line): the docs do not contain a technical specification sufficient for AI_4 at the time of the check.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the LUSH token: 0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0
  • Evidence: Tier‑1 — https://etherscan.io/token/0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0
  • Why sufficient / why not (one line): the token address and the network are confirmed 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 per Tier‑1 sources (other than the token).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0
  • Why sufficient / why not (one line): Tier‑1 sources do not confirm critical onchain logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core functionality (AI agents/generation) is described as offchain and is not proven to be tied to onchain.
  • Evidence: Tier‑1 — https://lushai.net/
  • Why sufficient / why not (one line): there is no Tier‑1 proof that the product stops working 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, LUSH (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0
  • Why sufficient / why not (one line): the token is observable in the Explorer.
  • 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): the necessity of paying with the token for the key service is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://lushai.gitbook.io/lushai
  • Why sufficient / why not (one line): Tier‑1 sources do not give an unambiguous requirement “the service does not work without the token”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/collateral/penalties via the token are not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://lushai.gitbook.io/lushai
  • Why sufficient / why not (one line): there are no confirmed parameters of incentives/slashing/collateral.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://lushai.gitbook.io/lushai
  • Why sufficient / why not (one line): there is no Tier‑1 description of a voting/DAO mechanism.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token has not been assessed (mandatory functions of the token are not established).
  • Evidence: Tier‑1 — https://lushai.gitbook.io/lushai
  • Why sufficient / why not (one line): without a clear mandatory utility, replaceability cannot be reasonably asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xec9333e7dadeebf82d290d6cb12e66cc30ce46b0 The LushAI token (LUSH): contract and max total supply 20,000,000,000.
Tier‑1 https://lushai.net/ Description of the product/ecosystem: AI models, AI agents, claimed products (Agents/Exchange/Chat).
Tier‑1 https://agents.lushai.net The available Lush Agents interface (demo/product for interaction).

No comments to display

Back to top