Skip to main content

XANA

XANA — 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).

XANA — Metaverse/Gaming + blockchain infrastructure (EVM), token: XETA.

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 metaverse product + an associated blockchain layer for the ecosystem’s assets and dApps (per the whitepaper).
  • Who it’s for: metaverse users, content/game creators, brands and event organizers.
  • Why onchain/token: the token and NFTs are used for access/purchases and incentives within the ecosystem (per the token utility in the whitepaper).

How it works (very briefly)

  1. The user does: participates in the metaverse, buys/sells digital assets and uses content.
  2. The system does: links assets and operations to the onchain layer (token/NFT/dApps, per the whitepaper).
  3. The user gets: digital assets and access to the ecosystem’s products/modules.
  4. Where the blockchain is: the token and part of the assets/operations are recorded onchain.
  5. Token role: XETA is used across several ecosystem products (land/avatars/items/events, etc., per the whitepaper).

Quick links: AI thesis fit

Project passport

Field Value
Project name XANA
Also known as (aliases) XANA, XETA
Logo (logo) ../assets/313_xana-new_logo.svg
Token symbol (ticker) XETA
Category Gaming | Metaverse | Infra
Primary chain (chain) Avalanche
Type EVM
Network status mainnet
Consensus (consensus) PoS (Avalanche)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x31c994AC062C1970C086260Bc61babB708643fAc
Token model (token_type) utility (payments + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) utility in ecosystem products; “staking incentives” (per the whitepaper)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI features/AI products in ecosystem
Use‑case (use_case) metaverse, UGC/builder, dApps + digital assets
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

In the whitepaper, XANA describes a combination of a “metaverse application + blockchain infrastructure”, where digital assets (tokens/NFTs) can be used inside the metaverse and the ecosystem’s dApps.

Features/modules

  • XANA Metaverse app: avatars, lands, worlds, games, social features (per the whitepaper).
  • Builder tools (per the structure of the whitepaper).
  • Token utility for ecosystem products (land/avatars/items/events/marketplace, etc.).

Typical scenarios

  • Scenario 1: a user buys/uses digital assets (land/avatars/items) → gets access/capabilities in the metaverse (per the whitepaper).
  • Scenario 2: a content creator uses the Builder tools → publishes/sells assets and works with the marketplace (per the structure of the whitepaper).

Getting started (wallet/network)

  • What you need: a wallet for EVM networks (for operations with the token/assets) and access to the XANA application/website.
  • Network/chain: per the token’s onchain artifact — Avalanche (SnowScan).
  • Fees: network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: a metaverse application + blockchain infrastructure (EVM‑compatible) and the XETA token (per the whitepaper).
  • Participant roles: metaverse users, content/game creators, ecosystem participants (per the whitepaper).
  • Where logic runs: onchain — the token and part of the accounting of assets/operations; the rest of the metaverse logic — as an application/service.
  • Dependencies: EVM infrastructure (wallets, RPC, explorers).

Token/economics (expanded, no forecasts)

The whitepaper contains a table of XETA utility by product: access/discounts, “staking incentives” and mechanics related to sales/royalties/fees within the ecosystem’s products.

Governance

  • Governance format: in Tier‑1 materials, XETA is described as a governance token; the specific voting procedure/venues require separate recording per Tier‑1.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: key risks — a lack of verifiable onchain artifacts for the key logic and possible mixing of “metaverse marketing” with verifiable facts.

Project status and timeline

  • Current status: an active website and documentation.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: basic scenarios and modules are described in the whitepaper (see links_*).

AI component of the project

  • What is real AI here? In the project’s Tier‑1 materials, AI is claimed as part of the product line/ecosystem (AI solutions; intent), but a Tier‑1 tech description of a specific AI component (model/metrics/architecture) is not recorded in this card.
  • What is truly onchain? The XETA token and onchain accounting of part of the ecosystem’s assets/operations (per the whitepaper).
  • Why is a token needed? XETA utility is tied to ecosystem products (land/avatar/items/events/marketplace, etc., per the whitepaper).
  • Red flags (based on the information found): AI positioning without a tech description/metrics; the “AI products” on the website require separate verification for reproducible artifacts.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity medium 2
