Skip to main content

Xeleb Protocol

Xeleb Protocol (Xeleb 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).

Xeleb Protocol — an AI/Agents / Infra project that positions itself as an “AI Agent Influencer Hub” with tokenization of AI influencers/agents and a “Proof‑of‑Utility” onchain economy. Token on BNB Smart Chain: XCX.

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 platform/protocol for creating and “tokenizing” AI influencer agents and accounting for their “usefulness” via onchain mechanics.
  • Who it’s for: creators/communities who want to launch AI agents; users/investors who interact with the agents and their tokens.
  • Why onchain/token: onchain is needed for transparent accounting of agent tokens, transactions and incentives; XCX is the “economic engine” of the ecosystem.

How it works (very briefly)

  1. The user does: creates/launches an AI influencer/agent (per the product model) and interacts with it.
  2. The system does: records “actions” and participation in the economy, and also supports the issuance/circulation of tokens.
  3. The user gets: access to agents and participation mechanics (creator/fan/investor).
  4. Where the blockchain is: tokenization and agent transactions, rewards and governance processes (as claimed).
  5. Token role (if any): XCX is used for transactions, rewards and (as claimed) governance.

Quick links: AI thesis fit

Project passport

Field Value
Project name Xeleb Protocol
Also known as (aliases) Xeleb AI, Xeleb
Logo (logo) ../assets/251_xeleb-protocol_logo.png
Token symbol (ticker) XCX
Category AI/Agents | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) — (not confirmed by Tier‑1)
Project status (status) active (the documentation was updated “6 months ago” in GitBook)
Token (standard) BEP-20
Token contract 0xE32f9e8F7f7222fcd83EE0fC68bAf12118448Eaf
Token model (token_type) utility (governance)
Max supply 1,000,000,000 XCX (per BscScan)
Issuance fixed (per max total supply)
Tokenomics (tokenomics, brief) XCX “powers all agent transactions, reward mechanisms, and governance processes” (per GitBook).
Governance governance claimed; details not extracted
Admins/keys — (not found)
Audit yes (this card links to the Verichains image; the report content as a PDF was not extracted)
Bug bounty —
Team (team) — (not found in the extracted Tier‑1)
Funding (investors/funding) partners/investors are claimed in the docs (MEXC Global, Amber, etc. — as a GitBook claim).
AI component (ai_component) AI influencer agents, Proof-of-Utility
Use‑case (use_case) launch + tokenize AI agents
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 3 / 2
Last verified 2026-02-11

General project overview

In its documentation, Xeleb Protocol is described as an “economy of AI agents” — a decentralized and tokenized platform where every AI influencer/agent must “prove usefulness” (Proof‑of‑Utility), one “verified action at a time”. The economy is tied to the XCX token.

Features/modules

  • AI Influencer Hub: creation/launch of AI influencer agents “without code” (claimed).
  • Proof‑of‑Utility: accounting of usefulness/actions as the criterion for rewards.
  • Token economy: transactions/rewards/possible governance via XCX.

Typical scenarios

  • Scenario 1: a creator launches an AI influencer → tokenizes it → gets an economy around the agent.
  • Scenario 2: a user interacts with an agent → receives participation/incentives (per the PoU model).
  • Scenario 3: an XCX holder participates in the protocol’s transactions/mechanics.

Getting started (wallet/network)

  • What you need: an EVM wallet and access to the dApp (the roadmap lists app.xeleb.io and a staking page), as well as the XCX token (if staking/participation is needed).
  • Network/chain: BNB Smart Chain (XCX — BEP‑20; the official contract address is listed in the docs).
  • Fees: BNB Chain network fees (BNB) for swaps/staking/transactions in the dApp; additional protocol fees are not described in the extracted Tier‑1.

Architecture/tech (non‑AI)

  • Components: smart contracts (the XCX token and related mechanics), a web dApp (app.xeleb.io) for the marketplace/staking, offchain components for launching/servicing AI agents.
  • Participant roles: creators of AI agents/influencers, users/fans (interact and participate in the economy), XCX holders/stakers.
  • Where logic runs: tokenization/staking/transaction accounting — onchain (BNB Chain); the “AI agents/influencers” and their behavior — predominantly offchain (the extracted Tier‑1 contain no indication of onchain inference).
  • Dependencies: BNB Smart Chain; the dApp web infrastructure. Oracles/DA/bridges are not described in the extracted Tier‑1.

Token/economics (expanded, no forecasts)

  • Token utility: the docs list the utilities: staking for access (Genesis AI Access), governance power (staker voting), advertising/sponsorship bids, insurance pool, exclusive NFT drops, metaverse customization.
  • Protocol necessity drivers: per the description in the docs, XCX is needed for staking and participation in the platform economy (access/voting/brand activations and other mechanics).
  • Who pays fees: users/stakers pay BNB Chain network fees (BNB) on transactions; the project’s protocol fees are not disclosed in the extracted Tier‑1.
  • Where fees go: the distribution of fees within the protocol (to whom and how) is not described in the extracted Tier‑1.
  • Issuance/burn: total supply 1,000,000,000 XCX, “no inflation” (in the docs). No data on burn mechanics was found in the extracted Tier‑1.
  • Security/incentive mechanisms: staking/rewards mechanics are claimed (including the “Staking reward 10%” allocation); slashing/penalty parameters are not described.
  • Distribution and token issuance schedule: the docs give the allocation: Staking reward 10%, Team 10%, Investors & Advisors 7%, Treasury 13%, Liquidity (DEX & CEX) 20%, Community & Marketing 20%, IDO + Initial Airdrops 10%, Partners & Acquisition Funds 10%. Vesting/lockups are mentioned for Team (“long-term vesting”), but exact schedules are not provided in the extracted Tier‑1.
  • Treasury: Treasury allocation 13% (in the docs); control/spending rules are not disclosed in the extracted Tier‑1.

