Skip to main content

Eliza (Eliza Wakes Up)

Eliza (Eliza Wakes Up) — 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).

Eliza (Eliza Wakes Up) — an AI/Agents project on the Solana network, token (symbol: ELIZA): a web app with the AI companion “Eliza”.

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 web app with the AI companion “Eliza” — a character who talks with the user, remembers them and develops a “relationship”.
  • Who it’s for: users who want a personal AI conversation partner, and holders of the ELIZA token.
  • Why onchain/token: the ELIZA token (SPL on Solana) pays for premium features, in the app — the Eliza+ subscription; per the Tier‑1 documents, the same paid features can also be paid for with SOL, $ai16z or stablecoins.
  • What you can actually touch (Tier‑1): the web app at elizawakesup.ai: the ENTER button → sign‑in → the /dashboard personal area with creating your own companion and chat.

How it works (very briefly)

  1. The user does: signs in to the app at elizawakesup.ai and creates their own Eliza companion.
  2. The system does: the AI agent holds the conversation and accumulates memory about the user; per the litepaper — persistent memory, “core memories”, a daily journal and a relationship system that weakens without interaction.
  3. The user gets: a personal AI conversation partner; with the Eliza+ subscription — connecting external apps (Connections) and advanced integrations.
  4. Where the blockchain is: the ELIZA token (SPL on Solana); paying for Eliza+ in ELIZA is a Solana transaction via the x402 protocol; the companion has built‑in wallets for SOL/ELIZA transfers and swaps via Jupiter.
  5. Token role: a means of payment and access to premium features; per the Tier‑1 documents, SOL, $ai16z and stablecoins are also accepted; buyback & burn and allocations to the ai16z DAO are declared out of revenue.

Quick links: AI thesis fit

Project passport

Field Value
Project name Eliza (Eliza Wakes Up)
Also known as (aliases) Eliza Wakes Up; ElizaWakesUp; $ELIZA
Logo (logo) ../assets/310_eliza-wakesup-ai_logo.ico
Token symbol (ticker) ELIZA
Category AI/Agents | Consumer
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) 2024-11-19
Project status (status) active
Token (standard) SPL
Token contract 5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM
Token model (token_type) utility (access + payments)
Max supply 999 892 266 ELIZA (onchain supply; mint authority revoked)
Issuance fixed (mint authority revoked); buyback & burn (declared)
Tokenomics (tokenomics, brief) Issued via Pump.fun; per the litepaper, 10% of net revenue goes to buyback & burn, 10% — to acquiring ELIZA for the ai16z DAO, 80% — to the treasury and development.
Governance — (an advisory role is declared for holders)
Admins/keys mint/freeze authority revoked; metadata immutable (onchain)
Audit —
Bug bounty —
Team (team) not disclosed; advisor — Matthew Graham (Ryze Labs)
Funding (investors/funding) incubator — Ryze Labs (rounds not disclosed)
AI component (ai_component) AI virtual companions (personalization/chat)
Use‑case (use_case) consumer AI companion app
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

Eliza Wakes Up is an AI companion project: the character “Eliza”, whom the litepaper describes as an experiment in social AI — an AI agent striving to become a “real girl”. Per the litepaper, the product is built on the ElizaOS framework (see the elizaOS card) in partnership with Eliza Labs; it is a separate project with its own ELIZA token, not the framework itself and not the elizaOS token. The litepaper sets out three directions: a companion in web and mobile apps, “DePIN for ELIZA” (wearables and a humanoid robot) and media content. The web app is available now (the site says “Powered by Amiko”); pre‑orders for the humanoid robot opened on 2025-01-15, no confirmation of deliveries was found; the 3D environment and personal clones remain in the plans.