Token necessity high 2
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): The project’s Tier‑1 materials claim AI solutions/AI products in the ecosystem (intent).
  • Evidence: Tier‑1 — https://xana.net/tokenomics
  • Why sufficient / why not (one line): The Tier‑1 website explicitly positions AI directions; this is intent and does not prove a working AI component with metrics (AI_1..AI_4 remain 0).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): A verifiable AI function/module (what exactly the AI does) is not described in Tier‑1 sources at a sufficient level of specificity.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): There are no specifics on “what the AI does” as a verifiable function.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/guide confirming an AI feature was found.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): There is no artifact that can be reproduced to see an AI result.
  • 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.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): Quality metrics of the AI part are not recorded per Tier‑1 in this card.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI part was not found per Tier‑1 in this card.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): Without a tech description, AI_4 cannot be confirmed.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Avalanche
  • Addresses/identifiers: XETA: 0x31c994AC062C1970C086260Bc61babB708643fAc
  • Evidence: Tier‑1 — https://snowscan.xyz/token/0x31c994AC062C1970C086260Bc61babB708643fAc
  • Why sufficient / why not (one line): There is an onchain artifact with the token contract.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the whitepaper describes its own EVM‑compatible infrastructure/sidechain for metaverse use cases, not just the issuance of a token.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): The Tier‑1 description includes the blockchain layer as part of the product (infrastructure for the metaverse and dApps).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not proven per Tier‑1 that the product “breaks down” without onchain.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper
  • Why sufficient / why not (one line): There is no sufficient justification of the criticality of the onchain layer.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, XETA.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper/tokenomics/what-is-the-token-utility
  • Why sufficient / why not (one line): The token and its utility are described in the official documentation.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): The token is used in products (for example, purchases/access/fees in the ecosystem).
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper/tokenomics/what-is-the-token-utility
  • Why sufficient / why not (one line): The utility table lists payment/access use cases by product.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The documentation mentions “staking incentives”.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper/tokenomics/what-is-the-token-utility
  • Why sufficient / why not (one line): Tier‑1 explicitly points to staking incentives as part of the token model.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • TK_3 (decision): 1
  • Claim (one line): In Tier‑1 materials, XETA is described as a governance token and grants DAO voting rights.
  • Evidence: Tier‑1 — https://xana.net/blog/xeta-tokenomics-the-core-of-xanas-ecosystem/
  • Why sufficient / why not (one line): The tokenomics article has a separate item on DAO voting rights and the participation of token holders in decision‑making.
  • 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.
  • Evidence: Tier‑1 — https://docs.xana.net/xana-whitepaper/tokenomics/what-is-the-token-utility
  • Why sufficient / why not (one line): A conclusion about replaceability requires a separate comparison of payment/access mechanisms.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.xana.net/xana-whitepaper Product description: a metaverse platform + blockchain infrastructure (EVM).
Tier‑1 https://docs.xana.net/xana-whitepaper/tokenomics/what-is-the-token-utility XETA utility by product; mention of “staking incentives”.
Tier‑1 https://snowscan.xyz/token/0x31c994AC062C1970C086260Bc61babB708643fAc Onchain artifact: the token contract (Avalanche).
Tier‑1 https://xana.net/tokenomics Tier‑1 website: claimed AI solutions/AI products in the ecosystem (AI intent).
Tier‑1 https://xana.net/blog/xeta-tokenomics-the-core-of-xanas-ecosystem/ Tokenomics: XETA utility (including gas on XANA Chain, staking rewards, DAO voting rights).
Tier‑2 https://www.coingecko.com/en/coins/xana Reference token profile and links (context).
Tier‑2 https://coinmarketcap.com/currencies/xana-new/ Reference token profile and links (context).

No comments to display

Back to top