Governance

  • Who makes decisions: governance via XCX staking is claimed in the docs (stakers “vote on AI agent decisions”), but a formal DAO scheme/voting venues are not specified in the extracted Tier‑1.
  • How protocol parameters change: via platform updates; a detailed change management process (proposals/voting) was not found.
  • Where decisions are discussed/made: the official documentation; the project’s public channels (X/Telegram/Discord) are listed in the links of this card.
  • Keys/multisig: — (not found in the extracted Tier‑1)

Security and incidents

  • Audits: an audit is claimed (this card links to the “Verichains” image), but a full‑text report was not obtained in the extracted Tier‑1.
  • Bug bounty: — (not found in the extracted Tier‑1)
  • Incidents: — (not found in the extracted Tier‑1)
  • Threat model: smart contract risks (token/staking), risks of offchain components (agents, accounts, infrastructure), as well as risks of the Proof‑of‑Utility “utility metrics” (activity manipulation).

Project status and timeline

  • Current status: a working platform/product in 2025 (the roadmap describes Alpha/Beta and the “Mainnet” launch of AI Influencer V1.0; the XCX token is traded per the list in the docs).
  • Key releases/milestones: Q1 2025 — Core Development & Alpha Launch; Q2 2025 — Beta Release & First Agent Campaigns (the roadmap lists “126 agents / 12,600+ transactions” and other activities); Q3 2025 — $XCX Token Launch and expansion; Q4 2025 — full platform + revenue oracle (planned).
  • Roadmap: https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol/roadmap

Ecosystem/integrations

  • Integrations: BNB Chain ecosystem (mentions of campaigns in the roadmap); the roadmap also lists links to the staking pool and the marketplace in the dApp.
  • Partners: — (the extracted Tier‑1 contain no list of confirmed partners as deeply integrated services)
  • Where it’s actually used: the roadmap gives examples of campaigns/activity (for example, the DappBay campaign and the launch of a staking pool), but this remains a project claim and does not replace independent validation.

AI component of the project

  • What is real AI here? the docs talk about “AI agents / AI influencers”, but the extracted Tier‑1 contain no technical details of the models/inference.
  • What is truly onchain? the XCX token on BNB Smart Chain; “tokenized” agents and the transactions around them (as claimed).
  • Why is a token needed? the token is claimed as the basis of transactions, rewards and governance processes.
  • Red flags (based on the information found): AI‑washing — there are no verifiable metrics/demos of the AI agents in operation; onchain‑washing — much may be offchain; token‑washing — it needs to be verified that the protocol does not work without XCX.

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 1
Token necessity medium 3
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the protocol is positioned as an “economy of AI agents / AI influencer hub”.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): this records the thesis, but is not proof of a working AI core.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): the extracted Tier‑1 contain no specifics about models/inference/limitations (what exactly the AI does).
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): “AI agents” are mentioned, but without an operational description.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a verifiable demo example was not found in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): the page is descriptive.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): there are no AI quality/efficiency metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the extracted Tier‑1 contain no technical architecture of the AI part; only the general economic model is described.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): insufficient for technical confirmation of AI.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain.
  • Addresses/identifiers: 0xE32f9e8F7f7222fcd83EE0fC68bAf12118448Eaf.
  • Evidence: Tier‑1 — https://bscscan.com/token/0xE32f9e8F7f7222fcd83EE0fC68bAf12118448Eaf
  • Why sufficient / why not (one line): BscScan confirms the existence of the token and the max supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: the extracted Tier‑1 show no contracts/mechanics other than the fact that the token exists.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): “tokenized” and PoU are declared, but without addresses/contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: “transparent accounting” is claimed, but there is no strict proof of the irreplaceability of onchain in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): there is not enough specificity on the onchain components.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the XCX token exists.
  • Evidence: Tier‑1 — https://bscscan.com/token/0xE32f9e8F7f7222fcd83EE0fC68bAf12118448Eaf
  • Why sufficient / why not (one line): BscScan.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): XCX “powers all agent transactions”.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): utility for transactions is claimed directly.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): XCX is intended for reward mechanisms (as claimed).
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): the reward role of the token is declared.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): XCX is claimed as the token for governance processes.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): a governance claim is present.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the irreplaceability of the token is not strictly proven in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol
  • Why sufficient / why not (one line): there are utility declarations, but no “it breaks without the token” test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/what-is-xeleb-protocol Positioning (AI agents/influencers), PoU and the role of XCX in the economy.
Tier‑1 https://bscscan.com/token/0xE32f9e8F7f7222fcd83EE0fC68bAf12118448Eaf The XCX token address and max supply 1B.
Tier‑2 https://coinmarketcap.com/currencies/xeleb-protocol/ For reference (not Tier‑1).
Tier‑3 https://paper.xeleb.io/ The whitepaper URL is listed in this card, but the content was not verified.

No comments to display

Back to top