Features/modules

  • Companion and chat: creating your own Eliza companion, conversation and agent memory (Agent Memories) — per the app interface.
  • Memory and relationships (per the litepaper): persistent memory of conversation partners, “core memories”, a daily journal; the relationship deepens with regular interaction and weakens without it.
  • Eliza+: a paid subscription that unlocks connecting external apps (Connections) and advanced integrations.
  • Agent wallets: the companion’s built‑in Solana wallet and a multichain smart wallet; transfers requested by the agent are executed after the user approves them; SOL/ELIZA swaps via Jupiter.
  • Plans (per the litepaper and press release): a 3D room for the companion, personal clones (possibly as NFTs), voice modules, wearables, a humanoid robot.

Typical scenarios

  • Scenario 1: a user signs in to the app → creates a companion → talks with it, while the agent accumulates memory about the user.
  • Scenario 2: a user pays for Eliza+ in ELIZA → after the payment is confirmed on Solana, gets access to connecting external apps.
  • Scenario 3: a user tops up the companion’s wallet with SOL or ELIZA → approves transfers requested by the agent or swaps SOL for ELIZA via Jupiter.

Getting started (wallet/network)

  • What you need: a browser and signing in to the app; for paid features — ELIZA in the built‑in Solana wallet.
  • Network/chain: Solana (mainnet).
  • Fees: Solana network fees on transfers and payments; the Eliza+ payment amount is set in the app and is not established per Tier‑1.

Architecture/tech (non‑AI)

  • Components: a web app with a server API (agents, memory, subscriptions, x402 payments, integrations); the ELIZA SPL token on Solana.
  • Participant roles: users; the project team as the operator of the app and treasury; an x402 facilitator that verifies and settles payments.
  • Where logic runs: the AI agent, memory and subscription checks — offchain on the app’s servers; onchain — the token and transfers (payments, agent wallets).
  • Dependencies: the ElizaOS framework (per the litepaper), the Amiko platform (per the site), Solana, Jupiter (swaps), Composio (app connections).

Token/economics (expanded, no forecasts)

  • Token utility: paying for premium features — the Eliza+ subscription in the app; per the litepaper, also gifts to the companion, the “Rizz Booster” and modules; holding ELIZA gives priority or discounts (per the tokenomics).
  • Protocol necessity drivers: not established — per the Tier‑1 documents, all paid products can also be paid for with $ai16z, SOL or stablecoins.
  • Who pays fees: users — for paid features and Solana network fees.
  • Where fees go: per the litepaper, operational costs are covered first, then 10% of net revenue goes to buyback & burn, 10% — to acquiring ELIZA for the ai16z DAO, 80% — to the treasury and development.
  • Issuance/burn: the mint authority is revoked, so additional issuance is impossible; the supply is 999 892 266 ELIZA (onchain); burns via buyback are declared, public reports on them were not found in the sources checked.
  • Security/incentive mechanisms: staking, collateral and penalties are not described; rewards to holders (“staking benefits”, airdrops) are mentioned in the tokenomics without mechanics.
  • Distribution and token issuance schedule: issued via Pump.fun; team allocations and vesting were not found per Tier‑1.
  • Treasury: the Eliza Treasury is the project’s central fund (per the litepaper); who controls it and what its addresses are is not established.

Governance

  • Who makes decisions: not established; an advisory role is declared for token holders (advisory board, feedback, polls), onchain voting is not described.
  • How protocol parameters change: not established; “DAO‑like” models and staking are mentioned as possible in the future.
  • Where decisions are discussed/made: the official channels are X and Telegram; no separate forum or Snapshot was found.
  • Keys/multisig: the token’s mint/freeze authorities are revoked, the metadata is immutable (onchain); the treasury and app keys are not disclosed.

Security and incidents

  • Audits: no Tier‑1 found.
  • Bug bounty: no Tier‑1 found.
  • Incidents: none identified in the sources checked.
  • Threat model: the app and memory run as the operator’s centralized service; transfers from the agent wallets require user approval (per the interface); the main risks are trust in the operator and key custody for the built‑in wallets.

Project status and timeline

  • Current status: active — the site and app are available, onchain transactions with the token continue (checked 2026-09-25); the token’s trading activity is low (CoinGecko: 24‑hour volume about 347 USD; CoinMarketCap: 0 USD).
  • Key releases/milestones: 2024-11-19 — token issued via Pump.fun; 2025-01-14 — litepaper and tokenomics v1.0; 2025-01-15 — pre‑orders opened for the Eliza humanoid robot (press release); later the app gained the Eliza+ subscription paid in ELIZA via x402 (date not established).
  • Roadmap: the Roadmap Highlights section of the litepaper: near‑term — the relationship system, journal and voice; mid‑term — a 3D app and device prototypes; long‑term — a humanoid robot and an open ecosystem for third‑party developers.

Ecosystem/integrations

  • Integrations: Amiko (per the site); Jupiter, Composio and x402 — per the app interface.
  • Partners: Eliza Labs (per the litepaper); Ryze Labs — incubator, Old World Labs — robotics (per the press release).
  • Where it’s actually used: the elizawakesup.ai web app; the number of users is not disclosed; the token has about 22 770 holders per CoinMarketCap (Tier‑2).

AI component of the project

  • What is real AI here? An AI companion: a conversational agent with memory about the user and personalization; the working app is available after sign‑in. Models, architecture and quality metrics are not disclosed per Tier‑1.
  • What is truly onchain? The ELIZA SPL token and its transfers: Eliza+ payments via x402 and the agent wallets. No project programs on Solana other than the token were found; the AI, memory and subscription logic run offchain.
  • Why is a token needed? For payment and access to premium features; but the Tier‑1 documents explicitly allow paying with SOL, $ai16z and stablecoins, so the token is replaceable. Buyback & burn and allocations to the ai16z DAO are described as a distribution of revenue.
  • Red flags (based on the information found): the token was issued via Pump.fun before the litepaper and tokenomics were published (2025-01-14); per Decrypt (Tier‑2), the first robots were expected by mid‑2025, no confirmation of deliveries was found; the promised public buyback & burn reports were not found; the app code contains the /api/mastra/status endpoint, so the framework of the current version (per the litepaper — ElizaOS) requires re-checking.

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 does not apply: Tier‑1 describes a working AI companion, not only intentions.
  • Evidence: Tier‑1 — https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): AI_0 is set only when AI_1..AI_4 are all 0; here AI_1 = 1.
  • Conflict note: —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Eliza is a conversational AI companion: text and voice chat, persistent memory of conversation partners, character personalization; in the app — creating your own companion and agent memory.
  • Evidence: Tier‑1 — https://elizawakesup.ai/litepaper.pdf ; https://elizawakesup.ai/dashboard
  • Why sufficient / why not (one line): The litepaper and the app interface directly describe what the AI part of the product does.
  • Conflict note: —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The web app at elizawakesup.ai: after the ENTER button and sign‑in, /dashboard opens with creating your own companion, chat and agent memory.
  • Evidence: Tier‑1 — https://www.elizawakesup.ai/ ; https://elizawakesup.ai/dashboard
  • Why sufficient / why not (one line): There is a product entrypoint where you can sign in and use the companion; the chat itself after sign‑in was not tested in this check.
  • Conflict note: —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): No quantitative quality metrics for the companion’s answers, memory or models were found in Tier‑1.
  • Conflict note: —

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

  • AI_4 (decision): 0
  • Claim (one line): Tier‑1 gives a functional description (memory, the relationship system) and names the ElizaOS framework, but does not describe the architecture, models or versions of the app itself; no public repository was found.
  • Evidence: Tier‑1 — https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): AI_4 = 1 requires a technical description of the product’s architecture, models or versions.
  • Conflict note: the app code contains the /api/mastra/status endpoint; that the current version runs on ElizaOS is not separately confirmed.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: ELIZA SPL mint — 5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM
  • Evidence: Tier‑1 — https://solscan.io/token/5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM ; https://ipfs.io/ipfs/QmQPvjNTK88dwGcGNzoEaKhmkxkVHoQgYpLrbG8SiKMjBV
  • Why sufficient / why not (one line): The mint’s onchain metadata (name “Eliza”, symbol “ELIZA”) points to the project’s site and X; the same mint is set in the app code.
  • Conflict note: —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: onchain is only the token and its transfers: Eliza+ payments via x402 (the facilitator verifies the payment, the server activates the subscription), transfers and swaps from the agent wallets; no project programs were found.
  • Evidence: Tier‑1 — https://elizawakesup.ai/dashboard
  • Why sufficient / why not (one line): Paying with the token and transfers are not onchain product logic (access, accounting, rules, DAO), so conservatively 0.
  • Conflict note: —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: replacing the blockchain with a server loses only settlement in the token; the companion, memory and subscription already run offchain.
  • Evidence: Tier‑1 — https://elizawakesup.ai/litepaper.pdf ; https://elizawakesup.ai/dashboard
  • Why sufficient / why not (one line): No Tier‑1 justification that the product stops working without the blockchain was found.
  • Conflict note: —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ELIZA (SPL on Solana).
  • Evidence: Tier‑1 — https://solscan.io/token/5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM ; https://elizawakesup.ai/tokenomics.pdf
  • Why sufficient / why not (one line): The mint is observable onchain, and the token’s utility is described in the Tier‑1 tokenomics.
  • Conflict note: —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): Premium features are paid for in ELIZA: the Eliza+ subscription in the app (x402, asset ELIZA); per the litepaper — gifts, the “Rizz Booster” and modules.
  • Evidence: Tier‑1 — https://elizawakesup.ai/dashboard ; https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): Tier‑1 describes paying for the service with the token, and the app implements it.
  • Conflict note: —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking, collateral and penalties are not described; rewards to holders (“staking benefits”, airdrops) are mentioned in the tokenomics without mechanics.
  • Evidence: Tier‑1 — https://elizawakesup.ai/tokenomics.pdf
  • Why sufficient / why not (one line): TK_2 = 1 requires described incentive or collateral mechanics, not a general mention of rewards.
  • Conflict note: —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): An advisory role is declared for holders (advisory board, feedback, polls); voting and “DAO‑like” models are mentioned only as possible in the future.
  • Evidence: Tier‑1 — https://elizawakesup.ai/tokenomics.pdf ; https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): No binding governance mechanics of the token are described in Tier‑1.
  • Conflict note: —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): Per Tier‑1, all products can be paid for in $ELIZA, $ai16z, SOL or USDC — “accommodates both $ELIZA holders and newcomers”.
  • Evidence: Tier‑1 — https://elizawakesup.ai/tokenomics.pdf ; https://elizawakesup.ai/litepaper.pdf
  • Why sufficient / why not (one line): The project itself allows paying with SOL and stablecoins instead of the token.
  • Conflict note: the current Eliza+ payment form in the app accepts ELIZA (asset ELIZA in the code); acceptance of other currencies in the app was not checked.

Evidence (table)

Tier Source What it proves
Tier‑1 https://elizawakesup.ai/litepaper.pdf Litepaper v1.0 (2025-01-14): Eliza Wakes Up ($ELIZA) is an AI companion built on the ElizaOS framework in partnership with Eliza Labs; text and voice chat, persistent memory, a journal (checked 2026-09-25).
Tier‑1 https://elizawakesup.ai/litepaper.pdf Distribution of net revenue: 10% to buyback & burn, 10% to acquiring ELIZA for the ai16z DAO, 80% to the treasury and development (checked 2026-09-25).
Tier‑1 https://elizawakesup.ai/tokenomics.pdf Tokenomics v1.0 (2025-01-14): products can be paid for in $ELIZA, $ai16z, SOL or USDC; holding the token gives priority or discounts (checked 2026-09-25).
Tier‑1 https://elizawakesup.ai/tokenomics.pdf The role of token holders is advisory (advisory board, polls); staking and rewards are mentioned without mechanics (checked 2026-09-25).
Tier‑1 https://www.elizawakesup.ai/ Official site: entry to the app (ENTER → sign‑in → /dashboard), the “Powered by Amiko” caption (checked 2026-09-25).
Tier‑1 https://elizawakesup.ai/dashboard App interface (per the public page code): creating your own AI companion, chat, agent memory, agent wallets, the Eliza+ subscription (checked 2026-09-25).
Tier‑1 https://elizawakesup.ai/dashboard The Eliza+ subscription is paid for with the ELIZA token via x402 on Solana mainnet; the code sets the mint 5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM (checked 2026-09-25).
Tier‑1 https://solscan.io/token/5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM SPL token: name “Eliza”, symbol “ELIZA”; created via the Pump.fun program on 2024-11-19 (onchain, checked 2026-09-25).
Tier‑1 https://solscan.io/token/5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM Token: mint and freeze authorities revoked, metadata immutable, supply 999 892 266 ELIZA (onchain, checked 2026-09-25).
Tier‑1 https://ipfs.io/ipfs/QmQPvjNTK88dwGcGNzoEaKhmkxkVHoQgYpLrbG8SiKMjBV The token’s JSON metadata at the URI from the onchain metadata: site elizawakesup.ai, X elizawakesup, createdOn pump.fun (checked 2026-09-25).
Tier‑1 https://www.prnewswire.com/news-releases/eliza-wakes-up-eliza-ai-agents-take-human-form-302351810.html The project’s press release (2025-01-15): pre‑orders for the Eliza humanoid robot based on Eliza Wakes Up and ElizaOS; incubator Ryze Labs, advisor Matthew Graham (checked 2026-09-25).
Tier‑1 https://t.me/ElizaWakesUpOfficial Official Telegram from the litepaper: the “Eliza Portal” channel, about 1 234 subscribers (checked 2026-09-25).
Tier‑1 — No Tier‑1 source for claim “quality metrics for the companion’s answers, memory or models” was found.
Tier‑1 — No Tier‑1 source for claim “architecture, models used and app version; a public repository” was found.
Tier‑1 — No Tier‑1 source for claim “the project’s own programs on Solana beyond the SPL mint” was found.
Tier‑1 — No Tier‑1 source for claim “ELIZA holders receive rewards under described mechanics or vote in a binding way” was found.
Tier‑2 https://coinmarketcap.com/currencies/eliza-wakesup-ai/ “Eliza (elizawakesup)”, ELIZA, the same mint; about 22 770 holders; 24‑hour trading volume — 0 USD (checked 2026-09-25).
Tier‑2 https://www.coingecko.com/en/coins/eliza CoinGecko eliza: the same mint, site and X; categories AI Agents, Pump.fun Ecosystem, x402 Ecosystem; 24‑hour volume about 347 USD (checked 2026-09-25).
Tier‑2 https://www.geckoterminal.com/solana/tokens/5voS9evDjxF589WuEub5i4ti7FWQmZCsAsyD5ucbuRqM The first ELIZA/SOL pool on Raydium was created on 2024-11-19; trading activity in the pools is low (checked 2026-09-25).
Tier‑2 https://decrypt.co/301084/ai-agent-elizaos-robot-body-not-for-sex The Eliza robot is based on the Unitree H1; the first deliveries were expected by mid‑2025 (context, checked 2026-09-25).
Tier‑2 https://www.ryzelabs.io/en/insights/2025-06-10/Investment-Thesis:-Amiko-%E2%80%93-Your-Personal-AI,-Owned-and-Evolved Ryze Labs on Amiko: an orchestration layer for AI agents in which the Eliza companion runs (context for “Powered by Amiko”, checked 2026-09-25).

No comments to display

Back to top